Product SiteDocumentation Site

15.10. Starting a Kickstart Installation

Important — Kickstart installations and firstboot

Firstboot は、デスクトップと X Window システムがインストールに含まれていてグラフィカルログインが有効になっていないと、システムがキックスタートファイルから インストールされた後に実行されません。追加のシステムをインストールする前にキックスタート ファイル内に user オプションでユーザーを指定する (詳細には 「Kickstart Options」 を参照) か、root として仮想コンソールでインストール済のシステムにログインして adduser コマンドでユーザーを追加します。
To begin a kickstart installation, you must boot the system from boot media you have made or the Fedora DVD, and enter a special boot command at the boot prompt. The installation program looks for a kickstart file if the ks command line argument is passed to the kernel.
DVD とローカルストレージ
The linux ks= command also works if the ks.cfg file is located on a vfat or ext2 file system on local storage and you boot from the Fedora DVD.
With Driver Disk
If you need to use a driver disk with kickstart, specify the dd option as well. For example, if installation requires a kickstart file on a local hard drive and also requires a driver disk, boot the system with:
linux ks=hd:partition:/path/ks.cfg dd
「Creating Kickstart Boot Media」 で説明してあるように、キックスタートファイルが ブート CD-ROM 上にある場合、 その CD-ROM をシステムに挿入してシステムをブートし、boot: プロンプトで以下のコマンドを入力します (ks.cfg はキックスタートファイルの名前):
linux ks=cdrom:/ks.cfg
Other options to start a kickstart installation are as follows:
Prompt the user to select an installation source, even if a Fedora installation DVD is detected on the system.
Prompt for network configuration in the first stage of installation regardless of installation method.
Make kickstart non-interactive.
Start up pdb immediately.
Use a driver disk.
カスタムの DHCP ベンダークラス識別子を送ります。ISC の dhcpcd は、"option vendor-class-identifier" を 使用して、この値を調べます。
Comma separated list of nameservers to use for a network installation.
'dd' と同等
Turns on special features:
  • allows partitioning of removable media
  • prompts for a driver disk
Gateway to use for a network installation.
Force graphical install. Required to have ftp/http use GUI.
Prompt user for ISA devices configuration.
ネットワークインストール用に使用の IP : DHCP として 'dhcp' 使用
ipv6=auto, ipv6=dhcp
IPv6 configuration for the device. Use auto to specify automatic neighbor discovery or dhcp for a stateful configuration with DHCPv6. You cannot specify a static IPv6 address.
Keyboard layout to use. Valid layouts include:
  • be-latin1 — Belgian
  • bg_bds-utf8 — Bulgarian
  • bg_pho-utf8 — Bulgarian (Phonetic)
  • br-abnt2 — Brazilian (ABNT2)
  • cf — French Canadian
  • croat — Croatian
  • cz-us-qwertz — Czech
  • cz-lat2 — Czech (qwerty)
  • de — German
  • de-latin1 — German (latin1)
  • de-latin1-nodeadkeys — German (latin1 without dead keys)
  • dvorak — Dvorak
  • dk — Danish
  • dk-latin1 — Danish (latin1)
  • es — Spanish
  • et — Estonian
  • fi — Finnish
  • fi-latin1 — Finnish (latin1)
  • fr — French
  • fr-latin9 — French (latin9)
  • fr-latin1 — French (latin1)
  • fr-pc — French (pc)
  • fr_CH — Swiss French
  • fr_CH-latin1 — Swiss French (latin1)
  • gr — Greek
  • hu — Hungarian
  • hu101 — Hungarian (101 key)
  • is-latin1 — Icelandic
  • it — Italian
  • it-ibm — Italian (IBM)
  • it2 — Italian (it2)
  • jp106 — Japanese
  • ko — Korean
  • la-latin1 — Latin American
  • mk-utf — Macedonian
  • nl — Dutch
  • no — Norwegian
  • pl2 — Polish
  • pt-latin1 — Portuguese
  • ro — Romanian
  • ru — Russian
  • sr-cy — Serbian
  • sr-latin — Serbian (latin)
  • sv-latin1 — Swedish
  • sg — Swiss German
  • sg-latin1 — Swiss German (latin1)
  • sk-qwerty — Slovak (qwerty)
  • slovene — Slovenian
  • trq — Turkish
  • uk — United Kingdom
  • ua-utf — Ukrainian
  • us-acentos — U.S. International
  • us — U.S. English
