The time now is Sat 25 May 2013, 01:46
All times are UTC - 4 |
| Author |
Message |
B.K. Johnson
Joined: 12 Oct 2009 Posts: 77
|
Posted: Sat 19 May 2012, 14:16 Post subject:
How to enter pfix command for Multi-boot Puppies? |
|
Whether puppy is booted from a CD or USB, syslinux.cfg invokes the display of the boot.msg graphic and provides a boot prompt where one can enter a puppy pfix=<something> command and after pressing the Enter key the puppy is launched. How is the puppy prefix command passed and to what?
I ask because in building a multi-boot puppy, I can enter the pfix command at the boot prompt but then the applicable puppy is not identified and the command will always apply to the default puppy. If I enter the menu-item number I can't also enter the pfix command. How can I pass the pfix command to the selected puppy?
The menu and bootloading is as with all puppies, not a Grub4DOS.
The syslinux.cfg works; it looks like this:
| Code: | #slacko-5.3.3 is the default
default 1
#Show splash graphic with menu options
display boot.msg
prompt 1
#Allow 5 secs to choose the puplet to launch or to look at help blurb s
timeout 50
#F1 is splash screen with menu options
F1 boot.msg
#F2 is a text file with ibasic help - puppy pfix commands
F2 F2
#F3 is a text file with advanced help
F3 F3
#F4 is a short text file describing the puplets.
F4 F4
# Slacko (currently version 5.3.3)
LABEL 1
kernel /slacko/vmlinuz
append initrd=/slacko/initrd.gz pmedia=usbflash pfix=copy pfix=2
# Quirky (currently version 1.4.2)
LABEL 2
kernel /quirky/vmlinuz
append initrd=/quirky/initrd.gz pmedia=usbflash pfix=copy
# Saluki (currently version 0.21)
LABEL 3
kernel /saluki/vmlinuz
append initrd=/saluki/initrd.gz pmedia=usbflash pfix=copy
|
|
|
Back to top
|
|
 |
666philb

Joined: 07 Feb 2010 Posts: 1229 Location: wales
|
Posted: Wed 23 May 2012, 02:44 Post subject:
|
|
one option, which may not be exactly what you're looking for, is to add an extra entry for each puppy with pfix=ram at the end.
_________________ Quickpet_Precise, install popular apps quickly http://www.murga-linux.com/puppy/viewtopic.php?t=83642
LÖVE2d, a collection of 27 lua gameshttp://www.murga-linux.com/puppy/viewtopic.php?t=76739
|
|
Back to top
|
|
 |
ETP

Joined: 19 Oct 2010 Posts: 310 Location: UK
|
Posted: Thu 24 May 2012, 02:38 Post subject:
USB Multi-boot puppies and syslinux.cfg |
|
B.K. Johnson
The option to enter the command line allows you to completely replace or modify on the fly the boot codes that follow (append initrd=). It only applies however to the default item.
If you want to invoke different boot codes simply make multiple entries in your menu.
I note that you are using “pmedia=usbflash” AND “pfix=copy”. You do not need “pfix=copy” as by default puppy loads the main SFS to RAM. (Your pfix=2 also should not be there)
By way of example say you wanted to boot Saluki on a PC that had very little RAM and wanted to use pfix=nocopy: create an additional entry as follows-
| Code: | # Saluki (currently version 0.21)
LABEL 3
kernel /saluki/vmlinuz
append initrd=/saluki/initrd.gz pmedia=usbflash
# Saluki – low RAM (currently version 0.21)
LABEL 4
kernel /saluki/vmlinuz
append initrd=/saluki/initrd.gz pmedia=usbflash pfix=nocopy |
Backing up your stick:
1. The simplest way, assuming that you have Windows on your laptop is to boot into that, insert the USB & then copy the directory containing the puppy to a place on the NTFS volume. (Exclude that directory on NTFS from your defrag routine)
2. If you have a second flash drive (and USB port) you could also copy from one stick to the other.
_________________ Regards ETP
Currently running Slacko 5.3.3 k-3.1.10
(demo with audio--play flash full screen & press F11)
http://megaswf.com/s/2484946 1080p version Oct 2012
|
|
Back to top
|
|
 |
