I think I've lost more time to this cotton-pickin' "resmgr" than any other problem in Linux. Once again, with this new version (9.2), I have to sort out why programs like Grip and sound-juicer can't read from my SCSI CD-ROM. Now, mind you, Grip can read the CD, and lookup the info in the CDDB, but I can't actually, you know, READ IT for actually playing the CD or ripping from it. Explain that one to me. Apparently, I'm the only mortal on the planet who has an actual, real-life SCSI CD-ROM. Because this problem has existed ever since SuSE decided to start using this infernal "resmgr" software. I've once again hacked up /etc/resmgr.conf, restarted the daemon, and as root done both ``resmgr logout <user>'' and ``resmgr login <user> :0''. As my user, I can see: rws- /dev/cdrom rws- /dev/cdrom11 rw-p /dev/dvd rws- /dev/sr0 rws- /dev/sr1 Which shows that I *ought* to have read-write access to my SCSI CD-ROM, my SCSI CD-RW, my IDE DVD ($10 after rebate!), and the base SCSI devices pointed to by the /dev/cdrom and /dev/cdrom11 devices. I've even got this on the actual device: lrwxrwxrwx 1 root root 3 Nov 2 18:43 /dev/cdrom -> sr0 brw------- 1 david disk 11, 0 Oct 2 03:38 /dev/sr0 I'm at a loss. Again. Can anyone out there tell me how many chickens I'm going to have to sacrifice before resmgr lets me access my hardware? And just to head it off early, yeah, I can rip a CD from the IDE DVD, but this same problem is also preventing me from burning discs with K3B. Thanks, dk