#Ventoy persistence how to
#Ventoy persistence update
#Ventoy persistence full
#Ventoy persistence software
#Ventoy persistence iso

# Liveslak ISO configuration file for SLACKWARE-CURRENT FOR X86_64 (LEAN LIVE 1.6.0) Here is an example of such a configuration file it is copied from my Ventoy disk, for a Slackware LEAN Live ISO image: The script will leave your customizations alone.

The “isocomp.sh” script manages this configuration file for you, but you can safely edit and modify it manually if you want to.

#Ventoy persistence full

The configuration of all these new features is stored in a file with the same name and full path as the ISO file but with a “.cfg” file extension instead of “.iso”.

This differs from containerfiles on a persistent USB stick created with “iso2usb.sh” where the container file extension is “.img”.

Containerfiles managed by “isocomp.sh” have the filename extension “.icc” which is shorthand for “ISO Companion Container” 😉.

creating a secondary liveslak root on the disk partition where you can add more optional/add-on live modules that you need in the Live OS but are not contained in the ISO.

size extension of existing encrypted containers if they threaten to run out of space.

creation of encrypted containers for OS persistence and a persistent homedirectory (actually not just for /home but you can create as many containers as fit on the disk and mount them wherever you want).

This script manages everything mentioned in the previous bullet:

#Ventoy persistence how to

Like with all of my scripts, it accepts a “–help” parameter which will show you how to use it.

A new script, “ isocomp.sh” aka the ISO Companion script, has been added to liveslak.

All of this is possible without the need for any modification to the ISO image.

When you are booting from an ISO file (whether via Ventoy, or through your own hand-crafted Grub menu entry, or Windows BCD), Operating System persistence and an encrypted homedirectory are now supported, as well as the ability to load additional live modules (as ‘addons’ or ‘optional’) that are not part of the ISO.

There is nothing you have to do, this works out of the box.

You’ll see the message “ SLACKWARELIVE: (UEFI) Ventoy ISO boot detected…” (or ‘BIOS’ instead of ‘UEFI’ if you have an older computer). This means, Ventoy won’t apply any “hooks” to liveslak when it boots its ISO image, and liveslak figures out for itself how to boot. Liveslak 1.6.0 implements the “ Ventoy-compatible” guideline. You get these Slackware-current Live ISOs from or from by the way, if you are curious and want to test the latest & greatest of Slackware straight from the press.Īfter releasing liveslak-1.5.4 I took its Ventoy support to the next level and used the opportunity to add a whole new feature set to liveslak.

#Ventoy persistence update

The liveslak ISO images that are generated automatically after every update for Slackware-current already support booting from a Ventoy disk since a month ago. It is fairly trivial for a Live OS maintainer to add support for Ventoy.Īnd actually that’s exactly what I did between the releases of liveslak 1.5.3 and 1.5.4. Ventoy provides “hooks” for a lot of Live OS-es that it already knows about and validated. A Live OS which starts from an ISO needs to know that it boots from an ISO, because its initrd will have to find that ISO file’s location on disk and then mount it in order to start the actual Live OS. Mostly installation ISOs work without issue.įor Live ISOs the situation is more delicate. Ventoy supports a lot of Operating Systems out of the box, in particular when the OS on the bootable image does not have to know it is chainloaded by Ventoy. You can then boot any ISO straight from that menu. Ventoy will automatically populate the Grub boot selection screen with all bootable images it could find on that partition. Then you can put as many bootable images (ISOs, IMGs and so on) on its first exfat-formatted partition as there is room. So what does it do? Ventoy takes a USB stick, formats it and puts a Linux kernel, a Grub bootloader and some smart tools on it.

#Ventoy persistence software

In fact, it is a quite the unique piece of software and I am using it myself now. At first I was like “I don’t care for it, why should I put effort in supporting it” but on second thought and reading through its web pages, my opinion changed in favor of Ventoy. Most of that inactivity was caused by burnout.īut then someone mentioned Ventoy to me, because liveslak ISOs would not boot from a Ventoy disk and they hoped I would be able to fix that.

There are times that it gets less attention though, and in the first half of 2022 there was not much activity – some minor updates whenever I needed to release a fresh batch of Live ISO images. Liveslak is my favorite project, it’s fully under my control, I built it from scratch, I get good improvement ideas from its users and Patrick helps when liveslak needs something new from Slackware.