From: Andrey Borzenkov <arvidjaar@mail.ru>
To: "H. J. Lu" <hjl@lucon.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Initrd problem with 2.6 kernel
Date: Sat, 9 Aug 2003 00:52:40 +0400 [thread overview]
Message-ID: <200308090052.40940.arvidjaar@mail.ru> (raw)
> 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.
{pts/1}% grep \"/sys\" *
do_mounts.c: sys_mkdir("/sys", 0700);
do_mounts.c: if (sys_mount("sysfs", "/sys", "sysfs", 0, NULL) < 0)
do_mounts.c: sys_umount("/sys", 0);
do_mounts.c: sys_rmdir("/sys");
or do you mean something different?
-andrey
next reply other threads:[~2003-08-08 20:52 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-08 20:52 Andrey Borzenkov [this message]
-- strict thread matches above, loose matches on Subject: below --
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
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=200308090052.40940.arvidjaar@mail.ru \
--to=arvidjaar@mail.ru \
--cc=hjl@lucon.org \
--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