Hi

i used the kernel from the cdrom. nearly everything worked perfect, and still does.
since i built the 2.6.7 kernel on my own there occur some things i dont understand

as user practically i cant listen to audio cds and kdeeject isnt found
as root i can eject cds but kdeeject cant be found

i use /dev/dvd which is a link on hdd, and /dev/cdrom which is a link on hdb
every time i restart my pc cdrom points on hdd too, although i created it pointing on hdb. whats this O_o ?
with the old kernel all four were used by the disk group
but now they are in the cdrom group, and if i change it to disk Konqueror still shows cdrom as group but the ls -la tells me disk is the group. whats that O_o ?

if i right click on my desktop cdrom icon and choose eject it says this:
Eject /dev/dvd failed!
Couldn't find the program 'kdeeject %v'

whats this O_o ?

do i need to add me as user to the cdrom group?
do i need to change sth in the kernel configuration?

thanks for explanation, suggestions and hints

Did you specify a path for users somewhere apart from the one Slackware sets when logging in ? That could be an explanation for the missing of /opt/kde/bin in your path.

If you're using a 2.6.7 kernel , Slackware 10 creates devices at boot using udev. If you want to change device links and permissions, you have to edit the config files of udev.

Adding normal users to the cdrom and audio group will result in usable cdrom and audio devices for that user.

Did you specify a path for users somewhere apart from the one Slackware sets when logging in ?
- no i didnt, and i can open everything else (i think) kwrite for instance
vi which is a link on vim doesnt work too, which makes me feel links and scripts (kdeeject is a script) dont work sometimes
although scripts in /sbin still wourk

thank you for the udev stuff that works, didnt notice before, seemes to be cool