Changes between Version 10 and Version 11 of SaliUsage/Installationparameters


Ignore:
Timestamp:
08/17/10 14:34:54 (14 years ago)
Author:
dennis
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • SaliUsage/Installationparameters

    v10 v11  
    55All 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.
    66
    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 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
     7Note 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
    88
    99== SALI kernel boot parameters ==
    … …  
    1616
    1717=== 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 with all the available interface on the client).
     18Set 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).
    1919
    2020=== IPADDR=x.x.x.x ===
    … …  
    8686
    8787=== MONITOR_CONSOLE=yes|no ===
    88 If set to yes enable full console view. When full console is enabled it's possible to follow all the installation session of the clients (stdout and stderr). See Monitoring for more details.
     88If 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.
    8989Default is: no.
    9090
    … …  
    103103
    104104=== 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
     105This 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
    107106
    108107=== PROTOCOL=protocol ===
    109 Select which protocl must be used for installation of the node(s):
     108Select which protocol must be used for installation of the node(s):
    110109 * rsync
    111110 * bittorrent