Comment 9 for bug 10550

I noticed this too. When I ran "pmount -d /dev/hda", I got the following output:
  resolved /dev/hda to device /dev/hda
  device /dev/hda handled by fstab, calling mount

This results in the following permissions:
  $ ls -l /media/cdrom0
  total 6
  drwxr-xr-x 2 4294967295 4294967295 40 2004-10-06 08:14 AUDIO_TS
  drwx------ 2 4294967295 4294967295 2588 2004-10-07 06:22 VIDEO_TS

The number 4294967295 corresponds to -1 when interpreted as a signed 32-bit
value, so it isn't just a random value.

I looked in /etc/fstab, and sure enough there is an entry for the drive. After
commenting it out in fstab, I get the following output from pmount -d:
  resolved /dev/hda to device /dev/hda
  mount point to be used: /media/hda
  no iocharset given, current locale encoding is ISO-8859-1
  Cleaning lock directory /var/lock/pmount/_dev_hda
  find_sysfs_device: looking for sysfs directory for device 3:0
  find_sysfs_device: checking whether /dev/hda is on /sys/block/fd0 (2:0)
  find_sysfs_device: checking whether /dev/hda is on /sys/block/dm-5 (254:5)
  find_sysfs_device: checking whether /dev/hda is on /sys/block/dm-4 (254:4)
  find_sysfs_device: checking whether /dev/hda is on /sys/block/dm-3 (254:3)
  find_sysfs_device: checking whether /dev/hda is on /sys/block/dm-2 (254:2)
  find_sysfs_device: checking whether /dev/hda is on /sys/block/dm-1 (254:1)
  find_sysfs_device: checking whether /dev/hda is on /sys/block/dm-0 (254:0)
  find_sysfs_device: checking whether /dev/hda is on /sys/block/hda (3:0)
  find_sysfs_device: major device numbers matchfind_sysfs_device: minor device
numbers also match, /dev/hda is a raw device
  device_removable: corresponding block device for /dev/hda is /sys/block/hda
  get_blockdev_attr: value of /sys/block/hda/removable == 1
  policy check passed
  attempting mount: executing '/bin/mount -t udf -o
rw,nosuid,exec,nodev,user,sync,atime,uid=1000,gid=1000,umask=007 /dev/hda
/media/hda'
  mount attempt terminated with status 0

In this case, the disc is readable when mounted. However, totem then complained
that it couldn't find an entry for /dev/hda in the fstab ...