FrugalPup 20 - Puppy frugal installer.

Under development: PCMCIA, wireless, etc.
Post Reply
Message
Author
gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

FrugalPup 20 - Puppy frugal installer.

#1 Post by gyro »

Downloads for "FrugalPup/StickPup" are available from http://www.mediafire.com/folder/rdyc5lg ... frugalpup/. Or indirectly via, http://www.fishprogs.software/puppy/.

See http://www.murga-linux.com/puppy/viewto ... 66#1052566 for v20 announcement.

Help pages for "FrugalPup" can be viewed at http://www.fishprogs.software/puppy/fru ... index.html.
Help page for "MOK manager" can be viewed at http://www.fishprogs.software/puppy/fru ... p-mok.html.

--------------- Announcement for FrugalPup v0.3, the first release, follows ------------------------

This could be called "Yet Another Puppy Frugal Installer", so why?
It all started when I discovered that grub2-efi supports not only booting a "vmlinuz" and "initrd.gz" on some partition other than the boot partition,
but also specifying this other partition with a label or uuid.

This utility can be used to setup one or more Puppy frugal installs in a directory,
and setup a fat32 partition to boot them.

It provides full support for the install directory and the save directory being on separate partitions, even on separate drives.
It provides full support for the boot partition containing only boot loader files, including with a uefi boot.
It writes boot entries containing boot parameters to communicate the above configurations to the "init" script.

It uses grub2-efi for uefi booting and grub4dos for mbr/legacy booting.

It supports uefi booting on gpt partitioned drives.
It does not support mbr/legacy booting on gpt partitioned drives.
It does not write an MBR for uefi only booting.

It assumes all booting is done with a fat32 partition, usually the first partition on some drive.
It assumes that relevant drives are partitioned, and that relevant partitions are formated.

It consists of 2 facilities:
"puppyfiles", manages the actual install directories and save directories.
"bootfiles", sets-up the selected boot partition to boot all Puppy frugal installs in the selected directory.
The idea is that you run "puppyfiles" for each Puppy you wish to install,
then run "bootfiles" once to enable booting of all these Puppies.
Although each facility can be run independently of the other.

Both facilities proceed through several selection dialogs to a confirming dialog, containing a summary of the current selections.
At this point, clicking on "Quit" safely abandons the process, clicking on "OK" continues on to copying files etc..

Some examples:

A. A single puppy, all on a single vfat(fat32) partition, e.g. a usb stick.

1. Under the "Setup" menu click on "FrugalPup - Puppy frugal installer".
2. Click on the "Puppy" button.
3. Click on "OK" to select "iso".
4. Select the relevant iso file.
5. Select the vfat partition to contain Puppy.
6. Create a directory to contain Puppy.
7. Click on "OK" with no selected partition to avoid defining a separate save partition.
8. Click on "OK" with no selected items to avoid defining any kernel boot parameters.
9. If selections look fine, click "OK" to start writing.
10. Click "OK" to confirm writing done.

11. Click on the "Boot" button.
12. Click on "OK" to select the root directory of the vfat partition as the source directory.
13. Select the vfat partition as the boot partition.
14. Click on "OK" to accept the default boot type, "both".
15. If selections look fine, click "OK" to start writing.
16. Click "OK" to confirm writing done.

17. Click on "Quit" to exit the utility.


B. Two Puppies (slakco and upupbb) that boot from a usb stick, with install directories on SSD (sda2), and save directories on HD (sdb2).

1. Under the "Setup" menu click on "FrugalPup - Puppy frugal installer".
2. Click on the "Puppy" button.
3. Click on "OK" to select "iso".
4. Select the slacko iso file.
5. Select "sda2" partition to contain Puppy.
6. Select/create "slacko" directory to contain Puppy.
7. Select "sdb2" as the save partition.
8. Select/create "slacko" directory to contain the savefolder.
9. Click on "OK" with no selected items to avoid defining any kernel boot parameters.
10. If selections look fine, click "OK" to start writing.
11. Click "OK" to confirm writing done.

