/var/log/messages-20151116:Nov 9 09:21:35 localhost org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path provided! /var/log/messages-20151116:Nov 9 09:45:59 localhost org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path provided! /var/log/messages-20151116:Nov 9 10:00:16 localhost org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path provided! /var/log/messages-20151116:Nov 9 15:07:52 localhost org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path provided! /var/log/messages-20151116:Nov 9 18:37:10 localhost org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path provided! /var/log/messages-20151116:Nov 10 09:25:59 localhost org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path provided! /var/log/messages-20151116:Nov 10 11:44:02 localhost org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path provided! /var/log/messages-20151116:Nov 10 17:13:40 localhost org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path provided! /var/log/messages-20151116:Nov 11 08:50:12 localhost org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path provided! /var/log/messages-20151116:Nov 11 11:32:21 localhost org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path provided! /var/log/messages-20151116:Nov 11 08:50:12 localhost org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path provided! /var/log/messages-20151116:Nov 11 11:32:21 localhost org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path provided! /var/log/messages-20151207:Dec 3 19:57:34 localhost org.gtk.Private.UDisks2VolumeMonitor: bluray.c:1347: No device path provided!
However, since the update to latest kernel, these messages stopped.
But, /dev still has no device named blueray or br or br0. Ditto with dvd. I have had to manually create dvd link to sr0. Interestingly, cdrom is there.
since what user creates disappears at reboot, I have added the creation of /dev/dvd in rc.local.
So, what should the blueray device be called in /dev? bd? br? bdr?
On 12/11/2015 10:56 AM, jd1008 wrote:
But, /dev still has no device named blueray or br or br0. Ditto with dvd. I have had to manually create dvd link to sr0. Interestingly, cdrom is there.
since what user creates disappears at reboot, I have added the creation of /dev/dvd in rc.local.
So, what should the blueray device be called in /dev? bd? br? bdr?
Why do you believe Blu-ray devices should be named "bd*"?
Optical devices, within the past handful of years, have been labeled "sr0" by the kernel, and only symlinked to "cdrom" by a udev rule. This convention occurs regardless of optical type.
If you wish for additional symlinks you may create custom udev rules to do so, but I have no idea why the names would be that important to you.
On 12/11/2015 12:35 PM, Michael Cronenworth wrote:
On 12/11/2015 10:56 AM, jd1008 wrote:
But, /dev still has no device named blueray or br or br0. Ditto with dvd. I have had to manually create dvd link to sr0. Interestingly, cdrom is there.
since what user creates disappears at reboot, I have added the creation of /dev/dvd in rc.local.
So, what should the blueray device be called in /dev? bd? br? bdr?
Why do you believe Blu-ray devices should be named "bd*"?
Optical devices, within the past handful of years, have been labeled "sr0" by the kernel, and only symlinked to "cdrom" by a udev rule. This convention occurs regardless of optical type.
If you wish for additional symlinks you may create custom udev rules to do so, but I have no idea why the names would be that important to you.
If you saw the thread earlier, some multimedia players want to use url's like dvd:// .... to open that media.
If dvd is not in /dev, then that url will not work, because currently fedora does not provide it in the udev rules. Also, I recall someone saying that udev and it's rules will be removed sometime in the future.
You probably did not see such threads, but only popping up your comment as a kneejerk reaction.
-
JD -
Michael Cronenworth