FrugalPup 20 - Puppy frugal installer.

[bigpup]

Bionicpup64 8.0
Frugal install
Save folder

Bionicpup updates installs Frugalpup v11 and only puts stickpup in the menu.
666philb only wanted to use Stickpup in the menu, but the complete Frugalpup is there, when frugalpup is run from terminal.

The Frugalpup _18sb.sfs loads. but no menu entry is made.
Still have to run from terminal.
does not seem to show up as 18sb when you run it.
It still shows as v11.
So, I assume it is still v11 running.

I turned the FrugalPup_18sb.sfs into a pet package.
Installed the pet.
Now have FrugalPup in menu.
It runs FrugalPup 18sb

[bigpup]

Error message:
It means exactly what it says, the script '/usr/local/frugalpup /frugalpup-dobootpart' failed because it could not find the named directory.
The named directory looks quite odd, as though the script got a little confused. The question is, why did it try to use that name?
Unfortunately I would need to know the full set of imputs used to get to that result, in order to have any chance reproducing it.

USB flash drive.
2 partitions.
sdb1 fat32 small 500MB
sdb2 ext 3 28GB

This is strange.
I originally got this error when trying to install a boot loader in sdb1.
Selected both as boot type.
I was using the Frugalpup 18sb sfs loaded in Xenialpup64 7.5.

I tried it again now using Frugalpup 18sb as an installed pet in Bionicpup64 8.0.
No error.
It installed both boot loader types in sdb1.

Process followed.
Main Window select Puppy button.
Source type iso.
Selected the iso containing files.
Selected sdb2 as location to contain Puppy.
Made directory bionicpup6480 on sdb2
Choose sdb2/bionicpup6480 as directory to contain frugal puppy files.
Click ok, on sanity check, show all my selections as good.
Installation complete with frugal install in sdb2/bionicpup6480
Boot loader on sdb1

[gyro]

Yes, the MOK screens need documentation. but since we are not the only folk who use MOK manager, I'm hoping to find some on the web before the release of FrugalPup v19.

You can find one here. The location of the key is a bit different, but everything else should more or less work the same way. Feel free to modify as needed (edit the image with mtpaint/gimp if you like )

Thanks.
I will "borrow" it and hopefully change it to more acurately reflect the directory structure, I use.

gyro

[gyro]

This is strange.
I originally got this error when trying to install a boot loader in sdb1.
Selected both as boot type.
I was using the Frugalpup 18sb sfs loaded in Xenialpup64 7.5.

I tried it again now using Frugalpup 18sb as an installed pet in Bionicpup64 8.0.
No error.
It installed both boot loader types in sdb1.

I was afraid of that.
I'll try using the .sfs in Xenialpup64.

Re Bionicpup64:
Aa you are aware, every time you update it, FrugalPup returns to v11, because that is included in the update .zip file.
So the update writes FrugalPup v11 to the savefolder, which of course "covers" the contents of any FrugalPup.sfs.
An alternative way of dealing with this is to remove all the files in '/usr/local/frugalpup' and '/usr/local/mi-utils' from the Bionicpup64 savefolder, using a different Puppy.
Also, 'FrugalPup' can be enabled in the menu with the menu editor.

gyro

[gyro]

@bigpup,
I am unable to reproduce the error you saw, even using Xenialpup64 and a stick with fat32 and ext3 partitions.

However I did find a bug:
The "Puppy" facility fails to write Puppy files to the root of a partiition, i.e. if there is no "psubdir" specified, even though it says it does.
The fix will be part of the next version.

gyro

[bigpup]

I got around the V11 problem in Bionicpup64 8.0 by installing FrugalPup 18sb as a pet package not loaded as a sfs.
That overwrites, what is in the save, to the newer version.

[gyro]

Tried different boot selection.
Selected boot type:
both.
Got this error. (see image)

I've found a situation that produces that error message.
The problem is FrugalPup's 2 step process in selecting a direcory,
1. Select a partition.
2. Select a directory.
The assumption is that the directory selected in step 2. is within the partition selected in step 1.
If the selected directory is in some other partition, then the problem occurs.

Unfortunately, FrugalPup often uses this process.
I'll have to review each of these cases to ensure that the selected partition always contains the selected directory.

It would be easiest if I could get yad to only allow selection of a directory within a specified partition, but I don't think that is possible.

The reason for using a 2 step process is so that FrugalPup can mount the selected partition before directory selection, if it is not already.mounted.

Note: I suspect that this is an issue for all versions of FrugalPup.

gyro

[gyro]

FrugalPup 18t, DiskPup 18t, StickPup 18t and f2StickPup 18t - Puppy frugal installer.

Download extra sfs 'frugalpup_18t.sfs' from http://www.mediafire.com/folder/rdyc5lgzpeij1/frugalpup (2.9 MiB).

This is a test release.

It includes fixes for both bugs mentioned above.
It does not include any MOK doco.

[gyro]

Known issue:

The "BootCD" facility in "FrugalPup" does not produce a bootable ".iso" file.
It needs to be re-worked since the change to booting grub4dos and then chaining to grub2.

gyro

[gyro]

FrugalPup 19, DiskPup 19, StickPup 19 and f2StickPup 19 - Puppy frugal installer.

Download extra sfs 'frugalpup_19.sfs' from http://www.mediafire.com/folder/rdyc5lgzpeij1/frugalpup (2.9 MiB).

This is a feature release.

