crosdiscover.blogg.se

#Ventoy json iso#
#Ventoy json download#

That means extend persistent.dat by 2048MB (+2GB), if the old size is 1GB, then it will grow to 3GB after you extend it. Sudo bash ExtendPersistentImg.sh persistent.dat 2048 Sudo bash ExtendPersistentImg.sh datfile extend_size_mb

#Ventoy json download#

Just download and run it in a linux shell as follows: Here I provide ExtendPersistentImg.sh script for you to nondestructively extend the persistent dat file. Of course you can use a new bigger persistence dat file, but you need to backup and restore your old data. Sometimes, you may find that the persistence space is insufficient after a period of use.

Once you have made a backend image file, you can compress and save it as a template in your computer (very small after compressed).

It can be in the root directory or any subdirectory.

The backend image file must be put in the first partition.

Different distros use different Labels by default, for example ubuntu use casper-rw and MX Linux use MX-Persist, you can use -l to set it.

When creating the image file and copy to USB, take care about the buffer.

Sh CreatePersistentImg.sh -l persistence -c nf -> persistence.dat in 1GB size and ext4 filesystem and persistence label. Sh CreatePersistentImg.sh -s 4096 -t xfs -> persistence.dat in 4GB size and xfs filesystem (ext2/3/4 xfs are supported) and casper-rw label Sh CreatePersistentImg.sh -s 2048 -> persistence.dat in 2GB size and ext4 filesystem and casper-rw label Sh CreatePersistentImg.sh -l MX-Persist -> persistence.dat in 1GB size and ext4 filesystem and MX-Persist label Sh CreatePersistentImg.sh -> persistence.dat in 1GB size and ext4 filesystem and casper-rw label I have provided a CreatePersistentImg.sh script here.ĭownload it and just run sudo bash CreatePersistentImg.sh in the linux shell, by default a persistence.dat file will be created with size=1GB fs=ext4 label=casper-rw.

If you don't want to use the pre-created file and want to create it by yourself. You can download pre-created image files from Create by yourself You can directly download the pre-created image files or create it by yourself.

The backend image file is a disk image with a label. Please refer Multi-Mode Option for details. You can set different configurations for different BIOS mode. If autosel not exist, it's the same as it set equal to 0. If autosel exist, then the corresponding menu item will be used and the prompt menu will NOT be popped up anymore. Prompt menu will be popped up, the default selected menu item is as described above, no timeout, will wait for user selection all the time. Prompt menu will be popped up, the default selected menu item is as described above, when timeout the corresponding menu item will be selected. Optional, if you set it, the value must be greater than or equal to 0 If not set, default is 1.Ġ: boot without persistence backend image fileġ: boot with the 1st persistence backend image fileĢ: boot with the 2nd persistence backend image fileģ: boot with the 3rd persistence backend image file If you set it, that means you auto select the corresponding option in the prompt menu.

#Ventoy json iso#

The persistence backend image file path for the iso file.

This option supports fuzzy matching, please refer About Path Matching Refer VentoyPlugsonĪ persistence array is defined to describe the configuration in /ventoy/ventoy.json.

Recommend to use VentoyPlugson, a GUI ventoy.json configurator. And use Live USB Persistence boot option.įedora-Workstation-Live-x86_64-33-1.2.iso Arch/ArchMan/ArchBang/ArchLabs/BlackArch.