DJ Lucas wrote: > > Bryan Kadzban <br...@kadzban.is-a-geek.net> wrote: > >> Although, hmm. Either way here, there's a possible problem, with >> symlinks for disk devices. If the USB ID file isn't present, then >> it's possible that the /etc/fstab entry for /usr refers to a >> symlink that relies on this file. Of course, in that case you're >> just as screwed even if you have an initramfs that does this >> mounting (since the initramfs doesn't have the file either), so >> it's probably not worth defending against. > > Unfortunately, I think inevitably we'll have to add it, but we aren't > there quite yet. I'm pretty sure upstream will eventually force it > upon us.
Probably. :-) > If a small /usr is in the initrd, it'll work. Does the > /lib/udev/devices get a recursive copy? If so, then can't a minimal > symlink tree be created to account for a particular device...and if > not, then in rootfs before real / is mounted. It'd work in /lib/udev/devices/disk/by-blah/, yes. Though a static symlink there would require that the kernel never change the sd* device ordering (otherwise the symlink will point at the wrong block device). This is a *very* theoretical corner case anyway, though, because nothing today (at least in upstream rules) uses the usb-db program to create disk symlinks. It's only used for TTY device and NIC descriptions (which only set an entry in the udev database; they don't use this entry for anything), and sound cards (and the comments imply this is only used by pulseaudio).
signature.asc
Description: OpenPGP digital signature
-- http://linuxfromscratch.org/mailman/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