12. Click on the "Puppy" button.
13. Click on "OK" to select "iso".
14. Select the upupbb iso file.
15. Select/create "upupbb" directory on sda2 to contain Puppy.
16. Select/create "upupbb" directory on sdb2 to contain the savefolder.
17. Click on "OK" with no selected items to avoid defining any kernel boot parameters.
18. If selections look fine, click "OK" to start writing.
19. Click "OK" to confirm writing done.

20. Click on the "Boot" button.
21. Click on "OK" to select the root directory of sda2 as the source directory.
22. Select the usb stick vfat partition as the boot partition.
23. Click on "OK" to accept the default boot type, "both".
24. If selections look fine, click "OK" to start writing.
25. Click "OK" to confirm writing done.

26. Click on "Quit" to exit the utility.


C. A usb stick to boot Puppies already installed in sub-directories under the /puppy directory on sdb2.

1. Under the "Setup" menu click on "FrugalPup - Puppy frugal installer".
2. Click on the "Boot" button.
3. Select the sdb2 partition as the source partition.
4. Select "puppy" as the source directory.
5. Select the usb stick vfat partition as the boot partition.
6. Click on "OK" to accept the default boot type, "both".
7. If selections look fine, click "OK" to start writing.
8. Click "OK" to confirm writing done.

9. Click on "Quit" to exit the utility.


Notes:

1. "puppyfiles" will not create an install directory on an f2fs partition, because the current grub2-efi will not find it's uuid or label.
(You can however define a save directory on an f2fs partition.)

2. "puppyfiles" can also be used to update an install directory with the newer files in a new version of the same Puppy.
(e.g. after a new delta release of upupbb.)

3. "bootfiles" always writes a "TZ=" boot parameter whose value is derived from the currently running Puppy.

4. "bootfiles" only writes an MBR if either "mbr" or "both" is selected for boot type, and it writes it to the drive (not the partition) when it does.

5. "grub2-efi" seems to be missing from current woof-ce 32bit puppies, i.e. upupbb.
So, the sfs contains it's own copy of "grub2-efi".

gyro
Last edited by gyro on Mon 13 Apr 2020, 13:42, edited 25 times in total.

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#2 Post by bigpup »

Something different for doing installs.
Seems OK as a way to do installs.
Just started trying to use it.

Trying to do install to a USB flash drive.
On the window where you select the directory to install to.
If you select create folder.
A line opens for typing in the name of the folder you want to create. Type in a name.
Selecting OK.
New folder is not created.

To make the new folder.
After typing in the name for folder.
Have to press enter on keyboard.

Is selecting OK suppose to make the folder?

It would be better if that create folder button was named create directory.
Attachments
capture8397.png
(44.22 KiB) Downloaded 3443 times
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
peebee
Posts: 4370
Joined: Sun 21 Sep 2008, 12:31
Location: Worcestershire, UK
Contact:

#3 Post by peebee »

5. "grub2-efi" seems to be missing from current woof-ce 32bit puppies, i.e. upupbb.
It looks quite big....??

Code: Select all

grub-efi-ia32_2.02|grub-efi-ia32|2.02|2ubuntu8.4|Setup|187K|pool/main/g/grub2|grub-efi-ia32_2.02-2ubuntu8.4_i386.deb|+debconf&ge0.5,+grub-common&eq2.02,+grub2-common&eq2.02,+grub-efi-ia32-bin&eq2.02,+ucf|GRand Unified Bootloader version 2 EFI-IA32 version|ubuntu|bionic||
grub-efi-ia32-bin_2.02|grub-efi-ia32-bin|2.02|2ubuntu8.4|Setup|2006K|pool/main/g/grub2|grub-efi-ia32-bin_2.02-2ubuntu8.4_i386.deb|+grub-common&eq2.02,+efibootmgr|GRand Unified Bootloader version 2 EFI-IA32 binaries|ubuntu|bionic||
ImageLxPup = Puppy + LXDE
Main version used daily: LxPupSc; Assembler of UPups, ScPup & ScPup64, LxPup, LxPupSc & LxPupSc64

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#4 Post by bigpup »

Running the boot setup.

Why would you want to create a folder when you are at this window?
Attachments
capture12954.png
(53.13 KiB) Downloaded 3429 times
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#5 Post by bigpup »

A. A single puppy, all on a single vfat(fat32) partition, e.g. a usb stick.

1. Under the "Setup" menu click on "FrugalPup - Puppy frugal installer".
2. Click on the "Puppy" button.
3. Click on "OK" to select "iso".
4. Select the relevant iso file.
5. Select the vfat partition to contain Puppy.
6. Create a directory to contain Puppy.


That step 6 is maybe a problem.

Installing a Puppy made with the latest WOOF-CE.
Installing Bionicpup64 7.9.3
At step 6 I made a directory named bionicpup.
Installed to that directory went OK.
Setup the boot loader.
That went OK.

Tried to boot Bionicpup64 7.9.3
Selected the correct menu entry to boot it.
The boot process started.
Got to a bunch of error messages. The main message was could not find the puppy_bionicpup64_7.9.3.sfs (the main sfs).

Here is how I fixed it:
Changed the name of the directory the install is in.
Changed it from bionicpup to bionicpup64793uefi
Tried booting again and no problem booting to the desktop.

So, seems to be something in the Puppy boot process that is searching for a very specific named directory to find the main sfs.

The boot menu entries are the same, only the name of the directory was changed. So, nothing in the boot menu entry setup was bad.
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#6 Post by gyro »

@peebee,
Yes it's on the large side, in xenialpup the uncompressed directory is 645K according to "du".
Interesting that it's in xenialpup, but not in later 32bit Puppies.

@bigpup,
The "Create Folder" button comes with the "yad --file --directory" dialog.
So, the chances that I will change it are virtually zero.

As to the problem with bionicpup64, I've not seen anythhing like this, I'll try to replicate.
From my memory, the "init" script does not expect any specific sub-directory for a particular puppy, it looks where it's told by boot parameters.

Thanks for testing

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#7 Post by gyro »

@bigpup,
Forgot to mention that the need to hit the "Enter" key to create a new folder, is part of the "yad --file --directory" dialog.
The idea of the "confirm" dialog, is that if anything is confusing, you can safely try different things and bail out if they don't end up looking correct.

As to bionicpup64, I just installed it to a usb stick using FrugalPup.
Unfortunately it all went fine, including the boot.
My generated grub4dos menu entry is:

Code: Select all

title Puppy bionicpup64_7.9.3
    uuid 
    kernel /bionicpup/vmlinuz pmedia=usbflash pupsfs=USBPBOOT psubdir=/bionicpup pfix=fsck,fsckp TZ=AEST-10
    initrd /bionicpup/initrd.gz
What was your generated menu entry?

Hmm... just noticed the missing uuid value, will fix.
Strange that it still boots on my machine.

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

FrugalPup v0.4 - Puppy frugal installer

#8 Post by gyro »

Bug-fix version:

Download extra sfs, http://www.fishprogs.software/puppy/fru ... up_0.4.sfs (684 KiB).

Fixes 2 issues:
1. Missing "uuid" value in grub4dos "menu.lst" generated by "bootfiles".
2. Using "puppyfiles" to update Puppy files, not work if Puppy source is a zip file.

gyro

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#9 Post by bigpup »

gyro wrote:@bigpup,
As to bionicpup64, I just installed it to a usb stick using FrugalPup.
Unfortunately it all went fine, including the boot.
My generated grub4dos menu entry is:

Code: Select all

title Puppy bionicpup64_7.9.3
    uuid 
    kernel /bionicpup/vmlinuz pmedia=usbflash pupsfs=USBPBOOT psubdir=/bionicpup pfix=fsck,fsckp TZ=AEST-10
    initrd /bionicpup/initrd.gz
What was your generated menu entry?

Hmm... just noticed the missing uuid value, will fix.
Strange that it still boots on my machine.

gyro
I did it again using the Frugalpup V04.
This time it boots OK.
So, maybe it was something to do with that uuid missing.
uuid is getting used in this new menu entry.
Notice the

Code: Select all

pupsfs=6BE4-77FA
My working menu entry.

Code: Select all

title Puppy bionicpup64_7.9.3
    uuid 6BE4-77FA
    kernel /bionicpup/vmlinuz pmedia=usbflash pupsfs=6BE4-77FA psubdir=/bionicpup pfix=fsck,fsckp TZ=EST5EDT,M3.2.0,M11.1.0
    initrd /bionicpup/initrd.gz
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#10 Post by gyro »

bigpup wrote:I did it again using the Frugalpup V04.
This time it boots OK.
So, maybe it was something to do with that uuid missing.
I'm pretty sure it was.
My v0.4 menu entry:

Code: Select all

title Puppy bionicpup64_7.9.3
    uuid F8FD-4197
    kernel /bionicpup/vmlinuz pmedia=usbflash pupsfs=USBPBOOT psubdir=/bionicpup pfix=fsck,fsckp TZ=AEST-10
    initrd /bionicpup/initrd.gz
Note that in my entry "pupsfs=" uses the label of the partition, rather than the uuid.
So, with the uuid value being empty, I gave grub4dos rubbish, but I gave the "init" script good info.
When your entry had an empty uuid value, you gave grub4dos rubbish, and the "init" script rubbish.

From my perspective, bug found, bug fixed.

Thanks for testing.

Note: A grub4dos menu entry always uses a

Code: Select all

uuid F8FD-4197
line to specify the partition to grub4dos.
But the "pupsfs=" parameter will use the partition label instead, if one exists.
(I am in the habit of adding a unique label to each of my partitions.)

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

FrugalPup v0.5 - Puppy frugal installer.

#11 Post by gyro »

FrugalPup v0.5 - Puppy frugal installer.

Now includes a "GParted" button for convenience,
and a companion utility StickPup v0.5, a no-frills formater/installer for usb flash drives.

Download extra sfs, http://www.fishprogs.software/puppy/fru ... up_0.5.sfs (688 KiB).

This utility uses 3 "places".

1. The "boot partition":
this is always a fat32 partition, for easy compatibility with uefi.

2. The "install partition" and "install directory":
This directory contains the Puppy release files, i.e. the sfs's and vmlinuz and initrd.gz.

3. The "save partition" and "save directory":
This directory contains the save layer.
If different from the "install partition" then the "save partition" is a Linux partition for savefolder support.

"FrugalPup" supports all 3 places being different, or any 2 the same, or all the same.

"StickPup" supports only all 3 being the same, (single fat32 partition),
or both the "boot partition" and the "install partition" being a fat32 partition and the "save partition" being on an f2fs partition, both on the usb flash drive.

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

FrugalPup v0.6 - Puppy frugal installer

#12 Post by gyro »

FrugalPup v0.6 - Puppy frugal installer.

This version includes a newer "grubx64.efi" file, significantly bigger than previous.

The companion utility StickPup v0.6 is now even simpler than previous.
It now supports only the creation of a single fat32 partition usb stick for both uefi and mbr booting.
It's only dialogs are:
1. Select a usb stick
2. Select a Puppy source type.
3. Select the Puppy source file/directory to use.
4. Confirm before doing anything.

Download extra sfs, http://www.fishprogs.software/puppy/fru ... up_0.6.sfs (920 KiB).

Note:
"StickPup" is just a different, simple gui frontend for the "FrugalPup" files, "frugalpup-puppyfiles" and "frugalpup-bootfiles".

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

FrugalPup v0.7 - Puppy frugal installer.

#13 Post by gyro »

FrugalPup v0.7 - Puppy frugal installer.

This version includes a different "grubx64.efi", one that does not do a 2 menu boot, it goes directly to the boot menu.
It also includes new versions of "grldr" and "bootlace.com".
So, it's now self contained, it doesen't depend on either boot facility being present in the running Puppy.

Also fixed a bug; If you tried to use the "Puppy" facility to store Puppy files on different partitions in the same run, it didn't give you an option to choose the second partition.

Download extra sfs, http://www.fishprogs.software/puppy/fru ... up_0.7.sfs (1.2 MiB).

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

FrugalPup v0.8 - Puppy frugal installer.

#14 Post by gyro »

Just a bug fix version, for features see version 0.7 in previous post.

Similar problem in "Boot" facility as fixed in "Puppy" facility in version 0.7.
If the default source partition was set by installing Puppy files using the "Puppy" facility, no option was provided to select a different partition as the source partition for Puppy install directories in the "Boot" facility.
Hmm.. probably should have fixed this in version 0.7.

Download extra sfs, http://www.fishprogs.software/puppy/fru ... up_0.8.sfs (1.2 MiB).

gyro

polekat
Posts: 30
Joined: Sun 28 Apr 2013, 06:51

#15 Post by polekat »

I get this when run from the terminal . it wouldn't run from the menu

"/usr/sbin/frugalpup: line 69: yad32: not found"

I'm running lxpup. quick search shows no yad32

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#16 Post by gyro »

polekat wrote:I get this when run from the terminal . it wouldn't run from the menu

"/usr/sbin/frugalpup: line 69: yad32: not found"

I'm running lxpup. quick search shows no yad32
Sorry, I've uploaded a new version to fix this.
Download extra sfs, http://www.fishprogs.software/puppy/fru ... up_0.9.sfs (1.4 MiB)

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

FrugalPup v0.10 - Puppy frugal installer.

#17 Post by gyro »

FrugalPup v0.10 - Puppy frugal installer.

This version is to fix the following bug:
"StickPup" is not as quiet as it should be, due to "default partition" handling introduced in v0.8.

Download extra sfs, http://www.fishprogs.software/puppy/fru ... p_0.10.sfs (1.4 MiB)

gyro

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

FrugalPup v11 & StickPup v11 - Puppy frugal installer.

#18 Post by gyro »

FrugalPup v11 & StickPup v11 - Puppy frugal installer.

This version includes 2 new features:

1) An "ISO" button that executes "frugalpup-isoboot".
This creates a "$HOME/puppy_boot.iso" file that contains only grub2 configured to non-uefi boot the selected Puppy frugal install(s).
Once you burn the "$HOME/puppy_boot.iso" file to a CD/DVD, you have a CD/DVD that can boot Puppies stored on your system.
It is meant to provide an alternate boot mechanism for machines that can't boot from usb.

Note: You can do a similar thing with "frugalpup-bootfiles" ("Boot" button), i.e. produce a bootable usb stick that doesn't contain any Puppies, but boots Puppies stored on your system.

2) A CLI utility called "bootentry".
This runs the script used by both "frugalpup-bootfiles" and "frugalpup-isoboot" to generate boot entries, so it can be used to preview the entry these scripts would produce.
Simply run "bootentry -h" in a console to see it's usage help message.

Download extra sfs, http://www.fishprogs.software/puppy/fru ... pup_11.sfs (2.7 MiB).

gyro

User avatar
bigpup
Posts: 13886
Joined: Sun 11 Oct 2009, 18:15
Location: S.C. USA

#19 Post by bigpup »

Thank you so much for this software!!

I was looking for any easy way to get a UEFI boot loader installed on an internal emmc drive used as the storage on this computer.
For the uefi bios to be able to select this as a bootable drive.
Secure boot needs to be enabled.
So, the boot loader on the emmc drive needs to be a UEFI boot loader.

What I did using the FrugalPup program.
The emmc drive has two partitions.
First one a small fat32 formatted for boot files.
Second one ext4 format using rest of drive.

I already had a frugal Install of Bionicpup64 8.0 on the ext4 partition.

Started the FrugalPup program.
Selected Boot button.
Selected the partition Bionicpup was on.
Selected the parent directory.
Selected the emmc fat32 first partition as the boot partition.
Selcted uefi for boot type.

Now have a working uefi boot loader that will work with secure boot enabled.

I really like that first window, giving you choices as to what you want to do, using FrugalPup.

I was looking for a installer program a new Puppy user could use.
This is very much one of them!!
The things they do not tell you, are usually the clue to solving the problem.
When I was a kid I wanted to be older.... This is not what I expected :shock:
YaPI(any iso installer)

gyro
Posts: 1798
Joined: Tue 28 Oct 2008, 21:35
Location: Brisbane, Australia

#20 Post by gyro »

bigpup wrote:Thank you so much for this software!
Thank you.
I'm glad you found it to be useful.

gyro

Post Reply