From: Ben Collins <bcollins@debian.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Differences between 2.2.x and 2.4.x initrd
Date: Tue, 13 Nov 2001 16:34:43 -0500 [thread overview]
Message-ID: <20011113163443.I329@visi.net> (raw)
In-Reply-To: <20011113150317.G329@visi.net> <E163kVM-0005Rf-00@gondolin.me.apana.org.au>
In-Reply-To: <E163kVM-0005Rf-00@gondolin.me.apana.org.au>
On Wed, Nov 14, 2001 at 07:50:00AM +1100, Herbert Xu wrote:
> Ben Collins <bcollins@debian.org> wrote:
>
> > Well, the point being that 2.2.x worked implicitly, and 2.4.x doesn't. I
> > don't want to have to tell people who have been using tilo forever and a
> > day that they now have to add additional command line to get it to work
> > with 2.4.x.
>
> You don't have to. Just setup linuxrc to echo the right stuff into
> /proc/sys/kernel/real-root-dev
Yeah, which is listed under the "Obsolete" section in
Documentation/initrd.txt. The assumption I'm making here is that if
/linuxrc fails to execute, it falls back to /sbin/init on the currently
mounted root filesystem. Assumptions are bad, but I don't see why it
can't work like this. If there is a filesystem already mounted, it
should be used.
Ben
--
.----------=======-=-======-=========-----------=====------------=-=-----.
/ Ben Collins -- Debian GNU/Linux \
` bcollins@debian.org -- bcollins@openldap.org -- bcollins@linux.com '
`---=========------=======-------------=-=-----=-===-======-------=--=---'
next prev parent reply other threads:[~2001-11-13 21:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-11-13 19:39 Differences between 2.2.x and 2.4.x initrd Ben Collins
2001-11-13 19:49 ` Jeff Garzik
2001-11-13 20:03 ` Ben Collins
2001-11-13 20:50 ` Herbert Xu
2001-11-13 21:34 ` Ben Collins [this message]
2001-11-13 22:48 ` Jeff Garzik
2001-11-14 1:27 ` Ben Collins
2001-11-14 1:48 ` Ben Collins
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=20011113163443.I329@visi.net \
--to=bcollins@debian.org \
--cc=herbert@gondor.apana.org.au \
--cc=linux-kernel@vger.kernel.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