GUI Tab: Larchify

You can repeat the 'larchify' command as often as you like, to test various configurations or to build differently configured live systems with the same underlying packages. This works because the 'larchify' process itself does not change anything within the installation - all the files it generates are placed in the 'overlay', which (thanks to aufs) will just cover up any old versions of the added files in the underlying installation. At present larch does not support the 'deletion' of installation files, they can only be overlayed by replacements.

Locales

You can select the (glibc) locales supported by the live system by editing the /etc/locale.gen file in the overlay. If there is no such file initially it will be copied from the new installation's (not the host's!) version. See (for example) the Arch Wiki for more information about locales. Note that larch tries to leave the locale files in the installation itself unchanged, new files are placed in the overlay.

/etc/rc.conf

This is the central configuration file for an Arch Linux system. You can edit it here (see for example the Arch Wiki for more information about this file).

Advanced options - the defaults are normally fine

mkinitcpio.conf

Here you can edit the mkinitcpio.conf used for building the initramfs for the live system. N.B. The details of mkinitcpio handling in larch are a bit complicated, so if you change something here please be careful - you are not editing /etc/mkinitcpio.conf, but rather etc/mkinitcpio.conf.larch0 in the 'rootoverlay' of the profile. Also, don't change the larch hooks.

overlay

Apart from the few customization options offered by the GUI directly, it is possible to include any files in the live system by adding them at the appropriate path within the overlay directory ('rootoverlay') of the profile. This button opens a file browser on the 'rootoverlay' directory of the current profile.

ssh-keys

See ssh host keys. The default is to generate these keys (if the openssh package is installed).

Reuse existing system.sqf

After 'larchify' has been run, the base installation will have been 'squashed' into a compressed archive. Setting this option will prevent the repetition of this compression (which is quite a lengthy process) on the next run of 'larchify'. This should only be enabled if no changes have been made to the base installation (otherwise these changes will not be picked up). This is a very useful option, also for non-'advanced' users, but I have put it in the 'advanced' section because you really need to consider whether you have changed anything in the installation before using it.