The file /usr/lib/python2.6/site-packages/system_config_keyboard/ on 32-bit systems or /usr/lib64/python2.6/site-packages/system_config_keyboard/ on 64-bit systems also contains this list and is part of the system-config-keyboard package.
The installation program looks for the kickstart file on the NFS server <server>, as file <path>. The installation program uses DHCP to configure the Ethernet card. For example, if your NFS server is and the kickstart file is in the NFS share /mydir/ks.cfg, the correct boot command would be
The installation program looks for the kickstart file on the HTTP server <server>, as file <path>. The installation program uses DHCP to configure the Ethernet card. For example, if your HTTP server is and the kickstart file is in the HTTP directory /mydir/ks.cfg, the correct boot command would be ks=
The installation program mounts the file system on <device> (which must be vfat or ext2), and looks for the kickstart configuration file as <file> in that file system (for example, ks=hd:sda3:/mydir/ks.cfg).
The installation program mounts the file system on the specified partition on the specified BIOS device <biosdev>, and looks for the kickstart configuration file specified in <path> (for example, ks=bd:80p3:/mydir/ks.cfg). Note this does not work for BIOS RAID sets.
The installation program tries to read the file <file> from the file system; no mounts are done. This is normally used if the kickstart file is already on the initrd image.
The installation program looks for the kickstart file on CD-ROM, as file <path>.
If ks is used alone, the installation program configures the Ethernet card to use DHCP. The kickstart file is read from NFS server specified by DHCP option server-name. The name of the kickstart file is one of the following:
  • If DHCP is specified and the boot file begins with a /, the boot file provided by DHCP is looked for on the NFS server.
  • If DHCP is specified and the boot file begins with something other than a /, the boot file provided by DHCP is looked for in the /kickstart directory on the NFS server.
  • If DHCP did not specify a boot file, then the installation program tries to read the file /kickstart/, where is the numeric IP address of the machine being installed.
The installation program uses this network device to connect to the network. You can specify the device in one of five ways:
  • the device name of the interface, for example, eth0
  • the MAC address of the interface, for example, 00:12:34:56:78:9a
  • the keyword link, which specifies the first interface with its link in the up state
  • the keyword bootif, which uses the MAC address that pxelinux set in the BOOTIF variable. Set IPAPPEND 2 in your pxelinux.cfg file to have pxelinux set the BOOTIF variable.
  • the keyword ibft, which uses the MAC address of the interface specified by iBFT
For example, consider a system connected to an NFS server through the eth1 device. To perform a kickstart installation on this system using a kickstart file from the NFS server, you would use the command ks=nfs:<server>:/<path> ksdevice=eth1 at the boot: prompt.
ks=http:// 要求に HTTP ヘッダーを追加します。これは provisioning システムに役に立ちます。 "X-RHN-Provisioning-MAC-0: eth0 01:23:45:67:89:ab" 形式の CGI 環境変数内の全ての nic の MAC アドレスを含んでいます。
インストールで使用する言語です。これは 'lang'キックスタートコマンドと共に使用する のに有効な言語でなければなりません。
Set the minimum level required for messages to be logged. Values for <level> are debug, info, warning, error, and critical. The default value is info.
Activates loader code to give user option of testing integrity of install source (if an ISO-based method).
Netmask to use for a network installation.
If GUI fails exit.
Do not load the VGA16 framebuffer required for doing text-mode installation in some languages.
Do not load support for firewire devices.
Disable IPv6 networking during installation.

このオプションは PXE インストール中には利用できません。

PXE サーバーからのインストール中に、IPv6 ネットワーキングは anaconda が キックスタートファイルをプロセスする前にアクティブになる可能性があります。そうなると、このオプションは インストール中に何の効果も持ちません。
インストールした Linux パーティションを自動的に、レスキューモードでマウントしません。
Do not auto-probe network devices.
Do not attempt to load support for parallel ports.
Do not pass information about the keyboard and mouse from anaconda stage 1 (the loader) to stage 2 (the installer).
Ignore PCMCIA controller in system.
Do not automatically probe for hardware; prompt the user to allow anaconda to probe for particular categories of hardware.
Do not put a shell on tty2 during install.
DVD ベースインストールを実行
Use <path> for an FTP installation.
Use <path> on <dev> for a hard drive installation.
Use <path> for an HTTP installation.
Use <path> for an NFS installation.
Run rescue environment.
Turns on serial console support.
Do not probe the Data Display Channel (DDC) of the monitor. This option provides a workaround if the DDC probe causes the system to stop responding.
Once installation is up and running, send log messages to the syslog process on <host>, and optionally, on port <port>. Requires the remote syslog process to accept connections (the -r option).
Force text mode install.


キックスタートインストール用にテキストモードを選択した場合、パーティション設定、ブート ローダ、及びパッケージ選択オプションの選択を指定することを確認して下さい。これらの ステップはテキストモードでは自動化されており、anaconda は足りない情報のための催促は出来ません。これらのオプション用の選択を 用意しないと、anaconda はインストールプロセスを 停止します。
更新 (バグ修正) を含むストレージデバイス用のプロンプトです。
Image containing updates over FTP.
Image containing updates over HTTP.
Offer to upgrade any Linux installation detected on the system, regardless of the contents or the existence of the /etc/redhat-release file.
Enable vnc-based installation. You will need to connect to the machine using a vnc client application.
Connect to the vnc client named <host>, and optionally use port <port>.
'vnc' オプションの指定も要求されます。
Enable a password for the vnc connection. This will prevent someone from inadvertently connecting to the vnc-based installation.
'vnc' オプションの指定も要求されます。