Re: [lfs-support] systemd-udev
On 08/25/2013 01:17 PM, Baho Utot wrote: On 08/25/2013 01:13 PM, Bruce Dubbs wrote: Baho Utot wrote: On 08/25/2013 12:17 PM, Bruce Dubbs wrote: Baho Utot wrote: On 08/25/2013 11:36 AM, Bruce Dubbs wrote: I have found that when there is not a cd/dvd in the drive there is no symlink /dev/cdrom so maybe eject then finds nothing to eject? After a cd/dvd/ is placed into the drive /dev/cdrom is there and eject works. What version of udev are you using? There is nothing that I know of that should remove the /dev/cdrom symlink. The symlink should be created when the system boots. Is this perhaps a usb cdrom? Do you have /dev/sr0? udev 204 This is on a Dell lapdog tye cd/dvd/ is internal Yes /dev/sr0 is there I should have a new system built with 206 sometime today as it is still building I really don't think there should be a difference for cdroms between udev 204 and 206. Try 'dmesg|grep -i cdrom' That should indicate whether the kernel found the device. When udev is started in the boot scripts, it should create a symlik from [ 1.471298] cdrom: Uniform CD-ROM driver Revision: 3.20 find / -name 60-cdrom_id.rules /lib/udev/rules.d/60-cdrom_id.rules 60-cdrom_id.rules: KERNEL==sr0, SYMLINK+=cdrom, OPTIONS+=link_priority=-100 Yes it is there Note that in /etc/udev/rules.d there are a couple of cdrom related rules. It should generate /etc/udev/rules.d/70-persistent-cd.rules. You might want to try to trace through that. -- Bruce I have /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/81-cdrom.rules /etc/udev/rules.d/83-cdrom-symlinks.rules One thing you might try is this. Change the bootscripts to not run udevd (or the retry). The system should come up fine, but some symlinks or permissions may be missing/wrong. The run from the command line as root: /lib/udev/udevd --debug |tee /run/udev-debug.log You should be able to get some info about how udev perceives the cdrom. -- Bruce Ok I will try that later after the current build finishes I have finished my build and I have checked it and found eject works like it is supposed to. The previous build was SVN-20130624 and the current build is SVN-20130822 The only things different are a few packages glibc, udev, boot scripts and kernel etc. The build was scripted and only packages differences between the two version was changed. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
On 08/24/2013 10:14 PM, Ken Moffat wrote:
On Sat, Aug 24, 2013 at 08:54:02PM -0400, Walter Webb wrote:
My latest computer has two dvd's; only one is a writer. I also have
a usb dvd writer that I occasionally use. Pre systemd udev generated
/etc/udev/rules.d/70-persistent-cd.rules for the devices on the first
boot. The first time I plugged in the usb device, entries were added
for that. I never understood why it worked, but it did.
For lfs-7.1, I eventually rebuilt it with pre systemd udev. I built
lfs-7.2 and some of blfs, but decided to make lfs-7.3 work.
After a lot of tries, I found that the old 70-persistent-cd.rules
worked after I replaced the ENV{ID_PATH} entries with ENV{ID_SERIAL}
entries. With lfs-7.4, I will attemt to generate the file properly.
That sounds odd - as if the usb writer appears ahead of, or
between, the non-usb drives. Do you plug it in before booting ? If
so, probably best not to do that (or make that change to ID_SERIAL
to allow you to do it). The appearance of drives connected via usb
is random and may change across kernel versions, or across different
kernel configs.
I had problems with my two ethernets. Since they use different
drivers, I eventually found that building one driver in the kernel
and the other as a module kept them in consistent order.
I discovered the file /etc/sysconfig/udev_retry and added sound to
it. This file must have appeared with sysstemd.
The latest problem I found a solution for was ejecting and closing
the dvd's. I didn't know it was a systemd problem until I found a
solution on the net for similar problems.
The file /lib/udev/rules.d/60-cdrom_id.rules has a line:
IMPORT{program}=cdrom_id --lock-media $devnode
Removing --lock-media from this line fixed it.
Thanks, I've got the same problem (on a built-in writer) with
7.4-rc1 except using eudev which now also has that same change.
With an earlier version of eudev (back in April) eject mostly
worked (failed once or twice over perhaps 30 uses). I've added
the need for a sed to fix this this on local builds to my ToDo
list. Seems to be a systemd problem, but I'm not surprised by that.
Does anyone else see eject failing to eject a CD/DVD with 7.3 or
later ? Eject is now part of util-linux so you don't need to
install anything extra to test this, just put a CD or DVD in
/dev/sr0.
ĸen
on the latest SVN if a cd/dvd is in the drive eject works.
If no cd/dvd is in the drive eject does nothing.
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
On Sat, Aug 24, 2013 at 10:50:55PM -0500, Bruce Dubbs wrote: Ken Moffat wrote: I haven't mounted any CDs or DVDs since I booted. My normal use of CDs is for ripping to flac, which is how I come to have used eject so much recently [ not yet ready to test flac, I need to build more packages and get to stuff that isn't in the book ]. I like k3b for that. Actually, I particularly meant cdparanoia and mediainfo (the commandline version). It lets me review the tags before I upload the flacs to my uPnP server (Twonky, on debian ppc). Seems, its a different problem for me, perhaps specific to eudev. I'll need to check the details against an older system - the /dev/cdrom and /dev/dvd symlinks exist, owned by root:root, but the underlying /dev/sr0 is correctly mode 660 but also owned by root:root. Looks as if the symlinks are supposed to be owned by root:cdrom, but I don't see how that could ever work and I need to boot to an older system to check that. sigh/ I have: lrwxrwxrwx 1 root root 3 Aug 23 07:06 cdrom - sr0 crw-rw 1 root cdrom21, 3 Aug 23 07:06 sg3 brw-rw 1 root cdrom11, 0 Aug 23 07:06 sr0 I've got my own rule. On previous builds sr0 was owned by the cdrom group. Will have to take a look at it in the future. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
On Sun, Aug 25, 2013 at 09:27:37AM -0400, Baho Utot wrote: On 08/24/2013 10:14 PM, Ken Moffat wrote: Does anyone else see eject failing to eject a CD/DVD with 7.3 or later ? Eject is now part of util-linux so you don't need to install anything extra to test this, just put a CD or DVD in /dev/sr0. on the latest SVN if a cd/dvd is in the drive eject works. If no cd/dvd is in the drive eject does nothing. Odd. As Bruce noted, it ought to let you open the drawer to load a CD. My problem turns out to be different, and I'm not sure about the OP's problem with eject. ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
On 08/25/2013 10:44 AM, Ken Moffat wrote: On Sun, Aug 25, 2013 at 09:27:37AM -0400, Baho Utot wrote: On 08/24/2013 10:14 PM, Ken Moffat wrote: Does anyone else see eject failing to eject a CD/DVD with 7.3 or later ? Eject is now part of util-linux so you don't need to install anything extra to test this, just put a CD or DVD in /dev/sr0. on the latest SVN if a cd/dvd is in the drive eject works. If no cd/dvd is in the drive eject does nothing. Odd. As Bruce noted, it ought to let you open the drawer to load a CD. My problem turns out to be different, and I'm not sure about the OP's problem with eject. ĸen I have found that when there is not a cd/dvd in the drive there is no symlink /dev/cdrom so maybe eject then finds nothing to eject? After a cd/dvd/ is placed into the drive /dev/cdrom is there and eject works. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
Baho Utot wrote: On 08/25/2013 10:44 AM, Ken Moffat wrote: On Sun, Aug 25, 2013 at 09:27:37AM -0400, Baho Utot wrote: On 08/24/2013 10:14 PM, Ken Moffat wrote: Does anyone else see eject failing to eject a CD/DVD with 7.3 or later ? Eject is now part of util-linux so you don't need to install anything extra to test this, just put a CD or DVD in /dev/sr0. on the latest SVN if a cd/dvd is in the drive eject works. If no cd/dvd is in the drive eject does nothing. Odd. As Bruce noted, it ought to let you open the drawer to load a CD. My problem turns out to be different, and I'm not sure about the OP's problem with eject. ĸen I have found that when there is not a cd/dvd in the drive there is no symlink /dev/cdrom so maybe eject then finds nothing to eject? After a cd/dvd/ is placed into the drive /dev/cdrom is there and eject works. What version of udev are you using? There is nothing that I know of that should remove the /dev/cdrom symlink. The symlink should be created when the system boots. Is this perhaps a usb cdrom? Do you have /dev/sr0? -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
On 08/25/2013 11:36 AM, Bruce Dubbs wrote: Baho Utot wrote: On 08/25/2013 10:44 AM, Ken Moffat wrote: On Sun, Aug 25, 2013 at 09:27:37AM -0400, Baho Utot wrote: On 08/24/2013 10:14 PM, Ken Moffat wrote: Does anyone else see eject failing to eject a CD/DVD with 7.3 or later ? Eject is now part of util-linux so you don't need to install anything extra to test this, just put a CD or DVD in /dev/sr0. on the latest SVN if a cd/dvd is in the drive eject works. If no cd/dvd is in the drive eject does nothing. Odd. As Bruce noted, it ought to let you open the drawer to load a CD. My problem turns out to be different, and I'm not sure about the OP's problem with eject. ĸen I have found that when there is not a cd/dvd in the drive there is no symlink /dev/cdrom so maybe eject then finds nothing to eject? After a cd/dvd/ is placed into the drive /dev/cdrom is there and eject works. What version of udev are you using? There is nothing that I know of that should remove the /dev/cdrom symlink. The symlink should be created when the system boots. Is this perhaps a usb cdrom? Do you have /dev/sr0? -- Bruce udev 204 This is on a Dell lapdog tye cd/dvd/ is internal Yes /dev/sr0 is there I should have a new system built with 206 sometime today as it is still building -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
Baho Utot wrote: On 08/25/2013 11:36 AM, Bruce Dubbs wrote: I have found that when there is not a cd/dvd in the drive there is no symlink /dev/cdrom so maybe eject then finds nothing to eject? After a cd/dvd/ is placed into the drive /dev/cdrom is there and eject works. What version of udev are you using? There is nothing that I know of that should remove the /dev/cdrom symlink. The symlink should be created when the system boots. Is this perhaps a usb cdrom? Do you have /dev/sr0? udev 204 This is on a Dell lapdog tye cd/dvd/ is internal Yes /dev/sr0 is there I should have a new system built with 206 sometime today as it is still building I really don't think there should be a difference for cdroms between udev 204 and 206. Try 'dmesg|grep -i cdrom' That should indicate whether the kernel found the device. When udev is started in the boot scripts, it should create a symlik from 60-cdrom_id.rules: KERNEL==sr0, SYMLINK+=cdrom, OPTIONS+=link_priority=-100 Note that in /etc/udev/rules.d there are a couple of cdrom related rules. It should generate /etc/udev/rules.d/70-persistent-cd.rules. You might want to try to trace through that. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
On 08/25/2013 12:17 PM, Bruce Dubbs wrote: Baho Utot wrote: On 08/25/2013 11:36 AM, Bruce Dubbs wrote: I have found that when there is not a cd/dvd in the drive there is no symlink /dev/cdrom so maybe eject then finds nothing to eject? After a cd/dvd/ is placed into the drive /dev/cdrom is there and eject works. What version of udev are you using? There is nothing that I know of that should remove the /dev/cdrom symlink. The symlink should be created when the system boots. Is this perhaps a usb cdrom? Do you have /dev/sr0? udev 204 This is on a Dell lapdog tye cd/dvd/ is internal Yes /dev/sr0 is there I should have a new system built with 206 sometime today as it is still building I really don't think there should be a difference for cdroms between udev 204 and 206. Try 'dmesg|grep -i cdrom' That should indicate whether the kernel found the device. When udev is started in the boot scripts, it should create a symlik from [ 1.471298] cdrom: Uniform CD-ROM driver Revision: 3.20 find / -name 60-cdrom_id.rules /lib/udev/rules.d/60-cdrom_id.rules 60-cdrom_id.rules: KERNEL==sr0, SYMLINK+=cdrom, OPTIONS+=link_priority=-100 Yes it is there Note that in /etc/udev/rules.d there are a couple of cdrom related rules. It should generate /etc/udev/rules.d/70-persistent-cd.rules. You might want to try to trace through that. -- Bruce I have /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/81-cdrom.rules /etc/udev/rules.d/83-cdrom-symlinks.rules -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
Baho Utot wrote: On 08/25/2013 12:17 PM, Bruce Dubbs wrote: Baho Utot wrote: On 08/25/2013 11:36 AM, Bruce Dubbs wrote: I have found that when there is not a cd/dvd in the drive there is no symlink /dev/cdrom so maybe eject then finds nothing to eject? After a cd/dvd/ is placed into the drive /dev/cdrom is there and eject works. What version of udev are you using? There is nothing that I know of that should remove the /dev/cdrom symlink. The symlink should be created when the system boots. Is this perhaps a usb cdrom? Do you have /dev/sr0? udev 204 This is on a Dell lapdog tye cd/dvd/ is internal Yes /dev/sr0 is there I should have a new system built with 206 sometime today as it is still building I really don't think there should be a difference for cdroms between udev 204 and 206. Try 'dmesg|grep -i cdrom' That should indicate whether the kernel found the device. When udev is started in the boot scripts, it should create a symlik from [ 1.471298] cdrom: Uniform CD-ROM driver Revision: 3.20 find / -name 60-cdrom_id.rules /lib/udev/rules.d/60-cdrom_id.rules 60-cdrom_id.rules: KERNEL==sr0, SYMLINK+=cdrom, OPTIONS+=link_priority=-100 Yes it is there Note that in /etc/udev/rules.d there are a couple of cdrom related rules. It should generate /etc/udev/rules.d/70-persistent-cd.rules. You might want to try to trace through that. -- Bruce I have /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/81-cdrom.rules /etc/udev/rules.d/83-cdrom-symlinks.rules One thing you might try is this. Change the bootscripts to not run udevd (or the retry). The system should come up fine, but some symlinks or permissions may be missing/wrong. The run from the command line as root: /lib/udev/udevd --debug |tee /run/udev-debug.log You should be able to get some info about how udev perceives the cdrom. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
On 08/25/2013 01:13 PM, Bruce Dubbs wrote: Baho Utot wrote: On 08/25/2013 12:17 PM, Bruce Dubbs wrote: Baho Utot wrote: On 08/25/2013 11:36 AM, Bruce Dubbs wrote: I have found that when there is not a cd/dvd in the drive there is no symlink /dev/cdrom so maybe eject then finds nothing to eject? After a cd/dvd/ is placed into the drive /dev/cdrom is there and eject works. What version of udev are you using? There is nothing that I know of that should remove the /dev/cdrom symlink. The symlink should be created when the system boots. Is this perhaps a usb cdrom? Do you have /dev/sr0? udev 204 This is on a Dell lapdog tye cd/dvd/ is internal Yes /dev/sr0 is there I should have a new system built with 206 sometime today as it is still building I really don't think there should be a difference for cdroms between udev 204 and 206. Try 'dmesg|grep -i cdrom' That should indicate whether the kernel found the device. When udev is started in the boot scripts, it should create a symlik from [ 1.471298] cdrom: Uniform CD-ROM driver Revision: 3.20 find / -name 60-cdrom_id.rules /lib/udev/rules.d/60-cdrom_id.rules 60-cdrom_id.rules: KERNEL==sr0, SYMLINK+=cdrom, OPTIONS+=link_priority=-100 Yes it is there Note that in /etc/udev/rules.d there are a couple of cdrom related rules. It should generate /etc/udev/rules.d/70-persistent-cd.rules. You might want to try to trace through that. -- Bruce I have /etc/udev/rules.d/70-persistent-net.rules /etc/udev/rules.d/81-cdrom.rules /etc/udev/rules.d/83-cdrom-symlinks.rules One thing you might try is this. Change the bootscripts to not run udevd (or the retry). The system should come up fine, but some symlinks or permissions may be missing/wrong. The run from the command line as root: /lib/udev/udevd --debug |tee /run/udev-debug.log You should be able to get some info about how udev perceives the cdrom. -- Bruce Ok I will try that later after the current build finishes -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
Ken Moffat wrote: On Sun, Aug 25, 2013 at 09:27:37AM -0400, Baho Utot wrote: On 08/24/2013 10:14 PM, Ken Moffat wrote: Does anyone else see eject failing to eject a CD/DVD with 7.3 or later ? Eject is now part of util-linux so you don't need to install anything extra to test this, just put a CD or DVD in /dev/sr0. on the latest SVN if a cd/dvd is in the drive eject works. If no cd/dvd is in the drive eject does nothing. Odd. As Bruce noted, it ought to let you open the drawer to load a CD. My problem turns out to be different, and I'm not sure about the OP's problem with eject. ĸen Before I removed the offending arg, I tested eject and eject -t on a freshly booted system with an empty tray. It worked every time. Then I put in a dvd. Regardless of whether or not I played the dvd, after I opened the tray, removed the dvd, and closed the tray; eject would no longer open the empty tray. The eject button on xine-ui would not work even with the dvd in the tray. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
Bruce Dubbs wrote: Baho Utot wrote: On 08/25/2013 10:44 AM, Ken Moffat wrote: On Sun, Aug 25, 2013 at 09:27:37AM -0400, Baho Utot wrote: On 08/24/2013 10:14 PM, Ken Moffat wrote: Does anyone else see eject failing to eject a CD/DVD with 7.3 or later ? Eject is now part of util-linux so you don't need to install anything extra to test this, just put a CD or DVD in /dev/sr0. on the latest SVN if a cd/dvd is in the drive eject works. If no cd/dvd is in the drive eject does nothing. Odd. As Bruce noted, it ought to let you open the drawer to load a CD. My problem turns out to be different, and I'm not sure about the OP's problem with eject. ĸen I have found that when there is not a cd/dvd in the drive there is no symlink /dev/cdrom so maybe eject then finds nothing to eject? After a cd/dvd/ is placed into the drive /dev/cdrom is there and eject works. What version of udev are you using? There is nothing that I know of that should remove the /dev/cdrom symlink. The symlink should be created when the system boots. Is this perhaps a usb cdrom? Do you have /dev/sr0? -- Bruce Before I got a working 70-persistent-cd.rules, ls -l | grep ' sr' showed something like this: lrwxrwxrwx 1 root root 3 Aug 25 16:16 cdrom - sr0 brw-rw 1 root cdrom 11, 0 Aug 25 16:16 sr0 brw-rw 1 root cdrom 11, 1 Aug 25 13:00 sr1 When I connected my usb drive, I got something like this: lrwxrwxrwx 1 root root 3 Aug 25 16:16 cdrom - sr2 brw-rw 1 root cdrom 11, 0 Aug 25 16:16 sr0 brw-rw 1 root cdrom 11, 1 Aug 25 13:00 sr1 brw-rw 1 root cdrom 11, 2 Aug 25 17:27 sr2 When I disconnected it, I got the original result. Disregard the time stamps. Apparently, having a 70-persistent-cd.rules that udev does not ignore, with an explicit cdrom link; holds cdrom still. -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
On Sat, Aug 24, 2013 at 08:54:02PM -0400, Walter Webb wrote:
My latest computer has two dvd's; only one is a writer. I also have
a usb dvd writer that I occasionally use. Pre systemd udev generated
/etc/udev/rules.d/70-persistent-cd.rules for the devices on the first
boot. The first time I plugged in the usb device, entries were added
for that. I never understood why it worked, but it did.
For lfs-7.1, I eventually rebuilt it with pre systemd udev. I built
lfs-7.2 and some of blfs, but decided to make lfs-7.3 work.
After a lot of tries, I found that the old 70-persistent-cd.rules
worked after I replaced the ENV{ID_PATH} entries with ENV{ID_SERIAL}
entries. With lfs-7.4, I will attemt to generate the file properly.
That sounds odd - as if the usb writer appears ahead of, or
between, the non-usb drives. Do you plug it in before booting ? If
so, probably best not to do that (or make that change to ID_SERIAL
to allow you to do it). The appearance of drives connected via usb
is random and may change across kernel versions, or across different
kernel configs.
I had problems with my two ethernets. Since they use different
drivers, I eventually found that building one driver in the kernel
and the other as a module kept them in consistent order.
I discovered the file /etc/sysconfig/udev_retry and added sound to
it. This file must have appeared with sysstemd.
The latest problem I found a solution for was ejecting and closing
the dvd's. I didn't know it was a systemd problem until I found a
solution on the net for similar problems.
The file /lib/udev/rules.d/60-cdrom_id.rules has a line:
IMPORT{program}=cdrom_id --lock-media $devnode
Removing --lock-media from this line fixed it.
Thanks, I've got the same problem (on a built-in writer) with
7.4-rc1 except using eudev which now also has that same change.
With an earlier version of eudev (back in April) eject mostly
worked (failed once or twice over perhaps 30 uses). I've added
the need for a sed to fix this this on local builds to my ToDo
list. Seems to be a systemd problem, but I'm not surprised by that.
Does anyone else see eject failing to eject a CD/DVD with 7.3 or
later ? Eject is now part of util-linux so you don't need to
install anything extra to test this, just put a CD or DVD in
/dev/sr0.
ĸen
--
das eine Mal als Tragödie, dieses Mal als Farce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
Ken Moffat wrote:
On Sat, Aug 24, 2013 at 08:54:02PM -0400, Walter Webb wrote:
The latest problem I found a solution for was ejecting and closing
the dvd's. I didn't know it was a systemd problem until I found a
solution on the net for similar problems.
The file /lib/udev/rules.d/60-cdrom_id.rules has a line:
IMPORT{program}=cdrom_id --lock-media $devnode
Removing --lock-media from this line fixed it.
Thanks, I've got the same problem (on a built-in writer) with
7.4-rc1 except using eudev which now also has that same change.
With an earlier version of eudev (back in April) eject mostly
worked (failed once or twice over perhaps 30 uses). I've added
the need for a sed to fix this this on local builds to my ToDo
list. Seems to be a systemd problem, but I'm not surprised by that.
Does anyone else see eject failing to eject a CD/DVD with 7.3 or
later ? Eject is now part of util-linux so you don't need to
install anything extra to test this, just put a CD or DVD in
/dev/sr0.
It doesn't seem to be an issue for me. I just ran eject from the
command prompt and it worked properly (no CD/DVD needed). Perhaps it
might be a problem after a mount/umount?
scsi 1:0:1:0: CD-ROM PLDS DVD+-RW DH-16A6S YD12 PQ: 0 ANSI: 5
sr0: scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw xa/form2 cdda tray
cdrom: Uniform CD-ROM driver Revision: 3.20
sr 1:0:1:0: Attached scsi CD-ROM sr0
sr 1:0:1:0: Attached scsi generic sg3 type 5
I rarely use a CD/DVD any more. USB thumb drives seem to be larger,
easier to use, and faster.
-- Bruce
--
http://linuxfromscratch.org/mailman/listinfo/lfs-support
FAQ: http://www.linuxfromscratch.org/lfs/faq.html
Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
On Sat, Aug 24, 2013 at 09:28:07PM -0500, Bruce Dubbs wrote: Ken Moffat wrote: It doesn't seem to be an issue for me. I just ran eject from the command prompt and it worked properly (no CD/DVD needed). Perhaps it might be a problem after a mount/umount? scsi 1:0:1:0: CD-ROM PLDS DVD+-RW DH-16A6S YD12 PQ: 0 ANSI: 5 sr0: scsi3-mmc drive: 48x/12x writer dvd-ram cd/rw xa/form2 cdda tray cdrom: Uniform CD-ROM driver Revision: 3.20 sr 1:0:1:0: Attached scsi CD-ROM sr0 sr 1:0:1:0: Attached scsi generic sg3 type 5 I rarely use a CD/DVD any more. USB thumb drives seem to be larger, easier to use, and faster. -- Bruce I haven't mounted any CDs or DVDs since I booted. My normal use of CDs is for ripping to flac, which is how I come to have used eject so much recently [ not yet ready to test flac, I need to build more packages and get to stuff that isn't in the book ]. And yes, it should work without a CD inserted. Guess I'm still tired. Seems, its a different problem for me, perhaps specific to eudev. I'll need to check the details against an older system - the /dev/cdrom and /dev/dvd symlinks exist, owned by root:root, but the underlying /dev/sr0 is correctly mode 660 but also owned by root:root. Looks as if the symlinks are supposed to be owned by root:cdrom, but I don't see how that could ever work and I need to boot to an older system to check that. sigh/ I guess I have to award your systemd-udev Makefile a point in this case :-) ĸen -- das eine Mal als Tragödie, dieses Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
Re: [lfs-support] systemd-udev
Ken Moffat wrote: I haven't mounted any CDs or DVDs since I booted. My normal use of CDs is for ripping to flac, which is how I come to have used eject so much recently [ not yet ready to test flac, I need to build more packages and get to stuff that isn't in the book ]. I like k3b for that. Seems, its a different problem for me, perhaps specific to eudev. I'll need to check the details against an older system - the /dev/cdrom and /dev/dvd symlinks exist, owned by root:root, but the underlying /dev/sr0 is correctly mode 660 but also owned by root:root. Looks as if the symlinks are supposed to be owned by root:cdrom, but I don't see how that could ever work and I need to boot to an older system to check that. sigh/ I have: lrwxrwxrwx 1 root root 3 Aug 23 07:06 cdrom - sr0 crw-rw 1 root cdrom21, 3 Aug 23 07:06 sg3 brw-rw 1 root cdrom11, 0 Aug 23 07:06 sr0 but no dvd. I see no reference to dvd in the udev rules. However the write_cd_rules script should create rules that make cdrw, dvd, or dvdrw under certain conditions. I think that buried in the hwdb now. I guess I have to award your systemd-udev Makefile a point in this case :-) LOL. -- Bruce -- http://linuxfromscratch.org/mailman/listinfo/lfs-support FAQ: http://www.linuxfromscratch.org/lfs/faq.html Unsubscribe: See the above information page
