-Jason
Code: Select all
# Start GRUB global section
# Boot automatically after 5 secs.
timeout 5
# By default, boot the second entry.
default 1
# Fallback to the first entry.
fallback 0
color light-gray/blue black/light-gray
# End GRUB global section
# Linux bootable partition config begins
title Puppy Linux 201 full (on /dev/hda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hda1 ro vga=normal
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 202 Frugal (on /dev/hda2)
root (hd0,1)
kernel /boot/vmlinuz root=/dev/ram0 PMEDIA=idehd
initrd /boot/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 203CE Frugal (on /dev/hda1)
root (hd0,0)
kernel /boot203/vmlinuz root=/dev/ram0 PMEDIA=idehd
initrd /boot203/initrd.gz
# Linux bootable partition config ends
title Install GRUB to floppy disk (on /dev/fd0)
pause Insert a formatted floppy disk and press enter.
root (hd0,0)
setup (fd0)
pause Press enter to continue.
title Install GRUB to Linux partition (on /dev/hda1)
root (hd0,0)
setup (hd0,0)
pause Press enter to continue.
title - For help press 'c', then type: 'help'
root (hd0)
title - For usage examples, type: 'cat /boot/grub/usage.txt'
root (hd0)
I have done some more poking around on this and I decided to change the name of the 203CE files from pup_202.sfs to pup202.bak and pup_save.3fs to pupsave.bak. Behold 202 can now boot again. This tells me that the problem has nothing to do with the menu.lst file. My question is why does Puppy install from a sfs file on a different partition. I had assumed incorrectly that if vmlinuz was at /dev/hda2/boot then it would boot the pup_202.sfs file at /dev/hda2 rather than the one at /dev/hda1. Since I am sure that I am not the first person to use Grub to boot multiple frugal installs could someone tell me the trick to keeping vmlinuz from initializing the wrong sfs file?
thanks,
-Jason