[systemd-devel] cdrom_id and 60-cdrom_id.rules behavior
rmilasan at suse.com
Mon Jan 12 00:39:30 PST 2015
Hello, a while back, around 2011, in cdrom_id was added --eject-media,
--lock-media and --unlock-media for not much explanation.
Now, recently some people noticed that this might actually be a
Here is a scenario:
1. add a CD/DVD into the driver
2. mount the driver: mount /dev/sr0 /mnt/my_cd (ensure you don't
use the Gnome/KDE auto-mounting or reproduce this in a server setup)
3. eject the media (using the hardware button) and add a new one media
4. ls /mnt/my_cd (it will be an empty output or the previous media)
Is this expected? Also, I remember a while back (long time ago) that
once you added a media into the driver and it was properly mounted, you
couldn't eject the media until you unmounted the media.
NOTE: This works somewhat OK in the desktop setup, probably due to
udisks (using Gnome/KDE), but in the console not really.
L3 Support Engineer
SUSE Linux (http://www.suse.com)
email: rmilasan at suse.com
GPG fingerprint: B6FE F4A8 0FA3 3040 3402 6FE7 2F64 167C 1909 6D1A
More information about the systemd-devel