From: Wakko Warner <wakko@animx.eu.org>
To: Samuel Thibault <samuel.thibault@ens-lyon.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: emergency or init=/bin/sh mode and terminal signals
Date: Sun, 18 Jun 2006 18:52:00 -0400 [thread overview]
Message-ID: <20060618225200.GB30726@animx.eu.org> (raw)
In-Reply-To: <20060618224051.GE4744@bouh.residence.ens-lyon.fr>
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???
next prev parent reply other threads:[~2006-06-18 22:50 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-18 21:23 Samuel Thibault
2006-06-18 21:33 ` Willy Tarreau
2006-06-19 22:03 ` Samuel Thibault
2006-06-20 11:15 ` linux-os (Dick Johnson)
2006-06-18 22:39 ` Wakko Warner
2006-06-18 22:40 ` Samuel Thibault
2006-06-18 22:44 ` Willy Tarreau
2006-06-18 22:48 ` Samuel Thibault
2006-06-19 3:59 ` Willy Tarreau
2006-06-19 7:59 ` Samuel Thibault
2006-06-18 22:52 ` Wakko Warner [this message]
2006-06-18 23:25 ` Joshua Hudson
2006-06-19 11:37 ` linux-os (Dick Johnson)
2006-06-19 11:46 ` Samuel Thibault
2006-06-19 12:05 ` linux-os (Dick Johnson)
2006-06-19 22:06 ` Samuel Thibault
2006-06-21 11:53 ` linux-os (Dick Johnson)
2006-06-21 11:57 ` Samuel Thibault
2006-06-19 22:09 ` Samuel Thibault
2006-06-20 0:02 ` David Luyer
2006-06-20 4:28 ` Willy Tarreau
2006-06-20 5:03 ` Valdis.Kletnieks
2006-06-20 8:04 ` Samuel Thibault
2006-07-01 14:57 ` Matthias Andree
2006-06-20 11:26 ` linux-os (Dick Johnson)
2006-06-20 11:32 ` Samuel Thibault
2006-06-19 12:08 ` Jan Engelhardt
2006-06-19 15:47 ` Samuel Thibault
2006-06-19 3:47 Albert Cahalan
2006-06-19 8:57 ` Samuel Thibault
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060618225200.GB30726@animx.eu.org \
--to=wakko@animx.eu.org \
--cc=linux-kernel@vger.kernel.org \
--cc=samuel.thibault@ens-lyon.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®