From: "H. J. Lu" <hjl@lucon.org>
To: Herbert Xu <herbert@gondor.apana.org.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Initrd problem with 2.6 kernel
Date: Fri, 8 Aug 2003 08:23:37 -0700 [thread overview]
Message-ID: <20030808152337.GA11088@lucon.org> (raw)
In-Reply-To: <E19l4o8-0001Jv-00@gondolin.me.apana.org.au>
On Fri, Aug 08, 2003 at 08:49:16PM +1000, Herbert Xu wrote:
> H. J. Lu <hjl@lucon.org> wrote:
> > There is a chicken and egg problem with initrd on 2.6. When
> > root=/dev/xxx is passed to kernel, kernel will call try_name, which
> > uses /sys/block/drive/dev, to find out the device number for ROOT_DEV.
> > The problem is /sys/block/drive may not exist if the driver is loaded
> > by /linuxrc in initrd. As the result, /linuxrc can't use
> > /proc/sys/kernel/real-root-dev to determine the root device number.
>
> You can replicate the sysfs probing in userspace. I did that in
> Debian initrd-tools 0.1.51.
It sounds a good idea. I will give it a try.
Thanks.
H.J.
next prev parent reply other threads:[~2003-08-08 15:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-07 22:30 Initrd problem with 2.6 kernel H. J. Lu
2003-08-08 0:32 ` Andrew Morton
2003-08-08 10:49 ` Herbert Xu
2003-08-08 15:23 ` H. J. Lu [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-08-08 20:52 Andrey Borzenkov
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=20030808152337.GA11088@lucon.org \
--to=hjl@lucon.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