Maxim Levitsky [2009-09-18 1:19 -0000]: > Here is the answer: > > > # probe filesystem metadata of disks > KERNEL!="sr*", IMPORT{program}="/sbin/blkid -o udev -p $tempnode" > > in 60-persistent-storage.rules
What's the problem here? CD-ROMs are probed in the rule right above:
KERNEL=="sr*", ENV{ID_CDROM_MEDIA}=="?*", IMPORT{program}="/sbin/blkid -o udev -p -u noraid -O $env{ID_CDROM_MEDIA_SESSION_LAST_OFFSET} $tempnode"
This is to avoid the "automatically closes after eject" effect.
I think devkit-disks is fine here, it sees the CD-ROM and has all the file system information.
However, as I said, I can reproduce the bug, so don't actually need more log files or program outputs.
-- Martin Pitt | http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)
Maxim Levitsky [2009-09-18 1:19 -0000]: program} ="/sbin/ blkid -o udev -p $tempnode" storage. rules
> Here is the answer:
>
>
> # probe filesystem metadata of disks
> KERNEL!="sr*", IMPORT{
>
> in 60-persistent-
What's the problem here? CD-ROMs are probed in the rule right above:
KERNEL=="sr*", ENV{ID_ CDROM_MEDIA} =="?*", IMPORT{ program} ="/sbin/ blkid -o udev -p -u noraid -O $env{ID_ CDROM_MEDIA_ SESSION_ LAST_OFFSET} $tempnode"
This is to avoid the "automatically closes after eject" effect.
I think devkit-disks is fine here, it sees the CD-ROM and has all the
file system information.
However, as I said, I can reproduce the bug, so don't actually need
more log files or program outputs.
-- www.piware. de
Martin Pitt | http://
Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org)