Puppy Linux Discussion Forum Forum Index Puppy Linux Discussion Forum
Puppy HOME page : puppylinux.com
"THE" alternative forum : puppylinux.info
 
 FAQFAQ   SearchSearch   MemberlistMemberlist   UsergroupsUsergroups   RegisterRegister 
 ProfileProfile   Log in to check your private messagesLog in to check your private messages   Log inLog in 

The time now is Tue 29 Jul 2014, 00:47
All times are UTC - 4
 Forum index » House Training » Users ( For the regulars )
How to tell grub which pupsave file to use? (SOLVED)
Moderators: Flash, Ian, JohnMurga
Post new topic   Reply to topic View previous topic :: View next topic
Page 1 of 2 [28 Posts]   Goto page: 1, 2 Next
Author Message
sullysat


Joined: 16 Oct 2007
Posts: 364
Location: San Antonio, TX

PostPosted: Mon 31 Aug 2009, 19:46    Post subject:  How to tell grub which pupsave file to use? (SOLVED)  

I've got several puplets loaded on a single partition and every time I load any of them, I have to tell the system which pup_save file to use.

Is there a way to set all that up in grub so that it just loads without the interruption? I searched the forum for 'grub' and 'edit grub' but didn't find anything and I can't be the only person with this question.

Thanks in advance!
Sully

Last edited by sullysat on Sat 05 Sep 2009, 01:59; edited 1 time in total
Back to top
View user's profile Send private message 
ICPUG

Joined: 24 Jul 2005
Posts: 1289
Location: UK

PostPosted: Wed 02 Sep 2009, 08:26    Post subject:  

I presume you have installed your puplets frugally. If you stick each puplet in a separate directory along with its associated pupsave file then all you have to do is specify the subdirectory in the menu.lst file with psubdir. Here is an example with Puppy 4.2.1 stored in the directory puppy421:

title Puppy Linux 4.2.1
kernel (hd0,0)/puppy421/vmlinuz PMEDIA=idehd PDEV1=sda1 psubdir=puppy421 psubOK=TRUE
initrd (hd0,0)/puppy421/initrd.gz
boot

The PMEDIA, PDEV1, psubOK are optional and relevant to my system. psubOK is only valid on Puppy 4.2.1 derivatives.

This method should work with any puplet based on series 3 or later. It will not work with Series 2 based puplets which usually cannot be stored in a directory.

One final point to note is that the diectory can only be at a depth of 1. That is, a directory such as /puppy/lighthouse is NOT allowed.
Back to top
View user's profile Send private message 
Ray MK


Joined: 05 Feb 2008
Posts: 760
Location: UK

PostPosted: Wed 02 Sep 2009, 08:50    Post subject:  

Hi

Here is an example of a multiboot menu.lst

# Start GRUB global section
# hiddenmenu
#timeout 30
timeout 10
default 3 (412ch)
color light-gray/blue black/light-gray
# End GRUB global section



title Tiny Core Linux
root (hd0,0)
kernel /boot/bzImage quiet
initrd /boot/tinycore.gz



# Linux bootable partition config begins
title 430 2ram (on /dev/hda1)
root (hd0,0)
kernel /430/vmlinuz psubdir=430
initrd /430/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title 481 2ram (on /dev/hda1)
root (hd0,0)
kernel /481/vmlinuz psubdir=481
initrd /481/initrd.gz
# Linux bootable partition config ends



# Linux bootable partition config begins
title 412CH 2ram (on /dev/hda1)
root (hd0,0)
kernel /z412CH/vmlinuz psubdir=z412CH
initrd /z412CH/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title 412Brz 2ram (on /dev/hda1)
root (hd0,0)
kernel /z412Brz/vmlinuz psubdir=z412Brz
initrd /z412Brz/initrd.gz
# Linux bootable partition config ends


# Linux bootable partition config begins
title 413box 2ram (on /dev/hda1)
root (hd0,0)
kernel /z413box/vmlinuz psubdir=z413box
initrd /z413box/initrd.gz
# Linux bootable partition config ends





