From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: "J.A. Magallon" <jamagallon@able.es>
Cc: Arjan van de Ven <arjan@infradead.org>,
Bernd Petrovitsch <bernd@firmix.at>,
Jan Engelhardt <jengelh@linux01.gwdg.de>,
Jiri Slaby <xslaby@fi.muni.cz>,
kavitha s <wellspringkavitha@yahoo.co.in>,
linux-kernel@vger.kernel.org
Subject: Re: root=LABEL= problem [Was: Re: Linux Issue]
Date: Thu, 02 Feb 2006 14:41:48 +0000 [thread overview]
Message-ID: <1138891308.9861.9.camel@localhost.localdomain> (raw)
In-Reply-To: <20060202091900.469e7394@werewolf.auna.net>
On Iau, 2006-02-02 at 09:19 +0100, J.A. Magallon wrote:
> > it's 100% done in the initrd.
>
> Isn't this a matter of the bootloader ?
The boot loader knows very little and the BIOS may not even be able to
drive some of the hardware to go looking for volume labels. The sequence
used is that the initrd is the root file system and contains application
code run very early on in order to find out where the 'real' root fs is
by label. Having mounted that it can then pivot_root() itself into the
final desired configuration.
All userspace, and all the initrd building is done by a tool called
mkinitrd.
Alan
next prev parent reply other threads:[~2006-02-02 14:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-01 6:59 Linux Issue kavitha s
2006-02-01 7:27 ` Andre Bender
2006-02-01 11:48 ` root=LABEL= problem [Was: Re: Linux Issue] Jiri Slaby
2006-02-01 16:14 ` Jan Engelhardt
2006-02-01 16:16 ` Bernd Petrovitsch
2006-02-01 16:18 ` Jan Engelhardt
[not found] ` <20060201124151.5b4c0435.seanlkml@sympatico.ca>
2006-02-01 17:41 ` sean
2006-02-02 6:51 ` Arjan van de Ven
2006-02-02 8:19 ` J.A. Magallon
2006-02-02 10:55 ` Bernd Petrovitsch
2006-02-02 14:41 ` Alan Cox [this message]
2006-02-02 15:42 ` Arjan van de Ven
2006-02-02 6:51 ` Arjan van de Ven
2006-02-02 10:53 ` Jiri Slaby
2006-02-02 16:51 ` Jan Engelhardt
2006-02-03 12:55 ` Arjan van de Ven
2006-02-03 13:45 ` Samer Azmy
2006-02-03 16:58 ` Fawad Lateef
2006-02-03 17:03 ` Fawad Lateef
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=1138891308.9861.9.camel@localhost.localdomain \
--to=alan@lxorguk.ukuu.org.uk \
--cc=arjan@infradead.org \
--cc=bernd@firmix.at \
--cc=jamagallon@able.es \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=wellspringkavitha@yahoo.co.in \
--cc=xslaby@fi.muni.cz \
/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
Powered by JetHome