On 13-Jan-2001 Dustin Puryear wrote: <em>> We discussed a little bit about specifying the init process at the LILO <em>> prompt in January's meeting. I believe I saw an article on just that at <em>> linux.com if anyone is interested. (I think it was linux.com.) <em>> <em>> Very useful technique, especially if you have an init script bonking <em>> your system startup. I agree. Though I've always used the sash shell (/bin/sh on Linux systems is almost always Bash) to substitute for init, since it's a statically compiled shell with most of the critical commands built into the executable (i.e. cp,mv,rm,ln,sync,mount/umount, and many others). ash is not as nice as bash, since it doesnt have command history or completion or editing. Since sash is static, it works even if /lib has been hosed. ================================================ BRLUG - The Baton Rouge Linux User Group Visit http://www.brlug.net for more information. Send email to [EMAIL PROTECTED] to change your subscription information. ================================================ <!-- body="end" --> <hr noshade> <ul> <li><strong>Next message:</strong> Dustin Puryear: "Re: [brluglist] init=/bin/sh rw" <li><strong>Previous message:</strong> Dustin Puryear: "Re: [brluglist] Samba book?" <li><strong>In reply to:</strong> Dustin Puryear: "[brluglist] init=/bin/sh rw" <li><strong>Next in thread:</strong> Dustin Puryear: "Re: [brluglist] init=/bin/sh rw" <li><strong>Reply:</strong> Dustin Puryear: "Re: [brluglist] init=/bin/sh rw" <li><strong>Messages sorted by:</strong> [ date ] [ thread ] [ subject ] [ author ] [ attachment ] </ul> <hr noshade>
<small> <em> This archive was generated by hypermail 2.1.2 : <em>Thu Sep 06 2001 - 11:10:50 CDT</em> </em> </small> </body> </html>