# Linux bootable partition config begins
title 215ce full hdd (on /dev/hda5)
root (hd0,4)
kernel /boot/vmlinuz root=/dev/hda5
# Linux bootable partition config ends
# Linux bootable partition config begins
title 216ce full hdd (on /dev/hda2)
root (hd0,1)
kernel /boot/vmlinuz root=/dev/hda2
# Linux bootable partition config ends






# Linux bootable partition config begins
# title NewPup frugal (on /dev/hda1)
# root (hd0,0)
# kernel /zNewPup/vmlinuz psubdir=zNewPup acpi=force pfix=ram
# initrd /zNewPup/initrd.gz
# Linux bootable partition config ends

# Linux bootable partition config begins
# title MinPup - frugal (on /dev/hda1)
# root (hd0,0)
# kernel /zMinPup/vmlinuz root=/dev/ram0 PMEDIA=idehd pdev1=hda1 ro vga=normal acpi=force
# initrd /zMinPup/initrd.gz
# Linux bootable partition config ends


Hope that helps - regards - Ray
Back to top
View user's profile Send private message 
sullysat


Joined: 16 Oct 2007
Posts: 364
Location: San Antonio, TX

PostPosted: Wed 02 Sep 2009, 09:22    Post subject:  

Thanks guys, but let me clarify...

I am running 4 frugal installs and they are all set up properly as you've outlined and boot from their subdirectory.

What I'm really wondering is if there is a way to also identify the pup_save file rather than having to select it manually during the boot process. After looking at your grub files, I'm assuming the answer is no. Sad

@ICPUG

I understand the other commands, but what does "psubOK" do?

Thanks,
Sully
Back to top
View user's profile Send private message 
8-bit


Joined: 03 Apr 2007
Posts: 3357
Location: Oregon

PostPosted: Wed 02 Sep 2009, 09:50    Post subject:  

What the others were getting at is that you should move or copy the corresponding pupsave files to their corresponding subdirectories.
When Puppy looks for a pupsave file and you have psubdir=[name of puppy subdirectory] set up in menu.lst, Puppy will find your pupsave file there and ignore the others.
Back to top
View user's profile Send private message 
sullysat


Joined: 16 Oct 2007
Posts: 364
Location: San Antonio, TX

PostPosted: Wed 02 Sep 2009, 10:30    Post subject:  

@8-bit

Okay, that makes sense, but the save files ARE in their respective subdirectories and grub is still asking me to choose.

Maybe I'm approaching it from the wrong direction. If the puplet should load the save file in it's own subdirectory, maybe the right question is what would cause it to ask instead of defaulting to the save file in the directory.

Thoughts?

Sully
Back to top
View user's profile Send private message 
trapster


Joined: 28 Nov 2005
Posts: 1999
Location: Maine, USA

PostPosted: Wed 02 Sep 2009, 12:27    Post subject:  

I don't think anything earlier than puppy4 will work with psubdir=.
At least mine don't (1.09. 2.16, 3.0)

_________________
trapster
Maine, USA

Asus eeepc 1005HA PU1X-BK
Frugal install: Puppeee4.31 + 1.0, Puppy4.10 + Lupu52
Currently using Slacko AND lupu52 w/ fluxbox
Back to top
View user's profile Send private message Visit poster's website 
disciple

Joined: 20 May 2006
Posts: 6426
Location: Auckland, New Zealand

PostPosted: Wed 02 Sep 2009, 17:10    Post subject:  

psubdir also seems to be about completely separate installs, which make sense more for running several versions. It would be nice to specify just the save file, particularly for running several save files with the same version.
_________________
DEATH TO SPREADSHEETS
- - -
Classic Puppy quotes
- - -
Beware the demented serfers!
Back to top
View user's profile Send private message 
sullysat


Joined: 16 Oct 2007
Posts: 364
Location: San Antonio, TX

PostPosted: Wed 02 Sep 2009, 17:12    Post subject:  

Well, they boot the distro just fine from the subdirectory. The issue I'm trying to understand better is that during boot ALL of my frugal installations ask which save file to use.

