diff options
| author | Jeremy Katz <katzj@redhat.com> | 2002-04-19 04:03:26 +0000 |
|---|---|---|
| committer | Jeremy Katz <katzj@redhat.com> | 2002-04-19 04:03:26 +0000 |
| commit | 34e94e67312be97452e79939ae7104afae3c041b (patch) | |
| tree | 8d20622fb803780206af9d563ed26e4bec11650e | |
| parent | 0b78cc84fbf808102dbf509000e9ef2b848c4f88 (diff) | |
| download | anaconda-34e94e67312be97452e79939ae7104afae3c041b.tar.gz anaconda-34e94e67312be97452e79939ae7104afae3c041b.tar.xz anaconda-34e94e67312be97452e79939ae7104afae3c041b.zip | |
more easy merging from hampton branch
| -rw-r--r-- | docs/anaconda-release-notes.txt | 201 | ||||
| -rw-r--r-- | docs/command-line.txt | 9 | ||||
| -rw-r--r-- | docs/install-methods.txt | 5 | ||||
| -rw-r--r-- | docs/kickstart-docs.html | 5435 | ||||
| -rw-r--r-- | docs/kickstart-docs.txt | 1531 |
5 files changed, 7173 insertions, 8 deletions
diff --git a/docs/anaconda-release-notes.txt b/docs/anaconda-release-notes.txt new file mode 100644 index 000000000..5ace02bce --- /dev/null +++ b/docs/anaconda-release-notes.txt @@ -0,0 +1,201 @@ +Anaconda Release Notes +---------------------- + +Last update: Mar 26 2002 + + +Contents + + - Overview + - Install mechanism summary + - Patching/updating installer + - Invocation options + - Troubleshooting + - More info + + +Overview +-------- + + Anaconda is the name of the install program used by Red Hat Linux. +It is python-based with some custom modules written in C. Being +written in a scripting language makes development quicker, and it is +easier to distribute updates in a non-binary form. The anaconda +installer works on a wide variety of Linux-based computing +architectures (ia32, Itanium, Alpha, S/390, PowerPC), and is designed to make +it easy to add platforms. + + The first stage of the installer is a loader program written in C. +This program is responsible for loading all the kernel modules +required to mount the second stage of the installer, which has a +fairly complete Linux runtime environment. The loader is designed to +be small to fit within the constraints of bootable media (floppies are +small by modern standards). Once the loader has mounted the second +stage image, the python installer is started up, and optionally, a +graphical X Windows based environment. + + The loader can install from local media (harddrive or CDROM), or +from a network source, via FTP, HTTP, or NFS. The installer can pull +updates for bugs or features via several sources as well. Finally, the +installer has an auto-install mechanism called kickstart that allows +installs to be scripted. The script can even be pulls from an HTTP +source that can create kickstart configurations dynamically based on +the machine which is requesting the script. This allows endless +possibilities in automating large sets of servers. + + This document's purpose is to go over technical details that will +make using and customizing the installer, and the distribution, much +easier. The anaconda installer arguably is one of the most flexible +and powerful installers available, and hopefully this document will +allow users to take advantage of this potential. + +Install Mechanism Summary +------------------------- + + The document 'install-methods.txt', which is distributed with the +anaconda package, goes over the various ways the installer can be +used. Essentially, the installer needs to access the contents of the +CD images distributed with the product. The installer can either work +with the CD images one at a time, or else from a single directory (the +install 'tree') which has the contents of all the CD images copied +into it. The later is useful if you are customizing the packages in +the distribution. The first stage of the installation process (the +'loader') is responsible for getting the system to the point it can +access the installation source, whether CD image or installation tree based. + + For CDROM-based installs the loader detects the presence of a CD in a +drive in the system with a distribution on it and jumps straight to the +second stage. For other interactive (non-kickstart) installation methods the +user is prompted for the installation source. For kickstart-based installs +the installation source is specified in the kickstart file, and the user is +not required to be present unless necessary information is missing from the +kickstart script. + + For NFS-based installs the installer mounts the directory specified +and looks for a set of ISO images, or an installation tree. If +present then a filesystem image is loopback-mounted and the second +stage installer is run from this image. For FTP and HTTP installs a +smaller (no graphical install options) second stage image is +downloaded into memory, mounted, and the second stage installer run +from this. On harddrive based installs a similar small second stage +image is put into memory and the second stage installer run from it. +This is necessary because for partitioning to suceed the installer can +not have partitions on the harddrive mounted in order for the kernel +to be able to acknowledge partition table changes. + + The bootable installation images are as follow: + + boot.img - boot image containing kernel modules for installing + on most systems from a CDROM or harddrive. + + bootnet.img - boot iamge containing kernel modules for + installing on most systems from a network source. + + pcmcia.img - boot image for installing on PCMCIA based systems + from a local or network source. + Requires pcmciadd.img driver disk. + + The supplemental driver disk images are: + + drvblock.img - block device drivers (for example, SCSI controllers). + + drvnet.img - extra network device drivers. + + oldcdrom.img - device drivers for non-SCSI, non-ATAPI cdroms. + + +Patching The Installer +---------------------- + + At times there are bugfixes or feature enhancements available for +the installer. These are typically replacement python source files +which override the versions distributed with the release. Python has +a mechanism similar to the command line shell search path for +executables. The installer can be updated by putting patched files in +a location earlier in the search path Python uses to find modules. +The 'install-methods.txt' document describes all the various ways the +installer can be told where to find the updating source files. +Typcially this is done from an 'update disk', which is a floppy with +an ext2 filesytem on it. The updated python source files are put in +the main directory of the floppy. The installer is invoked with an +'updates' option from the boot command line, and the user is prompted +to insert the update disk. The files are copied off into a ramdisk +location which Python has been instructed to look at first of modules. +For NFS installes, any files in the directory 'RHupdates' under the +directory mounted in the loader will also be used before the source +files shipped in the release. If one is customizing the distribution +and the installer then installing over NFS is the fastest way to work. + + The installer will also use an 'updates.img' file to get patched +source files. This is particularly useful for FTP and HTTP based installs. +When the second stage image is retrieved from the server, a download of +the updates.img is also attempted. This file must be an ext2 filesystem image. +It is mounted loopback, then the contents are copied to the ramdisk location +that Python is setup to look at for module updates. This update image will +also work with all the other installation mechanisms, although the exact +location where it is expected does vary. The 'install-methods.txt' file +has the details on this. + +Invocation Options +------------------ + The documentation file 'command-line.txt' has a quick summary of all the +command line options anaconda accepts. + +Troubleshooting +--------------- + +- Cannot get graphical installer working + + On some video hardware (laptops in particular) the graphical + installer will not work. The installer attempts to run at + 800x600, and some hardware does not work in this mode, or the + output looks poor when scaled to this mode. This can be worked + around by specifying the 'vga=xxx' option on the command line when + booting the installer. Here 'xxx' is the VESA mode number for the + video mode which will work on your hardware, and can be one of the + following: + + + | 640x480 800x600 1024x768 1280x1024 <-Resolution + ----+------------------------------------- + 256 | 769 771 773 775 + 32k | 784 787 790 793 + 64k | 785 788 791 794 + 16M | 786 789 792 795 + ^ + | + Number of colors + + Find the row with the number of colors and the column with the resolution + and then use the number at the intersection. For example, to run at + 1024x768 with 64k colors, use 'vga=791' + + Alternately, you can specify "resolution=<mode>", where mode is: + + 640x480 + 800x600 + 1024x768 + 1152x864 + 1280x1024 + 1400x1050 + 1600x1200 + + and the installer will start up in graphical mode in the resolution + specified. + + + +More Info +--------- + + For more info, goto the kickstart-list and anaconda-devel mailing lists +hosted by Red Hat. You can find these at: + + + anaconda-devel-list - + https://listman.redhat.com/mailman/listinfo/anaconda-devel-list + + kickstart-list - + https://listman.redhat.com/mailman/listinfo/kickstart-list + +<end of document> diff --git a/docs/command-line.txt b/docs/command-line.txt index e42468663..f74b3a8bb 100644 --- a/docs/command-line.txt +++ b/docs/command-line.txt @@ -6,12 +6,14 @@ Boot time command args: expert Turns on special features: - allows partitioning of removable media - - others? + - prompts for driver disk noshell Do not put a shell on tty2 during install. lowres Force GUI installer to run at 640x480. +resolution=<mode> Run installer in mode specified, '1024x768' for example. + nofb Do not use frame buffer for GUI install. nousb Do not load USB support (helps if install hangs @@ -63,8 +65,3 @@ ks=<url> Kickstart via HTTP. ks=hd:<dev> Kickstart via harddrive (dev = 'hda1', for example) ks=file:<path> Kickstart from a file (path = 'fd0/ks.cfg') - - - - - diff --git a/docs/install-methods.txt b/docs/install-methods.txt index 5e0154ae7..f200ddc8c 100644 --- a/docs/install-methods.txt +++ b/docs/install-methods.txt @@ -33,8 +33,9 @@ Current Installation Methods: Update Options: - floppy. - - 'updates.img' file in '/RedHat/base' or '/RHupdates' directory - of CD #1 image. + - 'updates.img' file in '/RedHat/base' directory of CD #1 image. + - updated python sources or modules in 'RHupdates/' directory of + CD #1 image are used in preference to those in original. - NFS (from a fully exploded tree) ---------------------------------- diff --git a/docs/kickstart-docs.html b/docs/kickstart-docs.html new file mode 100644 index 000000000..1939e11de --- /dev/null +++ b/docs/kickstart-docs.html @@ -0,0 +1,5435 @@ +<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN"> +<HTML +><HEAD +><TITLE +>Kickstart</TITLE +><META +NAME="GENERATOR" +CONTENT="Modular DocBook HTML Stylesheet Version 1.73 +"></HEAD +><BODY +CLASS="BOOK" +BGCOLOR="#FFFFFF" +TEXT="#000000" +LINK="#0000FF" +VLINK="#840084" +ALINK="#0000FF" +><DIV +CLASS="BOOK" +><A +NAME="INDEX" +></A +><DIV +CLASS="TITLEPAGE" +><H1 +CLASS="TITLE" +><A +NAME="AEN2" +>Kickstart</A +></H1 +><P +CLASS="COPYRIGHT" +>Copyright © 2002 by Red Hat, Inc.</P +><DIV +CLASS="LEGALNOTICE" +><A +NAME="LEGALNOTICE" +></A +><P +></P +><P +> <SPAN +CLASS="INLINEMEDIAOBJECT" +><IMG +SRC="./figs/rhlogo.png"></SPAN +> + Red Hat, Inc. + </P +><P +> <DIV +CLASS="ADDRESS" +><P +CLASS="ADDRESS" +> 1801 Varsity Drive<br> + Raleigh NC 27606-2072 USA<br> + Phone: +1 919 754 3700<br> + Phone: 888 733 4281<br> + Fax: +1 919 754 3701<br> + PO Box 13588<br> + Research Triangle Park NC 27709 USA<br> + </P +></DIV +> + </P +><P +> kickstart(EN)-7.3-HTML-RHI (2002-04-01T16:30-0500) + </P +><P +> Copyright © 2002 by Red Hat, Inc. This material may be distributed only + subject to the terms and conditions set forth in the Open Publication + License, V1.0 or later (the latest version is presently available at <A +HREF="http://www.opencontent.org/openpub/" +TARGET="_top" +>http://www.opencontent.org/openpub/</A +>). + </P +><P +> Distribution of substantively modified versions of this document is + prohibited without the explicit permission of the copyright holder. + </P +><P +> Distribution of the work or derivative of the work in any standard (paper) + book form for commercial purposes is prohibited unless prior permission is + obtained from the copyright holder. + </P +><P +> The admonition graphics (note, tip, important, caution, and warning) were + created by Marianne Pecci <TT +CLASS="EMAIL" +><<A +HREF="mailto:goddess@ipass.net" +>goddess@ipass.net</A +>></TT +>. They may be + redistributed with explicit permission from Marianne Pecci and Red Hat, Inc. + </P +><P +> Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum RPM, the RPM logo, Linux + Library, PowerTools, Linux Undercover, RHmember, RHmember More, Rough Cuts, + Rawhide and all Red Hat-based trademarks and logos are trademarks or registered + trademarks of Red Hat, Inc. in the United States and other countries. + </P +><P +> Linux is a registered trademark of Linus Torvalds. + </P +><P +> Motif and UNIX are registered trademarks of The Open Group. + </P +><P +> Intel and Pentium are a registered trademarks of Intel + Corporation. Itanium and Celeron are trademarks of Intel Corporation. + </P +><P +> AMD, AMD Athlon, AMD Duron, and AMD K6 are trademarks of Advanced Micro + Devices, Inc. + </P +><P +> Netscape is a registered trademark of Netscape Communications Corporation in + the United States and other countries. + </P +><P +> Windows is a registered trademark of Microsoft Corporation. + </P +><P +> SSH and Secure Shell are trademarks of SSH Communications Security, Inc. + </P +><P +> FireWire is a trademark of Apple Computer Corporation. + </P +><P +> S/390 and zSeries are trademarks of International Business Machines Corporation. + </P +><P +> All other trademarks and copyrights referred to are the property of their + respective owners. + </P +><P +></P +></DIV +><HR></DIV +><DIV +CLASS="CHAPTER" +><CHAPTER><H1 +><A +NAME="CH-INTRO" +>Chapter 1. Introduction</A +></H1 +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S1-KICKSTART-WHATIS" +>What are Kickstart Installations?</A +></H1 +><P +> Many system administrators would prefer to use an automated installation + method to install Red Hat Linux on their machines. To answer this need, Red Hat + created the kickstart installation method. Using kickstart, a system + administrator can create a single file containing the answers to all the + questions that would normally be asked during a typical Red Hat Linux + installation. + </P +><P +> Kickstart files can be kept on single server system, and read by + individual computers during the installation. This installation method + can support the use of a single kickstart file to install Red Hat Linux on + multiple machines, making it ideal for network and system + administrators. + </P +><P +> Kickstart lets you automate most of a Red Hat Linux installation, including: + </P +><P +></P +><UL +><LI +><P +>Language selection</P +></LI +><LI +><P +>Mouse configuration</P +></LI +><LI +><P +>Keyboard selection</P +></LI +><LI +><P +>Boot loader installation</P +></LI +><LI +><P +>Disk partitioning</P +></LI +><LI +><P +>Network configuration</P +></LI +><LI +><P +>NIS, LDAP, Kerberos, Hesiod, and Samba authentication</P +></LI +><LI +><P +>Firewall configuration</P +></LI +><LI +><P +>Package selection</P +></LI +><LI +><P +>X Window System configuration</P +></LI +></UL +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S1-KICKSTART-HOWUSE" +>How Do You Perform a Kickstart Installation?</A +></H1 +><P +> Kickstart installations can be performed using a local CD-ROM, a local + hard drive, or via NFS, FTP, or HTTP. + </P +><P +> To use kickstart, you must: + </P +><P +></P +><OL +TYPE="1" +><LI +><P +>Create a kickstart file.</P +></LI +><LI +><P +>Create a boot disk with the kickstart file or make the kickstart + file available on the network.</P +></LI +><LI +><P +>Start the kickstart installation.</P +></LI +></OL +></DIV +></DIV +><DIV +CLASS="CHAPTER" +><CHAPTER><H1 +><A +NAME="CH-KICKSTART-FILE" +>Chapter 2. Creating the Kickstart File</A +></H1 +><P +> The kickstart file is a simple text file, containing a list of items, each + identified by a keyword. You can create it by editing a copy of the + <TT +CLASS="FILENAME" +>sample.ks</TT +> file found in the + <TT +CLASS="FILENAME" +>RH-DOCS</TT +> directory of the Red Hat Linux Documentation + CD, using the <B +CLASS="APPLICATION" +>Kickstart Configurator</B +> + application, or writing it from scratch. The Red Hat Linux installation program + also creates a sample kickstart file based on the options that you + selected during installation. It is written to the file + <TT +CLASS="FILENAME" +>/root/anaconda-ks.cfg</TT +>. You should be able to edit + it with any text editor or word processor that can save files as ASCII + text. + </P +><P +> First, be aware of the following issues when you are creating your + kickstart file: + </P +><P +></P +><UL +><LI +><P +>Items must be specified <I +CLASS="EMPHASIS" +>in order</I +>. That + order is: + </P +><P +></P +><UL +><LI +><P +>Command section — Refer to <A +HREF="#CH-KICKSTART-OPTIONS" +>Chapter 3</A +> for a list of kickstart + options. You must include the required options. + </P +></LI +><LI +><P +>The <TT +CLASS="COMMAND" +>%packages</TT +> section — Refer to <A +HREF="#S2-KICKSTART-PACKAGESELECTION" +>the Section called <I +><TT +CLASS="COMMAND" +>%packages</TT +> — Package Selection</I +> in Chapter 3</A +> for details. + </P +></LI +><LI +><P +>The <TT +CLASS="COMMAND" +>%pre</TT +> and <TT +CLASS="COMMAND" +>%post</TT +> + sections — These two sections can be in any + order and are not required. Refer to <A +HREF="#S2-KICKSTART-PREINSTALLCONFIG" +>the Section called <I +><TT +CLASS="COMMAND" +>%pre</TT +> — Pre-Installation Configuration + Section</I +> in Chapter 3</A +> + and <A +HREF="#S2-KICKSTART-POSTINSTALLCONFIG" +>the Section called <I +><TT +CLASS="COMMAND" +>%post</TT +> — Post-Installation Configuration + Section</I +> in Chapter 3</A +> for + details. + </P +></LI +></UL +></LI +><LI +><P +>Items that are not required can be omitted. + </P +></LI +><LI +><P +>Omitting any required item will result in the installation program + prompting the user for an answer to the related item, just as the + user would be prompted during a typical installation. Once the + answer is given, the installation will continue unattended (unless + it finds another missing item). + </P +></LI +><LI +><P +>Lines starting with a pound sign ("#") are treated as comments and + are ignored. + </P +></LI +><LI +><P +>For kickstart <I +CLASS="EMPHASIS" +>upgrades</I +>, the following items are + required: + </P +><P +></P +><UL +><LI +><P +>Language</P +></LI +><LI +><P +>Installation method</P +></LI +><LI +><P +>Device specification (if device is needed to perform + installation)</P +></LI +><LI +><P +>Keyboard setup</P +></LI +><LI +><P +>The <TT +CLASS="COMMAND" +>upgrade</TT +> keyword</P +></LI +><LI +><P +>LILO configuration</P +></LI +></UL +><P +> If any other items are specified for an upgrade, those items will be + ignored (note that this includes package selection). + </P +></LI +></UL +></DIV +><DIV +CLASS="CHAPTER" +><CHAPTER><H1 +><A +NAME="CH-KICKSTART-OPTIONS" +>Chapter 3. Kickstart Options</A +></H1 +><P +> The following options can be placed in a kickstart file. If you prefer + to use a graphical interface for creating your kickstart file, you can + use the <B +CLASS="APPLICATION" +>Kickstart Configurator</B +> + application. + </P +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-AUTOSTEP" +><TT +CLASS="COMMAND" +>autostep</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>autostep</TT +> (optional)</DT +><DD +><P +>Similar to <TT +CLASS="COMMAND" +>interactive</TT +> except it goes to the + next screen for you. It is used mostly for debugging. + </P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-AUTH" +><TT +CLASS="COMMAND" +>auth</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>auth</TT +> or <TT +CLASS="COMMAND" +>authconfig</TT +> (required)</DT +><DD +><P +>Sets up the authentication options for the system. It's similar + to the <TT +CLASS="COMMAND" +>authconfig</TT +> command, which can be run + after the install. By default, passwords are normally encrypted + and are not shadowed. + </P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>--enablemd5</TT +></DT +><DD +><P +>Use md5 encryption for user passwords. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--enablenis</TT +></DT +><DD +><P +>Turns on NIS support. By default, + <TT +CLASS="COMMAND" +>--enablenis</TT +> uses whatever domain it + finds on the network. A domain should almost always be + set by hand (via <TT +CLASS="COMMAND" +>--nisdomain</TT +>). + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--nisdomain</TT +></DT +><DD +><P +>NIS domain name to use for NIS services. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--nisserver</TT +></DT +><DD +><P +>Server to use for NIS services (broadcasts by default). + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--useshadow</TT +> or <TT +CLASS="COMMAND" +>--enableshadow</TT +></DT +><DD +><P +>Use shadow passwords.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--enableldap</TT +></DT +><DD +><P +>Turns on LDAP support in + <TT +CLASS="FILENAME" +>/etc/nsswitch.conf</TT +>, allowing your + system to retrieve information about users (UIDs, home + directories, shells, etc.) from an LDAP directory. To + use this option, you must have the + <TT +CLASS="FILENAME" +>nss_ldap</TT +> package installed. You + must also specify a server and a base DN with + <TT +CLASS="COMMAND" +>--ldapserver=</TT +> and + <TT +CLASS="COMMAND" +>--ldapbasedn=</TT +>. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--enableldapauth</TT +></DT +><DD +><P +>Use LDAP as an authentication method. This enables the + <TT +CLASS="FILENAME" +>pam_ldap</TT +> module for authentication + and changing passwords, using an LDAP directory. To use + this option, you must have the + <TT +CLASS="FILENAME" +>nss_ldap</TT +> package installed. You + must also specify a server and a base DN with + <TT +CLASS="COMMAND" +>--ldapserver=</TT +> and + <TT +CLASS="COMMAND" +>--ldapbasedn=</TT +>. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--ldapserver=</TT +></DT +><DD +><P +>If you specified either <TT +CLASS="COMMAND" +>--enableldap</TT +> + or <TT +CLASS="COMMAND" +>--enableldapauth</TT +>, the name of the + LDAP server to use. This option is set in the + <TT +CLASS="FILENAME" +>/etc/ldap.conf</TT +> file. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--ldapbasedn=</TT +></DT +><DD +><P +>If you specified either <TT +CLASS="COMMAND" +>--enableldap</TT +> + or <TT +CLASS="COMMAND" +>--enableldapauth</TT +>, the DN (distinguished + name) in your LDAP directory tree + under which user information is stored. This option is + set in the <TT +CLASS="FILENAME" +>/etc/ldap.conf</TT +> file. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--enableldaptls</TT +></DT +><DD +><P +>Use TLS (Transport Layer Security) lookups. This option + allows LDAP to send encrypted usernames and passwords + to an LDAP server before authentication. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--enablekrb5</TT +></DT +><DD +><P +>Use Kerberos 5 for authenticating users. Kerberos + itself does not know about home directories, UIDs, or + shells. So if you enable Kerberos you will need to + make users' accounts known to this workstation by + enabling LDAP, NIS, or Hesiod or by using + the <TT +CLASS="COMMAND" +>/usr/sbin/useradd</TT +> command + to make their accounts known to this workstation. If + you use this option, you must have the + <TT +CLASS="FILENAME" +>pam_krb5</TT +> package installed. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--krb5realm</TT +></DT +><DD +><P +>The Kerberos 5 realm to which your workstation belongs.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--krb5kdc</TT +></DT +><DD +><P +>The KDC (or KDCs) that serve requests for the realm. If + you have multiple KDCs in your realm, separate their + names with commas (,).</P +></DD +><DT +><TT +CLASS="COMMAND" +>--krb5adminserver</TT +></DT +><DD +><P +>The KDC in your realm that is also running kadmind. + This server handles password changing and other + administrative requests. This server must be run on the + master KDC if you have more than one KDC. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--enablehesiod</TT +></DT +><DD +><P +>Enable Hesiod support for looking up user home + directories, UIDs, and shells. More information on + setting up and using Hesiod on your network is in + <TT +CLASS="FILENAME" +>/usr/share/doc/glibc-2.x.x/README.hesiod</TT +>, + which is included in the <TT +CLASS="FILENAME" +>glibc</TT +> + package. Hesiod is an extension of DNS that uses DNS + records to store information about users, groups, and + various other items. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--hesiodlhs</TT +></DT +><DD +><P +>The Hesiod LHS ("left-hand side") option, set in + <TT +CLASS="FILENAME" +>/etc/hesiod.conf</TT +>. This option is + used by the Hesiod library to determine the name to + search DNS for when looking up information, similar to + LDAP's use of a base DN. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--hesiodrhs</TT +></DT +><DD +><P +>The Hesiod RHS ("right-hand side") option, set in + <TT +CLASS="FILENAME" +>/etc/hesiod.conf</TT +>. This option is + used by the Hesiod library to determine the name to + search DNS for when looking up information, similar to + LDAP's use of a base DN. + </P +><DIV +CLASS="TIP" +><P +></P +><TABLE +CLASS="TIP" +WIDTH="90%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="./stylesheet-images/tip.png" +HSPACE="5" +ALT="Tip"></TD +><TH +ALIGN="LEFT" +VALIGN="CENTER" +><B +>Tip</B +></TH +></TR +><TR +><TD +> </TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +>To look up user information for "jim", the Hesiod + library looks up + <I +CLASS="EMPHASIS" +>jim.passwd<LHS><RHS></I +>, + which should resolve to a TXT record that looks like + what his passwd entry would look like + (<TT +CLASS="COMPUTEROUTPUT" +>jim:*:501:501:Jungle + Jim:/home/jim:/bin/bash</TT +>). For + groups, the situation is identical, except + <I +CLASS="EMPHASIS" +>jim.group<LHS><RHS></I +> + would be used. + </P +><P +>Looking up users and groups by number is handled by + making "501.uid" a CNAME for "jim.passwd", and + "501.gid" a CNAME for "jim.group". Note that the LHS + and RHS do not have periods <SPAN +CLASS="KEYCAP" +><KEYCAP +>[.]</KEYCAP +></SPAN +> put in + front of them when the library determines the name for + which to search, so the LHS and RHS usually begin with + periods. + </P +></TD +></TR +></TABLE +></DIV +></DD +><DT +><TT +CLASS="COMMAND" +>--enablesmbauth</TT +></DT +><DD +><P +>Enables authentication of users against an SMB server + (typically a Samba or Windows server). SMB + authentication support does not know about home + directories, UIDs, or shells. So if you enable it you + will need to make users' accounts known to the + workstation by enabling LDAP, NIS, or Hesiod or by using + the <TT +CLASS="COMMAND" +>/usr/sbin/useradd</TT +> command to make + their accounts known to the workstation. To use this + option, you must have the <TT +CLASS="FILENAME" +>pam_smb</TT +> + package installed. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--smbservers=</TT +></DT +><DD +><P +>The name of the server(s) to use for SMB + authentication. To specify more than one server, + separate the names with commas (,). + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--smbworkgroup=</TT +></DT +><DD +><P +>The name of the workgroup for the SMB servers.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--enablecache</TT +></DT +><DD +><P +>Enables the <TT +CLASS="COMMAND" +>nscd</TT +> service. The + <TT +CLASS="COMMAND" +>nscd</TT +> service caches information about + users, groups, and various other types of information. + Caching is especially helpful if you choose to + distribute information about users and groups over your + network using NIS, LDAP, or hesiod. + </P +></DD +></DL +></DIV +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-BOOTLOADER" +><TT +CLASS="COMMAND" +>bootloader</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>bootloader</TT +> (required)</DT +><DD +><P +>Specifies how the boot loader should be installed and whether + the boot loader should be LILO or GRUB. + </P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>--append</TT +></DT +><DD +><P +>Specifies kernel parameters.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--location=</TT +></DT +><DD +><P +>Specifies where the boot record is written. Valid + values are the following: <TT +CLASS="USERINPUT" +><B +>mbr</B +></TT +> + (the default), <TT +CLASS="USERINPUT" +><B +>partition</B +></TT +> + (installs the boot loader on the first sector of the + partition containing the kernel), or + <TT +CLASS="USERINPUT" +><B +>none</B +></TT +> (do not install the boot + loader). + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--password=<TT +CLASS="REPLACEABLE" +><I +>mypassword</I +></TT +></TT +></DT +><DD +><P +>If using GRUB, sets the GRUB boot loader password to + <TT +CLASS="REPLACEABLE" +><I +>mypassword</I +></TT +>. This should be + used to restrict access to the GRUB shell where + arbitrary kernel options can be passed. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--md5pass=<TT +CLASS="REPLACEABLE" +><I +>mypassword</I +></TT +></TT +></DT +><DD +><P +>If using GRUB, similar to <TT +CLASS="COMMAND" +>--password</TT +> + except <TT +CLASS="REPLACEABLE" +><I +>mypassword</I +></TT +> should be + the password already encrypted. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--useLilo</TT +></DT +><DD +><P +>Use LILO instead of GRUB as the boot loader. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--linear</TT +></DT +><DD +><P +>If using LILO, use the <TT +CLASS="COMMAND" +>linear</TT +> LILO + option; this is only for backwards compatibility (and + linear is now used by default). + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--nolinear</TT +></DT +><DD +><P +>If using LILO, use the <TT +CLASS="COMMAND" +>nolinear</TT +> LILO + option; linear is the default. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--lba32</TT +></DT +><DD +><P +>If using LILO, force use of lba32 mode instead of + autodetecting. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--upgrade</TT +> + <A +NAME="NEW-OPTION" +HREF="#FTN.NEW-OPTION" +>[1]</A +></DT +><DD +><P +>Upgrade the existing boot loader configuration. This + option is only available for upgrades. + </P +></DD +></DL +></DIV +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-CLEARPART" +><TT +CLASS="COMMAND" +>clearpart</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>clearpart</TT +> (optional)</DT +><DD +><P +>Removes partitions from the system, prior to creation of new + partitions. By default, no partitions are removed. + </P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +> --linux</TT +></DT +><DD +><P +>Erases all Linux partitions.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--all</TT +></DT +><DD +><P +>Erases all partitions from the system.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--drives</TT +></DT +><DD +><P +>Specifies which drives to clear partitions from.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--initlabel</TT +></DT +><DD +><P +>Initializes the disk label to the default for your + architecture (<TT +CLASS="COMMAND" +>msdos</TT +> for x86 and + <TT +CLASS="COMMAND" +>gpt</TT +> for Itanium). It is useful so + that the installation program does not ask if it should + initialize the disk label if installing to a brand new + hard drive. + </P +></DD +></DL +></DIV +></DD +></DL +></DIV +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="./stylesheet-images/note.png" +HSPACE="5" +ALT="Note"></TD +><TH +ALIGN="LEFT" +VALIGN="CENTER" +><B +>Note</B +></TH +></TR +><TR +><TD +> </TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +> If the <TT +CLASS="COMMAND" +>clearpart</TT +> command, then the + <TT +CLASS="COMMAND" +>--onpart</TT +> command cannot be used on a logical + partition. + </P +></TD +></TR +></TABLE +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-DEVICE" +><TT +CLASS="COMMAND" +>device</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>device</TT +> (optional)</DT +><DD +><P +>On most PCI systems, the installation program will autoprobe for + Ethernet and SCSI cards properly. On older systems and some PCI + systems, however, kickstart needs a hint to find the proper + devices. The <TT +CLASS="COMMAND" +>device</TT +> command, which tells + <B +CLASS="APPLICATION" +>Anaconda</B +> to install extra modules, is + in this format: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +>device <TT +CLASS="REPLACEABLE" +><I +><type></I +></TT +> <TT +CLASS="REPLACEABLE" +><I +><moduleName></I +></TT +> --opts <TT +CLASS="REPLACEABLE" +><I +><options></I +></TT +></PRE +></TD +></TR +></TABLE +><P +><TT +CLASS="REPLACEABLE" +><I +><type></I +></TT +> should be + <TT +CLASS="USERINPUT" +><B +>scsi</B +></TT +> or <TT +CLASS="USERINPUT" +><B +>eth</B +></TT +>, and + <TT +CLASS="REPLACEABLE" +><I +><moduleName></I +></TT +> is the name of the + kernel module which should be installed. + </P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>--opts</TT +></DT +><DD +><P +>Options to pass to the kernel module. Note that multiple + options may be passed if they are put in quotes. For + example: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>--opts "aic152x=0x340 io=11"</TT +></PRE +></TD +></TR +></TABLE +></DD +></DL +></DIV +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-DEVICEPROBE" +><TT +CLASS="COMMAND" +>deviceprobe</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>deviceprobe</TT +> (optional)</DT +><DD +><P +>Forces a probe of the PCI bus and loads modules for all the + devices found if a module is available. + </P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-DRIVERDISK" +><TT +CLASS="COMMAND" +>driverdisk</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>driverdisk</TT +> (optional)</DT +><DD +><P +>Driver disks can be used during kickstart installations. You + will need to copy the driver disk's contents to the root + directory of a partition on the system's hard drive. Then you + will need to use the <TT +CLASS="COMMAND" +>driverdisk</TT +> command to + tell the installation program where to look for the driver disk. + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>driverdisk <TT +CLASS="REPLACEABLE" +><I +><partition></I +></TT +> [--type <TT +CLASS="REPLACEABLE" +><I +><fstype></I +></TT +>]</TT +></PRE +></TD +></TR +></TABLE +><P +><TT +CLASS="REPLACEABLE" +><I +><partition></I +></TT +> is the partition + containing the driver disk. + </P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>--type</TT +></DT +><DD +><P +>Filesystem type (for example, vfat, ext2, or ext3).</P +></DD +></DL +></DIV +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-FIREWALL" +><TT +CLASS="COMMAND" +>firewall</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>firewall</TT +> (optional)</DT +><DD +><P +>Firewall options can be configured in kickstart. This + configuration corresponds to the <B +CLASS="GUILABEL" +>Firewall + Configuration</B +> screen in the installation program. + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>firewall [--high | --medium | --disabled] [--trust <TT +CLASS="REPLACEABLE" +><I +><device></I +></TT +>] [--dhcp] [--ssh] [--telnet] [--smtp] [--http] [--ftp] [--port <TT +CLASS="REPLACEABLE" +><I +><portspec></I +></TT +>]</TT +></PRE +></TD +></TR +></TABLE +></DD +></DL +></DIV +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +>Levels of security</DT +><DD +><P +>Choose one of the following levels of security:</P +><P +></P +><UL +><LI +><P +><TT +CLASS="COMMAND" +>--high</TT +></P +></LI +><LI +><P +><TT +CLASS="COMMAND" +>--medium</TT +></P +></LI +><LI +><P +><TT +CLASS="COMMAND" +>--disabled</TT +></P +></LI +></UL +></DD +><DT +><TT +CLASS="COMMAND" +>--trust + <TT +CLASS="REPLACEABLE" +><I +><device></I +></TT +></TT +></DT +><DD +><P +>Listing a device here, such as eth0, allows all traffic coming + from that device to go through the firewall. To list more than + one device, use <TT +CLASS="COMMAND" +>--trust eth0 --trust eth1</TT +>. Do + NOT use a comma-separated format such as <TT +CLASS="COMMAND" +>--trust eth0, + eth1</TT +>. + </P +></DD +><DT +>Allow incoming</DT +><DD +><P +>Enabling these options allow the specified services to pass + through the firewall.</P +><P +></P +><UL +><LI +><P +><TT +CLASS="COMMAND" +>--dhcp</TT +></P +></LI +><LI +><P +><TT +CLASS="COMMAND" +>--ssh</TT +></P +></LI +><LI +><P +><TT +CLASS="COMMAND" +>--telnet</TT +></P +></LI +><LI +><P +><TT +CLASS="COMMAND" +>--smtp</TT +></P +></LI +><LI +><P +><TT +CLASS="COMMAND" +>--http</TT +></P +></LI +><LI +><P +><TT +CLASS="COMMAND" +>--ftp</TT +></P +></LI +></UL +></DD +><DT +><TT +CLASS="COMMAND" +>--port</TT +> <TT +CLASS="REPLACEABLE" +><I +><portspec></I +></TT +></DT +><DD +><P +>You can specify that ports be allowed through the firewall using + the port:protocol format. For example, if you wanted to allow + IMAP access through your firewall, you can specify + <TT +CLASS="COMMAND" +>imap:tcp</TT +>. You can also specify numeric ports + explicitly; for example, to allow UDP packets on port 1234 + through, specify <TT +CLASS="COMMAND" +>1234:udp</TT +>. To specify + multiple ports, separate them by commas. + </P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-INSTALL" +><TT +CLASS="COMMAND" +>install</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>install</TT +> (optional)</DT +><DD +><P +>Tells the system to install a fresh system rather than upgrade + an existing system. This is the default mode. + </P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-INSTALLMETH" +>Installation Methods</A +></H1 +><P +> You must use one of these four commands to specify what type of + kickstart installation is being performed: + </P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>nfs</TT +></DT +><DD +><P +>Install from the NFS server specified. + <P +></P +><UL +><LI +><P +><TT +CLASS="COMMAND" +>--server + <TT +CLASS="REPLACEABLE" +><I +><server></I +></TT +></TT +></P +><P +>Server from which to install (hostname or IP).</P +></LI +><LI +><P +><TT +CLASS="COMMAND" +>--dir <TT +CLASS="REPLACEABLE" +><I +><dir></I +></TT +></TT +></P +><P +>Directory containing the Red Hat installation tree.</P +></LI +></UL +> + </P +><P +>For example:</P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>nfs --server <TT +CLASS="REPLACEABLE" +><I +><server></I +></TT +> --dir <TT +CLASS="REPLACEABLE" +><I +><dir></I +></TT +></TT +></PRE +></TD +></TR +></TABLE +></DD +><DT +><TT +CLASS="COMMAND" +>cdrom</TT +></DT +><DD +><P +>Install from the first CD-ROM drive on the system.</P +><P +> For example: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>cdrom</TT +></PRE +></TD +></TR +></TABLE +></DD +><DT +><TT +CLASS="COMMAND" +>harddrive</TT +></DT +><DD +><P +>Install from a Red Hat installation tree on a local drive, which + must be either vfat or ext2. + </P +><P +></P +><UL +><LI +><P +><TT +CLASS="COMMAND" +>--partition <TT +CLASS="REPLACEABLE" +><I +><partition></I +></TT +></TT +></P +><P +>Partition to install from (such as, sdb2).</P +></LI +><LI +><P +> <TT +CLASS="COMMAND" +>--dir <TT +CLASS="REPLACEABLE" +><I +><dir></I +></TT +></TT +> + </P +><P +> Directory containing the Red Hat installation tree. + </P +></LI +></UL +><P +>For example:</P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>harddrive --partition <TT +CLASS="REPLACEABLE" +><I +><partition></I +></TT +> --dir <TT +CLASS="REPLACEABLE" +><I +><dir></I +></TT +></TT +></PRE +></TD +></TR +></TABLE +></DD +><DT +><TT +CLASS="COMMAND" +>url</TT +></DT +><DD +><P +>Install from a Red Hat installation tree on a remote server via FTP + or HTTP.</P +><P +>For example:</P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>url --url http://<server>/<dir></TT +></PRE +></TD +></TR +></TABLE +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>url --url ftp://<username>:<password>@<server>/<dir></TT +></PRE +></TD +></TR +></TABLE +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-INTERACTIVE" +><TT +CLASS="COMMAND" +>interactive</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>interactive</TT +> (optional)</DT +><DD +><P +>Uses the information provided in the kickstart file during the + installation, but allow for inspection and modification of the + values given. You will be presented with each screen of the + installation program with the values from the kickstart + file. Either accept the values by clicking + <B +CLASS="GUIBUTTON" +>Next</B +> or change the values and click + <B +CLASS="GUIBUTTON" +>Next</B +> to continue. See also + <A +HREF="#S2-KICKSTART-AUTOSTEP" +>the Section called <I +><TT +CLASS="COMMAND" +>autostep</TT +></I +></A +>. + </P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-KEYBOARD" +><TT +CLASS="COMMAND" +>keyboard</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>keyboard</TT +> (required)</DT +><DD +><P +>Sets system keyboard type. Here is the list of available + keyboards on i386, Itanium, and Alpha machines: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +>azerty, be-latin1, be2-latin1, fr-latin0, fr-latin1, fr-pc, fr, wangbe, +ANSI-dvorak, dvorak-l, dvorak-r, dvorak, pc-dvorak-latin1, tr_f-latin5, +trf, bg, br-abnt2, cf, cz-lat2-prog, cz-lat2, defkeymap, defkeymap_V1.0, +dk-latin1, dk, emacs, emacs2, es, fi-latin1, fi, gr-pc, gr, hebrew, hu101, +is-latin1, it-ibm, it, it2, jp106, la-latin1, lt, lt.l4, nl, no-latin1, no, +pc110, pl, pt-latin1, pt-old, ro, ru-cp1251, ru-ms, ru-yawerty, ru, ru1, ru2, +ru_win, se-latin1, sk-prog-qwerty, sk-prog, sk-qwerty, tr_q-latin5, tralt, +trf, trq, ua, uk, us, croat, cz-us-qwertz, de-latin1-nodeadkeys, de-latin1, +de, fr_CH-latin1, fr_CH, hu, sg-latin1-lk450, sg-latin1, sg, sk-prog-qwertz, +sk-qwertz, slovene</PRE +></TD +></TR +></TABLE +><P +> Here is the list for SPARC machines: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +>sun-pl-altgraph, sun-pl, sundvorak, sunkeymap, sunt4-es, +sunt4-no-latin1, sunt5-cz-us, sunt5-de-latin1, sunt5-es, +sunt5-fi-latin1, sunt5-fr-latin1, sunt5-ru, sunt5-uk, sunt5-us-cz</PRE +></TD +></TR +></TABLE +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-LANG" +><TT +CLASS="COMMAND" +>lang</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>lang</TT +> (required) + + </DT +><DD +><P +>Sets the language to use during installation. For example, to + set the language to English, the kickstart file should contain + the following line: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMMAND" +>lang en_US</TT +></PRE +></TD +></TR +></TABLE +><P +> Valid language codes are the following (please note that these + are subject to change at any time): + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +>cs_CZ, da_DK, en_US, fr_FR, de_DE, is_IS, it_IT, ja_JP.eucJP, +ko_KR.eucKR, no_NO, pt_PT, ru_RU.koi8r, sl_SI, es_ES, sv_SE, uk_UA</PRE +></TD +></TR +></TABLE +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-LANGSUPPORT" +><TT +CLASS="COMMAND" +>langsupport</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>langsupport</TT +> (required)</DT +><DD +><P +>Sets the language(s) to install on the system. The same + language codes used with <TT +CLASS="COMMAND" +>lang</TT +> can be used + with <TT +CLASS="COMMAND" +>langsupport</TT +>. + </P +><P +> If you just want to install one language, specify it. For + example, to install and use the French language + <TT +CLASS="COMMAND" +>fr_FR</TT +>: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +>langsupport fr_FR</PRE +></TD +></TR +></TABLE +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>--default</TT +></DT +><DD +><P +>If you want to install language support for more than + one language, you must specify a default. + </P +></DD +></DL +></DIV +><P +>For example, to install English and French and use English as the + default language: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>langsupport --default en_US fr_FR</TT +></PRE +></TD +></TR +></TABLE +><P +> If you use <TT +CLASS="COMMAND" +>--default</TT +> with only one language, + all languages will be installed with the specified language set + to the default. + </P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-LILO" +><TT +CLASS="COMMAND" +>lilo</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>lilo</TT +> (replaced by <TT +CLASS="COMMAND" +>bootloader</TT +>)</DT +><DD +><DIV +CLASS="WARNING" +><P +></P +><TABLE +CLASS="WARNING" +WIDTH="90%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="./stylesheet-images/warning.png" +HSPACE="5" +ALT="Warning"></TD +><TH +ALIGN="LEFT" +VALIGN="CENTER" +><B +>Warning</B +></TH +></TR +><TR +><TD +> </TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +> This option has been replaced by <TT +CLASS="COMMAND" +>bootloader</TT +> + and is only available for backwards compatibility. Refer to + <A +HREF="#S2-KICKSTART-BOOTLOADER" +>the Section called <I +><TT +CLASS="COMMAND" +>bootloader</TT +></I +></A +>. + </P +></TD +></TR +></TABLE +></DIV +><P +>Specifies how the boot loader should be installed on the + system. By default, LILO installs on the MBR of the first disk, + and installs a dual-boot system if a DOS partition is found (the + DOS/Windows system will boot if the user types + <TT +CLASS="USERINPUT" +><B +>dos</B +></TT +> at the + <TT +CLASS="COMPUTEROUTPUT" +>LILO:</TT +> prompt). + </P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>--append</TT +> + <TT +CLASS="REPLACEABLE" +><I +><params></I +></TT +></DT +><DD +><P +>Specifies kernel parameters.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--linear</TT +></DT +><DD +><P +>Use the <TT +CLASS="COMMAND" +>linear</TT +> LILO option; this is + only for backwards compatibility (and linear is now used + by default). + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--nolinear</TT +></DT +><DD +><P +>Use the <TT +CLASS="COMMAND" +>nolinear</TT +> LILO option; linear + is now used by default. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--location=</TT +></DT +><DD +><P +>Specifies where the LILO boot record is written. Valid + values are the following: <TT +CLASS="USERINPUT" +><B +>mbr</B +></TT +> + (the default) or <TT +CLASS="USERINPUT" +><B +>partition</B +></TT +> + (installs the boot loader on the first sector of the + partition containing the kernel). If no location is + specified, LILO is not installed. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--lba32</TT +></DT +><DD +><P +>Forces the use of lba32 mode instead of autodetecting.</P +></DD +></DL +></DIV +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-LILOCHECK" +><TT +CLASS="COMMAND" +>lilocheck</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>lilocheck</TT +> (optional)</DT +><DD +><P +>If <TT +CLASS="COMMAND" +>lilocheck</TT +> is present, the installation + program checks for LILO on the MBR of the first hard drive, and + reboots the system if it is found — in this case, no + installation is performed. This can prevent kickstart from + reinstalling an already installed system. + </P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-MOUSE" +><TT +CLASS="COMMAND" +>mouse</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>mouse</TT +> (required)</DT +><DD +><P +>Configures the mouse for the system, both in GUI and text + modes. Options are: + </P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>--device</TT +> + <TT +CLASS="REPLACEABLE" +><I +><dev></I +></TT +></DT +><DD +><P +>Device the mouse is on (such as --device ttyS0).</P +></DD +><DT +><TT +CLASS="COMMAND" +>--emulthree</TT +></DT +><DD +><P +>If present, simultaneous clicks on the left and right + mouse buttons will be recognized as the middle mouse + button by the X Window System. This option should + be used if you have a two button mouse. + </P +><P +>After options, the mouse type may be specified as one of + the following: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +>alpsps/2, ascii, asciips/2, atibm, generic, generic3, +genericps/2, generic3ps/2, genericusb, generic3usb, +geniusnm, geniusnmps/2,geniusprops/2, geniusscrollps/2, +geniusscrollps/2+, thinking, thinkingps/2, logitech, +logitechcc, logibm, logimman, logimmanps/2, logimman+, +logimman+ps/2, logimmusb, microsoft, msnew, msintelli, +msintellips/2, msintelliusb, msbm, mousesystems, mmseries, +mmhittab, sun, none</PRE +></TD +></TR +></TABLE +><P +>If the mouse command is given without any arguments, or + it is omitted, the installation program will attempt to + autodetect the mouse. This procedure works for most + modern mice. + </P +></DD +></DL +></DIV +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-NETWORK" +><TT +CLASS="COMMAND" +>network</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>network</TT +> (optional)</DT +><DD +><P +>Configures network information for the system. If the kickstart + installation does not require networking (in other words, it is + not installed over NFS, HTTP, or FTP), networking is not + configured for the system. If the installation does require + networking and network information is not provided in the + kickstart file, the Red Hat Linux installation program assumes that the + installation should be done over eth0 via a dynamic IP address + (BOOTP/DHCP), and configures the final, installed system to + determine its IP address dynamically. The + <TT +CLASS="COMMAND" +>network</TT +> option configures networking + information for kickstart installations via a network as well as + for the installed system. + </P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>--bootproto</TT +></DT +><DD +><P +>One of <TT +CLASS="USERINPUT" +><B +>dhcp</B +></TT +>, + <TT +CLASS="USERINPUT" +><B +>bootp</B +></TT +>, or + <TT +CLASS="USERINPUT" +><B +>static</B +></TT +> (defaults to DHCP, and + <TT +CLASS="USERINPUT" +><B +>dhcp</B +></TT +> and + <TT +CLASS="USERINPUT" +><B +>bootp</B +></TT +> are treated the same). + Must be <TT +CLASS="USERINPUT" +><B +>static</B +></TT +> for static IP + information to be used. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--device</TT +> <TT +CLASS="REPLACEABLE" +><I +><device></I +></TT +></DT +><DD +><P +>Used to select a specific Ethernet device for + installation. Note that using + <TT +CLASS="COMMAND" +>--device</TT +> + <TT +CLASS="REPLACEABLE" +><I +><device></I +></TT +> will not be + effective unless the kickstart file is a local file + (such as <TT +CLASS="COMMAND" +>ks=floppy</TT +>), since the + installation program will configure the network to find + the kickstart file. Example: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>network --bootproto dhcp --device eth0</TT +></PRE +></TD +></TR +></TABLE +></DD +><DT +><TT +CLASS="COMMAND" +>--ip</TT +></DT +><DD +><P +>IP address for the machine to be installed.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--gateway</TT +></DT +><DD +><P +>Default gateway as an IP address.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--nameserver</TT +></DT +><DD +><P +>Primary nameserver, as an IP address.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--nodns</TT +></DT +><DD +><P +>Do not configure any DNS server.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--netmask</TT +></DT +><DD +><P +>Netmask for the installed system.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--hostname</TT +></DT +><DD +><P +>Hostname for the installed system.</P +></DD +></DL +></DIV +><P +>There are three different methods of network configuration:</P +><P +></P +><UL +><LI +><P +>DHCP</P +></LI +><LI +><P +>BOOTP</P +></LI +><LI +><P +>static</P +></LI +></UL +><P +>The DHCP method uses a DHCP server system to obtain its + networking configuration. As you might guess, the BOOTP method + is similar, requiring a BOOTP server to supply the networking + configuration. + </P +><P +>The static method requires that you enter all the required + networking information in the kickstart file. As the name + implies, this information is static, and will be used during the + installation, and after the installation as well. + </P +><P +>To direct a system to use DHCP to obtain its networking + configuration, use the following line: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>network --bootproto dhcp</TT +></PRE +></TD +></TR +></TABLE +><P +>To direct a machine to use BOOTP to obtain its networking + configuration, use the following line in the kickstart file: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>network --bootproto bootp</TT +></PRE +></TD +></TR +></TABLE +><P +>The line for static networking is more complex, as you must + include all network configuration information on one line. + You must specify: + </P +><P +></P +><UL +><LI +><P +>IP address</P +></LI +><LI +><P +>Netmask</P +></LI +><LI +><P +>Gateway IP address</P +></LI +><LI +><P +>Nameserver IP address</P +></LI +></UL +><P +>Here is an example static line:</P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +><SUP +>network --bootproto static --ip 10.0.2.15 --netmask 255.255.255.0 --gateway 10.0.2.254 --nameserver 10.0.2.1</SUP +></TT +></PRE +></TD +></TR +></TABLE +><P +>If you use the static method, be aware of the following two + restrictions:</P +><P +></P +><UL +><LI +><P +>All static networking configuration information must be + specified on <I +CLASS="EMPHASIS" +>one</I +> line; you cannot wrap + lines using a backslash, for example. + </P +></LI +><LI +><P +>You can only specify one nameserver here. However, you can + use the kickstart file's <TT +CLASS="COMMAND" +>%post</TT +> section + (described in <A +HREF="#S2-KICKSTART-POSTINSTALLCONFIG" +>the Section called <I +><TT +CLASS="COMMAND" +>%post</TT +> — Post-Installation Configuration + Section</I +></A +>) to add more name + servers, if needed. + </P +></LI +></UL +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-PARTITION" +><TT +CLASS="COMMAND" +>part</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>part</TT +> or <TT +CLASS="COMMAND" +>partition</TT +> (required for installs, ignored for + upgrades)</DT +><DD +><P +>Creates a partition on the system.</P +><P +>The <TT +CLASS="REPLACEABLE" +><I +><mntpoint></I +></TT +> is where the + partition will be mounted and must be of one of the following + forms: + <P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="FILENAME" +>/<TT +CLASS="REPLACEABLE" +><I +><mntpoint></I +></TT +></TT +></DT +><DD +><P +>For example, <TT +CLASS="USERINPUT" +><B +>/</B +></TT +>, + <TT +CLASS="USERINPUT" +><B +>/usr</B +></TT +>, <TT +CLASS="USERINPUT" +><B +>/home</B +></TT +> + </P +></DD +><DT +><TT +CLASS="COMMAND" +>swap</TT +></DT +><DD +><P +>The partition will be used as swap space.</P +><P +>To determine the size of the swap partition + automatically, use the + <TT +CLASS="COMMAND" +>--recommended</TT +><A +HREF="#FTN.NEW-OPTION" +>[1]</A +> option:</P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMMAND" +>swap --recommended</TT +></PRE +></TD +></TR +></TABLE +><P +>The minimum size of the automatically-generated swap + partition will be no smaller than the amount of RAM in the + system and no bigger than twice the amount of RAM in the + system.</P +></DD +><DT +><TT +CLASS="COMMAND" +>raid.<TT +CLASS="REPLACEABLE" +><I +><id></I +></TT +></TT +></DT +><DD +><P +>The partition will be used for software RAID (see the + <A +HREF="#S2-KICKSTART-RAID" +>the Section called <I +><TT +CLASS="COMMAND" +>raid</TT +></I +></A +> below). + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--size <TT +CLASS="REPLACEABLE" +><I +><size></I +></TT +></TT +></DT +><DD +><P +>The minimum partition size in megabytes. Specify an + integer value here such as 500. Do not append the number + with MB. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--grow</TT +></DT +><DD +><P +>Tells the partition to grow to fill available space (if + any), or up to the maximum size setting. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--maxsize <TT +CLASS="REPLACEABLE" +><I +><size></I +></TT +></TT +></DT +><DD +><P +>The maximum partition size in megabytes when the + partition is set to grow. Specify an integer value here, + and do not append the number with MB. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--noformat</TT +></DT +><DD +><P +>Tells the installation program not to format the + partition, for use with the <TT +CLASS="COMMAND" +>--onpart</TT +> + command. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--onpart <TT +CLASS="REPLACEABLE" +><I +><part></I +></TT +></TT +> or + <TT +CLASS="COMMAND" +>--usepart <TT +CLASS="REPLACEABLE" +><I +><part></I +></TT +></TT +></DT +><DD +><P +>Tells the installation program to put the partition on the + <I +CLASS="EMPHASIS" +>already existing</I +> device + <TT +CLASS="REPLACEABLE" +><I +><part></I +></TT +>. For example, + <TT +CLASS="COMMAND" +>partition /home --onpart hda1</TT +> will put + <TT +CLASS="FILENAME" +>/home</TT +> on + <TT +CLASS="FILENAME" +>/dev/hda1</TT +>, which must already + exist. If you use <TT +CLASS="COMMAND" +>--onpart</TT +>, you still + must specify a size with <TT +CLASS="COMMAND" +>--size</TT +> for + the file to be parsed correctly. The size will be + ignored since the partition already exists. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--ondisk + <TT +CLASS="REPLACEABLE" +><I +><disk></I +></TT +></TT +> or + <TT +CLASS="COMMAND" +>--ondrive <TT +CLASS="REPLACEABLE" +><I +><drive></I +></TT +></TT +></DT +><DD +><P +>Forces the partition to be created on a particular disk. + For example, <TT +CLASS="COMMAND" +>--ondisk sdb</TT +> will put + the partition on the second disk on the system. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--asprimary</TT +></DT +><DD +><P +>Forces automatic allocation of the partition as a + primary partition or the partitioning will fail. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--bytes-per-inode=<TT +CLASS="REPLACEABLE" +><I +><N></I +></TT +></TT +></DT +><DD +><P +><TT +CLASS="REPLACEABLE" +><I +><N></I +></TT +> represents the + number of bytes per inode on the filesystem when it is + created. It must be given in decimal format. This + option is useful for applications where you want to + increase the number of inodes on the filesystem. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--type=<TT +CLASS="REPLACEABLE" +><I +><X></I +></TT +></TT +> + (replaced by <TT +CLASS="COMMAND" +>fstype</TT +>)</DT +><DD +><P +>This option is no longer available. Use + <TT +CLASS="COMMAND" +>fstype</TT +>. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--fstype</TT +></DT +><DD +><P +>Sets the filesystem type for the partition. Valid + values are <TT +CLASS="USERINPUT" +><B +>ext2</B +></TT +>, + <TT +CLASS="USERINPUT" +><B +>ext3</B +></TT +>, + <TT +CLASS="USERINPUT" +><B +>swap</B +></TT +>, and + <TT +CLASS="USERINPUT" +><B +>vfat</B +></TT +>. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--start</TT +></DT +><DD +><P +>Specifies the starting cylinder for the partition. It + requires that a drive be specified with + <TT +CLASS="COMMAND" +>--ondisk</TT +> or + <TT +CLASS="COMMAND" +>ondrive</TT +>. It also requires that the + ending cylinder be specified with + <TT +CLASS="COMMAND" +>--end</TT +> or the partition size be + specified with <TT +CLASS="COMMAND" +>--size</TT +>. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--end</TT +></DT +><DD +><P +>Specifies the ending cylinder for the partition. It + requires that the starting cylinder be specified with + <TT +CLASS="COMMAND" +>--start</TT +>. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--badblocks</TT +></DT +><DD +><P +>Specifies that the partition should be checked for bad + sectors. + </P +></DD +></DL +></DIV +> + </P +><P +>All partitions created will be formatted as part of the + installation process unless <TT +CLASS="COMMAND" +>--noformat</TT +> and + <TT +CLASS="COMMAND" +>--onpart</TT +> are used. + </P +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="90%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="./stylesheet-images/note.png" +HSPACE="5" +ALT="Note"></TD +><TH +ALIGN="LEFT" +VALIGN="CENTER" +><B +>Note</B +></TH +></TR +><TR +><TD +> </TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +> If partitioning fails for any reason, diagnostic messages will + appear on virtual console 3. + </P +></TD +></TR +></TABLE +></DIV +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-RAID" +><TT +CLASS="COMMAND" +>raid</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>raid</TT +> (optional)</DT +><DD +><P +>Assembles a software RAID device. This command is of the form:</P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +>raid <TT +CLASS="REPLACEABLE" +><I +><mntpoint></I +></TT +> --level <TT +CLASS="REPLACEABLE" +><I +><level></I +></TT +> --device <TT +CLASS="REPLACEABLE" +><I +><mddevice></I +></TT +><TT +CLASS="REPLACEABLE" +><I +><partitions*></I +></TT +></PRE +></TD +></TR +></TABLE +><P +>The <TT +CLASS="REPLACEABLE" +><I +><mntpoint></I +></TT +> is the location + where the RAID filesystem is mounted. If it is + <TT +CLASS="FILENAME" +>/</TT +>, the RAID level must be 1 unless a boot + partition (<TT +CLASS="FILENAME" +>/boot</TT +>) is present. If a boot + partition is present, the <TT +CLASS="FILENAME" +>/boot</TT +> partition + must be level 1 and the root (<TT +CLASS="FILENAME" +>/</TT +>) partition + can be any of the available types. The + <TT +CLASS="REPLACEABLE" +><I +><partitions*></I +></TT +> (which denotes + that multiple partitions can be listed) lists the RAID + identifiers to add to the RAID array. + <P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>--level <TT +CLASS="REPLACEABLE" +><I +><level></I +></TT +></TT +></DT +><DD +><P +>RAID level to use (0, 1, or 5).</P +></DD +><DT +><TT +CLASS="COMMAND" +>--device <TT +CLASS="REPLACEABLE" +><I +><mddevice></I +></TT +></TT +></DT +><DD +><P +>Name of the RAID device to use (such as md0 or md1). + RAID devices range from md0 to md7, and each may only be + used once. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--spares=<TT +CLASS="REPLACEABLE" +><I +>N</I +></TT +></TT +></DT +><DD +><P +>Specifies that there should be N spare drives allocated + for the RAID array. Spare drives are used to rebuild the + array in case of drive failure. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--fstype </TT +></DT +><DD +><P +>Sets the filesystem type for the RAID array. Valid values + are ext2, ext3, swap, and vfat. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--noformat</TT +></DT +><DD +><P +>Do not format the RAID array.</P +></DD +></DL +></DIV +> + </P +><P +>The following example shows how to create a RAID level 1 + partition for <TT +CLASS="FILENAME" +>/</TT +>, and a RAID level 5 for + <TT +CLASS="FILENAME" +>/usr</TT +>, assuming there are three SCSI disks + on the system. It also creates three swap partitions, one on + each drive. + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>part raid.01 --size 60 --ondisk sda +part raid.02 --size 60 --ondisk sdb +part raid.03 --size 60 --ondisk sdc</TT +></PRE +></TD +></TR +></TABLE +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>part swap --size 128 --ondisk sda +part swap --size 128 --ondisk sdb +part swap --size 128 --ondisk sdc</TT +></PRE +></TD +></TR +></TABLE +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>part raid.11 --size 1 --grow --ondisk sda +part raid.12 --size 1 --grow --ondisk sdb +part raid.13 --size 1 --grow --ondisk sdc</TT +></PRE +></TD +></TR +></TABLE +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>raid / --level 1 --device md0 raid.01 raid.02 raid.03 +raid /usr --level 5 --device md1 raid.11 raid.12 raid.13</TT +></PRE +></TD +></TR +></TABLE +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-REBOOT" +><TT +CLASS="COMMAND" +>reboot</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>reboot</TT +> (optional)</DT +><DD +><P +>Reboot after the installation is complete (no + arguments). Normally, kickstart displays a message and waits for + the user to press a key before rebooting. + </P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-ROOTPW" +><TT +CLASS="COMMAND" +>rootpw</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>rootpw</TT +> (required)</DT +><DD +><P +><TT +CLASS="COMMAND" +>rootpw [--iscrypted] <TT +CLASS="REPLACEABLE" +><I +><password></I +></TT +></TT +></P +><P +>Sets the system's root password to the + <TT +CLASS="REPLACEABLE" +><I +><password></I +></TT +> argument.</P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>--iscrypted</TT +></DT +><DD +><P +>If this is present, the password argument is assumed to + already be encrypted.</P +></DD +></DL +></DIV +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-SKIPX" +><TT +CLASS="COMMAND" +>skipx</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>skipx</TT +> (optional)</DT +><DD +><P +>If present, X is not configured on the installed system.</P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-TEXT" +><TT +CLASS="COMMAND" +>text</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>text</TT +> (optional)</DT +><DD +><P +>Perform the kickstart installation in text mode. Kickstart + installations are performed in graphical mode by default.</P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-TIMEZONE" +><TT +CLASS="COMMAND" +>timezone</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>timezone</TT +> (required)</DT +><DD +><P +><TT +CLASS="COMMAND" +>timezone [--utc] <TT +CLASS="REPLACEABLE" +><I +><timezone></I +></TT +></TT +></P +><P +>Sets the system time zone to + <TT +CLASS="REPLACEABLE" +><I +><timezone></I +></TT +> which may be any of + the time zones listed by <TT +CLASS="COMMAND" +>timeconfig</TT +>. + </P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>--utc</TT +></DT +><DD +><P +>If present, the system assumes the hardware clock is set + to UTC (Greenwich Mean) time. + </P +></DD +></DL +></DIV +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-UPGRADE" +><TT +CLASS="COMMAND" +>upgrade</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>upgrade</TT +> (optional)</DT +><DD +><P +>Tells the system to upgrade an existing system rather than + install a fresh system. + </P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-XCONFIG" +><TT +CLASS="COMMAND" +>xconfig</TT +></A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>xconfig</TT +> (optional)</DT +><DD +><P +>Configures the X Window System. If this option is not given, the + user will need to configure X manually during the installation, + if X was installed; this option should not be used if X is not + installed on the final system. + </P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>--noprobe</TT +></DT +><DD +><P +>Do not probe the monitor.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--card <TT +CLASS="REPLACEABLE" +><I +><card></I +></TT +></TT +></DT +><DD +><P +>Use card <TT +CLASS="REPLACEABLE" +><I +><card></I +></TT +>; this + card name should be from the list of cards in + <B +CLASS="APPLICATION" +>Xconfigurator</B +>. If this + argument is not provided, + <B +CLASS="APPLICATION" +>Anaconda</B +> will probe the + PCI bus for the card. Since AGP is part of the PCI bus, + AGP cards will be detected if supported. The probe order + is determined by the PCI scan order of the motherboard. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--videoram <TT +CLASS="REPLACEABLE" +><I +><vram></I +></TT +></TT +></DT +><DD +><P +>Specify the amount of video RAM the video card has.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--monitor <TT +CLASS="REPLACEABLE" +><I +><mon></I +></TT +></TT +></DT +><DD +><P +>Use monitor <TT +CLASS="REPLACEABLE" +><I +><mon></I +></TT +>; this + monitor name should be from the list of monitors in + <B +CLASS="APPLICATION" +>Xconfigurator</B +>. This is + ignored if <TT +CLASS="USERINPUT" +><B +>--hsync</B +></TT +> or + <TT +CLASS="USERINPUT" +><B +>--vsync</B +></TT +> is provided. If no + monitor information is provided, the installation + program tries to probe for it automatically. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--hsync <TT +CLASS="REPLACEABLE" +><I +><sync></I +></TT +></TT +></DT +><DD +><P +>Specifies the horizontal sync frequency of the monitor.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--vsync <TT +CLASS="REPLACEABLE" +><I +><sync></I +></TT +></TT +></DT +><DD +><P +>Specifies the vertical sync frequency of the monitor.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--defaultdesktop=GNOME</TT +> or + <TT +CLASS="COMMAND" +>--defaultdesktop=KDE</TT +></DT +><DD +><P +>Sets the default desktop to either GNOME or KDE (and + assumes that GNOME and/or KDE has been installed through + <TT +CLASS="COMMAND" +>%packages</TT +>). + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--startxonboot</TT +></DT +><DD +><P +>Use a graphical login on the installed system.</P +></DD +><DT +><TT +CLASS="COMMAND" +>--resolution <TT +CLASS="REPLACEABLE" +><I +><res></I +></TT +></TT +></DT +><DD +><P +>Specify the default resolution for the X Window System + on the installed system. Valid values are 640x480, + 800x600, 1024x768, 1152x864, 1280x1024, 1400x1050, + 1600x1200. Be sure to specify a resolution that is + compatible with the video card and monitor. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--depth <TT +CLASS="REPLACEABLE" +><I +><cdepth></I +></TT +></TT +></DT +><DD +><P +>Specify the default color depth for the X Window System + on the installed system. Valid values are 8, 16, 24, and + 32. Be sure to specify a color depth that is + compatible with the video card and monitor. + </P +></DD +></DL +></DIV +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-ZEROMBR" +><TT +CLASS="COMMAND" +>zerombr</TT +> — Partition Table + Initialization</A +></H1 +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>zerombr</TT +> (optional)</DT +><DD +><P +>If <TT +CLASS="COMMAND" +>zerombr</TT +> is specified, and + <TT +CLASS="COMMAND" +>yes</TT +> is its sole argument, any + invalid partition tables found on disks are initialized. This + will destroy all of the contents of disks with invalid partition + tables. This command should be in the following format: + </P +><P +><TT +CLASS="COMMAND" +>zerombr yes</TT +></P +><P +> No other format is effective. + </P +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-PACKAGESELECTION" +><TT +CLASS="COMMAND" +>%packages</TT +> — Package Selection</A +></H1 +><P +> Use the <TT +CLASS="COMMAND" +>%packages</TT +> command to begin a kickstart file + section that lists the packages you would like to install (this is for + installations only, as package selection during upgrades is not + supported). + </P +><P +> Use the <TT +CLASS="COMMAND" +>%packages --resolvedeps</TT +><A +HREF="#FTN.NEW-OPTION" +>[1]</A +> to install the listed packages and automatically + resolve package dependencies. + </P +><P +> Use the <TT +CLASS="COMMAND" +>%packages --ignoredeps</TT +><A +HREF="#FTN.NEW-OPTION" +>[1]</A +> to ignore the unresolved dependencies and + install the listed packages without the dependencies. + </P +><P +> Packages can be specified by component or by individual package name. + The installation program defines several components that group + together related packages. See the + <TT +CLASS="FILENAME" +>RedHat/base/comps</TT +> file on any Red Hat Linux CD-ROM for a + list of components. The components are defined by the lines that + begin with a number followed by a space and then the component name. + Each package in that component is then listed, line-by-line. + Individual packages lack the leading number found in front of + component lines. + </P +><P +> Additionally, there are three other types of lines in the + <TT +CLASS="FILENAME" +>comps</TT +> file: + </P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +>Architecture specific (i386:, ia64:, alpha:, and sparc64:)</DT +><DD +><P +>If a package name begins with an architecture type, you only + need to type in the package name, not the architecture name. For + example: + </P +><P +>For <TT +CLASS="COMPUTEROUTPUT" +>i386: apmd</TT +> you only + need to use the <TT +CLASS="COMPUTEROUTPUT" +>apmd</TT +> part for + that specific package to be installed. + </P +></DD +><DT +>Lines beginning with <TT +CLASS="FILENAME" +>?</TT +></DT +><DD +><P +>Lines that begin with a <TT +CLASS="COMMAND" +>?</TT +> are used by the + installation program and should not be altered. + </P +></DD +><DT +>Lines beginning with <TT +CLASS="FILENAME" +>--hide</TT +></DT +><DD +><P +>If a package name begins with <TT +CLASS="FILENAME" +>--hide</TT +>, you + only need to type in the package name, without the + <TT +CLASS="FILENAME" +>--hide</TT +>. For example: + </P +><P +>For <TT +CLASS="FILENAME" +>--hide Network Server</TT +> you only need to + use the <TT +CLASS="FILENAME" +>Network Server</TT +> part for that + specific package to be installed. + </P +></DD +></DL +></DIV +><P +> In most cases, it is only necessary to list the desired components and + not individual packages. Note that the <TT +CLASS="COMMAND" +>Base</TT +> + component is always selected by default, so it is not necessary to + specify it in the <TT +CLASS="COMMAND" +>%packages</TT +> section. + </P +><P +> Here is an example <TT +CLASS="COMMAND" +>%packages</TT +> selection: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="SCREEN" +>%packages +@ Network Managed Workstation +@ Development +@ Web Server +@ X Window System +ImageMagick</PRE +></TD +></TR +></TABLE +><P +> As you can see, components are specified, one to a line, starting with + an <TT +CLASS="COMMAND" +>@</TT +> symbol, a space, and then the full component + name as given in the <TT +CLASS="FILENAME" +>comps</TT +> file. Specify + individual packages with no additional characters (the + <TT +CLASS="FILENAME" +>ImageMagick</TT +> line in the example above is an + individual package). + </P +><P +> You can also direct the kickstart installation to install the + default packages for a workstation (KDE or GNOME) or server + installation (or choose an everything installation to install all + packages). To do this, simply add <I +CLASS="EMPHASIS" +>one</I +> of the + following lines to the <TT +CLASS="COMMAND" +>%packages</TT +> section: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>@ GNOME +@ KDE +@ Server +@ Everything</TT +></PRE +></TD +></TR +></TABLE +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-PREINSTALLCONFIG" +><TT +CLASS="COMMAND" +>%pre</TT +> — Pre-Installation Configuration + Section</A +></H1 +><P +> You can add commands to run on the system immediately after the + <TT +CLASS="FILENAME" +>ks.cfg</TT +> has been parsed. This section must be at + the end of the kickstart file (after the commands) and must start with + the <TT +CLASS="COMMAND" +>%pre</TT +> command. Note that you can access the + network in the <TT +CLASS="COMMAND" +>%pre</TT +> section; however, + <I +CLASS="FIRSTTERM" +>name service</I +> has not been configured at this + point, so only IP addresses will work. Here is an example + <TT +CLASS="COMMAND" +>%pre</TT +> section: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>%pre + +# add comment to /etc/motd +echo "Kickstart-installed Red Hat Linux `/bin/date`" > /etc/motd + +# add another nameserver +echo "nameserver 10.10.0.2" >> /etc/resolv.conf</TT +></PRE +></TD +></TR +></TABLE +><P +> This section creates a message-of-the-day file containing the date the + kickstart installation took place. It also gets around the + <TT +CLASS="COMMAND" +>network</TT +> command's limitation of only one name + server by adding another nameserver to + <TT +CLASS="FILENAME" +>/etc/resolv.conf</TT +>. + </P +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="./stylesheet-images/note.png" +HSPACE="5" +ALT="Note"></TD +><TH +ALIGN="LEFT" +VALIGN="CENTER" +><B +>Note</B +></TH +></TR +><TR +><TD +> </TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +> Note that the pre-install script is not run in the change root + environment. + </P +></TD +></TR +></TABLE +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-POSTINSTALLCONFIG" +><TT +CLASS="COMMAND" +>%post</TT +> — Post-Installation Configuration + Section</A +></H1 +><P +> You have the option of adding commands to run on the system once the + installation is complete. This section must be at the end of the + kickstart file and must start with the <TT +CLASS="COMMAND" +>%post</TT +> + command. + </P +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="./stylesheet-images/note.png" +HSPACE="5" +ALT="Note"></TD +><TH +ALIGN="LEFT" +VALIGN="CENTER" +><B +>Note</B +></TH +></TR +><TR +><TD +> </TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +> If you configured the network with static IP information, including + a nameserver, you can access the network and resolve IP addresses in + the <TT +CLASS="COMMAND" +>%post</TT +> section. If you configured the network + for DHCP, the <TT +CLASS="FILENAME" +>/etc/resolv.conf</TT +> file has not + been completed when the installation executes the + <TT +CLASS="COMMAND" +>%post</TT +> section. You can access the network, + but you can not resolve IP addresses. Thus, if you are using DHCP, + you must specify IP addresses in the <TT +CLASS="COMMAND" +>%post</TT +> + section. + </P +></TD +></TR +></TABLE +></DIV +><P +> Here is an example <TT +CLASS="COMMAND" +>%post</TT +> section that creates a + message of the day file containing the date that the kickstart + installation took place, and gets around the + <TT +CLASS="COMMAND" +>network</TT +> command's limitation of one nameserver + only by adding another nameserver to + <TT +CLASS="FILENAME" +>/etc/resolv.conf</TT +>. + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="SCREEN" +>%post + +# add comment to /etc/motd +echo "Kickstart-installed Red Hat Linux `/bin/date`" > /etc/motd + +# add another nameserver +echo "nameserver 10.10.0.2" >> /etc/resolv.conf</PRE +></TD +></TR +></TABLE +><DIV +CLASS="NOTE" +><P +></P +><TABLE +CLASS="NOTE" +WIDTH="100%" +BORDER="0" +><TR +><TD +WIDTH="25" +ALIGN="CENTER" +VALIGN="TOP" +><IMG +SRC="./stylesheet-images/note.png" +HSPACE="5" +ALT="Note"></TD +><TH +ALIGN="LEFT" +VALIGN="CENTER" +><B +>Note</B +></TH +></TR +><TR +><TD +> </TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +><P +> The post-install script is run in a chroot environment; therefore, + performing tasks such as copying scripts or RPMs from the + installation media will not work. + </P +></TD +></TR +></TABLE +></DIV +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>--nochroot</TT +></DT +><DD +><P +>Allows you to specify commands that you would like to run + outside of the chroot environment. + </P +><P +>The following example copies the file + <TT +CLASS="FILENAME" +>/etc/resolv.conf</TT +> to the filesystem that was + just installed. +<TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>%post --nochroot +cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf</TT +></PRE +></TD +></TR +></TABLE +> + </P +></DD +><DT +><TT +CLASS="COMMAND" +>--interpreter <TT +CLASS="REPLACEABLE" +><I +>/usr/bin/perl</I +></TT +></TT +></DT +><DD +><P +>Allows you to specify a different scripting language, such as + Perl. Replace <TT +CLASS="REPLACEABLE" +><I +>/usr/bin/perl</I +></TT +> with the + scripting language of your choice. + </P +><P +>The following example uses a Perl script to replace + <TT +CLASS="FILENAME" +>/etc/HOSTNAME</TT +>. + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="90%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +>%post --interpreter /usr/bin/perl + +# replace /etc/HOSTNAME +open(HN, ">HOSTNAME"); +print HN "1.2.3.4 an.ip.address\n";</TT +></PRE +></TD +></TR +></TABLE +></DD +></DL +></DIV +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-INCLUDE" +><TT +CLASS="COMMAND" +>%include</TT +> — Include Contents of Another File + Section<A +HREF="#FTN.NEW-OPTION" +>[1]</A +></A +></H1 +><P +> Use the <TT +CLASS="COMMAND" +>%include + <TT +CLASS="REPLACEABLE" +><I +>/path/to/file</I +></TT +></TT +> command to include + the contents of another file in the kickstart file as though the + contents were at the location of the <TT +CLASS="COMMAND" +>%include</TT +> + command in the kickstart file. + </P +></DIV +></DIV +><DIV +CLASS="CHAPTER" +><CHAPTER><H1 +><A +NAME="CH-KICKSTART-PUTKICKSTARTHERE" +>Chapter 4. Where to Put A Kickstart File</A +></H1 +><P +> A kickstart file must be placed in one of two locations: + </P +><P +></P +><UL +><LI +><P +>On a boot disk</P +></LI +><LI +><P +>On a network</P +></LI +></UL +><P +> Normally a kickstart file is copied to the boot disk, or made + available on the network. The network-based approach is most commonly + used, as most kickstart installations tend to be performed on + networked computers. + </P +><P +> Let us take a more in-depth look at where the kickstart + file may be placed. + </P +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-DISKBASED" +>Creating a Kickstart Boot Disk</A +></H1 +><P +> To perform a diskette-based kickstart installation, the kickstart file + must be named <TT +CLASS="FILENAME" +>ks.cfg</TT +> and must be located in the + boot disk's top-level directory. Note that the Red Hat Linux boot disks are in + MS-DOS format, so it is easy to copy the kickstart file under Linux + using the <TT +CLASS="COMMAND" +>mcopy</TT +> command: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMMAND" +>mcopy ks.cfg a:</TT +></PRE +></TD +></TR +></TABLE +><P +> Alternatively, you can use Windows to copy the file. You can also + mount the MS-DOS boot disk and <TT +CLASS="COMMAND" +>cp</TT +> the file + over. + </P +></DIV +><DIV +CLASS="SECT1" +><SECT1><H1 +CLASS="SECT1" +><A +NAME="S2-KICKSTART-NETWORKBASED" +>Making the Kickstart File Available on the Network</A +></H1 +><P +> Network installations using kickstart are quite common, + because system administrators can easily + automate the installation on many networked computers quickly and + painlessly. In general, the approach most commonly used is for the + administrator to have both a BOOTP/DHCP server and an NFS server on + the local network. The BOOTP/DHCP server is used to give the client + system its networking information, while the actual files used during + the installation are served by the NFS server. Often, these two + servers run on the same physical machine, but they are not required + to. + </P +><P +> To perform a network-based kickstart installation, you must have a + BOOTP/DHCP server on your network, and it must include configuration + information for the machine on which you are attempting to install + Red Hat Linux. The BOOTP/DHCP server will provide the client with its + networking information as well as the location of the kickstart file. + </P +><P +> If a kickstart file is specified by the BOOTP/DHCP server, the client + system will attempt an NFS mount of the file's path, and will copy the + specified file to the client, using it as the kickstart file. The + exact settings required vary depending on the BOOTP/DHCP server you + use. + </P +><P +> Here is an example of a line from the <TT +CLASS="FILENAME" +>dhcpd.conf</TT +> + file for the DHCP server shipped with Red Hat Linux: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="COMPUTEROUTPUT" +><TT +CLASS="FILENAME" +>filename</TT +> <TT +CLASS="REPLACEABLE" +><I +>"/usr/new-machine/kickstart/"</I +></TT +>; +next-server <TT +CLASS="REPLACEABLE" +><I +>blarg.redhat.com;</I +></TT +></TT +></PRE +></TD +></TR +></TABLE +><P +> Note that you should replace the value after + <TT +CLASS="COMPUTEROUTPUT" +>filename</TT +> with the name of the + kickstart file (or the directory in which the kickstart file + resides) and the value after + <TT +CLASS="COMPUTEROUTPUT" +>next-server</TT +> + with the NFS server name. + </P +><P +> If the filename returned by the BOOTP/DHCP server ends with a slash + ("/"), then it is interpreted as a path only. In this case, the + client system mounts that path using NFS, and searches for a + particular file. The filename the client searches for is: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="FILENAME" +><TT +CLASS="REPLACEABLE" +><I +><ip-addr></I +></TT +>-kickstart</TT +></PRE +></TD +></TR +></TABLE +><P +> The <TT +CLASS="FILENAME" +><TT +CLASS="REPLACEABLE" +><I +><ip-addr></I +></TT +></TT +> + section of the filename should be replaced with the client's IP + address in dotted decimal notation. For example, the filename for a + computer with an IP address of 10.10.0.1 would be + <TT +CLASS="FILENAME" +>10.10.0.1-kickstart</TT +>. + </P +><P +> Note that if you do not specify a server name, then the client system + will attempt to use the server that answered the BOOTP/DHCP request as + its NFS server. If you do not specify a path or filename, the client + system will try to mount <TT +CLASS="FILENAME" +>/kickstart</TT +> from the + BOOTP/DHCP server, and will try to find the kickstart file using the + same + <TT +CLASS="FILENAME" +><TT +CLASS="REPLACEABLE" +><I +><ip-addr></I +></TT +>-kickstart</TT +> + filename as described above. + </P +></DIV +></DIV +><DIV +CLASS="CHAPTER" +><CHAPTER><H1 +><A +NAME="CH-KICKSTART--STARTINGINSTALL" +>Chapter 5. Starting a Kickstart Installation</A +></H1 +><P +> To begin a kickstart installation, you must boot the system from a Red Hat Linux + boot diskette or the CD-ROM and enter a special boot command at the boot prompt. If the + kickstart file is located on a boot diskette that was created from the + <TT +CLASS="FILENAME" +>boot.img</TT +> or <TT +CLASS="FILENAME" +>bootnet.img</TT +> image + file, the correct boot command would be: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="PROMPT" +>boot:</TT +> <TT +CLASS="USERINPUT" +><B +>linux ks=floppy</B +></TT +></PRE +></TD +></TR +></TABLE +><P +> The <TT +CLASS="USERINPUT" +><B +>linux ks=floppy</B +></TT +> command also works if the + <TT +CLASS="FILENAME" +>ks.cfg</TT +> file is located on a vfat or ext2 filesystem on a + floppy diskette and you boot from the Red Hat Linux CD-ROM. + </P +><P +> An alternate boot command for booting off the Red Hat Linux CD-ROM and having the + kickstart file on a vfat or ext2 filesystem on a floppy diskette is: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="PROMPT" +>boot:</TT +> <TT +CLASS="USERINPUT" +><B +>linux ks=hd:fd0/ks.cfg</B +></TT +></PRE +></TD +></TR +></TABLE +><P +> If you need to use a driver disk with kickstart, you can still have the + kickstart file on a floppy disk: + </P +><TABLE +BORDER="0" +BGCOLOR="#E0E0E0" +WIDTH="100%" +><TR +><TD +><PRE +CLASS="SCREEN" +><TT +CLASS="PROMPT" +>boot:</TT +> <TT +CLASS="USERINPUT" +><B +>linux ks=floppy dd</B +></TT +></PRE +></TD +></TR +></TABLE +><P +> The Red Hat Linux installation program looks for a kickstart file if the + <TT +CLASS="COMMAND" +>ks</TT +> command line argument is passed to the kernel. + The command line argument can take a number of forms: + </P +><P +></P +><DIV +CLASS="VARIABLELIST" +><DL +><DT +><TT +CLASS="COMMAND" +>ks=nfs:<TT +CLASS="REPLACEABLE" +><I +><server></I +></TT +>/<TT +CLASS="REPLACEABLE" +><I +><path></I +></TT +></TT +></DT +><DD +><P +>The installation program will look for the kickstart file on the NFS + server <TT +CLASS="REPLACEABLE" +><I +><server></I +></TT +>, as file + <TT +CLASS="REPLACEABLE" +><I +><path></I +></TT +>. The installation program + will use DHCP to configure the Ethernet card. For example, if your + NFS server is server.example.com and the kickstart file is in the + NFS share /mydir/ks.cfg, the correct boot command would be + <TT +CLASS="COMMAND" +>ks=nfs:server.example.com:/mydir/ks.cfg</TT +>. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>ks=http:<TT +CLASS="REPLACEABLE" +><I +><server></I +></TT +>/<TT +CLASS="REPLACEABLE" +><I +><path></I +></TT +></TT +></DT +><DD +><P +>The installation program will look for the kickstart file on the HTTP + server <TT +CLASS="REPLACEABLE" +><I +><server></I +></TT +>, as file + <TT +CLASS="REPLACEABLE" +><I +><path></I +></TT +>. The installation program + will use DHCP to configure the Ethernet card. For example, if your + HTTP server is server.example.com and the kickstart file is in the + HTTP directory /mydir/ks.cfg, the correct boot command would be + <TT +CLASS="COMMAND" +>ks=http:server.example.com:/mydir/ks.cfg</TT +>. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>ks=floppy</TT +></DT +><DD +><P +>The installation program looks for the file + <TT +CLASS="FILENAME" +>ks.cfg</TT +> on a vfat or ext2 filesystem on the floppy in + drive <TT +CLASS="FILENAME" +>/dev/fd0</TT +>. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>ks=hd:<TT +CLASS="REPLACEABLE" +><I +><device></I +></TT +>/<TT +CLASS="REPLACEABLE" +><I +><file></I +></TT +></TT +></DT +><DD +><P +>The installation program will mount the filesystem on + <TT +CLASS="REPLACEABLE" +><I +><device></I +></TT +> (which must be vfat or + ext2), and look for the kickstart configuration file as + <TT +CLASS="REPLACEABLE" +><I +><file></I +></TT +> in that filesystem (for + example, <TT +CLASS="COMMAND" +>ks=hd:sda3/mydir/ks.cfg</TT +>). + </P +></DD +><DT +><TT +CLASS="COMMAND" +>ks=file:/<TT +CLASS="REPLACEABLE" +><I +><file></I +></TT +></TT +></DT +><DD +><P +>The installation program will try to read the file + <TT +CLASS="REPLACEABLE" +><I +><file></I +></TT +> from the filesystem; no + mounts will be done. This is normally used if the kickstart file + is already on the <TT +CLASS="FILENAME" +>initrd</TT +> image. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>ks=cdrom:/<TT +CLASS="REPLACEABLE" +><I +><path></I +></TT +></TT +></DT +><DD +><P +>The installation program will look for the kickstart file on + CD-ROM, as file <TT +CLASS="REPLACEABLE" +><I +><path></I +></TT +>. + </P +></DD +><DT +><TT +CLASS="COMMAND" +>ks</TT +></DT +><DD +><P +>If <TT +CLASS="COMMAND" +>ks</TT +> is used alone, the installation program + will configure the Ethernet card in the system using DHCP. The + system will use the "bootServer" from the DHCP response as an NFS + server to read the kickstart file from (by default, this is the + same as the DHCP server). The name of the kickstart file is one + of the following: + </P +><P +></P +><UL +><LI +><P +>If DHCP is specified and the bootfile begins with a + <TT +CLASS="FILENAME" +>/</TT +>, the bootfile provided by DHCP is looked for + on the NFS server. + </P +></LI +><LI +><P +>If DHCP is specified and the bootfile begins with + something other then a <TT +CLASS="COMPUTEROUTPUT" +>/</TT +>, + the bootfile provided by DHCP is looked for in the + <TT +CLASS="FILENAME" +>/kickstart</TT +> directory on the NFS server. + </P +></LI +><LI +><P +>If DHCP did not specify a bootfile, then the installation + program tries to read the file + <TT +CLASS="FILENAME" +>/kickstart/1.2.3.4-kickstart</TT +>, where + <TT +CLASS="REPLACEABLE" +><I +>1.2.3.4</I +></TT +> is the numeric IP address + of the machine being installed. + </P +></LI +></UL +></DD +><DT +><TT +CLASS="COMMAND" +>ksdevice=<TT +CLASS="REPLACEABLE" +><I +><device></I +></TT +></TT +></DT +><DD +><P +>The installation program will use this network device to connect + to the network. For example, to start a kickstart installation + with the kickstart file on an NFS server that is connected to the + system through the eth1 device, use the command + <TT +CLASS="COMMAND" +>ks=nfs:<TT +CLASS="REPLACEABLE" +><I +><server:></I +></TT +>/<TT +CLASS="REPLACEABLE" +><I +><path></I +></TT +> + ksdevice=eth1</TT +> at the <TT +CLASS="PROMPT" +>boot:</TT +> prompt. + </P +></DD +></DL +></DIV +></DIV +></DIV +><H3 +CLASS="FOOTNOTES" +>Notes</H3 +><TABLE +BORDER="0" +CLASS="FOOTNOTES" +WIDTH="100%" +><TR +><TD +ALIGN="LEFT" +VALIGN="TOP" +WIDTH="5%" +><A +NAME="FTN.NEW-OPTION" +HREF="#NEW-OPTION" +>[1]</A +></TD +><TD +ALIGN="LEFT" +VALIGN="TOP" +WIDTH="95%" +><P +>This option is new to Red Hat Linux 7.3</P +></TD +></TR +></TABLE +></BODY +></HTML +>
\ No newline at end of file diff --git a/docs/kickstart-docs.txt b/docs/kickstart-docs.txt new file mode 100644 index 000000000..1a2107225 --- /dev/null +++ b/docs/kickstart-docs.txt @@ -0,0 +1,1531 @@ + +Kickstart + + Copyright © 2002 by Red Hat, Inc. + + [rhlogo.png] Red Hat, Inc. + + 1801 Varsity Drive + Raleigh NC 27606-2072 USA + Phone: +1 919 754 3700 + Phone: 888 733 4281 + Fax: +1 919 754 3701 + PO Box 13588 + Research Triangle Park NC 27709 USA + + kickstart(EN)-7.3-HTML-RHI (2002-04-01T16:30-0500) + + Copyright © 2002 by Red Hat, Inc. This material may be distributed + only subject to the terms and conditions set forth in the Open + Publication License, V1.0 or later (the latest version is presently + available at [1]http://www.opencontent.org/openpub/). + + Distribution of substantively modified versions of this document is + prohibited without the explicit permission of the copyright holder. + + Distribution of the work or derivative of the work in any standard + (paper) book form for commercial purposes is prohibited unless prior + permission is obtained from the copyright holder. + + The admonition graphics (note, tip, important, caution, and warning) + were created by Marianne Pecci <[2]goddess@ipass.net>. They may be + redistributed with explicit permission from Marianne Pecci and Red + Hat, Inc. + + Red Hat, Red Hat Network, the Red Hat "Shadow Man" logo, RPM, Maximum + RPM, the RPM logo, Linux Library, PowerTools, Linux Undercover, + RHmember, RHmember More, Rough Cuts, Rawhide and all Red Hat-based + trademarks and logos are trademarks or registered trademarks of Red + Hat, Inc. in the United States and other countries. + + Linux is a registered trademark of Linus Torvalds. + + Motif and UNIX are registered trademarks of The Open Group. + + Intel and Pentium are a registered trademarks of Intel Corporation. + Itanium and Celeron are trademarks of Intel Corporation. + + AMD, AMD Athlon, AMD Duron, and AMD K6 are trademarks of Advanced + Micro Devices, Inc. + + Netscape is a registered trademark of Netscape Communications + Corporation in the United States and other countries. + + Windows is a registered trademark of Microsoft Corporation. + + SSH and Secure Shell are trademarks of SSH Communications Security, + Inc. + + FireWire is a trademark of Apple Computer Corporation. + + S/390 and zSeries are trademarks of International Business Machines + Corporation. + + All other trademarks and copyrights referred to are the property of + their respective owners. + _________________________________________________________________ + + Table of Contents + [3]Introduction + + [4]What are Kickstart Installations? + [5]How Do You Perform a Kickstart Installation? + + [6]Creating the Kickstart File + [7]Kickstart Options + + [8]autostep + [9]auth + [10]bootloader + [11]clearpart + [12]device + [13]deviceprobe + [14]driverdisk + [15]firewall + [16]install + [17]Installation Methods + [18]interactive + [19]keyboard + [20]lang + [21]langsupport + [22]lilo + [23]lilocheck + [24]mouse + [25]network + [26]part + [27]raid + [28]reboot + [29]rootpw + [30]skipx + [31]text + [32]timezone + [33]upgrade + [34]xconfig + [35]zerombr -- Partition Table Initialization + [36]%packages -- Package Selection + [37]%pre -- Pre-Installation Configuration Section + [38]%post -- Post-Installation Configuration Section + [39]%include -- Include Contents of Another File Section[40][1] + + [41]Where to Put A Kickstart File + + [42]Creating a Kickstart Boot Disk + [43]Making the Kickstart File Available on the Network + + [44]Starting a Kickstart Installation + _________________________________________________________________ + +Introduction + _________________________________________________________________ + +What are Kickstart Installations? + + Many system administrators would prefer to use an automated + installation method to install Red Hat Linux on their machines. To + answer this need, Red Hat created the kickstart installation method. + Using kickstart, a system administrator can create a single file + containing the answers to all the questions that would normally be + asked during a typical Red Hat Linux installation. + + Kickstart files can be kept on single server system, and read by + individual computers during the installation. This installation method + can support the use of a single kickstart file to install Red Hat + Linux on multiple machines, making it ideal for network and system + administrators. + + Kickstart lets you automate most of a Red Hat Linux installation, + including: + + * Language selection + * Mouse configuration + * Keyboard selection + * Boot loader installation + * Disk partitioning + * Network configuration + * NIS, LDAP, Kerberos, Hesiod, and Samba authentication + * Firewall configuration + * Package selection + * X Window System configuration + _________________________________________________________________ + +How Do You Perform a Kickstart Installation? + + Kickstart installations can be performed using a local CD-ROM, a local + hard drive, or via NFS, FTP, or HTTP. + + To use kickstart, you must: + + 1. Create a kickstart file. + 2. Create a boot disk with the kickstart file or make the kickstart + file available on the network. + 3. Start the kickstart installation. + _________________________________________________________________ + +Creating the Kickstart File + + The kickstart file is a simple text file, containing a list of items, + each identified by a keyword. You can create it by editing a copy of + the sample.ks file found in the RH-DOCS directory of the Red Hat Linux + Documentation CD, using the Kickstart Configurator application, or + writing it from scratch. The Red Hat Linux installation program also + creates a sample kickstart file based on the options that you selected + during installation. It is written to the file /root/anaconda-ks.cfg. + You should be able to edit it with any text editor or word processor + that can save files as ASCII text. + + First, be aware of the following issues when you are creating your + kickstart file: + + * Items must be specified in order. That order is: + + Command section -- Refer to [45]the chapter called Kickstart + Options for a list of kickstart options. You must include the + required options. + + The %packages section -- Refer to [46]the Section called + %packages -- Package Selection in the chapter called + Kickstart Options for details. + + The %pre and %post sections -- These two sections can be in + any order and are not required. Refer to [47]the Section + called %pre -- Pre-Installation Configuration Section in the + chapter called Kickstart Options and [48]the Section called + %post -- Post-Installation Configuration Section in the + chapter called Kickstart Options for details. + * Items that are not required can be omitted. + * Omitting any required item will result in the installation program + prompting the user for an answer to the related item, just as the + user would be prompted during a typical installation. Once the + answer is given, the installation will continue unattended (unless + it finds another missing item). + * Lines starting with a pound sign ("#") are treated as comments and + are ignored. + * For kickstart upgrades, the following items are required: + + Language + + Installation method + + Device specification (if device is needed to perform + installation) + + Keyboard setup + + The upgrade keyword + + LILO configuration + If any other items are specified for an upgrade, those items will + be ignored (note that this includes package selection). + _________________________________________________________________ + +Kickstart Options + + The following options can be placed in a kickstart file. If you prefer + to use a graphical interface for creating your kickstart file, you can + use the Kickstart Configurator application. + _________________________________________________________________ + +autostep + + autostep (optional) + Similar to interactive except it goes to the next screen for + you. It is used mostly for debugging. + _________________________________________________________________ + +auth + + auth or authconfig (required) + Sets up the authentication options for the system. It's similar + to the authconfig command, which can be run after the install. + By default, passwords are normally encrypted and are not + shadowed. + + --enablemd5 + Use md5 encryption for user passwords. + + --enablenis + Turns on NIS support. By default, --enablenis uses + whatever domain it finds on the network. A domain should + almost always be set by hand (via --nisdomain). + + --nisdomain + NIS domain name to use for NIS services. + + --nisserver + Server to use for NIS services (broadcasts by default). + + --useshadow or --enableshadow + Use shadow passwords. + + --enableldap + Turns on LDAP support in /etc/nsswitch.conf, allowing + your system to retrieve information about users (UIDs, + home directories, shells, etc.) from an LDAP directory. + To use this option, you must have the nss_ldap package + installed. You must also specify a server and a base DN + with --ldapserver= and --ldapbasedn=. + + --enableldapauth + Use LDAP as an authentication method. This enables the + pam_ldap module for authentication and changing + passwords, using an LDAP directory. To use this option, + you must have the nss_ldap package installed. You must + also specify a server and a base DN with --ldapserver= + and --ldapbasedn=. + + --ldapserver= + If you specified either --enableldap or --enableldapauth, + the name of the LDAP server to use. This option is set in + the /etc/ldap.conf file. + + --ldapbasedn= + If you specified either --enableldap or --enableldapauth, + the DN (distinguished name) in your LDAP directory tree + under which user information is stored. This option is + set in the /etc/ldap.conf file. + + --enableldaptls + Use TLS (Transport Layer Security) lookups. This option + allows LDAP to send encrypted usernames and passwords to + an LDAP server before authentication. + + --enablekrb5 + Use Kerberos 5 for authenticating users. Kerberos itself + does not know about home directories, UIDs, or shells. So + if you enable Kerberos you will need to make users' + accounts known to this workstation by enabling LDAP, NIS, + or Hesiod or by using the /usr/sbin/useradd command to + make their accounts known to this workstation. If you use + this option, you must have the pam_krb5 package + installed. + + --krb5realm + The Kerberos 5 realm to which your workstation belongs. + + --krb5kdc + The KDC (or KDCs) that serve requests for the realm. If + you have multiple KDCs in your realm, separate their + names with commas (,). + + --krb5adminserver + The KDC in your realm that is also running kadmind. This + server handles password changing and other administrative + requests. This server must be run on the master KDC if + you have more than one KDC. + + --enablehesiod + Enable Hesiod support for looking up user home + directories, UIDs, and shells. More information on + setting up and using Hesiod on your network is in + /usr/share/doc/glibc-2.x.x/README.hesiod, which is + included in the glibc package. Hesiod is an extension of + DNS that uses DNS records to store information about + users, groups, and various other items. + + --hesiodlhs + The Hesiod LHS ("left-hand side") option, set in + /etc/hesiod.conf. This option is used by the Hesiod + library to determine the name to search DNS for when + looking up information, similar to LDAP's use of a base + DN. + + --hesiodrhs + The Hesiod RHS ("right-hand side") option, set in + /etc/hesiod.conf. This option is used by the Hesiod + library to determine the name to search DNS for when + looking up information, similar to LDAP's use of a base + DN. + + Tip Tip + + + To look up user information for "jim", the Hesiod library looks up + jim.passwd<LHS><RHS>, which should resolve to a TXT record that looks + like what his passwd entry would look like (jim:*:501:501:Jungle + Jim:/home/jim:/bin/bash). For groups, the situation is identical, + except jim.group<LHS><RHS> would be used. + Looking up users and groups by number is handled by making "501.uid" a + CNAME for "jim.passwd", and "501.gid" a CNAME for "jim.group". Note + that the LHS and RHS do not have periods . put in front of them when + the library determines the name for which to search, so the LHS and + RHS usually begin with periods. + + --enablesmbauth + Enables authentication of users against an SMB server + (typically a Samba or Windows server). SMB authentication + support does not know about home directories, UIDs, or + shells. So if you enable it you will need to make users' + accounts known to the workstation by enabling LDAP, NIS, + or Hesiod or by using the /usr/sbin/useradd command to + make their accounts known to the workstation. To use this + option, you must have the pam_smb package installed. + + --smbservers= + The name of the server(s) to use for SMB authentication. + To specify more than one server, separate the names with + commas (,). + + --smbworkgroup= + The name of the workgroup for the SMB servers. + + --enablecache + Enables the nscd service. The nscd service caches + information about users, groups, and various other types + of information. Caching is especially helpful if you + choose to distribute information about users and groups + over your network using NIS, LDAP, or hesiod. + _________________________________________________________________ + +bootloader + + bootloader (required) + Specifies how the boot loader should be installed and whether + the boot loader should be LILO or GRUB. + + --append + Specifies kernel parameters. + + --location= + Specifies where the boot record is written. Valid values + are the following: mbr (the default), partition (installs + the boot loader on the first sector of the partition + containing the kernel), or none (do not install the boot + loader). + + --password=mypassword + If using GRUB, sets the GRUB boot loader password to + mypassword. This should be used to restrict access to the + GRUB shell where arbitrary kernel options can be passed. + + --md5pass=mypassword + If using GRUB, similar to --password except mypassword + should be the password already encrypted. + + --useLilo + Use LILO instead of GRUB as the boot loader. + + --linear + If using LILO, use the linear LILO option; this is only + for backwards compatibility (and linear is now used by + default). + + --nolinear + If using LILO, use the nolinear LILO option; linear is + the default. + + --lba32 + If using LILO, force use of lba32 mode instead of + autodetecting. + + --upgrade [49][1] + Upgrade the existing boot loader configuration. This + option is only available for upgrades. + _________________________________________________________________ + +clearpart + + clearpart (optional) + Removes partitions from the system, prior to creation of new + partitions. By default, no partitions are removed. + + --linux + Erases all Linux partitions. + + --all + Erases all partitions from the system. + + --drives + Specifies which drives to clear partitions from. + + --initlabel + Initializes the disk label to the default for your + architecture (msdos for x86 and gpt for Itanium). It is + useful so that the installation program does not ask if + it should initialize the disk label if installing to a + brand new hard drive. + + Note Note + + + If the clearpart command, then the --onpart command cannot be used on + a logical partition. + _________________________________________________________________ + +device + + device (optional) + On most PCI systems, the installation program will autoprobe + for Ethernet and SCSI cards properly. On older systems and some + PCI systems, however, kickstart needs a hint to find the proper + devices. The device command, which tells Anaconda to install + extra modules, is in this format: + +device <type> <moduleName> --opts <options> + + <type> should be scsi or eth, and <moduleName> is the name of + the kernel module which should be installed. + + --opts + Options to pass to the kernel module. Note that multiple + options may be passed if they are put in quotes. For + example: + +--opts "aic152x=0x340 io=11" + _________________________________________________________________ + +deviceprobe + + deviceprobe (optional) + Forces a probe of the PCI bus and loads modules for all the + devices found if a module is available. + _________________________________________________________________ + +driverdisk + + driverdisk (optional) + Driver disks can be used during kickstart installations. You + will need to copy the driver disk's contents to the root + directory of a partition on the system's hard drive. Then you + will need to use the driverdisk command to tell the + installation program where to look for the driver disk. + +driverdisk <partition> [--type <fstype>] + + <partition> is the partition containing the driver disk. + + --type + Filesystem type (for example, vfat, ext2, or ext3). + _________________________________________________________________ + +firewall + + firewall (optional) + Firewall options can be configured in kickstart. This + configuration corresponds to the Firewall Configuration screen + in the installation program. + +firewall [--high | --medium | --disabled] [--trust <device>] [--dhcp] [--ssh] +[--telnet] [--smtp] [--http] [--ftp] [--port <portspec>] + + Levels of security + Choose one of the following levels of security: + + + --high + + --medium + + --disabled + + --trust <device> + Listing a device here, such as eth0, allows all traffic coming + from that device to go through the firewall. To list more than + one device, use --trust eth0 --trust eth1. Do NOT use a + comma-separated format such as --trust eth0, eth1. + + Allow incoming + Enabling these options allow the specified services to pass + through the firewall. + + + --dhcp + + --ssh + + --telnet + + --smtp + + --http + + --ftp + + --port <portspec> + You can specify that ports be allowed through the firewall + using the port:protocol format. For example, if you wanted to + allow IMAP access through your firewall, you can specify + imap:tcp. You can also specify numeric ports explicitly; for + example, to allow UDP packets on port 1234 through, specify + 1234:udp. To specify multiple ports, separate them by commas. + _________________________________________________________________ + +install + + install (optional) + Tells the system to install a fresh system rather than upgrade + an existing system. This is the default mode. + _________________________________________________________________ + +Installation Methods + + You must use one of these four commands to specify what type of + kickstart installation is being performed: + + nfs + Install from the NFS server specified. + + + --server <server> + Server from which to install (hostname or IP). + + --dir <dir> + Directory containing the Red Hat installation tree. + + For example: + +nfs --server <server> --dir <dir> + + cdrom + Install from the first CD-ROM drive on the system. + + For example: + +cdrom + + harddrive + Install from a Red Hat installation tree on a local drive, + which must be either vfat or ext2. + + + --partition <partition> + Partition to install from (such as, sdb2). + + --dir <dir> + Directory containing the Red Hat installation tree. + + For example: + +harddrive --partition <partition> --dir <dir> + + url + Install from a Red Hat installation tree on a remote server via + FTP or HTTP. + + For example: + +url --url http://<server>/<dir> + +url --url ftp://<username>:<password>@<server>/<dir> + _________________________________________________________________ + +interactive + + interactive (optional) + Uses the information provided in the kickstart file during the + installation, but allow for inspection and modification of the + values given. You will be presented with each screen of the + installation program with the values from the kickstart file. + Either accept the values by clicking Next or change the values + and click Next to continue. See also [50]the Section called + autostep. + _________________________________________________________________ + +keyboard + + keyboard (required) + Sets system keyboard type. Here is the list of available + keyboards on i386, Itanium, and Alpha machines: + +azerty, be-latin1, be2-latin1, fr-latin0, fr-latin1, fr-pc, fr, wangbe, +ANSI-dvorak, dvorak-l, dvorak-r, dvorak, pc-dvorak-latin1, tr_f-latin5, +trf, bg, br-abnt2, cf, cz-lat2-prog, cz-lat2, defkeymap, defkeymap_V1.0, +dk-latin1, dk, emacs, emacs2, es, fi-latin1, fi, gr-pc, gr, hebrew, hu101, +is-latin1, it-ibm, it, it2, jp106, la-latin1, lt, lt.l4, nl, no-latin1, no, +pc110, pl, pt-latin1, pt-old, ro, ru-cp1251, ru-ms, ru-yawerty, ru, ru1, ru2, +ru_win, se-latin1, sk-prog-qwerty, sk-prog, sk-qwerty, tr_q-latin5, tralt, +trf, trq, ua, uk, us, croat, cz-us-qwertz, de-latin1-nodeadkeys, de-latin1, +de, fr_CH-latin1, fr_CH, hu, sg-latin1-lk450, sg-latin1, sg, sk-prog-qwertz, +sk-qwertz, slovene + + Here is the list for SPARC machines: + +sun-pl-altgraph, sun-pl, sundvorak, sunkeymap, sunt4-es, +sunt4-no-latin1, sunt5-cz-us, sunt5-de-latin1, sunt5-es, +sunt5-fi-latin1, sunt5-fr-latin1, sunt5-ru, sunt5-uk, sunt5-us-cz + _________________________________________________________________ + +lang + + lang (required) + Sets the language to use during installation. For example, to + set the language to English, the kickstart file should contain + the following line: + +lang en_US + + Valid language codes are the following (please note that these + are subject to change at any time): + +cs_CZ, da_DK, en_US, fr_FR, de_DE, is_IS, it_IT, ja_JP.eucJP, +ko_KR.eucKR, no_NO, pt_PT, ru_RU.koi8r, sl_SI, es_ES, sv_SE, uk_UA + _________________________________________________________________ + +langsupport + + langsupport (required) + Sets the language(s) to install on the system. The same + language codes used with lang can be used with langsupport. + + If you just want to install one language, specify it. For + example, to install and use the French language fr_FR: + +langsupport fr_FR + + --default + If you want to install language support for more than one + language, you must specify a default. + + For example, to install English and French and use English as + the default language: + +langsupport --default en_US fr_FR + + If you use --default with only one language, all languages will + be installed with the specified language set to the default. + _________________________________________________________________ + +lilo + + lilo (replaced by bootloader) + + Warning Warning + + + This option has been replaced by bootloader and is only available for + backwards compatibility. Refer to [51]the Section called bootloader. + + Specifies how the boot loader should be installed on the + system. By default, LILO installs on the MBR of the first disk, + and installs a dual-boot system if a DOS partition is found + (the DOS/Windows system will boot if the user types dos at the + LILO: prompt). + + --append <params> + Specifies kernel parameters. + + --linear + Use the linear LILO option; this is only for backwards + compatibility (and linear is now used by default). + + --nolinear + Use the nolinear LILO option; linear is now used by + default. + + --location= + Specifies where the LILO boot record is written. Valid + values are the following: mbr (the default) or partition + (installs the boot loader on the first sector of the + partition containing the kernel). If no location is + specified, LILO is not installed. + + --lba32 + Forces the use of lba32 mode instead of autodetecting. + _________________________________________________________________ + +lilocheck + + lilocheck (optional) + If lilocheck is present, the installation program checks for + LILO on the MBR of the first hard drive, and reboots the system + if it is found -- in this case, no installation is performed. + This can prevent kickstart from reinstalling an already + installed system. + _________________________________________________________________ + +mouse + + mouse (required) + Configures the mouse for the system, both in GUI and text + modes. Options are: + + --device <dev> + Device the mouse is on (such as --device ttyS0). + + --emulthree + If present, simultaneous clicks on the left and right + mouse buttons will be recognized as the middle mouse + button by the X Window System. This option should be used + if you have a two button mouse. + + After options, the mouse type may be specified as one of + the following: + +alpsps/2, ascii, asciips/2, atibm, generic, generic3, +genericps/2, generic3ps/2, genericusb, generic3usb, +geniusnm, geniusnmps/2,geniusprops/2, geniusscrollps/2, +geniusscrollps/2+, thinking, thinkingps/2, logitech, +logitechcc, logibm, logimman, logimmanps/2, logimman+, +logimman+ps/2, logimmusb, microsoft, msnew, msintelli, +msintellips/2, msintelliusb, msbm, mousesystems, mmseries, +mmhittab, sun, none + + If the mouse command is given without any arguments, or + it is omitted, the installation program will attempt to + autodetect the mouse. This procedure works for most + modern mice. + _________________________________________________________________ + +network + + network (optional) + Configures network information for the system. If the kickstart + installation does not require networking (in other words, it is + not installed over NFS, HTTP, or FTP), networking is not + configured for the system. If the installation does require + networking and network information is not provided in the + kickstart file, the Red Hat Linux installation program assumes + that the installation should be done over eth0 via a dynamic IP + address (BOOTP/DHCP), and configures the final, installed + system to determine its IP address dynamically. The network + option configures networking information for kickstart + installations via a network as well as for the installed + system. + + --bootproto + One of dhcp, bootp, or static (defaults to DHCP, and dhcp + and bootp are treated the same). Must be static for + static IP information to be used. + + --device <device> + Used to select a specific Ethernet device for + installation. Note that using --device <device> will not + be effective unless the kickstart file is a local file + (such as ks=floppy), since the installation program will + configure the network to find the kickstart file. + Example: + +network --bootproto dhcp --device eth0 + + --ip + IP address for the machine to be installed. + + --gateway + Default gateway as an IP address. + + --nameserver + Primary nameserver, as an IP address. + + --nodns + Do not configure any DNS server. + + --netmask + Netmask for the installed system. + + --hostname + Hostname for the installed system. + + There are three different methods of network configuration: + + + DHCP + + BOOTP + + static + + The DHCP method uses a DHCP server system to obtain its + networking configuration. As you might guess, the BOOTP method + is similar, requiring a BOOTP server to supply the networking + configuration. + + The static method requires that you enter all the required + networking information in the kickstart file. As the name + implies, this information is static, and will be used during + the installation, and after the installation as well. + + To direct a system to use DHCP to obtain its networking + configuration, use the following line: + +network --bootproto dhcp + + To direct a machine to use BOOTP to obtain its networking + configuration, use the following line in the kickstart file: + +network --bootproto bootp + + The line for static networking is more complex, as you must + include all network configuration information on one line. You + must specify: + + + IP address + + Netmask + + Gateway IP address + + Nameserver IP address + + Here is an example static line: + +network --bootproto static --ip 10.0.2.15 --netmask 255.255.255.0 --gateway 10. +0.2.254 --nameserver 10.0.2.1 + + If you use the static method, be aware of the following two + restrictions: + + + All static networking configuration information must be + specified on one line; you cannot wrap lines using a + backslash, for example. + + You can only specify one nameserver here. However, you can + use the kickstart file's %post section (described in [52]the + Section called %post -- Post-Installation Configuration + Section) to add more name servers, if needed. + _________________________________________________________________ + +part + + part or partition (required for installs, ignored for upgrades) + Creates a partition on the system. + + The <mntpoint> is where the partition will be mounted and must + be of one of the following forms: + + /<mntpoint> + For example, /, /usr, /home + + swap + The partition will be used as swap space. + + To determine the size of the swap partition + automatically, use the --recommended[53][1] option: + +swap --recommended + + The minimum size of the automatically-generated swap + partition will be no smaller than the amount of RAM in + the system and no bigger than twice the amount of RAM in + the system. + + raid.<id> + The partition will be used for software RAID (see the + [54]the Section called raid below). + + --size <size> + The minimum partition size in megabytes. Specify an + integer value here such as 500. Do not append the number + with MB. + + --grow + Tells the partition to grow to fill available space (if + any), or up to the maximum size setting. + + --maxsize <size> + The maximum partition size in megabytes when the + partition is set to grow. Specify an integer value here, + and do not append the number with MB. + + --noformat + Tells the installation program not to format the + partition, for use with the --onpart command. + + --onpart <part> or --usepart <part> + Tells the installation program to put the partition on + the already existing device <part>. For example, + partition /home --onpart hda1 will put /home on + /dev/hda1, which must already exist. If you use --onpart, + you still must specify a size with --size for the file to + be parsed correctly. The size will be ignored since the + partition already exists. + + --ondisk <disk> or --ondrive <drive> + Forces the partition to be created on a particular disk. + For example, --ondisk sdb will put the partition on the + second disk on the system. + + --asprimary + Forces automatic allocation of the partition as a primary + partition or the partitioning will fail. + + --bytes-per-inode=<N> + <N> represents the number of bytes per inode on the + filesystem when it is created. It must be given in + decimal format. This option is useful for applications + where you want to increase the number of inodes on the + filesystem. + + --type=<X> (replaced by fstype) + This option is no longer available. Use fstype. + + --fstype + Sets the filesystem type for the partition. Valid values + are ext2, ext3, swap, and vfat. + + --start + Specifies the starting cylinder for the partition. It + requires that a drive be specified with --ondisk or + ondrive. It also requires that the ending cylinder be + specified with --end or the partition size be specified + with --size. + + --end + Specifies the ending cylinder for the partition. It + requires that the starting cylinder be specified with + --start. + + --badblocks + Specifies that the partition should be checked for bad + sectors. + + All partitions created will be formatted as part of the + installation process unless --noformat and --onpart are used. + + Note Note + + + If partitioning fails for any reason, diagnostic messages will appear + on virtual console 3. + _________________________________________________________________ + +raid + + raid (optional) + Assembles a software RAID device. This command is of the form: + +raid <mntpoint> --level <level> --device <mddevice><partitions*> + + The <mntpoint> is the location where the RAID filesystem is + mounted. If it is /, the RAID level must be 1 unless a boot + partition (/boot) is present. If a boot partition is present, + the /boot partition must be level 1 and the root (/) partition + can be any of the available types. The <partitions*> (which + denotes that multiple partitions can be listed) lists the RAID + identifiers to add to the RAID array. + + --level <level> + RAID level to use (0, 1, or 5). + + --device <mddevice> + Name of the RAID device to use (such as md0 or md1). RAID + devices range from md0 to md7, and each may only be used + once. + + --spares=N + Specifies that there should be N spare drives allocated + for the RAID array. Spare drives are used to rebuild the + array in case of drive failure. + + --fstype + Sets the filesystem type for the RAID array. Valid values + are ext2, ext3, swap, and vfat. + + --noformat + Do not format the RAID array. + + The following example shows how to create a RAID level 1 + partition for /, and a RAID level 5 for /usr, assuming there + are three SCSI disks on the system. It also creates three swap + partitions, one on each drive. + +part raid.01 --size 60 --ondisk sda +part raid.02 --size 60 --ondisk sdb +part raid.03 --size 60 --ondisk sdc + +part swap --size 128 --ondisk sda +part swap --size 128 --ondisk sdb +part swap --size 128 --ondisk sdc + +part raid.11 --size 1 --grow --ondisk sda +part raid.12 --size 1 --grow --ondisk sdb +part raid.13 --size 1 --grow --ondisk sdc + +raid / --level 1 --device md0 raid.01 raid.02 raid.03 +raid /usr --level 5 --device md1 raid.11 raid.12 raid.13 + _________________________________________________________________ + +reboot + + reboot (optional) + Reboot after the installation is complete (no arguments). + Normally, kickstart displays a message and waits for the user + to press a key before rebooting. + _________________________________________________________________ + +rootpw + + rootpw (required) + rootpw [--iscrypted] <password> + + Sets the system's root password to the <password> argument. + + --iscrypted + If this is present, the password argument is assumed to + already be encrypted. + _________________________________________________________________ + +skipx + + skipx (optional) + If present, X is not configured on the installed system. + _________________________________________________________________ + +text + + text (optional) + Perform the kickstart installation in text mode. Kickstart + installations are performed in graphical mode by default. + _________________________________________________________________ + +timezone + + timezone (required) + timezone [--utc] <timezone> + + Sets the system time zone to <timezone> which may be any of the + time zones listed by timeconfig. + + --utc + If present, the system assumes the hardware clock is set + to UTC (Greenwich Mean) time. + _________________________________________________________________ + +upgrade + + upgrade (optional) + Tells the system to upgrade an existing system rather than + install a fresh system. + _________________________________________________________________ + +xconfig + + xconfig (optional) + Configures the X Window System. If this option is not given, + the user will need to configure X manually during the + installation, if X was installed; this option should not be + used if X is not installed on the final system. + + --noprobe + Do not probe the monitor. + + --card <card> + Use card <card>; this card name should be from the list + of cards in Xconfigurator. If this argument is not + provided, Anaconda will probe the PCI bus for the card. + Since AGP is part of the PCI bus, AGP cards will be + detected if supported. The probe order is determined by + the PCI scan order of the motherboard. + + --videoram <vram> + Specify the amount of video RAM the video card has. + + --monitor <mon> + Use monitor <mon>; this monitor name should be from the + list of monitors in Xconfigurator. This is ignored if + --hsync or --vsync is provided. If no monitor information + is provided, the installation program tries to probe for + it automatically. + + --hsync <sync> + Specifies the horizontal sync frequency of the monitor. + + --vsync <sync> + Specifies the vertical sync frequency of the monitor. + + --defaultdesktop=GNOME or --defaultdesktop=KDE + Sets the default desktop to either GNOME or KDE (and + assumes that GNOME and/or KDE has been installed through + %packages). + + --startxonboot + Use a graphical login on the installed system. + + --resolution <res> + Specify the default resolution for the X Window System on + the installed system. Valid values are 640x480, 800x600, + 1024x768, 1152x864, 1280x1024, 1400x1050, 1600x1200. Be + sure to specify a resolution that is compatible with the + video card and monitor. + + --depth <cdepth> + Specify the default color depth for the X Window System + on the installed system. Valid values are 8, 16, 24, and + 32. Be sure to specify a color depth that is compatible + with the video card and monitor. + _________________________________________________________________ + +zerombr -- Partition Table Initialization + + zerombr (optional) + If zerombr is specified, and yes is its sole argument, any + invalid partition tables found on disks are initialized. This + will destroy all of the contents of disks with invalid + partition tables. This command should be in the following + format: + + zerombr yes + + No other format is effective. + _________________________________________________________________ + +%packages -- Package Selection + + Use the %packages command to begin a kickstart file section that lists + the packages you would like to install (this is for installations + only, as package selection during upgrades is not supported). + + Use the %packages --resolvedeps[55][1] to install the listed packages + and automatically resolve package dependencies. + + Use the %packages --ignoredeps[56][1] to ignore the unresolved + dependencies and install the listed packages without the dependencies. + + Packages can be specified by component or by individual package name. + The installation program defines several components that group + together related packages. See the RedHat/base/comps file on any Red + Hat Linux CD-ROM for a list of components. The components are defined + by the lines that begin with a number followed by a space and then the + component name. Each package in that component is then listed, + line-by-line. Individual packages lack the leading number found in + front of component lines. + + Additionally, there are three other types of lines in the comps file: + + Architecture specific (i386:, ia64:, alpha:, and sparc64:) + If a package name begins with an architecture type, you only + need to type in the package name, not the architecture name. + For example: + + For i386: apmd you only need to use the apmd part for that + specific package to be installed. + + Lines beginning with ? + Lines that begin with a ? are used by the installation program + and should not be altered. + + Lines beginning with --hide + If a package name begins with --hide, you only need to type in + the package name, without the --hide. For example: + + For --hide Network Server you only need to use the Network + Server part for that specific package to be installed. + + In most cases, it is only necessary to list the desired components and + not individual packages. Note that the Base component is always + selected by default, so it is not necessary to specify it in the + %packages section. + + Here is an example %packages selection: +%packages +@ Network Managed Workstation +@ Development +@ Web Server +@ X Window System +ImageMagick + + As you can see, components are specified, one to a line, starting with + an @ symbol, a space, and then the full component name as given in the + comps file. Specify individual packages with no additional characters + (the ImageMagick line in the example above is an individual package). + + You can also direct the kickstart installation to install the default + packages for a workstation (KDE or GNOME) or server installation (or + choose an everything installation to install all packages). To do + this, simply add one of the following lines to the %packages section: +@ GNOME +@ KDE +@ Server +@ Everything + _________________________________________________________________ + +%pre -- Pre-Installation Configuration Section + + You can add commands to run on the system immediately after the ks.cfg + has been parsed. This section must be at the end of the kickstart file + (after the commands) and must start with the %pre command. Note that + you can access the network in the %pre section; however, name service + has not been configured at this point, so only IP addresses will work. + Here is an example %pre section: +%pre + +# add comment to /etc/motd +echo "Kickstart-installed Red Hat Linux `/bin/date`" > /etc/motd + +# add another nameserver +echo "nameserver 10.10.0.2" >> /etc/resolv.conf + + This section creates a message-of-the-day file containing the date the + kickstart installation took place. It also gets around the network + command's limitation of only one name server by adding another + nameserver to /etc/resolv.conf. + + Note Note + + + Note that the pre-install script is not run in the change root + environment. + _________________________________________________________________ + +%post -- Post-Installation Configuration Section + + You have the option of adding commands to run on the system once the + installation is complete. This section must be at the end of the + kickstart file and must start with the %post command. + + Note Note + + + If you configured the network with static IP information, including a + nameserver, you can access the network and resolve IP addresses in the + %post section. If you configured the network for DHCP, the + /etc/resolv.conf file has not been completed when the installation + executes the %post section. You can access the network, but you can + not resolve IP addresses. Thus, if you are using DHCP, you must + specify IP addresses in the %post section. + + Here is an example %post section that creates a message of the day + file containing the date that the kickstart installation took place, + and gets around the network command's limitation of one nameserver + only by adding another nameserver to /etc/resolv.conf. +%post + +# add comment to /etc/motd +echo "Kickstart-installed Red Hat Linux `/bin/date`" > /etc/motd + +# add another nameserver +echo "nameserver 10.10.0.2" >> /etc/resolv.conf + + Note Note + + + The post-install script is run in a chroot environment; therefore, + performing tasks such as copying scripts or RPMs from the installation + media will not work. + + --nochroot + Allows you to specify commands that you would like to run + outside of the chroot environment. + + The following example copies the file /etc/resolv.conf to the + filesystem that was just installed. + +%post --nochroot +cp /etc/resolv.conf /mnt/sysimage/etc/resolv.conf + + --interpreter /usr/bin/perl + Allows you to specify a different scripting language, such as + Perl. Replace /usr/bin/perl with the scripting language of your + choice. + + The following example uses a Perl script to replace + /etc/HOSTNAME. + +%post --interpreter /usr/bin/perl + +# replace /etc/HOSTNAME +open(HN, ">HOSTNAME"); +print HN "1.2.3.4 an.ip.address\n"; + _________________________________________________________________ + +%include -- Include Contents of Another File Section[57][1] + + Use the %include /path/to/file command to include the contents of + another file in the kickstart file as though the contents were at the + location of the %include command in the kickstart file. + _________________________________________________________________ + +Where to Put A Kickstart File + + A kickstart file must be placed in one of two locations: + + * On a boot disk + * On a network + + Normally a kickstart file is copied to the boot disk, or made + available on the network. The network-based approach is most commonly + used, as most kickstart installations tend to be performed on + networked computers. + + Let us take a more in-depth look at where the kickstart file may be + placed. + _________________________________________________________________ + +Creating a Kickstart Boot Disk + + To perform a diskette-based kickstart installation, the kickstart file + must be named ks.cfg and must be located in the boot disk's top-level + directory. Note that the Red Hat Linux boot disks are in MS-DOS + format, so it is easy to copy the kickstart file under Linux using the + mcopy command: + mcopy ks.cfg a: + + Alternatively, you can use Windows to copy the file. You can also + mount the MS-DOS boot disk and cp the file over. + _________________________________________________________________ + +Making the Kickstart File Available on the Network + + Network installations using kickstart are quite common, because system + administrators can easily automate the installation on many networked + computers quickly and painlessly. In general, the approach most + commonly used is for the administrator to have both a BOOTP/DHCP + server and an NFS server on the local network. The BOOTP/DHCP server + is used to give the client system its networking information, while + the actual files used during the installation are served by the NFS + server. Often, these two servers run on the same physical machine, but + they are not required to. + + To perform a network-based kickstart installation, you must have a + BOOTP/DHCP server on your network, and it must include configuration + information for the machine on which you are attempting to install Red + Hat Linux. The BOOTP/DHCP server will provide the client with its + networking information as well as the location of the kickstart file. + + If a kickstart file is specified by the BOOTP/DHCP server, the client + system will attempt an NFS mount of the file's path, and will copy the + specified file to the client, using it as the kickstart file. The + exact settings required vary depending on the BOOTP/DHCP server you + use. + + Here is an example of a line from the dhcpd.conf file for the DHCP + server shipped with Red Hat Linux: +filename "/usr/new-machine/kickstart/"; +next-server blarg.redhat.com; + + Note that you should replace the value after filename with the name of + the kickstart file (or the directory in which the kickstart file + resides) and the value after next-server with the NFS server name. + + If the filename returned by the BOOTP/DHCP server ends with a slash + ("/"), then it is interpreted as a path only. In this case, the client + system mounts that path using NFS, and searches for a particular file. + The filename the client searches for is: + <ip-addr>-kickstart + + The <ip-addr> section of the filename should be replaced with the + client's IP address in dotted decimal notation. For example, the + filename for a computer with an IP address of 10.10.0.1 would be + 10.10.0.1-kickstart. + + Note that if you do not specify a server name, then the client system + will attempt to use the server that answered the BOOTP/DHCP request as + its NFS server. If you do not specify a path or filename, the client + system will try to mount /kickstart from the BOOTP/DHCP server, and + will try to find the kickstart file using the same <ip-addr>-kickstart + filename as described above. + _________________________________________________________________ + +Starting a Kickstart Installation + + To begin a kickstart installation, you must boot the system from a Red + Hat Linux boot diskette or the CD-ROM and enter a special boot command + at the boot prompt. If the kickstart file is located on a boot + diskette that was created from the boot.img or bootnet.img image file, + the correct boot command would be: + boot: linux ks=floppy + + The linux ks=floppy command also works if the ks.cfg file is located + on a vfat or ext2 filesystem on a floppy diskette and you boot from + the Red Hat Linux CD-ROM. + + An alternate boot command for booting off the Red Hat Linux CD-ROM and + having the kickstart file on a vfat or ext2 filesystem on a floppy + diskette is: + boot: linux ks=hd:fd0/ks.cfg + + If you need to use a driver disk with kickstart, you can still have + the kickstart file on a floppy disk: + boot: linux ks=floppy dd + + The Red Hat Linux installation program looks for a kickstart file if + the ks command line argument is passed to the kernel. The command line + argument can take a number of forms: + + ks=nfs:<server>/<path> + The installation program will look for the kickstart file on + the NFS server <server>, as file <path>. The installation + program will use DHCP to configure the Ethernet card. For + example, if your NFS server is server.example.com and the + kickstart file is in the NFS share /mydir/ks.cfg, the correct + boot command would be ks=nfs:server.example.com:/mydir/ks.cfg. + + ks=http:<server>/<path> + The installation program will look for the kickstart file on + the HTTP server <server>, as file <path>. The installation + program will use DHCP to configure the Ethernet card. For + example, if your HTTP server is server.example.com and the + kickstart file is in the HTTP directory /mydir/ks.cfg, the + correct boot command would be + ks=http:server.example.com:/mydir/ks.cfg. + + ks=floppy + The installation program looks for the file ks.cfg on a vfat or + ext2 filesystem on the floppy in drive /dev/fd0. + + ks=hd:<device>/<file> + The installation program will mount the filesystem on <device> + (which must be vfat or ext2), and look for the kickstart + configuration file as <file> in that filesystem (for example, + ks=hd:sda3/mydir/ks.cfg). + + ks=file:/<file> + The installation program will try to read the file <file> from + the filesystem; no mounts will be done. This is normally used + if the kickstart file is already on the initrd image. + + ks=cdrom:/<path> + The installation program will look for the kickstart file on + CD-ROM, as file <path>. + + ks + If ks is used alone, the installation program will configure + the Ethernet card in the system using DHCP. The system will use + the "bootServer" from the DHCP response as an NFS server to + read the kickstart file from (by default, this is the same as + the DHCP server). The name of the kickstart file is one of the + following: + + + If DHCP is specified and the bootfile begins with a /, the + bootfile provided by DHCP is looked for on the NFS server. + + If DHCP is specified and the bootfile begins with something + other then a /, the bootfile provided by DHCP is looked for + in the /kickstart directory on the NFS server. + + If DHCP did not specify a bootfile, then the installation + program tries to read the file /kickstart/1.2.3.4-kickstart, + where 1.2.3.4 is the numeric IP address of the machine being + installed. + + ksdevice=<device> + The installation program will use this network device to + connect to the network. For example, to start a kickstart + installation with the kickstart file on an NFS server that is + connected to the system through the eth1 device, use the + command ks=nfs:<server:>/<path> ksdevice=eth1 at the boot: + prompt. + + Notes + + [58][1] + + This option is new to Red Hat Linux 7.3 + +References + + 1. http://www.opencontent.org/openpub/ + 2. mailto:goddess@ipass.net + 3. file://localhost/tmp/html-FlPi65#CH-INTRO + 4. file://localhost/tmp/html-FlPi65#S1-KICKSTART-WHATIS + 5. file://localhost/tmp/html-FlPi65#S1-KICKSTART-HOWUSE + 6. file://localhost/tmp/html-FlPi65#CH-KICKSTART-FILE + 7. file://localhost/tmp/html-FlPi65#CH-KICKSTART-OPTIONS + 8. file://localhost/tmp/html-FlPi65#S2-KICKSTART-AUTOSTEP + 9. file://localhost/tmp/html-FlPi65#S2-KICKSTART-AUTH + 10. file://localhost/tmp/html-FlPi65#S2-KICKSTART-BOOTLOADER + 11. file://localhost/tmp/html-FlPi65#S2-KICKSTART-CLEARPART + 12. file://localhost/tmp/html-FlPi65#S2-KICKSTART-DEVICE + 13. file://localhost/tmp/html-FlPi65#S2-KICKSTART-DEVICEPROBE + 14. file://localhost/tmp/html-FlPi65#S2-KICKSTART-DRIVERDISK + 15. file://localhost/tmp/html-FlPi65#S2-KICKSTART-FIREWALL + 16. file://localhost/tmp/html-FlPi65#S2-KICKSTART-INSTALL + 17. file://localhost/tmp/html-FlPi65#S2-KICKSTART-INSTALLMETH + 18. file://localhost/tmp/html-FlPi65#S2-KICKSTART-INTERACTIVE + 19. file://localhost/tmp/html-FlPi65#S2-KICKSTART-KEYBOARD + 20. file://localhost/tmp/html-FlPi65#S2-KICKSTART-LANG + 21. file://localhost/tmp/html-FlPi65#S2-KICKSTART-LANGSUPPORT + 22. file://localhost/tmp/html-FlPi65#S2-KICKSTART-LILO + 23. file://localhost/tmp/html-FlPi65#S2-KICKSTART-LILOCHECK + 24. file://localhost/tmp/html-FlPi65#S2-KICKSTART-MOUSE + 25. file://localhost/tmp/html-FlPi65#S2-KICKSTART-NETWORK + 26. file://localhost/tmp/html-FlPi65#S2-KICKSTART-PARTITION + 27. file://localhost/tmp/html-FlPi65#S2-KICKSTART-RAID + 28. file://localhost/tmp/html-FlPi65#S2-KICKSTART-REBOOT + 29. file://localhost/tmp/html-FlPi65#S2-KICKSTART-ROOTPW + 30. file://localhost/tmp/html-FlPi65#S2-KICKSTART-SKIPX + 31. file://localhost/tmp/html-FlPi65#S2-KICKSTART-TEXT + 32. file://localhost/tmp/html-FlPi65#S2-KICKSTART-TIMEZONE + 33. file://localhost/tmp/html-FlPi65#S2-KICKSTART-UPGRADE + 34. file://localhost/tmp/html-FlPi65#S2-KICKSTART-XCONFIG + 35. file://localhost/tmp/html-FlPi65#S2-KICKSTART-ZEROMBR + 36. file://localhost/tmp/html-FlPi65#S2-KICKSTART-PACKAGESELECTION + 37. file://localhost/tmp/html-FlPi65#S2-KICKSTART-PREINSTALLCONFIG + 38. file://localhost/tmp/html-FlPi65#S2-KICKSTART-POSTINSTALLCONFIG + 39. file://localhost/tmp/html-FlPi65#S2-KICKSTART-INCLUDE + 40. file://localhost/tmp/html-FlPi65#FTN.NEW-OPTION + 41. file://localhost/tmp/html-FlPi65#CH-KICKSTART-PUTKICKSTARTHERE + 42. file://localhost/tmp/html-FlPi65#S2-KICKSTART-DISKBASED + 43. file://localhost/tmp/html-FlPi65#S2-KICKSTART-NETWORKBASED + 44. file://localhost/tmp/html-FlPi65#CH-KICKSTART--STARTINGINSTALL + 45. file://localhost/tmp/html-FlPi65#CH-KICKSTART-OPTIONS + 46. file://localhost/tmp/html-FlPi65#S2-KICKSTART-PACKAGESELECTION + 47. file://localhost/tmp/html-FlPi65#S2-KICKSTART-PREINSTALLCONFIG + 48. file://localhost/tmp/html-FlPi65#S2-KICKSTART-POSTINSTALLCONFIG + 49. file://localhost/tmp/html-FlPi65#FTN.NEW-OPTION + 50. file://localhost/tmp/html-FlPi65#S2-KICKSTART-AUTOSTEP + 51. file://localhost/tmp/html-FlPi65#S2-KICKSTART-BOOTLOADER + 52. file://localhost/tmp/html-FlPi65#S2-KICKSTART-POSTINSTALLCONFIG + 53. file://localhost/tmp/html-FlPi65#FTN.NEW-OPTION + 54. file://localhost/tmp/html-FlPi65#S2-KICKSTART-RAID + 55. file://localhost/tmp/html-FlPi65#FTN.NEW-OPTION + 56. file://localhost/tmp/html-FlPi65#FTN.NEW-OPTION + 57. file://localhost/tmp/html-FlPi65#FTN.NEW-OPTION + 58. file://localhost/tmp/html-FlPi65#NEW-OPTION |