Richard Fish <bigfish <at> asmallpond.org> writes:
> Rather than changing the permissions, a better plan is to add any > users that should be able to access cdrom/dvd devices to the cdrom > group. In /etc/group it has been like this for some time: cdrom::19:root,james video::27:root,james > > What does "/sbin/cdrom_id /dev/hdc" report? > > ID_CDROM=1 > > ID_CDROM_MRW=1 > > ID_CDROM_MRW_W=1 > > ID_CDROM_RAM=1 > Ok, this is why you have no /dev/dvd device. A DVD reader should also > report ID_CDROM_DVD=1, and a burner will report ID_CDROM_DVD_R=1. > The /sbin/cdrom_id program is a part of udev, and is used by udev to > determine what symlinks to create. So as I see it, you have two > choices: > 1. Try upgrading to a more recent version of udev. The current ~x86 > version is 073. Tried this first, (added ~x86 to packages.keywords and emerged udev) Did not work. This look reasonable so I'll stay on version 073 of udev for > 2. Write a custom rule for your device, and add it to > /etc/udev/rules.d/10-local.rules. Something like this should do the > trick: OK, this file does not exist, only: -rw-r--r-- 1 root root 54 Sep 14 10:38 30-svgalib.rules -rw-r--r-- 1 root root 11492 Nov 17 18:31 50-udev.rules so I created it: -rw-r--r-- 1 root root 120 Nov 17 18:47 10-local.rules > KERNEL=="hdc", NAME="%k", GROUP="cdrom", ACTION=="add", > SYMLINK+="_dvd%e", IMPORT="/sbin/cdrom_id --export $tempnode" Now: cat /etc/udev/rules.d/10-local.rules KERNEL=="hdc", NAME="%k", GROUP="cdrom", ACTION=="add", SYMLINK+="dvd%e", IMPORT="/sbin/cdrom_id --export $tempnode" > > Which startup script do I edit to start logging to /var/log/messages? > Actually, it depends upon what logger you have merged....I use > syslog-ng, configured so that my kernel and other logs go to > /var/log/messages. Your messages may go somewhere else... vixie-cron I can swith if you think it's necessary to debug this problem? James -- gentoo-user@gentoo.org mailing list
