puredyne-team team mailing list archive

[Claude Heiland-Allen <claudiusmaximus@xxxxxxxxxx>]

It seems that in Lucid hald might not be always be running so hal-lock
might fail (?), so yet more logic is probably needed to detect hald and
only then run hal-lock.

----8<----
ubiquity (2.1.7) lucid; urgency=low
  ...
  * Only run hal-lock if hald is actually running due to changes in
    hal 0.5.14-0ubuntu2.
  ...
----8<----

http://www.ubuntu.com/testing/lucid/beta1#HAL%20removal "hald removed
from boot process."

-- 
use hal-lock to prevent automount of make-live-device.sh target
https://bugs.launchpad.net/bugs/508203
You received this bug notification because you are a member of puredyne
team, which is the registrant for bouilloncube.

Status in bouillon cube: In Progress

Bug description:
If make-live-device.sh is ran from XFCE hal and co will automount the target device as they are created, turning the whole process in a mess. At the moment the script umount the partitions (thx claude) but the most elegant way would be use hal-locking during the whole process so we are not interrupted at all.

see: http://tuxradar.com/answers/706 (thx dan)