On 11/17/05, James <[EMAIL PROTECTED]> wrote: > Richard Fish <bigfish <at> asmallpond.org> writes: > > > Does /dev/hdc exist? If so, what are the permissions there? What > > about /dev/cdrom? > Initially: > brw-rw---- 1 cdrom 22, 0 Nov 17 16:41 /dev/hdc > so I change it to 777 > brwxrwxrwx 1 cdrom 22, 0 Nov 17 16:41 /dev/hdc > but that did not fix it. > ls -alg /dev/cdrom > lrwxrwxrwx 1 root root 3 Nov 17 16:41 /dev/cdrom -> hdc
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. > > > 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. 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: KERNEL=="hdc", NAME="%k", GROUP="cdrom", ACTION=="add", SYMLINK+="_dvd%e", IMPORT="/sbin/cdrom_id --export $tempnode" > Hum, /var/log/messages does not exist. Lots of specific log files > are in /var/log > > 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... -Richard -- gentoo-user@gentoo.org mailing list
