-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Hi Vincent,
Am So den 10. Feb 2008 um 11:06 schrieb Vincent Fourmond: > Thanks. I think I might understand the problem here. Just to make > sure, could you please provide the output of: > > pmount -d /dev/cdrom resolved /dev/cdrom to device /dev/hdc Checking for device '/dev/hdc' in '/etc/fstab' mount point to be used: /media/cdrom no iocharset given, current locale encoding is ISO-8859-1 Cleaning lock directory /var/lock/pmount_dev_hdc Checking for device '/dev/hdc' in '/etc/mtab' Checking for device '/dev/hdc' in '/proc/mounts' device_whitelist: checking /etc/pmount.allow... device_whitlisted(): nothing matched, returning 0 find_sysfs_device: looking for sysfs directory for device 22:0 find_sysfs_device: checking whether /dev/hdc is on /sys/block/dm-3 (254:3) find_sysfs_device: checking whether /dev/hdc is on /sys/block/dm-2 (254:2) find_sysfs_device: checking whether /dev/hdc is on /sys/block/dm-1 (254:1) find_sysfs_device: checking whether /dev/hdc is on /sys/block/dm-0 (254:0) find_sysfs_device: checking whether /dev/hdc is on /sys/block/loop7 (7:7) find_sysfs_device: checking whether /dev/hdc is on /sys/block/loop6 (7:6) find_sysfs_device: checking whether /dev/hdc is on /sys/block/loop5 (7:5) find_sysfs_device: checking whether /dev/hdc is on /sys/block/loop4 (7:4) find_sysfs_device: checking whether /dev/hdc is on /sys/block/loop3 (7:3) find_sysfs_device: checking whether /dev/hdc is on /sys/block/loop2 (7:2) find_sysfs_device: checking whether /dev/hdc is on /sys/block/loop1 (7:1) find_sysfs_device: checking whether /dev/hdc is on /sys/block/loop0 (7:0) find_sysfs_device: checking whether /dev/hdc is on /sys/block/hdc (22:0) find_sysfs_device: major device numbers match find_sysfs_device: minor device numbers also match, /dev/hdc is a raw device device_removable: corresponding block device for /dev/hdc is /sys/block/hdc get_blockdev_attr: value of /sys/block/hdc/removable == 1 policy check passed spawnv(): executing /sbin/cryptsetup '/sbin/cryptsetup' 'isLuks' '/dev/hdc' spawn(): /sbin/cryptsetup terminated with status 255 device is not LUKS encrypted, or cryptsetup with LUKS support is not installed locking mount point directory mount point directory locked blkid gave FS iso9660 for '/dev/hdc' spawnv(): executing /bin/mount '/bin/mount' '-t' 'iso9660' '-o' 'nosuid,nodev,user,async,atime,noexec,uid=10230,gid=101' '/dev/hdc' '/media/cdrom' spawn(): /bin/mount terminated with status 0 unlocking mount point directory mount point directory unlocked So the handling is absolutely wrong in this case. The cdrom has to be mounted under /cdrom and not under /media/cdrom. I never would have the cdrom under /media/.... > >> Well, the great thing about pmount is that it precisely calls mount > >> for devices in /etc/fstab - saving trouble (except, of course, when that > >> behavior is buggy). > > > > True. But why was it changed from a working state to using pumount for > > devices not under /media? > > I'll need to investigate that. I've been neglecting pmount for a > while, and the bug count keeps increasing... So, just understand. I never use pmount mounting /cdrom. I use mount as it is in the fstab. With eject switched to always using pumount also for drives mounted via fstab this issue makes eject nearly unusable at all as the first reason for eject is to eject a cdrom. (I know that there is more as ejecting USB deice. But those use is much less common.) Gruß Klaus - -- Klaus Ethgen http://www.ethgen.de/ pub 2048R/D1A4EDE5 2000-02-26 Klaus Ethgen <[EMAIL PROTECTED]> Fingerprint: D7 67 71 C4 99 A6 D4 FE EA 40 30 57 3C 88 26 2B -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.6 (GNU/Linux) iQEVAwUBR6+gc5+OKpjRpO3lAQJHKAgAs0Yfu/S4lT1Azdj4vvQ1vKtipoWm6B/j DUJqNV1Gt6VaJamwF4XTC7kkVicuWB/a05xP2LQKx8h07SNm3vOv13zQPLp6o3tR 813AijuePc+/hy9WQVnoYhM/69Oxv68F0U5Wwg02Ee4mgxoun1YrmUt1HATguaEG x6DwmTlt4UdOJS209QhrFdVNF8HOP1IYV0o2sAVZXpo1KjX0rLH+xYDimW/eBw76 /stKE+xYo6yQXcBgV9wMpww8fN7kFOURKvh8pkHgHhtwe+OTKdYjAfHSHaqwatTN YhI2+8i65+nYK/AoY5bUypSEqqkw4OCVkRhsKjTY1Nqs+F+pIENTXA== =euoj -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
