From: Arrigo Triulzi via COFF <coff@minnie.tuhs.org>
To: Grant Taylor <gtaylor@tnetconsulting.net>
Cc: The Unix Heritage Society <tuhs@minnie.tuhs.org>,
COFF <coff@minnie.tuhs.org>
Subject: Re: [COFF] Will someone please explain the history and usage of gpasswd / newgrp / sg?
Date: Mon, 15 Nov 2021 17:26:03 +0100 [thread overview]
Message-ID: <6882B4A4-EE01-4189-B7E0-2E9BF5383272@alchemistowl.org> (raw)
In-Reply-To: <a04c7d8c-e9e1-4714-70a3-affc570bd871@spamtrap.tnetconsulting.net>
On 15 Nov 2021, at 17:11, Grant Taylor via COFF <coff@minnie.tuhs.org> wrote:
> I've run across them again recently while reading old Unix texts. I've been aware of them for years, but I've never actually used them for anything beyond kicking the tires. So I figured that I'd inquire of the hive mind that is TUHS / COFF.
The only time I ever used it was back in the early ‘90s when on a SunOS system (dirac, for friends) it was used to allow graduate students access to the grading database (i.e. a text file) which was within a directory normally only accessible to teaching staff. The directory was group writable to a special “marking group” to which the various graduate students were added each term.
We’d "newgrp grades” and type the password we had been given to be able to edit the file and add the grades for the assessments we had marked (for food money).
I eventually became root on the machine and found my “su -“ screen to be a faster solution to accessing the file (sorry Franco, should you ever read this).
Cheers,
Arrigo
_______________________________________________
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 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-15 16:11 Grant Taylor via COFF
2021-11-15 16:26 ` Arrigo Triulzi via COFF [this message]
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
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=6882B4A4-EE01-4189-B7E0-2E9BF5383272@alchemistowl.org \
--to=coff@minnie.tuhs.org \
--cc=arrigo@alchemistowl.org \
--cc=gtaylor@tnetconsulting.net \
--cc=tuhs@minnie.tuhs.org \
/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.
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).