Joined: April 2007
||Posted: May 03 2007,23:16
Thanks for the tip. That makes perfect sense in a normal full Linux install. I seem to be too slow however, to recognize the darn default kernel in DSL! Booting a DSL CD with toram cheatcode should put the whole filesystem in RAM, and I can't find a vmlinuz* in there anywhere.
Looking back on my dev environment at /boot/grub/menu.1st there is no reference to vmlinuz either. The default 0 entry starts with:
then has some cheatcode parameters, and then ends with:
|Code Sample |
|kernel /boot/linux24 root=/dev/hda2|
|Code Sample |
I see the linux24 file in /boot but if I just point the default entry to /boot/vmlinuz-2.4.26 I wonder what I will be losing by not using linux24? Easy enough to try it, I suppose.
Also, I have a vmlinuz file that is symlinked to the vmlinuz-2.4.26 image, and they have the same timestamps (I noticed this upon kernel compile). I will try pointing the grub menu just to /boot/vmlinuz
EDIT: OK, after more searching, I see that linux24 is the actual kernel image. I changed the menu.1st to /boot/vmlinuz but it still fails. For reference, it goes through:
The initial screen where you can enter cheatcodes, then:
Scanning for USB devices... Done
Accessing DSL image at /dev/scd0...
Total memory found: 386692 kB
Creating /ramdisk (dynamic size=302168k) on shared memory... Done.
Creating directories and symlinks on ramdisk...Done.
Starting init process.
INIT: version 2.78-knoppix booting
And there it stops.