From: zimoun <zimon.toutoune@gmail.com>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: 39023@debbugs.gnu.org
Subject: bug#39023: adduser/addgroup vs useradd/groupadd
Date: Wed, 22 Jan 2020 09:31:09 +0100 [thread overview]
Message-ID: <CAJ3okZ0+8dJmTX5crHuhAG_bvEP8rNUNHxMdq0M4GF3vVXdZAQ@mail.gmail.com> (raw)
In-Reply-To: <87eevs9lyo.fsf@nckx>
Hi Tobias,
On Wed, 22 Jan 2020 at 05:03, Tobias Geerinckx-Rice <me@tobias.gr> wrote:
> zimoun 写道:
> > a/ explicitly notice in the parenthesis that the chunk needs to
> > be
> > adapted; mentioning adduser/addgroup instead of useradd/groupadd
> > for
> > example.
>
> There's also:
>
> c/ do nothing, or
It is not fair, IMHO. :-)
> d/ include the complete code snippet provided by symphonia, but
> as an ‘out-of-band’ footnote to avoid confusion/blind
> copy-pasting/distracting the majority of (GNU) users with
> irrelevant variants.
Well, mixing the option a/ and b/. :-)
- telling explicitly
- providing copy/paste-able variant snippet
Yes, it is a better option.
> With a/, the user won't know which options to change, or how.
> They might not understand our ‘useradd’ syntax, and won't have its
> man page installed.
Yes, and they would not know neither if their foreign distro comes
with exotic 'adduser/addgroup'.
> As implied by my reply to Gábor, b/ isn't an option so I've
> snipped it.
Yes, it is my assumption --based on my small experience-- that
'adduser/addgroup' is less portable than 'useradd/groupadd'.
> I strongly prefer option d/.
Let go to this one. :-)
Hum? let see I am able to include the complete code snippet as an
footnote using Texinfo...
(Maybe someone will beat me. :-)
> > What do the *NIX gurus think?
>
> GNU's not *NIX! :o) (Nor is it POSIX.)
Héhé! Schrödinger's distro: by installing Guix on your foreign *NIX
distro, the user will have in the same time "not *NIX" and *NIX. ;-)
(Even if *NIX needs to run linux which mitigate the joke. :-))
next prev parent reply other threads:[~2020-01-22 8:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-07 21:29 bug#39023: binary installation manual doesn't work on Alpine Linux symphonia
2020-01-08 12:34 ` Gábor Boskovits
2020-01-22 3:53 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-01-22 19:42 ` Gábor Boskovits
2020-01-22 19:58 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-01-22 20:03 ` Gábor Boskovits
2020-02-19 15:56 ` zimoun
2020-01-22 1:44 ` bug#39023: adduser/addgroup vs useradd/groupadd zimoun
2020-01-22 4:03 ` Tobias Geerinckx-Rice via Bug reports for GNU Guix
2020-01-22 8:31 ` zimoun [this message]
2020-04-23 11:55 ` bug#39023: binary installation manual doesn't work on Alpine Linux Vincent Legoll
2020-04-23 13:29 ` zimoun
2020-04-23 14:15 ` Vincent Legoll
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAJ3okZ0+8dJmTX5crHuhAG_bvEP8rNUNHxMdq0M4GF3vVXdZAQ@mail.gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=39023@debbugs.gnu.org \
--cc=me@tobias.gr \
/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://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).