On Sun, Apr 26, 2009 at 23:37, Jamie Lokier <jamie@xxxxxxxxxxxxx> wrote: > Alan Stern wrote: >> As for searching for a particular UUID, I believe recent changes to >> sysfs/udev should improve the situation. There will be a "by_UUID" >> directory somewhere, containing a bunch of symbolic links whose names >> are the UUID values of all the registered drives. Programs won't have >> to read every disk; they'll only have to search through this directory. > > That will be great. It is like that for years now, and it is completely in userspace at /dev/disk/by-uuid/. I don't know of any plans to add filesystem/raid signature uuid probing support to the kernel. And I think that will be almost impossible to get right in the kernel. Yes, you need to look at all the disks from userspace, if you request to mount them by filesystem metadata like label/UUID. It works fine even on boxes with thousands of disks. > _If_ the system doesn't wait for all block devices present at boot to > be enumerated before the boot script, then when the script looks in > that directory for a specific UUID, it would be good to wait until > "has everything present at boot been enumerated?" says yes. That's what distros do with initramfs today. > Otherwise you have hacks like my boot script which waits 5 seconds for > a disk to show up on USB, and then continues if not. It sounds > awfully like waiting X seconds for a USB console to show up :-) > > Since this is all about making boot faster, it would be quite nice not > to wait for all block devices before starting the boot script, or at > least the initramfs module-loading script :-) You wait in initramfs until the device show up. Usually dynamic udev rules created from the root= string of the kernel commandline create a rule which matches on the UUID, and creates a /dev/root symlink when the device shows up. As soon as this link shows up, init mounts it and goes ahead. Thanks, Kay -- To unsubscribe from this list: send the line "unsubscribe linux-embedded" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
