From: Clem Cole <email@example.com> To: firstname.lastname@example.org Cc: email@example.com, firstname.lastname@example.org, email@example.com Subject: Re: [COFF] [TUHS] Will someone please explain the history and usage of gpasswd / newgrp / sg? Date: Mon, 15 Nov 2021 16:37:55 -0500 [thread overview] Message-ID: <CAC20D2PvuBOdeRjgyGmKcbG-_QKrZauYfDte0+xtW8K3mfBHkg@mail.gmail.com> (raw) In-Reply-To: <202111152017.1AFKH9Om032644@freefriends.org> [-- Attachment #1.1: Type: text/plain, Size: 675 bytes --] Fair enough. ᐧ On Mon, Nov 15, 2021 at 3:17 PM <firstname.lastname@example.org> wrote: > Clem Cole <email@example.com> wrote: > > > I'm sure it was used in many other ways, but that was certainly one > scheme > > we used at UCB when wnj added them. Again check the 4.2 docs, where the > > BSD group scheme is explained. This did seem useful and System V picked > > it up also fairly soon after BSD released it to the world, and > fortunately > > did not change the BSD semantics. > > Not so soon, really. The new group scheme was widely released with > 4.2 BSD (~ 1983). System V didn't pick up multiple groups until > System V Release 4, circa 1989. > > Arnold > [-- Attachment #1.2: Type: text/html, Size: 1425 bytes --] [-- Attachment #2: Type: text/plain, Size: 141 bytes --] _______________________________________________ COFF mailing list COFF@minnie.tuhs.org https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff
prev parent reply other threads:[~2021-11-15 21:39 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2021-11-15 16:11 [COFF] " Grant Taylor via COFF 2021-11-15 16:26 ` Arrigo Triulzi via COFF 2021-11-15 18:29 ` Clem Cole [not found] ` <CAEdTPBeNo-4vEVxxMzDTL_YYWvPb9VgMGTJBs7RaQhcDeJzeAg@mail.gmail.com> 2021-11-15 18:51 ` [COFF] [TUHS] " Clem Cole 2021-11-15 18:54 ` Warner Losh 2021-11-15 18:56 ` Clem Cole 2021-11-15 20:17 ` arnold 2021-11-15 21:37 ` Clem Cole [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=CAC20D2PvuBOdeRjgyGmKcbG-_QKrZauYfDte0+xtW8K3mfBHkg@mail.gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: [COFF] [TUHS] Will someone please explain the history and usage of gpasswd / newgrp / sg?' \ /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
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 NNTP newsgroup(s).