Here is a list of the parameters/arguments you can set, note these don't apply to early versions of Puppy especially pre Puppy2.
Specifies the subdirectory in which the kernel is located in on the boot partition. If not specified init will look in / and /boot , I'm not sure which order. As of puppy 3.00 this parameter also restricts the boot search for existing pup_save files only pup_saves inside this directory will used. This can be used to allow multiple puppy installation on the same partition to be used without risk of using the wrong one in error. example: psubdir=boot/puppy216
Not specifying this should automatically detect the boot media. Manually specify the boot media and interface using one of the following: usbflash usbhd usbcd ideflash idehd idecd idezip satahd satacd scsihd. This would be where USB, IDE, SATA, SCSI are the accepted interfaces and flash memory, hard drive, CD/DVD drive, ZIP drive are the accepted drives, e.g. PMEDIA=idehd.
(Applies to Puppy 2x and later).
Specifics device, for example-
- pfix=ram will run Puppy totally in RAM and ignore saved sessions/storage file(s)
- pfix=<n> where <n> is the number of saved sessions to ignore for a multisession-CD
- pfix=rdsh will exit to initial ramdisk commandline (do not pivot_root)
- pfix=usbcard for booting from USB flash drive via USB 2.0 to PCMCIA adapter
- pfix=clean will force a simulated version upgrade (for Puppy 2.13 and later)
- pfix=purge will force an even more radical file cleanup (to fix broken system) (for Puppy 2.14 and later)
- pfix=#debug may help with debugging
- pfix=copy or nocopy controls if main sfs file is loaded (copied) to RAM
If using multiple pfix options, separate them with a comma, e.g. pfix=rdsh,usbcard
Controls what file is loaded as BaseSfs. Specify full path and filename, for example
Add nopcmcia if you don't want the PCMCIA (PC card) drivers and card ~manager to be started during the boot process.
The keyboard layout for a country. Default is "us". Choices are: be br cf de dk es fi fr gr hu it jp no pl ru se uk us See Barry's recent blog post for more on this.