From: Warner Losh <firstname.lastname@example.org> To: Clem Cole <email@example.com> Cc: The Unix Heritage Society <firstname.lastname@example.org>, Henry Bent <email@example.com>, COFF <firstname.lastname@example.org>, Grant Taylor <email@example.com> Subject: Re: [COFF] [TUHS] Will someone please explain the history and usage of gpasswd / newgrp / sg? Date: Mon, 15 Nov 2021 11:54:40 -0700 [thread overview] Message-ID: <CANCZdfrRG6J8XSxMdo2HL7NTGZY8ePuks-n8y6SH6TiWciuq7Q@mail.gmail.com> (raw) In-Reply-To: <CAC20D2NeFBMc27-9889R=qg1JNZLpk980Cs-Yh5ZXVZKqD8PNw@mail.gmail.com> [-- Attachment #1.1: Type: text/plain, Size: 1730 bytes --] Yes. V7 had chgrp too. It dealt only with adjusting the group "ownership" of a file. Warner On Mon, Nov 15, 2021 at 11:52 AM Clem Cole <firstname.lastname@example.org> wrote: > 3BSD has the V7 scheme, the new kernel code where there is a group list in > the process is not introduced until later/ > ᐧ > > On Mon, Nov 15, 2021 at 1:46 PM Henry Bent <email@example.com> wrote: > >> On Mon, 15 Nov 2021 at 13:31, Clem Cole <firstname.lastname@example.org> wrote: >> >>> Grant, >>> >>> Mashey and crew basically did most of the original group work as part of >>> PWB. If you look at the Sixth Edition sources and the PWB 1.0 stuff, that >>> is one of the places you will find differences. With Seventh Edition (or I >>> believe as part of the UNIX/TS work that Ken picked up), the Mashey group >>> changes went back into the Research stream. With one of the predecessors to >>> 4.2BSD (it may have 4.1A or 4.1B but frankly I have forgotten) Joy >>> introduced the group scheme we all use today. >>> >>> >> Looking at the TUHS archives, unless I'm missing something, 3BSD has >> groups that appear to be in the modern format: >> >> % ls -l /bsd/3bsd/etc/group >> -r--r--r-- 1 root root 44 1980-01-02 22:08 /bsd/3bsd/etc/group >> % cat /bsd/3bsd/etc/group >> staff:*:10:bill,ozalp >> grad:*:20: >> prof:*:30: >> % find . -name 'chgrp*' | xargs ls -l >> -r-xr-xr-x 1 root root 6960 Dec 30 1979 ./usr/bin/chgrp >> -r--r--r-- 1 root root 26 Feb 12 1979 ./usr/man/man1/chgrp.1 >> -r--r--r-- 1 root root 754 Feb 12 1979 ./usr/src/cmd/chgrp.c >> >> -Henry >> > _______________________________________________ > COFF mailing list > COFF@minnie.tuhs.org > https://minnie.tuhs.org/cgi-bin/mailman/listinfo/coff > [-- Attachment #1.2: Type: text/html, Size: 3363 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
next prev parent reply other threads:[~2021-11-15 18:56 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 [this message] 2021-11-15 18:56 ` Clem Cole 2021-11-15 20:17 ` arnold 2021-11-15 21:37 ` Clem Cole
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=CANCZdfrRG6J8XSxMdo2HL7NTGZY8ePuks-n8y6SH6TiWciuq7Q@mail.gmail.com \ --email@example.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).