>> If you don't want udev, make an initramfs, build your disk driver as
>> modules, and load them in the order you want your disks numbered.
>>
>> udev or initramfs, you ought to choose at least one.
>
>Nope, you don't. I'm now using a kernel without modules for what's disk
>related, and unless people (read kernel developpers) change something
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.
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.)
>in the init order, I'm now with a stable environment, without udev or
>initramfs.
>
>Paul
>
-`J'
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
[Index of Archives]
[Kernel Newbies]
[Netfilter]
[Bugtraq]
[Photo]
[Stuff]
[Gimp]
[Yosemite News]
[MIPS Linux]
[ARM Linux]
[Linux Security]
[Linux RAID]
[Video 4 Linux]
[Linux for the blind]
[Linux Resources]
