* Steve Willer said: > > On Thu, 19 Aug 1999, Justin Wells wrote: > > > I think there are some unresolved issues that need to be decided: > > > > -- A way for root to get sash started, either from an existing > > shell (presumably a static su) or from a login prompt, or > > via a linked and loaded sshd (which would not need to be static > > If ssh is installed on a machine, I would think you would be able to > launch sash with "ssh somemachine /bin/sash". Perhaps you need -t, but it > should work. This would allow you to make use of sash at login without > setting it as anybody's shell. Yes, it would work even locally, that's true. Nevertheless, sash and accompanying stuff should all be there. And I vote for the single mode shell for root to be sash, and the multiuser mode should use a normally linked shell IF there's a way to get a static shell prompt should dynamics fail - which is an argument in favor of an alternative UID 0 account. Or, alternatively (I admit - the idea is a bit weird, but it might work :)), root shell should be set to some small static binary which would exec a "real" shell depending on the conditions. Basically it would work just like lshell does. The difference is that it would determine whether it is possible to load a dynamic shell (or a preferred one - settable in config file) and, if the exec fails, then load an emergency shell - a static one. How about that idea? marek
Attachment:
pgpKszazHKoV0.pgp
Description: PGP signature