At the time when I made the statement in the EXT4 HOWTO, vol_id didn't understand difference between ext4dev and ext4 filesystems. The bigger problem which is a major issue for people like me who are creating plenty of test filesystems is that vol_id patches to mount has the Windows-like property that newly created filesystems won't work until after you reboot. Personally, if you are willing to accept Windows- like flaws, you should use Windows. I am constantly creating and destroying filesystems, and the blkid libraries will detect and be able to resolve LABEL= and UUID= arguments right away.
The vol_id patches to mount will fail to resolve LABEL= and UUID= parameters for newly created filesystems until you reboot, or give some magic command to force the vol_id subsystem to recreate and reprobe the /dev/disk/by-uuid and /dev/disk/by-label directories. Personally, I can never remember the magic command, and arguably, you shouldn't have to remember said magic command, especially when it's easier to recompile and replace util-linux with one that is compiled to use blkid. After all, if I was willing to deal with systems that require reboots before they function correctly, I'd be using Windows. :-) -- In order to support ext4, util-linux must use blkid (and not vol_id) https://bugs.launchpad.net/bugs/197311 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
