From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by passt.top (Postfix) with ESMTP id 88CD05A0298 for ; Mon, 13 May 2024 13:22:18 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1715599337; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=yOn0q24d4eBLsdv6tQAVKOqaOwRln4rsEAxju4Z0ark=; b=B7Nm7oUzh29ykGD1KU0cweGMtzp32A326WZIG3tarRN8vkb4YKSwrkCmTGamgCS121nXBz Cg6N1birGCmWpd6gz4vLeEIezsTQnkwIMLTZM2U6aE1sdNq6kkG3xHJHy6FCK6Stznpl4y NuQz3pheNn9kYJSlgUYTwWytUjv1yGQ= Received: from mail-ej1-f69.google.com (mail-ej1-f69.google.com [209.85.218.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-591-T6SqA7pyOL6L7zs4Mzivpg-1; Mon, 13 May 2024 07:22:16 -0400 X-MC-Unique: T6SqA7pyOL6L7zs4Mzivpg-1 Received: by mail-ej1-f69.google.com with SMTP id a640c23a62f3a-a59eea00cafso304797466b.1 for ; Mon, 13 May 2024 04:22:15 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20230601; t=1715599333; x=1716204133; h=content-transfer-encoding:mime-version:organization:references :in-reply-to:message-id:subject:cc:to:from:date:x-gm-message-state :from:to:cc:subject:date:message-id:reply-to; bh=yOn0q24d4eBLsdv6tQAVKOqaOwRln4rsEAxju4Z0ark=; b=HdEeaTlykMypgQ4c6PePzjbqCZfccWM43TLEs86zl3mXc8mSVJTVoVqANeHOwDU2Bp /aE5POc+XhC39L7hCGjC+WdMP2mzAKU5JNRSpB1NUO3h0YhNEn5MaheckRVoIB5sFAGA iMdDyENcbf+EfcoIw53IiOHGeimHvnVSQFi2/2actQZxLGszEV0crP0GPFxyobq3aV2W pJv3/toMXJpbPWAZxK9wXb8PcVggXr2F8Zexm8Lleo4qLnbBCK2ZtBNjlbELPKMDg9DS urBpxQpKVGQUBGV5XFXJ4NOgu+KqMrgEBoYfXukAb2AYySoFda99MCpsYAWLHMimkJG3 /7Hg== X-Gm-Message-State: AOJu0YwJe3vZ9+ZLlV6c/27fn5AcehGLxxAGPwG0EnvYHaDNoIILhbQz xymKwZsuNqBh4wwZ5Ar3VJGI/l9laQdnepCnn+gE02iGpHb+5q6af2gzkyaKgqv4c73Oilx9zDt pMRd6zTrYHfPpTCwcrvo2JrLp9VUJ33E5lSdo1Grj9Lt583nh02Vb7tRFg2oFVD2jvLyMEWTyAh o7ayImxtugwyZMOkMUXJ0npMKo4C63Vio9/YQ= X-Received: by 2002:a17:907:320b:b0:a59:b177:22d7 with SMTP id a640c23a62f3a-a5a2d53b75emr1197177366b.8.1715599333222; Mon, 13 May 2024 04:22:13 -0700 (PDT) X-Google-Smtp-Source: AGHT+IGxmWb7G7jrNgyxzk/qtwNNpx9gKmQMW/syTS4N/P/FCa9Wg8fUUsJ2+B2ccq0JtE/uDqdLng== X-Received: by 2002:a17:907:320b:b0:a59:b177:22d7 with SMTP id a640c23a62f3a-a5a2d53b75emr1197173766b.8.1715599332538; Mon, 13 May 2024 04:22:12 -0700 (PDT) Received: from maya.cloud.tilaa.com (maya.cloud.tilaa.com. [164.138.29.33]) by smtp.gmail.com with ESMTPSA id a640c23a62f3a-a5a1781d4bdsm581195266b.9.2024.05.13.04.22.11 (version=TLS1_2 cipher=ECDHE-ECDSA-AES128-GCM-SHA256 bits=128/128); Mon, 13 May 2024 04:22:11 -0700 (PDT) Date: Mon, 13 May 2024 13:21:38 +0200 From: Stefano Brivio To: Danish Prakash Subject: Re: Setting hostname while spawning pasta Message-ID: <20240513132138.21af6e3b@elisabeth> In-Reply-To: References: <20240510190301.10528a96@elisabeth> Organization: Red Hat X-Mailer: Claws Mail 4.2.0 (GTK 3.24.36; x86_64-pc-linux-gnu) MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Message-ID-Hash: KA3APB472YF7GVEYJWGN2NSMN3RIBJ4T X-Message-ID-Hash: KA3APB472YF7GVEYJWGN2NSMN3RIBJ4T X-MailFrom: sbrivio@redhat.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: passt-dev@passt.top X-Mailman-Version: 3.3.8 Precedence: list List-Id: Development discussion and patches for passt Archived-At: Archived-At: List-Archive: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: On Mon, 13 May 2024 13:45:51 +0530 Danish Prakash wrote: > > But we could still retain the existing hostname and prefix with > > something like 'pasta-on-' (sure, we would need to truncate at 63 > > characters, but it shouldn't be a common case). What do you think? > > That sounds like a good idea. I didn't realize you'd be running > pasta-in-pasta.. but that's reasonable. Though this will be helpful, > I'm not entirely sure if this would override the prompts that many > have set. At least my rudimentary shell prompt doesn't recognize the > pasta user namespace and continues to show the same old prompt. I hope > I'm the only one having this issue. I currently have these behaviours with default prompts: - Alpine: host:~$ pasta host:~# - Debian: user@host:~$ pasta root@host:~# - Fedora: [user@host ~]$ pasta [root@host ~]# - openSUSE: user@host:~> pasta host:~ # so I generally have a hint of something going on, but in any case, changing the hostname is helpful for unfamiliar users or even just for the pasta-in-pasta case I mentioned. > > What I can't tell from the prompt, though, is at what "level" I'm at > > (at least pasta-in-pasta is something I try very commonly to reproduce > > pasta's behaviour with particular network setups). Having > > root@pasta-on-pasta-on-machine would be a nice plus. > > But in general, this idea sounds good, I'd like to take a shot at > this, and I can send over the patch for you to test once I'm done. > What do you think? Sure, thanks, looking forward to it! -- Stefano