[TUHS] History of chown semantics

scj at yaccman.com scj at yaccman.com
Fri Jan 10 23:17:44 AEST 2014

Recall that in those days, "systems administrator" was an entry level,
minimum wage job.  Most worked third shift, and their primary duties were
to mount and dismount disc backup tapes.  Those people who actually did
administration in the sense we think of it were greatly underpaid and
disrespected.  The next decade or two, particularly with networking,
caused a huge change.  The Usenix LISA conferences did a lot to raise
consciousness that there was a real there there.

> Yep, but where did the user base from PWB come from? They were
> existing professional programmers from the mainframe world, still
> writing for the mainframe, now sumbmitting via UNIX RJE.
> Where did the sysadmins of PWB that added these users come from?
> Same answer. If users are not added into the right groups, and
> the users don't know (or need, care, or be able change) groups,
> they don't get implemented properly.
> And if you don't have gids, want to collaborate, and are discouraged
> from copying, you need to do a ton of chown()s
>> From: Larry McVoy <lm at bitmover.com>
>> > Now you are going to say this could all be done with proper use of
>> group ids
>> > and group permissions.  I agree, but in practice it was not done
>> Bzzt.  We have a solution, they should have used it.
> _______________________________________________
> TUHS mailing list
> TUHS at minnie.tuhs.org
> https://minnie.tuhs.org/mailman/listinfo/tuhs

More information about the TUHS mailing list