Ltsp-build-client

Usage
The default behavior of ltsp-build-client can be configured with commandline options or using the ltsp-build-client.conf configuration file.

The possible full usage is different for each distribution, refer to your distro's installation page for those details. Also, the following command shows all distro specific options:

[[File:developer-24x24.png]] Plugins
The command is able to perform a distro specific client installation by making use of plugins. When starting, plugins are called by the "load_plugins" function. Common plugins are located in /usr/share/ltsp/plugins/ltsp-build-client/common, while vendor-specific plugins are defined in /usr/share/ltsp/plugins/ltsp-build-client/$DISTRO. If a distro plugin has the same filename as a common plugin, it will override the common plugin. The plugin code is used in different phases. A plugin typically only uses some of the available phases.
 * 1) commandline
 * 2) configure
 * 3) before-install
 * 4) install
 * 5) after-install
 * 6) finalization

Commandline
Any commandline options for ltsp-build-client are defined here. The commandline argument itself can be specified as well as the value type (string or boolean). Also a description and an "advanced" flag for display in the regular help section or the advanced help section. The syntax is as follows: add_option " " "`eval_gettext " "`" "" ""

Configure
Any commandline or config file options can be processed here. The commandline options will be available as $option_ _value, where any dashes in the option name will be converted to underscores. The config file variables are available as is.

Install
In this phase the initial chroot is built. This will obviously vary greatly for each distro.

Finalization
In the finalization phase, you may want to install additional packages that needed custom configurations to other software before installing, such as a kernel (which may require certain initramfs tweaks). you may also want to copy the kernel images into a location accessible by tftp at this phase, or seed the chroot's /etc/ssh/ssh_known_hosts file with your server's public ssh keys.