Frugal coexist install in a directory

[brucehohl]

I completed a frugal coexist install in a directory (/mnt/home/puppy217) but was unable to get Puppy to boot properly unless the pup_217.sfs and zdrv_217.sfs files were in the root directory (/mnt/home). Thanks to anyone who can comment on how to change my install such that Puppy will use sfs files located within directory puppy217 (/mnt/home/puppy217). Or, perhaps someone can confirm that sfs files can only be located at /mnt/home.

Hard drive install coexist with existing Linux install:

(1)- Start Puppy Linux from CD without pup_save.2fs file:
"boot: puppy pfix=ram"

(2)- Frugal install (6 files total):
Mount Puppy CD and mount partition where Puppy will be installed.
Create directory for Puppy (example: puppy217).

Copy following files from Puppy CD as follows:
1 puppy217/initrd.gz
2 puppy217/vmlinuz
3 pup_217.sfs ##???##
4 zdrv_217.sfs ##???##

##???## = How to get Puppy to boot if these files are in directory puppy217 ?

Create install media empty file in puppy217 directory:
5 puppy217/idehd

User files are saved to this file during first shutdown.
6 puppy217/pup_save.2fs

(3)- Add entry in existing GRUB install (/boot/grub/menu.lst):
title Puppy Linux 301 frugal on hdc3
rootnoverify (hd0,2)
kernel /puppyXXX/vmlinuz root=/dev/ram0 pmedia=idehd psubdir=puppyXXX ## fixed ##
initrd /puppyXXX/initrd.gz
.

[trapster]

Code: Select all

psusdir=puppyXXX

Maybe it's just a typo, but it should read

Code: Select all

psubdir=puppyXXX

[brucehohl]

Yes, it was just a typo in my post. I did use "psubdir=puppyXXX" in the actual menu.lst file.

[Everitt]

Try:

Code: Select all

psubdir=puppy217

[brucehohl]

Well actually I did use "psubdir=puppy217". I meant the "XXX" in "psubdir=puppyXXX" to represent the version number. Well my post was not as clear as it should have been.

initrd.gz, vmlinuz, and pup_save.2fs can be included in a directory specified in the GRUB entry as noted above.

The question remains: With some other configuration can the sfs files be included in a directory? Thus, the entire install could be in a single directory.

[8-bit]

I have puppy301 and puppy4alpha as frugal installs on a partition that also contains firehydrant puppy as a full install.
All 4 files for each, plus the savepup file are in their respective directories.
All versions boot just fine and do not interfere with each other.
One thind I did notice from your menu.lst entry is that you show in your title puppy on hdc3.
But you set up root as (hd0,2).
Are we talking one hard drive here?
I thought hdc would signify booting from second drive.
So wouldn't root be set up as (hd1,2) for the second hard drive or
(hd2,2) for a third drive?
Also, this is a word of caution if you have a full install of another puppy on the same partition. Be SURE TO PUT psubdir=<your puppy directory> in your menu list.
I did not once and when I booted, puppy just went off and updated my full install.

[brucehohl]

8-bit thanks for that reply. This machine does actually have one hard drive but due to the layout of the system the single hard drive is plugged into the 2nd IDE port. Thus, the system sees the drive as hdc but the drive is hd0. Can you post your /boot/grub/menu.lst entries?

[8-bit]

This is my menu.lst for my 2 hard drive setup:
(Note: I have a swap partition on each drive)
# GRUB configuration file '/boot/grub/menu.lst'.
# generated by 'grubconfig'. Mon Sep 17 21:23:23 2007
#
# The backup copy of the MBR for drive '/dev/hda' is
# here '/boot/grub/mbr.hda.18362'. You can restore it like this.
# dd if=/boot/grub/mbr.hda.18362 of=/dev/hda bs=512 count=1
#
# Start GRUB global section
#timeout 30
color light-gray/blue black/light-gray
# End GRUB global section
# Linux bootable partition config begins
title Puppy Linux 2.17.1 (on /dev/hda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/hda1 ro vga=normal
# Linux bootable partition config ends
# Other bootable partition config begins
title Windows 98SE(on /dev/hda3)
map (hd0,0) (hd0,2)
map (hd0,2) (hd0,0)
rootnoverify (hd0,2)
makeactive
chainloader +1
# Other bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 3.01 (on /dev/hdd1)
root (hd1,0)
kernel /boot/vmlinuz root=/dev/hdd1 ro vga=normal
# Linux bootable partition config ends
# Linux bootable partition config begins
title Firehydrant pup (on /dev/hdd3)
root (hd1,2)
kernel /boot/vmlinuz root=/dev/hdd3 ro vga=normal
Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy 301 (on /dev/hdd3)
root (hd1,2)
kernel /pup301/vmlinuz root=/dev/ram0 PMEDIA=idehd psubdir=pup301
initrd /pup301/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy 4a(on /dev/hdd3)
root (hd1,2)
kernel /pup4a/vmlinuz root=/dev/ram0 PMEDIA=idehd psubdir=pup4a
initrd /pup4a/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 (hd1,0)
setup (fd0)
pause Press enter to continue.
title Install GRUB to Linux partition (on /dev/hdd1)
root (hd1,0)
setup (hd1,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)

[pupshock]

I ... was unable to get Puppy to boot properly unless the pup_217.sfs and zdrv_217.sfs files were in the root directory (/mnt/home). .

version 2.17 has that problem. See
http://www.murga-linux.com/puppy/viewtopic.php?t=21741

and
http://www.murga-linux.com/puppy/viewtopic.php?t=19967


Use version 3.01 instead