It seems that the version of HAL that's in ~AMD64 assigns different permissions for my DVD writer, depending on what disk I place in the drive. e.g. If I insert a CD-audio, CD-data or DVD-video disk into the drive, the ownership is set to meirion:meirion (the user I'm logged in as) and I can see the contents of the disk. If I insert a DVD-data disk (like a game disk) then the ownership is set to root:root, and I can't see the data on the disk. The above URL is a forum discussion where 2 other people have confirmed the same behaviour. It seems to be linked to the HAL version, as one user reports that downgrading to the version in the stable AMD64 branch solves this. Perhaps related: in KDE I see that the device is created at system:/media/hdc rather than /media/cdrecorder as I would expect from the default policy file. It's worth mentioning I have 2 DVD writers installed in my PC, on /dev/hda and /dev/hdc. I'm running architecture ~AMD64, and have the following versions installed hal 0.5.5.1-r3 dbus 0.60-r3 udev 0.81-r1 pmount 0.9.6 meirion@ingrid ~ $ emerge --info Portage 2.1_pre4-r1 (default-linux/amd64/2005.1, gcc-3.4.5, glibc-2.3.6-r2, 2.6.15-gentoo-r1 x86_64) ================================================================= System uname: 2.6.15-gentoo-r1 x86_64 AMD Athlon(tm) 64 Processor 3000+ Gentoo Base System version 1.12.0_pre15 ccache version 2.4 [enabled] dev-lang/python: 2.3.5-r2, 2.4.2 sys-apps/sandbox: 1.2.17 sys-devel/autoconf: 2.13, 2.59-r7 sys-devel/automake: 1.4_p6, 1.5, 1.6.3, 1.7.9-r1, 1.8.5-r3, 1.9.6-r1 sys-devel/binutils: 2.16.1-r1 sys-devel/libtool: 1.5.22 virtual/os-headers: 2.6.11-r3 ACCEPT_KEYWORDS="amd64 ~amd64" AUTOCLEAN="yes" CBUILD="x86_64-pc-linux-gnu" CFLAGS="-O2 -march=athlon64 -pipe" CHOST="x86_64-pc-linux-gnu" CONFIG_PROTECT="/etc /usr/kde/2/share/config /usr/kde/3.5/env /usr/kde/3.5/share/config /usr/kde/3.5/shutdown /usr/kde/3/share/config /usr/lib/X11/xkb /usr/share/config /var/qmail/control" CONFIG_PROTECT_MASK="/etc/gconf /etc/splash /etc/terminfo /etc/env.d" CXXFLAGS="-O2 -march=athlon64 -pipe" DISTDIR="/usr/portage/distfiles" FEATURES="autoconfig ccache distlocks sandbox sfperms strict userpriv usersandbox" GENTOO_MIRRORS="ftp://ftp.snt.utwente.nl/pub/os/linux/gentoo ftp://pandemonium.tiscali.de/pub/gentoo/ ftp://linux.rz.ruhr-uni-bochum.de/gentoo-mirror/ http://mir.zyrianes.net/gentoo/" LANG="en_GB.utf8" LC_ALL="nl_NL.utf8" LINGUAS="en_GB en nl" PKGDIR="/usr/portage/packages" PORTAGE_TMPDIR="/var/tmp" PORTDIR="/usr/portage" PORTDIR_OVERLAY="/usr/local/portage" SYNC="rsync://rsync.europe.gentoo.org/gentoo-portage" USE="amd64 X a52 aac acpi aim alsa arts avi bash-completion berkdb bitmap-fonts bluetooth calendar cdparanoia cdr crypt dts dvd dvdr dvdread eds emboss encode ffmpeg foomaticdb fortran gif gpm gstreamer gtk gtk2 hal icq imlib ipv6 java javascript jpeg kde kdeenablefinal lzw lzw-tiff mcal mime mp3 mpeg msn nas ncurses nls nptl nptlonly nsplugin ogg opengl pam pdflib perl png python qt quicktime readline sdl spell ssl tcpd theora tiff truetype-fonts type1-fonts unicode usb userlocales vorbis xmms xpm xv xvid yahoo zlib elibc_glibc kernel_linux linguas_en_GB linguas_en linguas_nl userland_GNU" Unset: ASFLAGS, CTARGET, EMERGE_DEFAULT_OPTS, LDFLAGS, MAKEOPTS
This is a) not a KDE issue and b) no, it's up to you to decide who has the rights to do what on your box.
The problem is that the rights and mount points specified in /usr/share/hal/fdi/policy/10osvendor are being ignored as far as I can see
Are you using pmount ?
Yes, I'm using pmount. Version as in comment #1
Then the problem is that pmount defaults to root:root with 0700 on UDF filesystems.
OK... but can this also be the reason HAL is not creating /media/cdrecorder but /media/hdc instead? I can't see anything wrong in the storage policy file. Or would this be a separate issue?
OK, this seems to a pmount issue, and I can work around it by passing in the correct mask from the command line... not an elegant solution, but it seems to work.
