![]() For common variables, Ventoy will pop up a prompt box to prompt the user to enter the actual value of the variables.ĥ. Each line in the script can only contain at most 1 variables.Ĥ. The variables name XXX can only contain digits, underscores and letters. The auto installation script which contains variables must be in UTF-8 encoding.Ģ. The variables must be in $$XXX$$ format (XXX is the variables name).ġ. So Ventoy supports Variables Expansion in the auto installation script since 1.0.77. So this may install the OS to the wrong disk, or even to the disk where Ventoy is located.īesides, sometimes we want to dynamically input some variables when install, for exmaple ComputerName UserName. The most common is the disk name or disk id.įor example, we set DISK0 or /dev/sda in the auto installation script file, but in some computer, When we do auto installation, there are some configurations in the installation script that cannot be fixed and hard-coded. 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 with the 1st installation templateĢ: boot with the 2nd installation templateģ: boot with the 3rd installation template If you set it, that means you auto select the corresponding option in the prompt menu. Can be a single string or an array of strings. The full path of the installation template for the iso file. All iso files under this directory will use the same template. This option supports fuzzy matching, please refer About Path Matching "template": "/ventoy/script/suse_autoyast.xml" "/ventoy/script/windows_unattended8.xml", "/ventoy/script/windows_unattended7.xml", "/ventoy/script/windows_unattended5.xml", "/ventoy/script/windows_unattended4.xml", "/ventoy/script/windows_unattended3.xml", "/ventoy/script/windows_unattended2.xml", ![]() "/ventoy/script/windows_unattended1.xml", "template": "/ventoy/script/centos_kickstart.cfg" Refer VentoyPlugsonĪ auto_install array is defined to describe the auto installation configuration in /ventoy/ventoy.json. Recommend to use VentoyPlugson, a GUI ventoy.json configurator. You need to modify it for your hardware enviroment, especially the configuration for disk partition. In theory, as long as the distribution supports automatic installation through script or template, Ventoy can support it,ĭistros based on them are also supported.Īttention! The sample script here is just for reference. ![]() You can also update these scripts whenever you want. You can specify more than one scripts for an iso file at a time, ventoy will provide a menu to choose before boot. The USB drive and tell ventoy, that's all. You just need to put a script or template in You don't need to recreate a new iso file, just use the original one. Script or template into the new iso file. In normal case, if you want to make an unattended deployment, you need to recreate a new iso file based on the original iso file, and add the ![]() You just need to give a script or template for the installation.įor example, unattend xml for Windows, kickstart script for Redhat/CentOS, autoYast xml for SUSE, preseed script for Debian and so on. ![]() Many distros provide unattended deployment solution. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |