RRFish72,

What Markus was suggesting was two possible ways to do the fix, one was to create a file, called fixdrives, and place the following in it:
Code:
#!/bin/sh
rm -rf /dev/cdrom /dev/cdrom1 /dev/dvd
ln -s /dev/scd0 /dev/cdrom
ln -s /dev/scd1 /dev/cdrom1
ln -s /dev/scd1 /dev/dvd
chmod 770 /dev/cdrom /dev/cdrom1 /dev/dvd
chgrp cdrom /dev/cdrom /dev/cdrom1 /dev/dvd
and then, do the following:
Code:
Place it in /etc/init.d and do a chmod 700 /etc/init.d/fixdrives , then do (including the dot at the end): update-rc.d fixdrives start 99 5 .

Although it might be easier to just add it to the end of /etc/init.d/bootmisc.sh , not the #!bin/sh line though
But, as Markus said in that last line, you could simply just add the following code:
Code:
rm -rf /dev/cdrom /dev/cdrom1 /dev/dvd
ln -s /dev/scd0 /dev/cdrom
ln -s /dev/scd1 /dev/cdrom1
ln -s /dev/scd1 /dev/dvd
chmod 770 /dev/cdrom /dev/cdrom1 /dev/dvd
chgrp cdrom /dev/cdrom /dev/cdrom1 /dev/dvd
within your bootmisc.sh file, at the bottom. If you wanted to create the file, then you would have put the line: #!/bin/sh at the top of that file, it tells Knoppix that the file is a script, you would have needed to change the file to executable, and then would have needed to place the file in the boot up init.d -=- but we opted to just put the commands in the /etc/init.d/bottmisc.sh file - so you don't need the #!/bin/sh now, nor do you need to do a change on the file we didn't use, or need to add it into the init.d

Since you ensured that your bootmisc.sh file isn't being recreated, nor is your fstab file, I think you can uncomment those lines in your bootmisc.sh file now, and try a reboot... First test you should do, upon completion of your reboot, is to test to see that your symlinks exist for your devices -=- within any Konsole, user or root, ls -la /dev/cdrom* /dev/dvd /dev/cdaudio

If all goes well, you should have symlinks for all the devices, your fstab file should remain intact, and the above devices should work... ( again )

Ms. Cuddles