AppMan VS Ventoy

I have been working on two CLI tools to install AppImage packages system wide and locall (they are AM and AppMan respectively). I've also written a website that acts as a catalog and a better source for downloading them all for real, https://portable-linux-apps.github.io !

3:57, often appear the message "find: './containerd': Permission denied", this is because AM expects you install everything in /opt, to use a version that can work in any container or custom $HOME you want, use the portable version of AM, i.e. "AppMan", at https://github.com/ivan-hc/AppMan

I started writing AM/AppMan two years ago, it was just a custom script to install and always keep any Appimage package I needed updated to the latest version. Then become something much bigger.

AppMan, at https://github.com/ivan-hc/AppMan, a copy of "AM" but portable, it can install everything into a directory of your choice in your $HOME, no root privileges are required.

AppMan, a copy of AM but that allows you to choose where to install the apps in your HOME directory and without root access.

More details at https://github.com/ivan-hc/AppMan

https://github.com/ivan-hc/AM-AppMan ("AppMan", local integration only).

RELEASE: https://github.com/ivan-hc/AppMan/releases/tag/3.0.6.1

Ventoy is an open-source tool to create a bootable USB drive for ISO/WIM/IMG/VHD(x)/EFI files. Using Ventoy, we can create live USB for multiple distros in one flash disk. This is a revolutionary feature compared to other tools, e.g., Etcher, Rufus, etc, that can only create one live USB at a time. This tool is so important. Don't call yourself a distro hopper if you don't know this tool.

I'm thinking you mean Ventoy? They say they can load vhd and img files, though I've only tried ISO's myself.

https://www.ventoy.net/

View on GitHub

I faced it too. There is a PR on the ventoy GitHub repository that fixes Proxmox boot.

https://github.com/ventoy/Ventoy/actions/runs/7088423200

> While this works, I find this method a bit tedious to use, at least compared to Ventoy [0].

I find ventoy more tedious, because you can't use it on your hard drive with a sane partitioning scheme.

The only reason is because of how the ventoy detection hardcode the partition boundaries in its checks, and it means Ventoy can only run with the partitions set in a way that may lead to alignment issues like write-amplification: I've detailed that in https://github.com/ventoy/Ventoy/issues/1342

Ideally I'd have a 10G partition after the EFI (or it could even be the EFI itself) with a few ISOs for rescue purposes + a UEFI entry to avoid having to use a bootable USB, but that's not possible with Ventoy unless I accept Ventoy choices of partition boundaries:

                (pMBR->PartTbl[0].StartSectorId != 2048 ||

I downloaded and made a bootable USB Ventoy (https://www.ventoy.net) with its Windows GUI app in my updated 64-bit W10 Pro PC. However, I couldn't seem to get VirtualBox v7.0.12 to boot it. I read VirtualBox can boot from bootable USB flash sticks so it should work. Am I missing something?

So, yes. The installer will need to install grub to that first partition. You can install ventoy to a usb drive, put a windows iso there and your q4os iso. In case you mess up big time, you can reinstall windows.