Xref: utzoo unix-pc.general:6090 comp.sys.att:10431
Path: utzoo!attcan!uunet!midway!ncar!asuvax!mcdphx!mcdchg!chinet!floydd
From: floydd@chinet.chi.il.us (Floyd Davidson)
Newsgroups: unix-pc.general,comp.sys.att
Subject: Re: my ROOT is DEAD !  What am I going to do ?!
Message-ID: <1990Sep20.041318.17306@chinet.chi.il.us>
Date: 20 Sep 90 04:13:18 GMT
References: <2633@ttardis.UUCP>
Organization: Chinet - Chicago Public Access UNIX
Lines: 28

In article <2633@ttardis.UUCP> rlw@ttardis.UUCP (Ron Wilson) writes:
>In article <1990Sep18.035609.9248@chinet.chi.il.us>, floydd@chinet.chi.il.us (Floyd Davidson) writes:
>>In article <1070@das13.snide.com> dave@das13.snide.com (das13!dave) writes:
>>>In article <245@geocub.greco-prog.fr>, lath@geocub.greco-prog.fr (Laurent Lathieyre) writes:
>>>> 
>>>> /bin/rootsh is a shell script which make an echo to warn
>>>> that you are super-user and make /bin/ksh
>>>> /bin/rootsh has the following access rights -rwx------ root users
>>>
>>>The shell script is your problem.  If you aren't running 'sh' or 'ksh', whats
>>>going to run your shell script?  What you need is a 'C' program!  Try this one.
>>
>>The default in /etc/password can be set to a shell script, and in some
>>cases it is very handy.  You do not get the services of /etc/profile
>>or a $HOME/.profile, instead you get exactly what you put in the shell
>>script.
>
>It's been my experience that login and su insist on the shell for root be
>/bin/sh

True for the root login.  Sorry if I implied that, it was not
intended.  Several things break if root doesn't default to /bin/sh
by name.  Others will break if it does not provide the functionality
of sh.

The previous statement implied that a C program would work as the
default login shell and that a script would not.  In fact either
will work.