Booting modern PUPPY from USB only via its download (DOGs too)

[hundido]

This looks really cool. I want to try this soon, and downloaded the iso. I just haven't yet. But cool creation. Thank you in advance.

Edit: here goes the try.

Unzipped the download. md5sum is good.
Read the instructions. They basically say burn the image to the usb?

I have a USB that I etched many times. Let's see how it goes.
Using Gparted to make an msdos partition table. Do I format the whole thing to ext3 since it's low error? I'll try that. K, 57 Gb of ext3. I think that drive used to be 64 Gb. Hmm...
Using USBimager
It says the image was written successfully.
I tried to boot on my other computer. I'm going to take a pic from my cell phone. I don't know what to do from here.

[hundido]

20210813_223015.jpg (72.96 KiB) Viewed 3144 times

What do I do from here?

[bigpup]

This is going to do a search for all OS's it finds on computer.
Next gives you a menu to select which OS to boot.
Next shows the specific OS boot menu.
So, you actually go through 3 menus, before the OS actually boots up.

On that Super Grub2 menu. (your image of it)
Select the entry at the top.
Detect and show boot methods.
It will search on all drives for what it finds for bootable OS installs.
A new menu will pop up showing what it found.
The Installs on the USB will be listed at the end of that menu.
Select one to boot it.

