Re: Request for feature: adduser --alias
Raul Miller <rdm@test.legislate.com> writes:
> This way, you can sign on as sashroot for recover work, while retaining
> the command line editting features, etc. of your normal root shell.
>
> sash is a statically linked root shell, whose primary benefit is to
> let you log on as root and do something about a system whose shared
> libraries are damaged.
If the shared libraries are damaged, then how are init, getty, and
login running, in order for sashroot to be invoked? The only thing a
special UID is going to help with is if the root shell is messed up.
A better use of sashroot is booting the machine `init=/bin/sashroot'.
Nothing is gained by having a special uid 0 account with sashroot as
its shell.
Guy
Reply to: