The first release of the onePup project, 2 Puppy installs where all of Puppy is contained in a single file.
(Inspired by "Pseudo Full Install", @amethyst's "SFS-Merger" and "Save2SFS", and @taersh's "PaDS")
ffiPup or Frugal Full Install
The single file is a directory.
It boots without a layered filesystem.
Useful for "maintainence" because all the files are "just there".
It can be generated from a Puppy release ISO, or a directory.
Or from an fsiPup install directory.
The main difference in this version is the 'ffiMan' gui frontend for running all the support scripts.
These scripts have mostly been already documented in previous releases.
'ffiPuppy' now copies 'rc.sysinit' and 'local-initrd.gz' into their appropriate locations in the new 'ffi'.
'ffi2fsiPup' converts the "ffi" root directory into an "fsi" 'puppy...sfs'.
fsiPup or Frugal Squashfs Install
The single file is a 'puppy...sfs' file.
Yes, the name is derived by replacing "Full" with "Squashfs", because that's exactly what happens when it is created from an "ffi".
It is a normal layered frugal install, and boots as such.
A suitable grub2 "menuentry" can be installed as per "normal", e.g. with "FrugalPup->Boot".
Useful as a running system, since it has virtually no dependence on a "save",
so it runs very efficiently, even in pupmode=66.
It can be generated from a Puppy frugal install, this includes an existing fsiPup install directory.
Or from an ffiPup install directory.
This can be a personalised Puppy, including the configuration and software you want, but without the software you don't want.
Provided you do all this modification in the "source" Puppy install.
A fresh fsiPup install has no "save" but contains the content of the "save" of the source frugal install.
Since it has no "save", it can be booted using either aufs or overlayfs.
While the first boot is in pupmode=5, it doesn't look like a first boot.
It's probably a good idea to "save" on first shutdown, just so it runs in the way you are used to.
There is a new utility:
'fsiMergeSfs' is yet another utility that merges sfs files, but will also merge directories.
It does so by mounting the layers specified on the command line in stack order, as a stack.
If the first item is a directory containing any '.wh.' files, aufs is used, otherwise overlayfs is used.
It then runs 'mksquashfs' against the mount-point of the stack.
It is fairly IO efficient, as the files are copied only once, during the 'mksquashfs' run.
It is called by 'fsiPupSfs'.
(Hm..., maybe I should have called it 'mergeLayers'.)
This release also contains a gui frontend, 'fsiMan', for the following new scripts.
'fsiPuppy' creates and populates an 'fsiPup' directory, from an exitsing frugal install.
'fsiPupSfs' generates a fresh 'puppy...sfs' from an existing frugal install
It supports the use of "_include.lst" files to control the extraction of files from an sfs file.
It can extract files from savefolders and pupmode=66 archive files, but not savefiles.
It is called by 'fsiPuppy'.
'fsi2ffiPup' converts an "fsi" 'puppy...sfs' into an "ffi" root directory.
Try
You could actually build an "fsi" 'puppy...sfs' using existing utilities to save to sfs, and merge sfs files.
Using my code:
Extract 'onePup-04.tar' into an empty directory on a linux partition.
In a terminal change directory to the one containing the extracted files.
Run the command:
All the onePup utilities are now symbolic linked in $HOME/my-applications/bin, so are available via $PATH.
You can run them via a terminal in any diretory, e.g.
or
to run the gui's.
(There are quite a few of these symbolic links, so you may want to try this in a pupmode=13 puppy, so you can discard the "save" at the end of the session.)
NOTE: The GUI utilities require Python3 with gtk3. Works fine on either BookwormPup.
The CLI utilities, are just scripts, so should run on any Puppy.
- onePup-04.tar
- tar xf onePup-04.tar to extract files
- (31.25 KiB) Downloaded 29 times