Path: utzoo!attcan!uunet!husc6!mit-eddie!apollo!weber_w From: weber_w@apollo.uucp (Walt Weber) Newsgroups: comp.sys.apollo Subject: Re: /bin/login vs. Aegis login Message-ID: <3cf4a72a.10b48@apollo.uucp> Date: 29 Jun 88 20:19:00 GMT References: <8806212136.AA05200@umix.cc.umich.edu> Reply-To: weber_w@apollo.UUCP (Walt Weber) Organization: Apollo Computer, Chelmsford, MA Lines: 33 In article <8806212136.AA05200@umix.cc.umich.edu> FERGUSON@BKNLVMS.BITNET writes: > > >After running /etc/crpasswd, I should be able to log in through >/bin/login without trouble right? Only if the balance of the installation has been done correctly. >I boiled the problem down to this: > > I tried logging in through /bin/login, and I got the same > errors. I've done the crpasswd procedure, so what am I missing? > >Thanks to anyone who can help. Scott -- Two things come to mind (and that's stretching it's capacity :-) 1) is /bin/login owned by & setuid root?? (ls -l should show 4755, owner == root , group == staff) 2) the person "root" in the registry MUST have been created by the one-time-only execution of the command /install/addroot, and not by manually adding a person named "root" to the registry. (Addroot does some magic inside the registry to add root as a "special" person.) ...walt... -- Walt Weber PHONE: (617) 256-6600 x7004 Apollo Computer GENIE: W.WEBER Chelmsford, People's Republic of Massachusetts