On Mon, 2010-03-22 at 23:24 +0000, Daniel Richard G. wrote: > The bug is that the system didn't invoke blkid(8) in the first place, > whether in the installer or the startup scripts. Are you saying that > /etc/blkid.tab should be a dangling symlink until/unless the user > manually creates the target? Even many technical users don't know what > the blkid(8) command is about. > The system frequently invokes blkid, however it invokes it in "direct probe" mode and stores the results in the udevdb - which is where all modern software gets the information.
So it's quite normal for blkid.tab to be a dangling symlink until an application that hasn't been ported to udev runs blkid (at which point it's populated) The reason you don't see one is because most things have switched to udev Scott -- Scott James Remnant sc...@ubuntu.com -- /etc/blkid.tab symlink is broken (or: /dev/.blkid.tab doesn't exist) https://bugs.launchpad.net/bugs/514130 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
