Hi Martin, thanks for the response!
I guess what I'm puzzled about is that looking at what has changed in
that part of the code of hald/linux/blockdev.c it appears that they have
removed the check to see if it matches the dm- pattern and consequent
debug message and usleep(). The comment before the test that triggers
the usleep(1000*1000) in the 0.5.8.1 version says:
/* sleep one second since device mapper needs additional
* time before the device file is ready
*
* this is a hack and will only affect device mapper block
* devices. It can go away once the kernel emits a "changed"
* event for the device file (this is about to go upstream)
* and we can depend on a released kernel with this feature.
*/
If the current Feisty kernel does emit that "changed" event then would
it be safe to just make that usleep() go away ?
Yours,
Confused of Melbourne. :-)
--
hal takes about 60 seconds to start up
https://bugs.launchpad.net/bugs/92647
You received this bug notification because you are a member of Ubuntu
Bugs, which is the bug contact for Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
