From: der.eremit@email.de
To: "Jim Gifford" <maillist@jg555.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Initrd Question
Date: Fri, 13 Feb 2004 14:30:29 +0100 [thread overview]
Message-ID: <E1ArdOn-00005C-4T@localhost> (raw)
In-Reply-To: <1oC26-8eW-9@gated-at.bofh.it>
> echo "Initial RAMDISK Loading Starting..."
Did you get this message when trying your initrd? If not, you probably
forgot to pass the kernel a root=/dev/ram0 boot option.
> insmod /lib/megaraid.ko
> insmod /lib/aic7xxx.ko
> insmod /lib/uhci-hcd.ko
> echo "Mounting proc..."
> mount -n -t proc none /proc
> echo 0x0100 > /proc/sys/kernel/real-root-dev
This makes no sense as you're using pivot_root. The old method requires
terminating the initrd script, then the kernel attempts to mount
real-root-dev. That never happens as your script doesn't exit, but execs
init instead.
> echo "Mounting real root dev..."
> mount -n -o ro /dev/sda2 /new_root
This doesn't even match with the 0x0100 above, now does it?
> echo "Running pivot_root..."
> pivot_root /new_root /new_root/initrd
You should cd into /new_root before running pivot_root, or does the
pivot_root from busybox somehow do this for you?
> if [ -c initrd/dev/.devfsd ]
> then
> echo "Mounting devfs..."
> mount -n -t devfs none dev
> fi
Should you check for /dev/.devfsd on the real root here? I thought .devfsd
is created by the devfsd process, so wouldn't be on the initrd /dev?
--
Ciao,
Pascal
next parent reply other threads:[~2004-02-13 13:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1oC26-8eW-9@gated-at.bofh.it>
2004-02-13 13:30 ` der.eremit [this message]
[not found] <1oMkR-1Zk-21@gated-at.bofh.it>
2004-02-13 15:23 ` Initrd Question der.eremit
2004-02-13 16:42 ` Jim Gifford
2004-02-13 17:12 ` H. Peter Anvin
2004-02-13 14:14 "Andrey Borzenkov"
2004-02-13 14:22 ` Valdis.Kletnieks
2004-02-18 2:05 ` Robert White
-- strict thread matches above, loose matches on Subject: below --
2004-02-13 3:12 Jim Gifford
2004-02-13 20:34 ` Chris Lingard
2001-06-18 7:20 initrd question Kelledin Tane
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=E1ArdOn-00005C-4T@localhost \
--to=der.eremit@email.de \
--cc=linux-kernel@vger.kernel.org \
--cc=maillist@jg555.com \
/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