Browse Source

Mentioned my sysadmin workarounds to cope with udisks on Debian 6.0.2 amd64

master
Thomas Schmitt 11 years ago
parent
commit
b1bfa16e28
  1. 26
      README
  2. 22
      xorriso/README_gnu_xorriso

26
README

@ -95,7 +95,8 @@ are present. This dependcy can be avoided by running
Never omit the "make clean" command after switching libreadline enabling.
Other deliberate dependency reduction options of ./configure are:
--disable-libacl avoid use of ACL functions like acl_to_text()
--disable-xattr avoid use of xattr functions like listxattr()
--disable-xattr avoid use of xattr functions like listxattr() on Linux
resp. extattr_list_file() on FreeBSD
--disable-zlib avoid use of zlib functions like compress2()
--disable-libjte avoid use of libjte for -jigdo command
@ -155,15 +156,26 @@ resp. by xorriso API call
resp. by libburn API call
burn_drive_scan()
A possible source of problems are hald or other automounters.
If you can spot a process "hald-addon-storage" with the address of
your desired drive, then consider to kill it.
If you cannot get rid of the automounter that easily, try whether it helps
to always load the drive tray manually before starting a write run of
xorriso. Wait until the drive light is off.
Better try to unmount a mounted media before a write run.
A similar process "udisks-daemon: polling ..." can be seen on newer Linuxes.
On Debian GNU/Linux 6.0.2 amd64 there is
/lib/udev/rules.d/80-udisks.rules
where one can remove all CD drives ("sr*") from the list of automountable
devices:
KERNEL=="sd*|hd*|mmcblk*|mspblk*", ENV{UDISKS_PRESENTATION_NOPOLICY}="0"
# KERNEL=="sd*|hd*|sr*|mmcblk*|mspblk*", ENV{UDISKS_PRESENTATION_NOPOLICY}="0"
Copying the recognition criterion from
/etc/udev/rules.d/70-persistent-cd.rules
one can prevent automounting a single drive, too. E.g.:
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-2:0:0:0", ENV{UDISKS_PRESENTATION_NOPOLICY}:="1"
If you cannot get rid of the automounter, try whether it helps to always load
the drive tray manually before starting a write run of xorriso. Wait until the
drive light is off and the mounted media appears.
Then try to unmount the mounted media before a write run.
Besides true optical drives, libisoburn can also address disk files as input or

22
xorriso/README_gnu_xorriso

@ -177,11 +177,23 @@ and to add users to it.
A possible source of problems are hald or other automounters.
If you can spot a process "hald-addon-storage" with the address of
your desired drive, then consider to kill it.
If you cannot get rid of the automounter that easily, try whether it helps
to always load the drive tray manually before starting a write run of
xorriso. Wait until the drive light is off.
Better try to unmount a mounted media before a write run.
A similar process "udisks-daemon: polling ..." can be seen on newer Linuxes.
On Debian GNU/Linux 6.0.2 amd64 there is
/lib/udev/rules.d/80-udisks.rules
where one can remove all CD drives ("sr*") from the list of automountable
devices:
KERNEL=="sd*|hd*|mmcblk*|mspblk*", ENV{UDISKS_PRESENTATION_NOPOLICY}="0"
# KERNEL=="sd*|hd*|sr*|mmcblk*|mspblk*", ENV{UDISKS_PRESENTATION_NOPOLICY}="0"
Copying the recognition criterion from
/etc/udev/rules.d/70-persistent-cd.rules
one can prevent automounting a single drive, too:
SUBSYSTEM=="block", ENV{ID_CDROM}=="?*", ENV{ID_PATH}=="pci-0000:00:11.0-scsi-2:0:0:0", ENV{UDISKS_PRESENTATION_NOPOLICY}:="1"
If you cannot get rid of the automounter, try whether it helps to always load
the drive tray manually before starting a write run of xorriso. Wait until the
drive light is off and the mounted media appears.
Then try to unmount the mounted media before a write run.
Besides true optical drives, xorriso can also address disk files as input or

Loading…
Cancel
Save