WORKAROUND (found on http://chakra-project.org/bbs/viewtopic.php?id=7513 , to give credit where its due):
There is a UDEV rule that prevents "eject -i" from working. The following method helps it to get working again, but I have *no* real idea why.
1. open "/lib/udev/rules.d/60-cdrom_id.rules" for editing
2. comment out (using the "#" symbol) the following line:
ENV{DISK_EJECT_REQUEST}=="?*", RUN+="cdrom_id --eject-media $tempnode", GOTO="cdrom_end"
3. If you don't feel like rebooting, reload the UDEV rules with
sudo udevadm control --reload-rules
Now locking with "eject -i 1" or "eject -i on" should work. I can confirm this to be the case on my Thinkpad w510.
WORKAROUND (found on http:// chakra- project. org/bbs/ viewtopic. php?id= 7513 , to give credit where its due):
There is a UDEV rule that prevents "eject -i" from working. The following method helps it to get working again, but I have *no* real idea why.
1. open "/lib/udev/ rules.d/ 60-cdrom_ id.rules" for editing
2. comment out (using the "#" symbol) the following line:
3. If you don't feel like rebooting, reload the UDEV rules with
sudo udevadm control --reload-rules
Now locking with "eject -i 1" or "eject -i on" should work. I can confirm this to be the case on my Thinkpad w510.