1. Support for "Secure Boot"
Thanks to forum member "jamesbond", support is included for booting Puppy while "Secure Boot" is enabled.
Although this does require the "enrolling" of a MOK (Machine Owner Key), with MOK manager.
The Puppy MOK is contained in the file "/puppy.cer" in the fat32 install partition.
Documentation of the "enroll" process is included in FrugalPup's "Help" facility.

2. Non-uefi boots now use grub4dos to chainload Grub2, rather than directly booting Grub2.
Installing the mbr for grub4dos is a lot simpler than installing the mbr for Grub2.

3. The FrugalPup "BootCD" facility has been re-worked to cleanly ignore installing grub4dos.
Even though it is a non-uefi boot, it still boots Grub2 directly.

gyro

[s243a]

.

2. Non-uefi boots now use grub4dos to chainload Grub2, rather than directly booting Grub2.
Installing the mbr for grub4dos is a lot simpler than installing the mbr for Grub2.

I like that idea I'm going to have to look to see how you did it.

[gyro]

2. Non-uefi boots now use grub4dos to chainload Grub2, rather than directly booting Grub2.
Installing the mbr for grub4dos is a lot simpler than installing the mbr for Grub2.

I like that idea I'm going to have to look to see how you did it.

This is the 'menu.lst':

Code: Select all

timeout 0
default 0

title grub2
  kernel /boot/grub/i386-pc/core.img

gyro

[bigpup]

Tried using f2StickPup 19
It seems to have done everything OK.
Made a bootable install of Bionicpup64 8.0 to a USB flash drive.
sda1 small 100mb partition with boot files on it.
sda2 f2fs partition with Bionicpup64 8.0 frugal install.

Boots OK with secure boot enabled.
Did not have to do any MOK manager stuff, but I had already done that with another install.
So, probably is already setup in computer, to just look for the Puppy MOK.

[bigpup]

In the FrugalPup help. (index.html)

I suggest you make this change to the information on;

<b>DiskPup</b><br />
Does no partitioning or formating; The drive will need to already be partitioned and formatted. <br />
Best to have minimum of two partitions. First partition; a 100mb size, formatted fat32 (boot partition).<br />
One or more other partition(s), any format (ext 3 or 4 recommended), and minimum several GB in size (install location).<br />
Installs a single Puppy linux in a specified directory, and the boot loader (Grub2) in a specified fat32 partition.<br />
The Puppy linux directory can be on the same partition as the boot loader (if there is enough free space), or on a different partition.</p>

[gyro]

@bigpup,
Thanks for testing, and your suggestion.
I have accepted lines 1, 4, and 5.

The modified entry, that will appear in the next version, follows:

<b>DiskPup</b><br />
Does no partitioning or formating; The drive will need to already be partitioned and formatted. <br />
Installs a single Puppy linux in a specified directory, and the boot loader (Grub2) in a specified fat32 partition.<br />
The Puppy linux directory can be on the same partition as the boot loader, or on a different partition.</p>

My rationale for not using lines 2, and 3, is that I want this stuff to focus on simply, what the utility does.

One day I might write some "How To" stuff, that includes recommendations.

gyro

[gyro]

FrugalPup 20, DiskPup 20, StickPup 20 and f2StickPup 20 - Puppy frugal installer.

Download extra sfs 'frugalpup_20.sfs' from http://www.mediafire.com/folder/rdyc5lgzpeij1/frugalpup (2.9 MiB).

This release contains a feature and a bug-fix.

Feature:
If Puppy install directory is on an 'f2fs' partition, pupmode=12 will be used rather than pupmode=13.
'bootentry' always uses "pmedia=???hd" for 'f2fs' partitions.

Bug:
'f2StickPup' frequently fails to format 'f2fs' partition, fixed.

gyro

[01micko]

Tested out stickpup and f2stickpup and both seem to work fine in a dev version of slacko I built.

At first they wouldn't boot so I tried to do a debugsave and kept getting errors which was a bit perplexing. It turns out that there is a bug in that script that fails to save the variable $mount_point so the files were copied to '/' which I manually copied over to a drive. That allowed me to debug my issue.. simply unplugging my powered usb hdd fixed that, but I dare say wait4usb needs some attention as I could proceed with boot to functional desktop running ./init manually.

I fixed the debugsave file in woof. See commit 01bae0f so an indirect thanks must go to you for that fix! Thanks

[gyro]

Tested out stickpup and f2stickpup and both seem to work fine in a dev version of slacko I built.

At first they wouldn't boot so I tried to do a debugsave and kept getting errors which was a bit perplexing. It turns out that there is a bug in that script that fails to save the variable $mount_point so the files were copied to '/' which I manually copied over to a drive. That allowed me to debug my issue.. simply unplugging my powered usb hdd fixed that, but I dare say wait4usb needs some attention as I could proceed with boot to functional desktop running ./init manually.

I fixed the debugsave file in woof. See commit 01bae0f so an indirect thanks must go to you for that fix! Thanks

You're welcome.
Thanks for testing.

Actually I should thank you for FrugalPup.
It was as I was playing with your 'install2usb' that I conceived 'FrugalPup'.

gyro

[gyro]

I have uploaded "FrugalPup" help pages to http://www.fishprogs.software/puppy/fru ... index.html.
"MOK manager" help page can be viewed at http://www.fishprogs.software/puppy/fru ... p-mok.html.

gyro

[01micko]

I have uploaded "FrugalPup" help pages to http://www.fishprogs.software/puppy/fru ... index.html.
"MOK manager" help page can be viewed at http://www.fishprogs.software/puppy/fru ... p-mok.html.

gyro

I created a wikka entry for FrugalPup with a very brief explanation and links to your index page and the first page of this thread. Let me know if want anything in that wikka page changed.