Puppy Linux Discussion Forum

@fredx181 @Clarity

Hi

I found simple way to boot DogLinux with Porteus Initrd with Ventoy
From .iso file in grub2 mode

Just replace from=/ with from=$vt_chosen_path

And don't require to enable VTOY_LINUX_REMOUNT=1

EDIT: For my custom build need to do something with extramod=/live/firmware
Currently i boot .iso with my build from ventoy.img in Qemu only.
It is a problem, because i am not sure about how to load extramod= from .iso file.
I will look for ways to fix this later.
EDIT2: Hmm. No problem. All boot variants loaded ok.

Don't need this crap anymore

Clarity wrote: Wed May 05, 2021 9:30 pm

Hello @gumanzoy. Saw the last 2 post on this thread and offer some info.

Ventoy can be made to run on other filesystem vs exFAT. Its not too difficult to change the filesystem on the booting USB while maintaining the boot expectations. It is described on the Ventoy forum.

The reason that author uses exFat is because of his view of the OS world which includes MACs & Windows; namely flexibility.

As for the DOG/PUP community, you will find implementations of almost every filesystem known to man. EAch author, here, can choose the FS he wants to enHello @gumanzoy. Saw the last 2 post on this thread and offer some info.

Ventoy can be made to run on other filesystem vs exFAT. Its not too difficult to change the filesystem on the booting USB while maintaining the boot expectations. It is described on the Ventoy forum.

The reason that author uses exFat is because of his view of the OS world which includes MACs & Windows; namely flexibility.

As for the DOG/PUP community, you will find implementations of almost every filesystem known to man. EAch author, here, can choose the FS he wants to enclose when building.

I prefer to use SG2D versus Ventoy for its simplicity in PUP-DOG ISO boots.

BTW, @gumanzoy you can ALSO add the SG2D ISO to a Ventoy USB and have the luxury of using either to boot ISO files to desktop. To insure compatibility with BOTH, PLEASE put all your ISO files in a folder on the USB named BOOTISOS. This way both Ventoy and SG2D's ISO will find all the ISOs and present them for booting. SG2D gets past some of the few issues that arise in Ventoy when attempting to boot some PUP ISOs. In that case, you boot the USB and on the Ventoy menu, select SGbuild-x86_64-slackware64-15.0-112D and it will find and list the same ISOs: And the problematic "Ventoy boot" for some of the ISOs, disappear.

An example of a Ventoy boot process using USB with a ext4 format vs exFatPC boot process.png

This is presently tested. Hope this clears some concepts.

It is possible to add code to grub.cfg to make universal config. For Ventoy and for other cases.

if [ -n "$vt_chosen_path" ]; then set from="$vt_chosen_path"; else set from=/ ; fi

EDIT: Maybe set is not needed

if [ -n "$vt_chosen_path" ]; then from="$vt_chosen_path"; else from=/ ; fi

Good to do this also.

https://www.ventoy.net/en/doc_name_identifier.html

2. If the ISO file name ends with _VTGRUB2, Ventoy will automatically use GRUB2 mode. For example: ubuntu-22.04-desktop-amd64_VTGRUB2.iso

https://ventoy.net/en/doc_compatible_mark.html

If the OS in the iso file is "Ventoy Compatible", there must be some way for Ventoy to know that it is ventoy compatible. Once Ventoy treats the iso file as Ventoy Compatible, it will just make the virtual disk and will not do the hook.

Option 1
Just put a file with name ventoy.dat or VENTOY.DAT in the root directory of the iso image (inside of the ISO). The content of the file doesn't matter, however this file (ventoy.dat) is recommended.

gumanzoy wrote: Wed Jan 08, 2025 3:11 pm

EDIT: For my custom build need to do something with extramod=/live/firmware
Currently i boot .iso with my build from ventoy.img in Qemu only.
It is a problem, because i am not sure about how to load extramod= from .iso file.
I will look for ways to fix this later.

Hmm. No problem. All boot variants loaded ok.

extramod=/live/firmware

extramod=/live/firmware\;/live/dk5