From: "Paul Rolland" <rol@as2917.net>
To: "'Jan Engelhardt'" <jengelh@linux01.gwdg.de>
Cc: "'Marc Perkel'" <marc@perkel.com>,
"'Chris Lalancette'" <clalance@redhat.com>,
"'Rafael J. Wysocki'" <rjw@sisk.pl>,
<linux-kernel@vger.kernel.org>
Subject: RE: could not find filesystem /dev/root
Date: Tue, 7 Nov 2006 17:13:25 +0100 [thread overview]
Message-ID: <00da01c70287$aa8c2420$4b00a8c0@donald> (raw)
In-Reply-To: <Pine.LNX.4.61.0611071514270.11892@yvahk01.tjqt.qr>
Hello,
> Yeah, "unless". But the kernel should be considered fuzzy logic in
> this area :) after all, it does not even need a kernel developer -- a
> binutils contributor might also change something that results in a
> change of link order.
Right... but I do change my kernel more often than my binutils ;)
> On the other side, you can run udev _once_ to create device
> nodes like
> /dev/disk/by-label/ to allow at least correct booting (possibly using
> LABEL=) Once the box is up, one can always figure out which drive is
> which by looking at fdisk or other info. (Gets a little hard when
> they're all the same manufacturer and type, but then again, LABEL=
> will work without udev in the "normal" userspace.)
I may give it a try... Using uuid could also be an option but I'm not
sure this can be configured thru fstab...
Paul
next prev parent reply other threads:[~2006-11-07 16:13 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-06 1:54 could not find filesystem /dev/root Marc Perkel
2006-11-06 10:18 ` Mathieu SEGAUD
2006-11-06 10:26 ` Arjan van de Ven
2006-11-06 14:20 ` Marc Perkel
2006-11-06 20:12 ` Rafael J. Wysocki
2006-11-06 21:18 ` Marc Perkel
2006-11-06 21:25 ` Rafael J. Wysocki
2006-11-06 21:30 ` Marc Perkel
2006-11-06 23:46 ` Chris Lalancette
2006-11-06 23:53 ` Marc Perkel
2006-11-07 7:04 ` Paul Rolland
2006-11-07 9:17 ` Jan Engelhardt
2006-11-07 9:52 ` Paul Rolland
2006-11-07 14:18 ` Jan Engelhardt
2006-11-07 16:13 ` Paul Rolland [this message]
2006-11-07 17:31 ` Jan Engelhardt
2006-11-07 15:10 ` could not find filesystem /dev/root - menucinfig Marc Perkel
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='00da01c70287$aa8c2420$4b00a8c0@donald' \
--to=rol@as2917.net \
--cc=clalance@redhat.com \
--cc=jengelh@linux01.gwdg.de \
--cc=linux-kernel@vger.kernel.org \
--cc=marc@perkel.com \
--cc=rjw@sisk.pl \
/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