Changes between Version 10 and Version 11 of SaliUsage/Installationparameters
- Timestamp:
- 08/17/10 14:34:54 (14 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
SaliUsage/Installationparameters
v10 v11 5 5 All of the documented kernel boot parameters plus those below may be used during the installation. All the parameters can be appended to the kernel boot parameters in /etc/systemimager/pxelinux.cfg/syslinux.cfg on your image server. 6 6 7 Note that ALL kernel parameters listed below are CASE SENSITIVE, and that a trailing = on the name of any parameter states that that parameter will be entered as an environment variable, whereas its absence indicates that it will appear as a kernel argument readable via /proc/cmdline by programs running once the system is up. The number of kernel parameters is not limited, but the length of the complete command line (parameters including spacesetc.) is limited to a fixed number of characters. This limit depends on the architecture and is between 256 and 4096 characters. It is defined in the file ./include/asm/setup.h as COMMAND_LINE_SIZE7 Note that ALL kernel parameters listed below are CASE SENSITIVE, and that a trailing = on the name of any parameter states that that parameter will be entered as an environment variable, whereas its absence indicates that it will appear as a kernel argument readable via /proc/cmdline by programs running once the system is up. The number of kernel parameters is not limited, but the length of the kernel command line (including parameters, spaces, etc.) is limited to a fixed number of characters. This limit depends on the architecture and is between 256 and 4096 characters. It is defined in the file ./include/asm/setup.h as COMMAND_LINE_SIZE 8 8 9 9 == SALI kernel boot parameters == … … 16 16 17 17 === DEVICE=ethi === 18 Set the management interface of the client to ethi. The client will contact the image server on that interface. Starting from SystemImager 3.8.1 this parameter can be used also to force the execution of the DHCP client only on a single interface (default is to try withall the available interface on the client).18 Set the management interface of the client to ethi. The client will contact the image server on that interface. Starting from SystemImager 3.8.1 this parameter can be used also to force the execution of the DHCP client only on a single interface (default is to try all the available interface on the client). 19 19 20 20 === IPADDR=x.x.x.x === … … 86 86 87 87 === MONITOR_CONSOLE=yes|no === 88 If set to yes enable full console view. W hen full console is enabled it's possible to follow all the installation session of theclients (stdout and stderr). See Monitoring for more details.88 If set to yes enable full console view. With full console is enabled it is possible to follow the full installation process on clients (stdout and stderr). See Monitoring for more details. 89 89 Default is: no. 90 90 … … 103 103 104 104 === GRUB2=yes|no === 105 Must we install the grub2 bootloader. It will install the grub2 bootloader on a seperate partition, see: [wiki:SaliUsage/Functions/partition partition function]. 106 Default is: no 105 This flag has been added to be used in the installation script. A recommendation with grub2 is to install it on a separate partition with the flag bios_grub. This is only posible with GPT enabled disk. So this variable has been added to determine which disk table must be used. For a example see this [source:trunk/example/masterscript.new#L27 install script] and [wiki:SaliUsage/Functions/partition partition function]. Default is: no 107 106 108 107 === PROTOCOL=protocol === 109 Select which protoc l must be used for installation of the node(s):108 Select which protocol must be used for installation of the node(s): 110 109 * rsync 111 110 * bittorrent