Note:
(Each OS has it's own boot loader menu for the boot loader in it).

That will bring up the boot loader menu that is for the specific OS you selected.
Select the first entry. (that is normal boot)
The OS boot process should now go through booting to a working desktop.

Note:
The boot menu for each specific OS may have other than the normal boot entry.
Depends on the OS what other boot options it offers, but the first one is the normal boot.
Most entries have some info on what they do.

[bigpup]

Tried a burn of the dd-2GB_SG2D-f2fs.img

As I already talked about possible issues, with f2fs format, and the support for it, in the Puppy version you use, to do the burn.
What the Gparted in it can do with f2fs format.

This is what I ended up with, in Gparted, for info on the f2fs formatted 2nd partition.

Screenshot(2).jpg (29.2 KiB) Viewed 3131 times

.
.
Here you can see Gparted cannot grow it's size.

Screenshot(3).jpg (14.09 KiB) Viewed 3131 times

.
So, the f2fs-tools in this version of Puppy is not a new enough version.
It seems to also have a bug in creating a f2fs format.

[Clarity]

What do I do from here?

Good question.
Answer
You should have hit the Enter key as soon as you got that menu. That will find all bootable OSs, including the PUPs+DOGs.
Thus,

1. hit the Enter key at 'Detect and show ..'

   

   dd-2GB_SG2D-f2fs.jpg (13.15 KiB) Viewed 3086 times

2. wait about 30-45 seconds while GRUB2 collects all bootables it finds.

3. When the next orange menu emerges, page to the screen's bottom for the list of all PUPs & DOGs.
   Hit the enter key for whichever distro you want in the list.

Enjoy.
P.S. Let us know if you run into any other issues. The one you hit was mentioned in a request to add that instruction to the opening post. I think it a good idea to do so.

[bigpup]

Update to using the dd-2GB_SG2D-f2fs.img and will the operating system, you burn it in, have the needed support for f2fs format, making and resizing.

Using a newer Puppy version, that has newer versions of the needed f2fs support files/programs.
Burning the image and resizing the 2nd partition, was no problem.
This is what Gparted shows for support.

Screenshot(6).jpg (42.37 KiB) Viewed 3092 times

.
Notice this Gparted can create, grow, and check f2fs formats.
Where an older version of f2fs support did not do grow or check.

[Clarity]

I had just completed testing where I was trying to recreate the conditions you had reported, earlier. I:

1. downloaded the f2fs image.

2. compared the md5.

3. burned to a 8GB stick.

4. booted the stick on 4 PCs

and could NOT hit any problems at all in using the stick or the ISOs it displays.

I did follow-up those tests with further testing with multiple USB sticks inserted at the time of boot to investigate the other errors I had with new USB sticks. In my case additional USB sticks did not cause a problem. At PC boot, I merely entered its BIOS and selected the correct stick and again, each test booted without errors. I have not retested using the new USB 3.2 sticks.

So the f2fs image is currently OK and boots its PUPs-DOGS without issues...same as the ext image.

Thanks @bigpup for the follow-up report. We are seeing consistent behavior.

[redandwhitestripes]

Interesting. I have Windows 10 and Linux Mint on my HD, I am going to try and drop Fossapup and Batocera ISOs onto the stick and see what happens. I will also need to figure out how to point Batocera to my game roms as I don't want to copy all of them onto the stick. Will report back.

[Clarity]

@redandwhitestripes when you create the USB, you will notice that it already has FossaPUP64 and few other PUP-DOGs already present.

As has been suggested, earlier, at some point you will want to expand the 2nd partition to make room for more modern PUPs or modern forum DOGs you might desire. All ISO files are to be placed in the USB's BOOTISOS folder, as that is the place that SG2D searches for ISOs to list, on screen, for your boot selection.

Also, if you have Windows or other OS installed on your HDD, it will list those as well for your selection.

Have fun: this is to make it easy for us to add and boot PUPs with no regard beyond a mere download. No additional needs are required for PUP-DOG ISOs.

[redandwhitestripes]

EDIT: After wasting two hours on USB sticks that I should have remembered also failed me when trying to install Puppy, I finally had the sense to use a more reliable flash drive and voila! All is working well! I have extended the partition and dropped Batocera Linux in to the right folder but for whatever reason it doesn't get picked up at boot.

@clarity, thank you, and what is the most simple tool for creating a backup of my now working flash drive in case it gets lost, broken, etc?

Also, is there any way to add a default option for loading, so if I do nothing after 10 seconds, it loads windows? Thanks again.

[Clarity]

... Batocera Linux ... is there any way to add a default option for loading ...

Glad you got it operating.
Batocera looks like it's not a ISO on Distrowatch. SG2D does not boot IMG files. There's another solution for that and I hope to show that later in the week.

SG2D is a "selection" approach as it is distributed. So, it's design is to present a screen of what it finds and allow the user to choose what to boot. If you boot your PC normally, without the USB, your default OS starts...correct?

Add any modern PUP or DOG to your liking. I am not a gamer, but I have noticed a plethora of games and such in FossaPUP64, here.

Enjoy.
P.S. Someone else may know of a PUP/DOG that is "geared/suitable for gaming". If so, would you PM @redandwhitestripes with your suggestion.

[bigpup]

dropped Batocera Linux in to the right folder but for whatever reason it doesn't get picked up at boot.

This is because Batocera is an image package.
This only works for ISO packages.

If you can get it in an ISO package, it should work.

[Clarity]

YES, @bigpup: Assuming its boot approach is similar or matches modern PUPPY Linux; namely a matching GRUB2-EFI-loopback.cfg that PUPs-DOGs now use which makes this SG2D solution so simple to boot ISO files.

[Grey]

Batocera Linux

Hi. Batocera is a "colleague" of RetroPie. RetroPie, in turn, is based on RetroArch. You can simply install RetroArch for Fossapup. By the way, 666philb added it to the repository.

There are other emulators in the topic. For example MAME.

[redandwhitestripes]

This is great, thanks to all not only for the help but also for educating me.

MAME is built in to retroarch so now I have a project to work on: get Retropie working inside puppy.

[Grey]

get Retropie working inside puppy.

If a complete RetroPie is needed, then it has an installation script for Ubuntu. In theory, it should work for Fossapup too. Of course, you should ignore commands like "apt install" and install dependencies from the PPM instead.

But I don't see the point in that. RetroPie is 32-bit only. And RetroArch is 64-bit and can do the same thing.

[redandwhitestripes]

Got retropie working but the presentation is so much better when it's inside emulation station. That app seems to have a lot of dependencies and whatnot so I'll just stick to Batocera.

@Clarity is there any way to know ahead of time which isos are likely to boot from the script? I've tested Bionicpup, puppy arcade, and freeBSD but they don't seem to work. My next plan is Haiku OS.

[Clarity]

@Clarity is there any way to know ahead of time which isos are likely to boot from the script? ...

Yes, there is a way: Use any modern (meaning since Dec 2019 to now) WoofCE PUPs or DOG ISOs.

Those PUPs-DOGs have all necessary structures for SG2D to find and list them (as well as your current Windows and installed Linux OSes on your drives.

The PUP-DOG boot models are consistent with Ubuntu boot models, as well. So, for example, I have tested Ubuntu and MX distros on the same USB: They, too, are found and presented for booting, as well.

Older PUPs before, do not have the advancements that GRUB2 has afforded Puppy Linux found on the modern PUPs.

AND, many other OSes may not be using the Ubuntu-Puppy-DOG GRUB2-EFI 'model' that allows booting on BIOS+UEFI PCs.

Hope this info is helpful understanding that this solution is a rather Puppy "proprietary" solution for Puppy forum members and its users.

[redandwhitestripes]

Excellent information, many thanks.

[shinobar]

@Clarity
This is nice. But the usage of the Super Grub2 menu is to be shown at the top post of this thread.

On that Super Grub2 menu. (your image of it)
Select the entry at the top.
Detect and show boot methods.
It will search on all drives for what it finds for bootable OS installs.
A new menu will pop up showing what it found.
The Installs on the USB will be listed at the end of that menu.
Select one to boot it.

[geo_c]

Folder layout for consistent management of distro operations

• The ISO files are ALL kept on the USB in its 'BOOTISOS' (actual name) folder.

• Each PC has a Linux partition with a 'Sessions' (actual name) folder where ALL save sessions from every distro is contained.

Well I stumbled on this thread right on time, since I'm doing some scripting along the lines of changing and storing theme settings on Fossapup. I've also been wanting to try out other pups. So I downloaded the SG2D and used @wiak's terminal command to flash to disk, and now I'm in a fresh boot of Fossapup. All went well.

So two things,

• How do I get an option to load a pupsave at boot?

• Do I need to be booted off another drive to expand the second partion with Gparted? I'd like to expand this partion and start downloading iso's. Or does the boot sequence look for partitions with folders named "Sessions?"

[Clarity]

So two things,

1. How do I get an option to load a pupsave at boot?

2. Do I need to be booted off another drive to expand the second partion with Gparted? I'd like to expand this partion and start downloading iso's. Or does the boot sequence look for partitions with folders named "Sessions?"

Hello GC
Answers (based upon my several years of using these methods
A. ... pupsave ...

1. On EVERY PC, I have a Linux partition on its system drive that I label "Persistence" AND on that partition, I make a folder named "Sessions" to house ALL of my sessions no matter which PUPs I boot.

2. On Boot of the USB I choose the PUP-DOG I want to boot from the list the USB presents

3. On the selected PUP's Menu, I on its top line, I interrupt the boot by hitting "e" to edit the stanza line

4. I add the options "psave=<partition name-number>:/sessions foldername/" and allow the PUP-DOG to boot after entry. Example "psave=sda7:/Sessions/"

ALL modern PUPs-DOGs and find their appropriate save-session(s) in my Sessions folder when booting...if present (There will be none on a pristine boot. On pristine boots, the PUP will show your session folder for saving at shutdown.)

B. ... Do I need to be booted off another drive ...

• In most every case, the PUP-DOG boots without mounting your USB when you arrive a desktop.

• Such is the case, as, you can expand or manipulate your USB's 2nd partition as you see fit.

My setup is to eliminate ANY misunderstand AND to keep everything is a simple organized manner ... consistent across all of my PCs that I use/test.

Enjoy!

[geo_c]

On the selected PUP's Menu, I on its top line, I interrupt the boot by hitting "e" to edit the stanza line.
I add the options "psave=<partition name-number>:/sessions foldername/" and allow the PUP-DOG to boot after entry. Example "psave=sda7:/Sessions/"

Well I'm still coming up empty on getting fossapup to find the save folder when booting from a Sandisk Ultra Fit with the sdb2 partition grown to fill the full 128GB stick. I've tried on two different laptops 5 and 10 years old.

I'm not well versed in the syntax of the stanza line. Not sure what the 'stanza' actually is. But here's what I've tried so far:

Code: Select all

setparam 'fossapup64 9.5'

                 linux /vmlinuz pfix=fsck pmedia=cd find_iso=${iso_path}
                 initrd /initrd.gz
                 psave=sdb2:/saves/

That one clean boots into RAM.

Code: Select all

setparam 'fossapup64 9.5'

                 linux /vmlinuz pfix=fsck pmedia=cd find_iso=${iso_path}
                 initrd /initrd.gz psave=sdb2:/saves/

That one says 'invalid file name' and results in kernel panic

Code: Select all

setparam 'fossapup64 9.5'

                 linux /vmlinuz pfix=fsck pmedia=cd find_iso=${iso_path}
                 initrd /initrd.gz 
                 psave=hd0:/saves/

And that one clean boots into RAM also.

NOTE:None of my hard drives show up in supergrub for some reason. I notice there's an entry for booting in BIOS mode, but choosing gives the message: sorry, booted in efi mode, try using BIOS compatibility mode.

So at the moment it's a good tool to check out distros, but not to use as a persistent system boot stick.

[Clarity]

HI @geo_c
I saw this from you and wanted to share that statement it is not true, as persistence works!

... but not to use as a persistent system boot stick.

Puppy parms are always placed on the linux line. ... for example pfix=, pmedia=, etc.

Try modifying the vmlinux line (this is where any/all PUP boot parms are placed in case you use other boot parms in the future)

• On the PUP's top line, hit the 'e' to edit the top-line stanza on the screen showing all the lines in the stanza, add the 'psave'

  Code: Select all

  linux /vmlinuz pfix=fsck pmedia=cd find_iso=${iso_path} psave=sdb2:/saves/

This tells the PUP "during boot, open sda2 and find the folder you named /saves"; in that folder PUP init will check for the presence of the save file/folder (fossapup64save in your case) for your booting distro.

Important fact to know: Upon shutdown, your PUP will store your save-session on sda2 in folder /saves/ for you.

I use a folder named /Sessions and keep ALL of my save-sessions in that folder. In your case, you are making your folder named /saves. Works the same.

If I get a moment I will try to create a gif image showing this, but I think you get the picture. Or, if you know how to make a gif, you might do so to show the easy step.

Post back here when you complete, so we can help you thru this.

[geo_c]

Post back here when you complete, so we can help you thru this.

OKAY! That did the trick. I knew I just didn't know where to put the parameter. Now I get it. I thought it was all one line wrapped. So don't put it on the kernel line or it panics, and don''t put it on it's own line because that does nothing.

Thanks, this is going to open up a world of fun.

[Clarity]

Great

this is going to open up a world of fun.

One question: Would you like to know a wee tiny bit more about the "world of fun"?

[geo_c]

One question: Would you like to know a wee tiny bit more about the "world of fun"?

Of course!

[geo_c]

@Clarity

Does it matter where on the sdb2 drive I store .sfs packages? It seems with all manner of distros in the BOOTISOS folder, those sfs files should be sorted as to what systems they are built for, like in separate folders. Normally I put them in the same folder as the frugal install, as the load sfs dialog recommends.

EDIT:

Well I just put the sfs files and portable app directory on the sdb/ directory, and it's all working well! I'm thinking at this point that having frugals on the hard drives of my machines isn't going to be necessary in the future. I'll be looking at making a couple of these USB sticks.

[Clarity]

Hello @geo_c Sorry for the absence.

... I'm thinking at this point that having frugals on the hard drives of my machines isn't going to be necessary in the future. ...

YES! That is the benefit to use of this methods. It removes all of the past hardships of Frugals from the frugal process of getting the download ISO properly managed, to disk locations, to boot manager changes, to disk issues of Frugal bases, to ...... "GONE!" All of those nightmarish issues taking our time just to get to the PUP's desktop, are now gone!"

For those of us who have discovered this benefit, we merely download and boot the desired PUP/DOG from its ISO file and save all session changes in our persistence folder. (Identical to what the old frugal method provides.)

The benefit is that it is identical to a Frugal operation; in fact, it is a Frugal without the hassles.

...I'll be looking at making a couple of these USB sticks.

I assume you mean that you will make 1 for permanent on one PC and another for travel. The ONLY thing I have on any USB is /BOOTISOS folder with the myriad of ISO files contained within it.

BTW: I assume you have seen the picture in this post. If so, it shows how 1 USB boots every PC shown. I have a /Sessions folder on EVERY PC I now touch for obvious reasons.

[vtpup]

Any chance you could do this just for Fossa and not the other three pups for us internet connection challenged? 3 mbits/sec at best here on DSL in rural Vermont. Then we could add later whatever we wanted. 2gb download takes 2 hours+, assuming no other family member is using the Internet.