Bug#655924: udev: {dvd,cdrom,…} symlinks are not created

2014-02-04 Thread Marcel Partap
Package: udev Version: 204-6 Followup-For: Bug #655924 There is an easy fix for creating new /dev/dvd[0-9] symlinks, i.e. drop the 'by-path' method and use 'by-id' for all optical drive types in 75-cd-aliases- generator.rules: # These rules generate rules for the /dev/{cdrom,dvd,...} symlinks and

Bug#655924: udev: {dvd,cdrom,?} symlinks are not created

2013-10-26 Thread David Starner
Michael Biebl bi...@debian.org writes: Am 10.10.2013 21:40, schrieb Colomban Wendling: Really? I'm not finding each and every application that uses /dev/dvd as the default DVD device and convince their developers to use a new library. This is not realistic, and IMO not a sensible

Bug#655924: udev: {dvd,cdrom,?} symlinks are not created

2013-10-10 Thread Colomban Wendling
Hi, Ron Murray wrote: [...] but I created an entry for it using the ID_SERIAL variable (which was present) and, on reboot, all symlinks are created as expected. I have the very same problem, and could workaround it like this, by editing the persistent CD rules to use the ID_SERIAL

Bug#655924: udev: {dvd,cdrom,?} symlinks are not created

2013-10-10 Thread Michael Biebl
Am 10.10.2013 17:09, schrieb Colomban Wendling: I don't think it's sensible, because there still are many an application that use /dev/dvd as the default DVD device. First coming to mind is MPlayer. Of course you can tell it to use another device, but it won't detect the device

Bug#655924: udev: {dvd,cdrom,?} symlinks are not created

2013-10-10 Thread Michael Biebl
Am 10.10.2013 17:09, schrieb Colomban Wendling: Just FTR, all by-path entries seem to be gone, no more /dev/disks/by-path/ I talked to udev upstream about this. Apparently the kernel changed the sysfs layout for ATA devices, so support for ATA devices was disabled in path_id [1]. Kay didn't

Bug#655924: udev: {dvd,cdrom,?} symlinks are not created

2013-10-10 Thread Michael Biebl
Am 10.10.2013 17:09, schrieb Colomban Wendling: Hi, Ron Murray wrote: [...] but I created an entry for it using the ID_SERIAL variable (which was present) and, on reboot, all symlinks are created as expected. I have the very same problem, and could workaround it like this, by

Bug#655924: udev: {dvd,cdrom,?} symlinks are not created

2013-10-10 Thread Michael Biebl
Am 10.10.2013 19:08, schrieb Michael Biebl: Unfortunately this will not fix any existing /etc/udev/rules.d/70-persistent-cd.rules, and the result would most likely be that the symlinks are then named cdrw2, dvd2 etc. I don't see a good way to fixup existing entries in

Bug#655924: udev: {dvd,cdrom,?} symlinks are not created

2013-10-10 Thread Colomban Wendling
Le 10/10/2013 18:02, Michael Biebl a écrit : Am 10.10.2013 17:09, schrieb Colomban Wendling: I don't think it's sensible, because there still are many an application that use /dev/dvd as the default DVD device. First coming to mind is MPlayer. Of course you can tell it to use another device,

Bug#655924: udev: {dvd,cdrom,?} symlinks are not created

2013-10-10 Thread Colomban Wendling
Le 10/10/2013 19:08, Michael Biebl a écrit : Am 10.10.2013 17:09, schrieb Colomban Wendling: Hi, Ron Murray wrote: [...] but I created an entry for it using the ID_SERIAL variable (which was present) and, on reboot, all symlinks are created as expected. I have the very same problem,

Bug#655924: udev: {dvd,cdrom,?} symlinks are not created

2013-10-10 Thread Michael Biebl
Am 10.10.2013 21:47, schrieb Colomban Wendling: What about only nuking entries that won't work anymore, aka ID_PATH ATA How can you differentiate which entries don't work anymore which do? entries? Or maybe even better, find what ID_PATH entry matches the device and replace them (which

Bug#655924: udev: {dvd,cdrom,?} symlinks are not created

2013-10-10 Thread Colomban Wendling
Le 10/10/2013 22:08, Michael Biebl a écrit : Am 10.10.2013 21:47, schrieb Colomban Wendling: What about only nuking entries that won't work anymore, aka ID_PATH ATA How can you differentiate which entries don't work anymore which do? I don't know, any one that uses ID_PATH and for which this

Bug#655924: udev: {dvd,cdrom,?} symlinks are not created

2013-10-10 Thread Michael Biebl
Am 10.10.2013 21:40, schrieb Colomban Wendling: Le 10/10/2013 18:02, Michael Biebl a écrit : Am 10.10.2013 17:09, schrieb Colomban Wendling: I don't think it's sensible, because there still are many an application that use /dev/dvd as the default DVD device. First coming to mind is MPlayer.

Bug#655924: udev: {dvd,cdrom,?} symlinks are not created

2013-10-09 Thread Michael Biebl
Am 09.10.2013 03:09, schrieb Ron Murray: Package: udev Version: 204-5 Followup-For: Bug #655924 I have the same kind of problem. I have four Debian machines, and on three of them the only symlink created is /dev/cdrom (linked to sr0). The fourth machine (the one I'm submitting this on,

Bug#655924: udev: {dvd,cdrom,?} symlinks are not created

2013-10-08 Thread Ron Murray
Package: udev Version: 204-5 Followup-For: Bug #655924 -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 I have the same kind of problem. I have four Debian machines, and on three of them the only symlink created is /dev/cdrom (linked to sr0). The fourth machine (the one I'm submitting this on, and

Bug#655924: udev: {dvd,cdrom,…} symlinks are not created

2012-01-14 Thread Didier Raboud
Package: udev Version: 175-3 Severity: important Hi, as of today (but can't tell for how long), my cdrom reader doesn't get its /dev/{dvd,cdrom,…}# symlinks. The particularity of my cdrom reader is that its hotpluggable, hence /was/ getting different numbers at each plug (but that was