Create a symlink from /dev/dvd to /dev/sr2

[Cuddles]

As a matter of information, RRFish72, with the new Knoppix v3.4, the installer has more options, than just the "usual" Debian Style...

Beginner and Knoppix Style installs, are "basically" the same as the "Debian Style", except that they still do the "autoconfiguration" that the Live CD does, each time you boot... Whereas, the "Debian Style" install, does an "autoconfiguration" once, during the install, and then leaves everything alone after that...

The reason why it "makes a differance" which install you used, is for the exact same reason you don't have everything you had setup before your reboot, and after the reboot, everything seems to have been "re-done" again, and this now explains why when I first started to work with you on this whole thing, why everything was so "weird" compared to what I have. With the Beginner and Knoppix Style installs, you are still doing an autoconfiguration of your devices every time you reboot. Some things are "sticking" after you reboot, but, some things are not, like the etc/fstab file entries, and your symlinks for your devices.

Even with the Debian Style install, which I have, you still can have "some things" replace on a reboot, but, in my case, the fstab file and my symlinks, do not get overwritten every time I reboot...

Thats all,
Ms. Cuddles
PS -=- I knew the new installer options were gonna come-round and bite us in the rear, having more options, especially ones that are not explained what they do, or how they work, can end up to cause situations like this...

[Markus]

Oh well, installing Knoppix style does explain this mess as Cuddles noted. Let's see if we can find a solution other than reinstalling debian style.
The first thing to do is add nofstab to the "append" line in /etc/lilo.conf and after saving the file make sure to run lilo as root by typing lilo -v or /sbin/lilo -v . It should say something like Added Linux, Added Windows. This will keep you fstab intact after a reboot.
Now is the time to recreate the symlinks and check that /dev/cdrom, /dev/cdrom1, /dev/dvd, /cdrom, /cdrom1 and /dvd still exist, and tell us what exists and what doesn't.
Not sure about the autoconfig script as I haven't even seen the new knoppix version let alone done a knoppix style install. If you want to take a shot at it, it's at /etc/init.d/knoppix-autoconfig. While looking at the version in Kanotix BH5 I would start at commenting out with a # the following:
AUTOMOUNTS="floppy cdrom"
# Add new devices to /etc/fstab and /etc/auto.mnt
for i in /dev/cdrom?*; do
if [ -L $i ]; then
addautomount "$i" "ro"
fi
done
NB: You should know how to restore it if you're going to edit knoppix-autoconfig.

You could perhaps try a short script and have it start with a high Snumber like 99.
Say you created a script called fixdrives with the following content:

#!/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

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

PS: This is probably also the reason why you're ZIPdrive isn't working. We had it working and lost it probably after a reboot.
I wish people would install debian style unless they need autodetection

PS -=- I knew the new installer options were gonna come-round and bite us in the rear, having more options, especially ones that are not explained what they do, or how they work, can end up to cause situations like this...

Well said!

[rrfish72]

Got the nofstab in lilo and ran lilo -v. Don't know how to restore the file. Just know how to comment things out and uncommment them. Will that work. Want to know before I change things. Should I just go ahead and add this to init.d/bootmisc.sh?

[Cuddles]

RRFish72,

Maybe you can post what your /etc/fstab file looks like now, with that nofstab entry in LILO, that should allow changes to "stick" now...

The bootmisc.sh script file sounds good, place it down at the bottom, and put a few comments with it, so later, when this all fades away, you will know why, and what it is doing...

