puredyne-team team mailing list archive

[Claude Heiland-Allen <claudiusmaximus@xxxxxxxxxx>]

from hal-lock man page:

--8<--
NOTES
       This program is only useful for launching software that doesn’t use HAL at all (since such software launched using hal-lock would be  locked  out  itself); for example a partition table editor part-foo may use wrapper script like this
       hal-lock --interface org.freedesktop.Hal.Device.Storage --exclusive --run /path/to/part-foo-program
--8<--

Thinking, it should be possible for the script to do something clever
and get hal-lock to call it itself with an additional argument like --I
-certify-that-I-have-a-lock-on-hal-device-storage - would be maybe nicer
than having to have two script files, but the logic would be hairier.

I will run some tests to see if hal-lock actually does do what is
required.


** Changed in: bouilloncube
   Importance: Undecided => High

** Changed in: bouilloncube
       Status: New => In Progress

** Changed in: bouilloncube
     Assignee: (unassigned) => Claude Heiland-Allen (claudiusmaximus)

-- 
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)