B.K. Johnson
Joined: 12 Oct 2009 Posts: 77
|
Posted: Mon 28 May 2012, 23:22 Post subject:
USB Multi-boot puppies and syslinux.cfg |
|
ETP
| Quote: | | The option to enter the command line allows you to completely replace or modify on the fly the boot codes that follow (append initrd=). It only applies however to the default item. |
I understood the case that when booting from a CD or a flash drive with a single puppy the "on the fly" mods would affect that puppy by default because there is no other.. I now see that the multiple puppies make no difference. One can either enter the menuitem number or pfix command(s) at the boot prompt. When it is the latter, it is the "programmed" default in syslinux.cfg that is selected. That's not what I want. I was hoping that both menuitem and pfix command would be passed. Thanks for letting me see the light .
| Quote: | | If you want to invoke different boot codes simply make multiple entries in your menu. |
I thought of and discarded multiple menu items as a solution for there would be too many items to accommodate all the permutations and combinations. I don't know what commands I will use/need and with which puppy. I want to plan with flexibility. I don't want to have to edit my syslinux.cfg to either change the default puppy or add a pfix command for a one-off. Suppose I have adequate RAM on my machines. Saluki is the default pup on my flash drive. I go to a customer or friend in need and their machine is RAM challenged and the software set I want to use is not in the default. What to do?
Clearly, this is a syslinux issue, not a puppy problem.
The pfix=2 is not a permanent part of my syslinux.cfg. It's a remnant from when I wanted to ignore the last 2 bootings of that particular pup. I could not do it on the fly so edited the config file and forgot to remove it not only before my post but after too. The result was a corrupt .2fs that necessitated me removing it and starting over .
Re backing up your stick, would not both scenarios just be backing up the files? Case 2 could work but I'd have to use gparted to set the boot flag. What I wanted was to clone the flash drive in puppy with a tool in puppy. Thanks for your interest.
B.K. Johnson
|
|
Back to top
|
|
 |
puppyluvr

Joined: 06 Jan 2008 Posts: 3053 Location: Chickasha Oklahoma
|
Posted: Tue 29 May 2012, 00:53 Post subject:
|
|
Hello,
Have Grub point to Grub.. LOL
@ my meownplanet signature link, (username: puppy password: linux) you will find my MultiPup .pet which does what you are asking to create a MultiPup ISO with Grub setup as you need.. After choosing your Pup, you get another Grub menu, where you can add bootcodes..
D/L it and look inside at how it works...
Or just use it to make your ISO..
Rename it to MultiPup_3.3.tar.gz to unpack it without installing the .pet...
Direct link:http://puppylinuxstuff.meownplanet.net/puppyluvr/Multipup-3.3.pet
Or have a look around my stuff!!
_________________ "Close the "Windows", and open your eyes, to a whole new world"
http://puppylinuxstuff.meownplanet.net/puppyluvr/
http://theplpd.webs.com/
Nothing but Puppy since 2.15CE...
|
|
Back to top
|
|
 |
B.K. Johnson
Joined: 12 Oct 2009 Posts: 77
|
Posted: Wed 27 Jun 2012, 23:39 Post subject:
|
|
puppyluvr
Belated thanks for your recommendation of Multipup. Unfortunately, I haven't yet been able to install it as I don't have an ext2/ext3 partition in my system and creating one on an external drive at this time is not convenient. (I am running puppy from a headless laptop). Furthermore, I am at a loss as to when I am using/not using the pupsave - still (embarrassed ) though the Readme assures me the pet will prevent me from any folly.
If I format a 4gb flash drive as ext2 , place a puppy on it and install Multipup to it, would that work? With a puplet (e.g. slacko) in which the Multipup pet is installed, would I then run the creator from the menu? Must the puplets that creator needs to make the menu be on the flash drive or it doesn't matter? Sorry about these questions; asked only because there is no ext2 to try.
|
|
Back to top
|
|
 |
puppyluvr

Joined: 06 Jan 2008 Posts: 3053 Location: Chickasha Oklahoma
|
Posted: Thu 28 Jun 2012, 09:31 Post subject:
|
|
Hello,
Where MultiPup must be on an ext2/3 partition, because it created a huge directroy and would overflow a pupsave, and some of the scripts need to be run from ext2/3 to function..
However, the ISO`s you use can be anywhere, where ever they are, as you just (absolute) symlink them in to MultiPup..
While running your usual Puppy, you can just place (or install) MultiPup to the jump drive, so it runs from there...
After install, the menu entry runs a dialog to assist you in placing the directory, just direct it to the jump drive...
_________________ "Close the "Windows", and open your eyes, to a whole new world"
http://puppylinuxstuff.meownplanet.net/puppyluvr/
http://theplpd.webs.com/
Nothing but Puppy since 2.15CE...
|
|
Back to top
|
|
 |
|
|
|
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
|