Its like something in the boot process looks at the entire drive and lists all the pup_save files on the drive, regardless of which subdirectory they are in.

Its not a huge issue, but it requires that I sit here and select the right one. Just seems like it shouldn't do that.

I'm not sure if its a Puppy issue or a grub issue, but it looks like a Puppy thing.

Sully
Back to top
View user's profile Send private message 
8-bit


Joined: 03 Apr 2007
Posts: 3357
Location: Oregon

PostPosted: Wed 02 Sep 2009, 18:17    Post subject:  

sullysat,

Can you post your menu.lst file for us to be able to better serve you?

Mine with Multiple frugal installs of Puppy looks like this:

# Linux bootable partition config begins
title U Puppy Linux 471 SCSI frugal
root (hd1,2)
kernel /upup/vmlinuz pmedia=atahd psubdir=upup nosmp
initrd /upup/initrd.gz
# Linux bootable partition config ends
# Other bootable partition config begins
title Windows Vista(on /dev/sda1)
rootnoverify (hd0,0)
makeactive
chainloader +1
# Other bootable partition config ends
# Other bootable partition config begins
title Windows recovery(on /dev/sda2)
map (hd0,0) (hd0,1)
map (hd0,1) (hd0,0)
rootnoverify (hd0,1)
makeactive
chainloader +1
# Other bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 421 frugal
root (hd1,2)
kernel /puppy421/vmlinuz pmedia=atahd psubdir=puppy421 nosmp
initrd /puppy421/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 421m frugal
root (hd1,2)
kernel /pup421m/vmlinuz pmedia=atahd psubdir=pup421m nosmp
initrd /pup421m/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 412 frugal
root (hd1,2)
kernel /puppy412/vmlinuz pmedia=atahd psubdir=puppy412 nosmp
initrd /puppy412/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Jaunty Puppy Linux frugal
root (hd1,2)
kernel /upup/vmlinuz pmedia=atahd psubdir=upup nosmp
initrd /upup/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy Linux 43 scsi frugal
root (hd1,2)
kernel /pup414/vmlinuz pmedia=atahd psubdir=pup414 nosmp
initrd /pup414/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Slacker Puppy frugal
root (hd1,2)
kernel /slacker/vmlinuz pmedia=atahd psubdir=slacker nosmp
initrd /slacker/initrd.gz
# Linux bootable partition config ends
# Linux bootable partition config begins
title Puppy 214v6 frugal
root (hd1,2)
kernel /pup214/vmlinuz root=/dev/ram0 pmedia=atahd subdir=pup214 nosmp
initrd /pup214/initrd.gz
# Linux bootable partition config ends
Back to top
View user's profile Send private message 
Jim1911

Joined: 19 May 2008
Posts: 2445
Location: Texas, USA

PostPosted: Wed 02 Sep 2009, 20:16    Post subject:  

sullysat wrote:
Its like something in the boot process looks at the entire drive and lists all the pup_save files on the drive, regardless of which subdirectory they are in.

You may have vmlinuz and initrd.gz in the root. If you find some extras, rename them and report the results.
Back to top
View user's profile Send private message 
sullysat


Joined: 16 Oct 2007
Posts: 364
Location: San Antonio, TX

PostPosted: Wed 02 Sep 2009, 21:34    Post subject:  

8-bit wrote:
sullysat,

Can you post your menu.lst file for us to be able to better serve you?


Here you go:

# GRUB configuration file '/boot/grub/menu.lst'.
# generated by 'grubconfig'. Mon Aug 31 18:49:38 2009
#
# The backup copy of the MBR for drive '/dev/sda' is
# here '/boot/grub/mbr.sda.7371'. You can restore it like this.
# dd if=/boot/grub/mbr.sda.7371 of=/dev/sda bs=512 count=1
#
# Start GRUB global section
timeout 30
color light-gray/blue black/light-gray
gfxmenu /boot/grub/deep_stage1
# End GRUB global section

# Linux bootable partition config begins
title Puppy Linux 4.2.1 Full (on /dev/sda1)
root (hd0,0)
kernel /boot/vmlinuz root=/dev/sda1 ro vga=normal
# Linux bootable partition config ends