For the time being, put the lines at the bottom of the bootmisc.sh file, and comment them out, until we can figure out how bad the fstab file is... ( also, you might try to change the /etc/fstab file and the bootmisc.sh file, like add a comment at the bottom of them, save them, and then reboot - just to check that the files aren't being "re-created" after you reboot, like the fstab file was doing )

Ms. Cuddles

[rrfish72]

Here is the fstab:

# /etc/fstab: filesystem table.
#
# filesystem mountpoint type options dump pass
/dev/hda3 / ext3 defaults,errors=remount-ro 0 1

proc /proc proc defaults 0 0
/dev/fd0 /floppy vfat defaults,users,showexec,umask=022 0 0
usbdevfs /proc/bus/usb usbdevfs defaults 0 0
sysfs /sys sysfs defaults 0 0

/dev/sda4 /mnt/zip vfat defaults,noauto,users,noatime,umask=000 0 0
/dev/cdrom /cdrom iso9660 defaults,ro,users,noexec,noauto,uid=knoppix,gid=kn oppix 0 0
/dev/cdrom1 /cdrom1 iso9660 defaults,ro,users,noexec,noauto,uid=knoppix,gid=kn oppix 0 0
/dev/dvd /dvd iso9660 defaults,ro,users,noexec,noauto,uid=knoppix,gid=kn oppix 0 0
/dev/cdaudio /cdaudio iso9660 defaults,ro,users,noexec,noauto 0 0
#/dev/cdrom1 /mnt/auto/cdrom1 auto users,noauto,exec,ro 0 0
# Added by KNOPPIX - took out noauto after ntfs and added auto after exec and ro after exec
/dev/hda1 /mnt/hda1 ntfs users,exec,auto,umask=000,uid=knoppix,gid=knoppix 0 0
# Added by KNOPPIX
/dev/hda5 none swap defaults 0 0


This is what was added before to help my zip drive work properly and it looks like things are not being changed back to the originl or recreated again. These are just a few lines at the end:

if [ "$EDITMOTD" != no ]
then
uname -a > /etc/motd.tmp
sed 1d /etc/motd >> /etc/motd.tmp
mv /etc/motd.tmp /etc/motd
fi

#
# Save kernel messages in /var/log/dmesg
#
dmesg > /var/log/dmesg
#This was added by rrfish72
modprobe imm
insmod usb-storage

But I added this to it anyway and will try the chmod 700 /etc/init.d/fixdrives and update-rc.d fixdrives start 99 5 . after a reply back to see if this is what should be done.

#Added for a test
#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

Uncomment out, run ( chmod 700 /etc/init.d/fixdrives and update-rc.d fixdrives start 99 5 .) . Is that correct?

What is this line for?: #!/bin/sh Is that # supposed to be the 99 thing Markus was talking about?

All of my icons stay to what I set them at through code: 'chmod 0 /usr/bin/mkdesktophdicons'

[Cuddles]

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:

#!/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:

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:

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

[rrfish72]

Something is happening to that to not get it to stick. The changes made to the dvd drive stuck. Now if I ln -sf /dev/scd0 /dev/cdrom then the drive plays all discs. But that has to be done everytime I want to use the drive after a bootup. This is the output:

root@0[knoppix]# ls -la /dev/cdrom* /dev/dvd /dev/cdaudio
ls: /dev/cdrom*: No such file or directory
lrwxrwxrwx 1 root root 3 Sep 1 21:07 /dev/cdaudio -> sr1
lrwxrwxrwx 1 root cdrom 9 Sep 5 06:59 /dev/dvd -> /dev/scd1

root@0[knoppix]# ls -la /dev/sr*
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr1 -> scd1
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr10 -> scd10
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr11 -> scd11
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr12 -> scd12
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr13 -> scd13
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr14 -> scd14
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr15 -> scd15
lrwxrwxrwx 1 root root 5 Aug 6 02:05 /dev/sr16 -> scd16
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr2 -> scd2
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr3 -> scd3
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr4 -> scd4
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr5 -> scd5
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr6 -> scd6
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr7 -> scd7
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr8 -> scd8
lrwxrwxrwx 1 root root 4 Aug 6 02:05 /dev/sr9 -> scd9

root@0[knoppix]# ln -sf /dev/scd0 /dev/cdrom
root@0[knoppix]# ls -la /dev/cdrom
lrwxrwxrwx 1 root root 9 Sep 10 08:54 /dev/cdrom -> /dev/scd0

Now the drive works. How to get the changes to stay in place in the question now?

[Markus]

Let's try a different approach and hope that knoppix doesn't notice it, if /dev/cdrom is being recreated all the time, try naming it /dev/cddrive instead.
Comment out this line in fstab: /dev/cdrom /cdrom iso9660 defaults,ro,users,noexec,noauto,uid=knoppix,gid=kn oppix 0 0
Add this line to it: /dev/cddrive /cdrom iso9660 defaults,ro,users,noexec,noauto,uid=knoppix,gid=kn oppix 0 0

Then do:
ln -s /dev/scd0 /dev/cddrive
chgrp cdrom /dev/cddrive

Now, hopefully you'll have the symlink intact after a reboot, check with:
ll /dev/cddrive

[rrfish72]

Hate to tell you this but I just reinstalled debian style and did alitte work and now everything works. I just couldn't wait any longer. Thanks for all the help you gave.

[Markus]

No need to feel sorry about that, wise decision IMHO.