On Thu, 2008-08-07 at 08:21 +, Aaron Whitehouse wrote:
On your system, have you a /dev/dvdrw1 for example?
Yes. Couldn't the (or one of the) dvd drives be set as /dev/dvd as
well, for all of the programs that use it?
We don't ordinarily reuse symlinks, once a drive has been /dev/dvd
On your system, have you a /dev/dvdrw1 for example?
Yes. Couldn't the (or one of the) dvd drives be set as /dev/dvd as
well, for all of the programs that use it?
--
[hardy] [udev] Failure to create symlinks /dev/dvd. /dev/dvdrw. /dev/cdrw etc.
https://bugs.launchpad.net/bugs/211993
You
They aren't dropped, they are maintained in a persistent fashion by a
different set of rules.
This means that the same link will always point to the same device.
On your system, have you a /dev/dvdrw1 for example?
--
[hardy] [udev] Failure to create symlinks /dev/dvd. /dev/dvdrw. /dev/cdrw
Scott,
Can you please tell me why these symlinks were dropped? This breaks a
default mythbuntu install and I would like to know whether to file a bug
against mythbuntu (detect and remap dvd to the relevant drive) or a udev
bug to fix all apps that point to /dev/dvd.
--
[hardy] [udev] Failure to
Apparently cd and dvd drives are now treated like network interfaces:
they have their own 75-persistent* udev rule. So the best thing to do
is just remove all entries on /etc/udev/rules.d/70-persistent-cd.rules
and reboot. This should fix all the links.
--
[hardy] [udev] Failure to create
We deliberately dropped these in gutsy (udev 111-0ubuntu1)
** Changed in: udev (Ubuntu)
Status: New = Invalid
--
[hardy] [udev] Failure to create symlinks /dev/dvd. /dev/dvdrw. /dev/cdrw etc.
https://bugs.launchpad.net/bugs/211993
You received this bug notification because you are a
Attached: Output of diff between 60-symlinks.rules in /etc/udev/rules.d
on a 7.04 and the hardy install.
** Attachment added: diff.feisty.hardy-60-symlinks.rules
http://launchpadlibrarian.net/13125388/diff.feisty.hardy-60-symlinks.rules
--
[hardy] [udev] Failure to create symlinks /dev/dvd.
Confirming that the above diff when applied in hardy fixes the issue:
Insert
# Create /dev/cdrom* symlinks for CD-ROM devices
ENV{ID_CDROM}==?*,SYMLINK+=cdrom
ENV{ID_CDROM_CD_RW}==?*, SYMLINK+=cdrw
ENV{ID_CDROM_DVD}==?*,SYMLINK+=dvd
Attached: Output of sudo lshw
** Description changed:
Binary package hint: udev
Hardy fails to create symlinks for /dev/dvd, /dev/cdrw. /dev/dvdrw
These should exist and point, for example, at /dev/scd1 or whatever the
device is in a particular case.
The result is that apps
