Path: utzoo!attcan!uunet!mcvax!kth!sunic!dkuug!harald.ruc.dk!d.jba
From: d.jba@harald.ruc.dk (Jan B. Andersen)
Newsgroups: comp.bugs.sys5
Subject: admin/acct/joe (Was: 'ls -n' opens password file for rea)
Message-ID: <44@harald.UUCP>
Date: 22 May 89 17:05:23 GMT
References: <1326@rivm05.UUCP> <7400003@gistdev>
Organization: RUC - Roskilde University Center, Denmark
Lines: 33

flint@gistdev.UUCP writes:

-In the "what I'd really like to see" department, would be to get rid of the
-one-level username system we have, and go to a hierarchial username system.
-(For example, instead of being identified as "joe", a user might be
-identified as admin/acct/joe if Joe was in the Administration Department,
-Accounting Section of the company.  If there was another Joe doing working
-in customer support, he'd be ops/cs/joe (for Operations/Customer Support/Joe)

What prevents you from creating usernames like that (or admin.acct.joe) ?
d.jba works fine for me.

-...: and many advantages would
-result.  Search time through an excessively long passwd file would be a lot
-less,

How often do you actually have to search the passwd file?

-... the whole system
-wouldn't die if the passwd file got corrupted (you'd be able to switch to
-a different group and log in and fix it), etc.

Don't you keep a copy of passwd.old around?
---
Jan B. Andersen, Datalogi 19.1     .---------------------------.       /^^^\
Roskilde Universitetscenter       ( "SIMULA does it with CLASS" )     { o_o }
Postbox 260,                       `---------------------------'  <--- \ o /
DK-4000  Roskilde (Denmark)       IfUmust: +45 46 75 77 11            -mm--mm-
-- 
Jan B. Andersen, Datalogi 19.1     .---------------------------.       /^^^\
Roskilde Universitetscenter       ( "SIMULA does it with CLASS" )     { o_o }
Postbox 260,                       `---------------------------'  <--- \ o /
DK-4000  Roskilde (Denmark)       IfUmust: +45 46 75 77 11            -mm--mm-