USB booting :: How to reconfigure the minirt image
Quote
some text is shown twice, first in linuxrc and then during knoppix-autoconfig
I have not come across knoppix-autoconfig before. Given that the test I did with an empty linuxrc seems to show that this file is (at least partially) ineffectual, should I be looking to make some changes in the knoppix-autoconfig?You sure you edited the right file? Maybe your bootloader points to another initrd, because that file does count..knoppix-autoconfig is inside the DSL core, so it's harder to edit..Well, I have good news and bad news. I was making a monumental error with the minirt24 file I was editing (I was editing the minirt24.gz from the /boot in the DSL partition on the external HDD whereas -- because I can't boot directly from the external drive -- the kernel and initrd.img equivalent are called from the internal HDD). Anyway that explains a lot -- particularly why the sleep command wasn't working and why booting went ahead even when linuxrc was an empty file. OK, so having made this prodigious breakthrough I inserted a 10 second sleep into linuxrc and rebooted to DSL. Yes, the delay certainly occurred this time and the external drive was totally ready to go -- but then the very same error message re-appeared about not finding the KNOPPIX image. But then I saw this comment in the linuxrc
Quote
# Harddisk-installed script part version has been removed # (KNOPPIX can be booted directly from HD now).
Does this indicate that only a CDROM image is being looked for and not anything on a hard disk? Certainly, it looks at a whole list of devices (I think it's 45) but if it's only looking for something on a CDROM, this could be why it can't find anything on my external drive. Perhaps I need to use a different minirt24 or hack the one I have to make it look for a HD image. Given how easy it is to boot from the external drive, this might not be too difficult. Any thoughts?OK, I managed to apply the appropriate hacks to the linuxrc file so that it boots without stopping. This essentially involved inserting the command "exit" immediately after the TTY1 call (shell) as well as a few cosmetic changes to take out unnecessary stuff. BTW, although the sleep command certinly works, I did not after all have to use it. Thanks for all your help PaulNext Page...
original here.