From: Helge Hafting <helgehaf@aitel.hist.no>
To: Andrew Morton <akpm@osdl.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: 2.6.0-test4-mm2 didn't try to mount root
Date: Wed, 27 Aug 2003 13:52:37 +0200 [thread overview]
Message-ID: <3F4C9B85.7040602@aitel.hist.no> (raw)
In-Reply-To: 20030827031534.29b08946.akpm@osdl.org
Andrew Morton wrote:
> Helge Hafting <helgehaf@aitel.hist.no> wrote:
>
>>test4-mm1 with the same config works on the same machine,
>> and mounts root between "md: ... autorun DONE" and "Mounted devfs on /dev"
>>
>> Root is supposed to be on the raid array, which did come up.
>> Lilo uses append="root=/dev/md/0".
>
>
> Does reverting this fix it?
>
>
Thanks, that did the trick. Seems this "no root" stuff
didn't realize that I want a root after all.
> This patch allows a person to not require mounting a root device at
startup.
> This works idealy for people trying to use the initramfs/sysfs as the
only
> filesystem.
> What happens is that when the root device is set to 0,0 mount_root is
not
> called.
There is more than one way to specify a root, it seems. I never
set any numbers for my root, I use the root=/dev/md/0 parameter
to the kernel. I don't have any initramfs.
Why don't those who want to keep an initramfs simply
specify root=/dev/root which don't need extra parsing?
Helge Hafting
next prev parent reply other threads:[~2003-08-27 11:44 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-27 5:10 2.6.0-test4-mm2 Andrew Morton
2003-08-27 10:12 ` 2.6.0-test4-mm2 didn't try to mount root Helge Hafting
[not found] ` <20030827031534.29b08946.akpm@osdl.org>
2003-08-27 11:52 ` Helge Hafting [this message]
2003-08-27 12:58 ` 2.6.0-test4-mm2 Christian Axelsson
2003-08-27 15:54 ` 2.6.0-test4-mm2 Steven Cole
2003-08-27 17:25 ` 2.6.0-test4-mm2 Andrew Morton
2003-08-27 17:59 ` 2.6.0-test4-mm2 Hans Reiser
2003-08-27 19:48 ` 2.6.0-test4-mm2 Christian Axelsson
2003-08-28 12:53 ` 2.6.0-test4-mm2 Luiz Capitulino
2003-08-28 16:02 ` 2.6.0-test4-mm2 Andrew Morton
2003-08-28 17:11 ` 2.6.0-test4-mm2 Luiz Capitulino
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=3F4C9B85.7040602@aitel.hist.no \
--to=helgehaf@aitel.hist.no \
--cc=akpm@osdl.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