# Linux bootable partition config begins
title Puppy 214R v8 by ttuuxxx Frugal (on /dev/hda2)
rootnoverify (hd0,1)
kernel /puppy214R/vmlinuz root=/dev/ram0 pmedia=idehd psubdir=puppy214R
initrd /puppy214R/initrd.gz
# Linux bootable partition config ends

# Linux bootable partition config begins
title Puppy 4.0 Frugal (on /dev/hda2)
rootnoverify (hd0,1)
kernel /puppy400/vmlinuz pmedia=idehd psubdir=puppy400
initrd /puppy400/initrd.gz
# Linux bootable partition config ends

# Linux bootable partition config begins
title HanSamBen (Puppy 4.12 for kids) Frugal (on /dev/hda2)
rootnoverify (hd0,1)
kernel /edupup_412/vmlinuz root=/dev/ram0 pmedia=idehd psubdir=edupup_412 nosmp
initrd /edupup_412/initrd.gz
# Linux bootable partition config ends



# Linux bootable partition config begins
# title Linux (on /dev/sda2)
# root (hd0,1)
# kernel /boot/vmlinuz root=/dev/sda2 ro vga=normal
# Linux bootable partition config ends
# Linux bootable partition config begins
# title Linux (on /dev/sda3)
# root (hd0,2)
# kernel /boot/vmlinuz root=/dev/sda3 ro vga=normal
# 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/sda1)
# 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)
Back to top
View user's profile Send private message 
sullysat


Joined: 16 Oct 2007
Posts: 364
Location: San Antonio, TX

PostPosted: Wed 02 Sep 2009, 21:46    Post subject:  

Jim1911 wrote:

You may have vmlinuz and initrd.gz in the root. If you find some extras, rename them and report the results.


The root is empty except for the subdirectories my little puplets are in.

Back to top
View user's profile Send private message 
8-bit


Joined: 03 Apr 2007
Posts: 3357
Location: Oregon

PostPosted: Thu 03 Sep 2009, 02:15    Post subject:  

Try this:
Move your pupsave file out of your Puppy400 directory.
Reboot and on the boot options, add pfix=ram
Then select your Puppy 400 entry to boot from
Go through just enough to get you to the desktop of it.
Pick shutdown
Make sure of the path for the save file when it asks where to save it.
It should show Puppy400 in the save path.
Say you want to save and let it make a small pupsave file.
Again, make sure it shows Puppy400 in the path to create the save file in.
Now..
Reboot to any other puppy version
Copy your old pupsave file over the one you just created in the Puppy400 directory.
Cross your fingers and reboot.
Select your Puppy 400 to boot from
It should now find it's own pupsave file without asking.

I know it may sound strange, but I had to go through that once.

If your pupsave files were originally created by Puppy in the subdirectories. Ignore the above.
Back to top
View user's profile Send private message 
vg1

Joined: 02 Dec 2007
Posts: 142

PostPosted: Thu 03 Sep 2009, 03:57    Post subject:  

Psubok= enables psubdir to work from two levels deep, say puppy4/pup421. It only works for p421, for other series 4 [or 3] you would need to edit the init.

In series 4, with a correct setup and only one pup_save in your 'psubdir' it should be used by default, and you should not get a choice of pup_saves. With more than one pup_save in a directory you get the choice. With p421 you can use 'psave=' and specify the pup_save to use in case of several pup_saves in the same dir. To enable this in other series 4 you would need to edit the init as above.

For p214R you need a different set of parameters to specify the pup_save to use. See my post in the p214x thread.

vg
Back to top
View user's profile Send private message 
Display posts from previous:   Sort by:   
Page 1 of 2 [28 Posts]   Goto page: 1, 2 Next
Post new topic   Reply to topic View previous topic :: View next topic
 Forum index » House Training » Users ( For the regulars )
Jump to:  

You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
You cannot attach files in this forum
You can download files in this forum


Powered by phpBB © 2001, 2005 phpBB Group
[ Time: 0.1038s ][ Queries: 11 (0.0130s) ][ GZIP on ]