From: "\"Andrey Borzenkov\" " <arvidjaar@mail.ru>
To: der.eremit@email.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: Initrd Question
Date: Fri, 13 Feb 2004 17:14:25 +0300 [thread overview]
Message-ID: <E1Are5J-000KGt-00.arvidjaar-mail-ru@f22.mail.ru> (raw)
>> echo 0x0100 > /proc/sys/kernel/real-root-dev
>
> This makes no sense as you're using pivot_root.
this makes all sort of sense. Please check sources. It is required so that kernel will not attempt to mount root passed to it by loader. You are welcome to clean up the code :)
>> mount -n -o ro /dev/sda2 /new_root
>
> This doesn't even match with the 0x0100 above, now does it?
so what? kernel happily ignores real-root-dev, it is possible that some user-level tools may be confused but I have not seen any so far.
>> pivot_root /new_root /new_root/initrd
>
> You should cd into /new_root before running pivot_root,
Huh? Why?
SYNOPSIS
pivot_root new_root put_old
>> 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,
you are wrong here, sorry. .devfsd is created by devfs.
-andrey
next reply other threads:[~2004-02-13 14:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-13 14:14 "Andrey Borzenkov" [this message]
2004-02-13 14:22 ` Initrd Question Valdis.Kletnieks
2004-02-18 2:05 ` Robert White
[not found] <1oMkR-1Zk-21@gated-at.bofh.it>
2004-02-13 15:23 ` der.eremit
2004-02-13 16:42 ` Jim Gifford
2004-02-13 17:12 ` H. Peter Anvin
[not found] <1oC26-8eW-9@gated-at.bofh.it>
2004-02-13 13:30 ` der.eremit
-- 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=E1Are5J-000KGt-00.arvidjaar-mail-ru@f22.mail.ru \
--to=arvidjaar@mail.ru \
--cc=der.eremit@email.de \
--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;
as well as URLs for NNTP newsgroup(s).