Puppy Linux Discussion Forum

I created a frugal install of both the latest voidpup and vanilladpup on sda2 of an internal ssd.

boot parameter pmedia=ataflash boots pupmode 13, offering to save on exit, which is the desired behavior. A savefolder has been created in the same subfolder as the install files.

I am wishing to boot into a clean install so I can create a additional savefolder to keep along side the first in the install folder.

pfix=ram added to kernel line does nothing, the pups still boot with the existing savefolder.

I also use these pups.
I usually do the backup of the savefolder with Utility->Pupsave Backup.
Once the backup of the savefolder is created, I get a choice during boot what savefolder to boot into and there is also the choice "none" (which is the clean install).

Or try the trick with "fake" empty folder created next to your savefolder (with the correct name to be visible for booting puppy - e.g. "vanilladpupsave-empty").

It's interesting that the param "pfix=ram" does nothing. I haven't needed it with these puppies yet.

@williwaw :-

Hm. Odd, indeed.

My entire kennels - around 9 or 10 Pups - also occupy sda2 of my internal 1 TB SSD. Anytime I need a 'clean boot' - for whatever reason - I simply add 'pfix=ram' to the kernel line. Never known it to fail yet. Here's my menu.lst:-

# menu.lst produced by grub4dosconfig-v1.9.3
color white/blue black/cyan white/black cyan/black
splashimage=/pupsplash2.xpm
timeout 20
default 0

# Frugal installed Puppy

title Quirky April 64 'lite' (sda2/Quirky7_64_lite)
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Quirky7_64_lite/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Quirky7_64_lite pmedia=satahd pfix=fsckp
  initrd /Quirky7_64_lite/initrd.gz
  
title Fossapup 64 9.5 (sda2/Fossapup64)
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Fossapup64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Fossapup64 pmedia=satahd pfix=fsckp
  initrd /Fossapup64/initrd.gz
  
title KLV "Airedale" (sda2/KLV-test)
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /KLV-test/vmlinuz  w_bootfrom=/mnt/sda2/KLV-test net.ifnames=0
  initrd /KLV-test/initrd.gz

title Bionicpup64 8.0 (sda2/Bionicpup64)
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Bionicpup64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Bionicpup64 pmedia=satahd pfix=fsckp
  initrd /Bionicpup64/initrd.gz

title Xenialpup 64 7.5 (sda2/Xenialpup64)
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Xenialpup64/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Xenialpup64 pmedia=satahd pfix=fsckp
  initrd /Xenialpup64/initrd.gz
  
title Slacko 5.7.1 (sda2/Slacko_571)
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Slacko_571/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Slacko_571 pmedia=satahd pfix=fsckp
  initrd /Slacko_571/initrd.gz
  
title Xenialpup (sda2/Xenial32)
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Xenial32/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Xenial32 pmedia=satahd pfix=fsckp
  initrd /Xenial32/initrd.gz
  
title Tahrpup32 (sda2/Tahr32)
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Tahr32/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Tahr32 pmedia=satahd pfix=fsckp
  initrd /Tahr32/initrd.gz
  
title Slacko 560 (sda2/Slacko560)
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Slacko560/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3 psubdir=/Slacko560 pmedia=satahd pfix=fsckp
  initrd /Slacko560/initrd.gz
  
title Studio 1337 (sda2/Studio1337)
  find --set-root uuid () b142cd08-ce81-413e-b963-12b393d8eaa3
  kernel /Studio1337/vmlinuz  pdrv=b142cd08-ce81-413e-b963-12b393d8eaa3  psubdir=/Studio1337 pmedia=satahd pfix=fsckp
  initrd /Studio1337/initrd.gz

Notice what I'm using here; "pmedia=satahd". AFAIK, "ataflash" is generally used if you want to fool Puppy into thinking a hard drive is a flash drive, so that you get the 'save' icon on the desktop & option for manual save behaviour, yes?

Try changing "pmedia=ataflash" to "pmedia=satahd". See what happens, and let us know the outcome, please.

-----------------------------

Anyhoo; if it's an extra save-folder you want, you don't need to go through the shut-down/re-boot procedure. A save-folder is simply a standard, empty directory when first created.....and we all of us create those on a regular basis, don't we? It's simply the name that sets it apart as being for Puppy's use, as specified by the 'DISTRO_FILE_PREFIX' in each Puppy's /etc/DISTRO_SPECS file.

The format is always

[DISTRO_FILE_PREFIX](save)-(distinguishing name/letters/whatever.....this added by you, the user)

Like, for my default boot-entry (top of the list), the save is specified by:-

DISTRO_FILE_PREFIX = april64
Distinguishing name, added by me = Mike

That gives us "april64save-Mike".......which is the name of my save-folder in Quirky64 April 7.0.1. You MUST use the first part as-is, since Puppy expects a certain format.....but the last bit, you add to suit yourself. Anything you want, so long as Puppy can distinguish between them, and see that there two different ones.

If Puppy detects two or more save-folders at boot time - the DISTRO_SPECS file is duplicated within the initrd.gz itself, and is, I would guess, called by the init script itself - then you get offered the choice of which one to run with. And that's what you want, yes?

Mike.