>Another side-effect on earlier Solaris revisions is that quite a number of >startup scripts assumed they were running in /sbin/sh, so if one changed the root's shell, there would be "breakage" all o ver the place, and the system wouldn't boot properly.
I believe that his is no more than an OS legend; nothing in Solaris startup ever cared about root's shell. There was only one case where such things would go wrong; not all init.d scripts started with #!/sbin/sh. If you used a non-Bourne compatible shell as root, running /etc/init.d/foo start from the shell would fail. But that would only happen when su'ed or logged in as root; not during ordinary system startup. >Ever since then, I can't bring myself to change the root's shell, lest some >start/stop method assu me it's still running in /sbin/sh. > >Theoretically, nothing will break. But it's just safer not to mess with it. The worst breakage people have been confronted with was: su: Cannot exec /sbin/tcsh or some such when root's password entry was changed to a non-existent shell. Casper _______________________________________________ opensolaris-discuss mailing list [email protected]
