use hal-lock to prevent automount of make-live-device.sh target
Bug #508203 reported by
Aymeric Mansoux
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bouilloncube |
Won't Fix
|
High
|
Claude Heiland-Allen |
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://
Changed in bouilloncube: | |
milestone: | none → 10.04 |
To post a comment you must log in.
from hal-lock man page:
--8<-- .Hal.Device. Storage --exclusive --run /path/to/ part-foo- program
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
--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.