#include <hallo.h>
* Vincent Fourmond [Wed, Jul 04 2007, 09:20:54PM]:
>
> Hello !
>
> I've just taken over maintenance of pmount, and I'm trying to give a
> decent cleaning to the BTS entries... I find that your case is somehow
> puzzling. If the problem still occurs, could you please provide the
> output of
>
> pumount -d hda
> pumount -d hdb
>
> That should help me locate the problem...
pumount -d hda
checking whether hda is a mounted directory
checking whether /media/hda is a mounted directory
resolved mount point /media/hda to device /dev/hda
resolved /dev/hda to device /dev/hda
device /dev/cdrom handled by fstab, calling umount
umount: /dev/hda is not in the fstab (and you are not root)
checking whether hdb is a mounted directory
checking whether /media/hdb is a mounted directory
resolved mount point /media/hdb to device /dev/hdb
resolved /dev/hdb to device /dev/hdb
policy check passed
spawnv(): executing /bin/umount '/bin/umount' '/dev/hdb'
spawn(): /bin/umount terminated with status 0
spawnv(): executing /sbin/cryptsetup '/sbin/cryptsetup' 'luksClose' '/dev/hdb'
spawn(): /sbin/cryptsetup terminated with status 234
It mentions fstab but...
grep cdrom /etc/fstab
/dev/cdrom /media/cdrom0 iso9660 ro,user,noauto 0 0
/dev/cdrom1 /media/cdrom1 iso9660 ro,user,noauto 0 0
ls -la /dev/cdrom*
lrwxrwxrwx 1 root root 3 2007-06-17 19:02 /dev/cdrom -> hda
lrwxrwxrwx 1 root root 3 2007-06-17 19:02 /dev/cdrom7 -> hdb
Looks like it maps hda back to the cdrom symlink. Maybe the authors tried to
make
sure that the user gets the same permissions and options as she would
have through simple mount usage, but they failed since mount does not
work this way and only resolves symlinks to files when needed, not vice
versa. Or maybe it uses major/minor numbers internally to check the
devices and just gets confuses (simple bug)... I don't know, have not
looked at the source yet.
Eduard.
PS: some more info...
cat /etc/pmount.allow
# /etc/pmount.allow
# pmount will allow users to additionally mount all devices that are
# listed here.
/dev/scd0
/dev/scd1
/dev/scd2
/dev/dvd
/dev/dvd1
/dev/dvd2
/dev/cdrom
/dev/cdrom1
/dev/hda
/dev/hdb
/dev/hdc
/dev/cdrw
pmount -d hda
hda cannot be resolved to a proper device node
trying to prepend '/dev/' to device argument, now /dev/hda
mount point to be used: /media/hda
no iocharset given, current locale encoding is UTF-8
locale encoding uses UTF-8, setting iocharset to 'utf8'
Cleaning lock directory /var/lock/pmount_dev_hda
device_whitelist: checking /etc/pmount.allow...
comparing /dev/hda against whitelisted '/dev/scd0'
comparing /dev/hda against whitelisted '/dev/scd1'
comparing /dev/hda against whitelisted '/dev/scd2'
comparing /dev/hda against whitelisted '/dev/dvd'
comparing /dev/hda against whitelisted '/dev/dvd1'
comparing /dev/hda against whitelisted '/dev/dvd2'
comparing /dev/hda against whitelisted '/dev/cdrom'
comparing /dev/hda against whitelisted '/dev/cdrom1'
comparing /dev/hda against whitelisted '/dev/hda'
device_whitlisted(): match, returning 1
policy check passed
spawnv(): executing /sbin/cryptsetup '/sbin/cryptsetup' 'isLuks' '/dev/hda'
spawn(): /sbin/cryptsetup terminated with status 234
device is not LUKS encrypted, or cryptsetup with LUKS support is not installed
locking mount point directory
mount point directory locked
spawnv(): executing /bin/mount '/bin/mount' '-t' 'udf' '-o' 'nosuid,nodev,user,a
sync,atime,noexec,uid=500,gid=500,umask=000,iocharset=utf8' '/dev/hda' '/media/h
da'
spawn(): /bin/mount terminated with status 32
spawnv(): executing /bin/mount '/bin/mount' '-t' 'udf' '-o' 'nosuid,nodev,user,a
sync,atime,noexec,uid=500,gid=500,umask=000' '/dev/hda' '/media/hda'
spawn(): /bin/mount terminated with status 32
spawnv(): executing /bin/mount '/bin/mount' '-t' 'iso9660' '-o' 'nosuid,nodev,us
er,async,atime,noexec,uid=500,gid=500,iocharset=utf8' '/dev/hda' '/media/hda'
spawn(): /bin/mount terminated with status 0
unlocking mount point directory
mount point directory unlocked
--
Naja, Garbage Collector eben. Holt den Müll sogar vom Himmel.
(Heise Trollforum über Java in der Flugzeugsteuerung)
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
