From: Stefano Brivio <sbrivio@redhat.com>
To: Paul Holzinger <pholzing@redhat.com>
Cc: Danish Prakash <danish.prakash@suse.com>, passt-dev@passt.top
Subject: Re: Setting hostname while spawning pasta
Date: Mon, 13 May 2024 18:02:08 +0200 [thread overview]
Message-ID: <20240513180208.45ae9add@elisabeth> (raw)
In-Reply-To: <cbeb7792-2cb8-4273-83d8-e488e3e22311@redhat.com>
On Mon, 13 May 2024 13:59:22 +0200
Paul Holzinger <pholzing@redhat.com> wrote:
> [...]
>
> I don't have an issue with the hostname suggestion but it will not solve
> the problem of users not understanding that they are in a new user
> namespace. Maybe a more universal solution is to print a log line with a
> hint when no explicit command is given. Something like: "Spawning new
> shell in user+network namespace". That at least tells the user what
> pasta did and works even in cases where the prompt does not contain the
> hostname.
Hmm, sure, that's probably the clearest indication possible in the
general case (minus the fact that it doesn't really help for
pasta-in-pasta as Danish pointed out).
On the other hand I would find it quite noisy, and the man page already
explains what we're doing. Sure, one could run it with '-q', but then
it's more typing just to avoid that noise.
By the way, I'm (sloowly) reworking the website, and the namespacing
aspect is something I plan to show in a separate diagram as well.
Plus, I guess we wouldn't print that when a command is explicitly
given, but then 'pasta' would print that message, while 'pasta -- sh'
wouldn't, so things would quite easily look inconsistent.
All in all, I have quite a preference against an additional message, but
if more people on the list think it's a nice addition, then let's go
for it.
--
Stefano
prev parent reply other threads:[~2024-05-13 16:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-09 7:00 Setting hostname while spawning pasta Danish Prakash
2024-05-10 17:03 ` Stefano Brivio
[not found] ` <CACVuxaZEos=JK3XaFGM7d9z+qk-QLeChh7HuGxcdaEfmM02ywg@mail.gmail.com>
2024-05-13 11:21 ` Stefano Brivio
2024-05-13 11:56 ` Danish Prakash
2024-05-13 11:59 ` Paul Holzinger
2024-05-13 14:28 ` Danish Prakash
2024-05-13 16:02 ` Stefano Brivio [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20240513180208.45ae9add@elisabeth \
--to=sbrivio@redhat.com \
--cc=danish.prakash@suse.com \
--cc=passt-dev@passt.top \
--cc=pholzing@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://passt.top/passt
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for IMAP folder(s).