Samuel Thibault wrote:
> Wakko Warner, le Sun 18 Jun 2006 18:39:06 -0400, a ?crit :
> > why not only set this if the shell is /bin/sh ?
>
> Because you can't know that. /bin/sh is one example of shell, /bin/ash
> is another /usr/bin/myprog is yet another...
I realized that before I sent the email. /bin/sh is guaranteed (usually) to
be there. I myself prefer zsh, but when I'm booting with init=, it's always
/bin/sh (unless I'm testing something else). Of course, that's just me.
The one time I did use init=/bin/zsh, it failed to function properly (forgot
the details), but booting with /bin/sh and exec zsh worked fine.
Is there any (non-embedded) linux systems out there that do not have
/bin/sh ? On the boot cd I built, there is no /bin/sh but there is a
/bin/init (shell script with #! busybox ash at the top)
Anyway, it's a thought. Or you could only enable it if the init= is not
init (Any other inits?)
--
Lab tests show that use of micro$oft causes cancer in lab animals
Got Gas???
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
