linux-kernel - RE: could not find filesystem /dev/root

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <00da01c70287$aa8c2420$4b00a8c0@donald>
Date:	Tue, 7 Nov 2006 17:13:25 +0100
From:	"Paul Rolland" <rol@...917.net>
To:	"'Jan Engelhardt'" <jengelh@...ux01.gwdg.de>
Cc:	"'Marc Perkel'" <marc@...kel.com>,
	"'Chris Lalancette'" <clalance@...hat.com>,
	"'Rafael J. Wysocki'" <rjw@...k.pl>, <linux-kernel@...r.kernel.org>
Subject: RE: could not find filesystem /dev/root

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

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/