Thanks for the tips guys. Symlinking let me continue. There is no ./configure step to the iptables install, just make && make install. After this is done (no major errors) I generate the ISO files as before, but when I just add vmlinuz-2.4.26 at the prompt, I get "Could not find kernel image: vmlinuz-2.4.26" message.
I can look in my /mnt/sda1/source/boot dir and see the vmlinuz-2.4.6 image. At first I was thinking that I had been too aggressive in cutting unwanted things from the kernel. Then I realized that I am not getting that far, it's not even finding the image.
I half-heartedly tried the fromhd cheatcode a few times, thinking I could perhaps give it the right path. I tried:
Code Sample
dsl fromhd=/dev/sda1
and also tried a few variants, sd0, tried appending /boot/vmlinuz-2.4.26 to it. I have never used the fromhd cheatcode, perhaps that is intended to be pointed to an ISO image?
I need to back up a few steps and examine what is happening. Thanks again for the help, any further suggestions? If not for the help, I could be doing this for the rest of my life and still not be making progress ;^)fromhd is for the KNOPPIX image. See wiki, etc. for more information.
I haven't booted like what juanito suggested... I would've thought you'd have to change {sys|iso}linux to get that working... And if you use the default paths, I would've assume the kernels would have to be in the same dir. Did you also try editing grub instead?I was ready to edit menu.1st and see if that would be a better way, but sending it a cheatcode was an easy thing to try. I think I would have to set up a cheatcode for it. I saw that stuff go by somewhere, was it in isolinux.cfg ? I am upstairs away from the dev machine now, I will go look.
For curiosity, I am also looking through minirt24.gz like this:
Code Sample
gunzip -d minirt24.gz mkdir /mnt/test mount -o loop minirt24 /mnt/test
Juanito, I think I saw in one of your how-tos about mv/renaming the new image to /boot/vmlinuz. That sounds easier than changing grub for me. I have been a LILO kinduva guy for some time, and I am just cold on grub. At this point I am not too interested in trying to maintain multiple kernels to boot from, I just want to get the new one working and default to it. thx
Quote
Juanito, I think I saw in one of your how-tos about mv/renaming the new image to /boot/vmlinuz
Yes, but this was a USB boot - I copied the vmlinuz file to the root directory, left everything as-is and then entered vmlinuz at the boot prompt at the bottom of the DSL splash screen.
I don't know if you can do this from a hd install - you might have to edit lilo/grub to point to vmlinuz instead of minirt24.gzHi again un-master!
You make me remember when I was fooling around with gentoo a few years ago. I think you can solve your problem this way:
1. Rename the original kernel with mv (I used to append .old to the name) 2. Copy your new kernel to the same dir as the original. 3. Rename the new kernel so it has the name of the original with mv (if it doesn't already have that of course) 4. If everything works you can remove the old kernel with rm.
That's what I used to do when I compiled a new kernel using gentoo and I can't see why it shouldn't work with DSL.