Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!van-bc!sl
From: sl@van-bc.wimsey.bc.ca (Stuart Lynne)
Newsgroups: comp.unix.sysv386
Subject: Re: Which UNIX?
Message-ID: <2064@van-bc.wimsey.bc.ca>
Date: 22 Sep 90 06:38:00 GMT
References: <1990Sep19.011303.13481@NCoast.ORG> <gL3TP2w163w@mudos.ann-arbor.mi.us>
Organization: USENET Public Access, Vancouver, B.C., Canada
Lines: 24

In article <gL3TP2w163w@mudos.ann-arbor.mi.us> mju@mudos.ann-arbor.mi.us (Marc Unangst) writes:
}allbery@NCoast.ORG (Brandon S. Allbery KB8JRR/KT) writes:
}> about security violations when I attempted to add a new shell to the sysadmsh
}
}Oh, you use sysadmsh.  That explains a lot.
}
}One thing I learned is the first month of ODT is to stay as far away
}from sysadmsh as possible.  I do most modifications to the password
}database by editing the authentication files under /tcb/files/auth,
}the /etc/passwd file, and the various files under /etc/auth.
}/tcb/bin/authck is useful for checking that I didn't forget a file
}somewhere along the line and that everything checks out.
}
}sysadmsh may be good for the novice sysadmin who doesn't know a
}password file from device driver.  But it's an absolute pain in the

Amen. It only took me 2 minutes to figure out I really didn't like sysadmsh
when it wouldn't let me have my usual login id. "sl" is only two characters
long and it wanted a minimum of three. It didn't take too long to find the
spots to fix :-) 

-- 
Stuart Lynne	Unifax Communications Inc.
		...!van-bc!sl 604-937-7532(voice)     	sl@wimsey.bc.ca