Author: emap Date: Mon Nov 7 11:04:43 2011 New Revision: 66732 URL: http://svn.opensuse.org/viewcvs/yast?rev=66732&view=rev Log: edited by emap Modified: trunk/autoinstallation/doc/xml/Installation.xml Modified: trunk/autoinstallation/doc/xml/Installation.xml URL: http://svn.opensuse.org/viewcvs/yast/trunk/autoinstallation/doc/xml/Installation.xml?rev=66732&r1=66731&r2=66732&view=diff ============================================================================== --- trunk/autoinstallation/doc/xml/Installation.xml (original) +++ trunk/autoinstallation/doc/xml/Installation.xml Mon Nov 7 11:04:43 2011 @@ -9,33 +9,33 @@ Introduction </title> <para> - After the system has booted and the control file has been retrieved, - &yast2; performs configuration of the system according to the information - provided in the control file. All the configuration is summarized in a window that is shown by - default and should be deactivated if a full automatic installation is - needed. + After the system has booted into an automatic installation and the + control file has been retrieved, &yast; configures the system according + to the information provided in the control file. All configuration + settings are summarized in a window that is shown by default and should + be deactivated if a fully automatic installation is needed. </para> <para> - When &yast2; has reached the point where the summary of the configuration is shown, - &yast2; has only probed hardware and prepared the system for - auto-installation, thus, nothing has been changed in the system yet, so - that in case of any error, the process still can be aborted. + By the time &yast; displays the summary of the configuration, &yast; has + only probed hardware and prepared the system for + auto-installation. Nothing has been changed in the system yet. In case + of any error, you can still abort the process. </para> <para> A system should be automatically installable without the need to have - any graphic adaptor or monitor. Having a monitor attached to the - client machine is nevertheless recommended to follow the process and - to get feedback in case of any errors. Choosing between the Qt and the - Ncurses interfaces is possible. For headless - clients, system messages can be monitored using the serial console. + any graphic adaptor or monitor. Having a monitor attached to the client + machine is nevertheless recommended so you can supervise the process and + to get feedback in case of errors. Choose between the Qt<remark>emap 2011-11-07: Should this read 'graphical' or 'X11'?</remark> and the text-based + Ncurses interfaces. For headless clients, system messages + can be monitored using the serial console. </para> <section id="Installation.Interface.X11"> <title> - X11 Interface + X11 Interface (graphical) </title> <para> - This is the default interface while auto-installing. No special + This is the default interface while auto-installing. No special variables are required to activate it. </para> </section> @@ -44,23 +44,23 @@ Serial console </title> <para> - You can start installing a system using the serial console by adding - the keyword console (i.e. console=ttyS0) to the command line of the - kernel. This will start linuxrc in console mode and later in the - process, &yast2; also is started in serial console mode. + Start installing a system using the serial console by adding the + keyword "console" (i.e. console=ttyS0) to the command line of the + kernel. This starts linuxrc in console mode and later &yast; in serial + console mode. </para> </section> <section id="Installation.Interface.Ncurses"> <title> - Text based YaST2-Installation + Text-based &yast; Installation </title> <para> This option can also be activated on the command line. This will start - YaST2 in <emphasis>Ncurses</emphasis> mode. To start &yast2; in text + YaST2 in <emphasis>Ncurses</emphasis> mode. To start &yast; in text mode, add <emphasis>textmode=1</emphasis> on the command line. </para> <para> - Starting &yast2; in text mode is recommended when installing a client + Starting &yast; in text mode is recommended when installing a client with less than 64 MB or when X11 is not being configured at all, especially on headless machines. </para> @@ -68,12 +68,12 @@ </section> <section id="bootmedium"> - <title>Choosing the right Boot Medium</title> + <title>Choosing the Right Boot Medium</title> <para> - There are different methods for booting the client. The computer can boot from - its network interface card (NIC) to receive the boot images via &dhcp; /TFTP - or a suitable kernel as well as an initrd image are loaded from a - floppy or a boot-able CD-ROM. + There are different methods for booting the client. The computer can + boot from its network interface card (NIC) to receive the boot images + via &dhcp; or TFTP. Alternatively a suitable kernel and initrd image can + be loaded from a floppy or a bootable CD-ROM. </para> <section> <title> @@ -81,21 +81,22 @@ </title> <para> For testing/rescue purposes or because the NIC does not have a PROM or PXE - you can build a boot floppy to use with &autoyast2;. Using a floppy + you can build a boot floppy to use with &ay;. Using a floppy to initiate an auto-install process is limited due to the size of the data a floppy can hold. However, it is still possible to use floppies when auto-installing a single, disconnected machine. </para> <para> - Floppies can be used to store the control file, especially when using - the original &company-suse; CD-ROMs for a single, disconnected machine. Using the + Floppies can also store the control file, especially when using + the original &company-suse; CD-ROMs for a single, disconnected machine. Via the kernel command line, you can specify the location of the control file on the floppy. - </para> + </para><remark>emap 2011-11-07: Would people still use floppies these days? I'd expect USB sticks to be a lot more common.</remark> <para> - Even without specifying any command line options, it is still possible to initiate the - auto-install process by placing a control file on a floppy with a - special, pre-defined file name. (<filename>autoinst.xml</filename>) &yast2; will check for + Even without specifying any command line options, it is still possible + to initiate the auto-install process by placing a control file on a + floppy with the pre-defined file name + <filename>autoinst.xml</filename>. &yast; will check for <filename>autoinst.xml</filename> upon startup and if it was found it will switch from interactive to automated installation. </para> @@ -104,15 +105,15 @@ <section> <title>Booting from CD-ROM</title> <para> - You can use the original &company-suse; CD-ROMs in combination with other - media, i.e. with a floppy to hold the control file or in combination - with network where the control file can be located. + You can use the original &company-suse; CD-ROMs in combination with + other media. For example, the control file can be provided via a + floppy or a specified location on the network. </para> <para> - It is also possible to create customized CD-ROMs to hold only the - package you need in addition to the control file which also can be - saved on the CD-ROM. This method requires creation of CD-ROMs - every time you wish to change the configuration though. + Alternatively, create a customized CD-ROM that holds only the package + you need <remark>emap 2011-11-07: Why not name the + package?</remark>and the control file. If you need to change the + configuration, you'll have to create a new CD-ROM. </para> </section> @@ -123,8 +124,9 @@ will boot then without a physical media like a boot floppy or CDROM. </para> <para> - Here is a small example of a "/srv/tftp/pxelinux.cfg/default" file: - </para> + Here is an example of a + <filename>/srv/tftp/pxelinux.cfg/default</filename> file: + </para><remark>emap 2011-11-07: Update the example to SLES11?</remark> <screen> default SLES9 @@ -138,12 +140,12 @@ LOCALBOOT 0 </screen> <para> - It's recommended to add the vga=... parameter with a valid value for graphical + We recommended you add the vga=... parameter with a valid value for graphical installations, to trigger an installation with the frame buffer device instead of the vesa driver or ncurses mode. </para> <para> - Here is as a small example my "/etc/dhcp.conf" file: + Here is as an example of a <filename>/etc/dhcp.conf</filename> file: </para> <screen> option domain-name-servers 192.168.66.1; @@ -173,21 +175,20 @@ } </screen> <para> - A problem you might run into if you do installation via PXE is, that the + A problem you might run into if you do installation via PXE is that the installation will run into an endless loop, because after the first reboot, - the machine is doing PXE boot again and will restart the installation instead - of booting from harddisc for the second stage of the installation. + the machine is doing PXE boot again and restarts the installation instead + of booting from hard disk for the second stage of the installation. </para> <para> - This problem can be solved in different ways. One way is to use a http server - to provide the autoyast profile and instead of a static profile, a CGI script - on the webserver is run that provides the profile and then changes the TFTP server - configuration then for this special host, so that the next PXE boot from that - machine will be from harddisc by default. + This problem can be solved in different ways. One way is to use an http server + to provide the &ay; profile. And, instead of a static profile, run a CGI script + on the web server that provides the profile and changes the TFTP server + configuration for your target host. Then the next PXE boot of the + machine will be from hard disk by default. </para> <para> - Another way is to use autoyast to upload a new PXE boot configuration for that host. - That is done via autoyast profile like this: + Another way is to use &ay; to upload a new PXE boot configuration for the target host via the profile: </para> <screen> <![CDATA[ @@ -207,54 +208,54 @@ ]]> </screen> <para> - This will upload a new configuration for the actual machine to the tftp server short + This entry will upload a new configuration for the target host to the tftp server shortly before the first reboot happens. In most installations the TFTP daemon runs as user - "nobody". You have to make sure that that user has write permissions to the "pxelinux.cfg" - directory if you use that mechanism. - So if your machine got the IP address "192.168.66.195" a file "C0A842C3" will - be uploaded and if the machine reboots and will get the same IP address - via DHCP again, the new configuration will be used that has the harddisc as - a default boot media. - </para> - <para> - Of course this requires that the machine will get the same IP address again after the - reboot and if you want to do another autoinstallation for that machine, you have to - remove the file from the TFTP server. - </para> - <para> - Since openSUSE 11.2 (not SLES11) you can configure the filename too that will be uploaded. - If you use the "magic" __MAC__ filename, the filename will be the mac address of your machine like this "01-08-00-27-79-49-ee". - A missing filename creates the IP address filename like in the past. + "nobody". You have to make sure this user has write permissions to the <filename>pxelinux.cfg</filename> + directory. + So if your machine has the IP address "192.168.66.195", a file <filename>C0A842C3</filename> will + be uploaded. When the machine reboots and receives the same IP address + via DHCP, the new configuration will be used, telling the target host to book from hard disk. + </para> + <para> + If you want to do another auto-installation on the same machine, you + have to remove the file from the TFTP server. + </para> + <para> + Since openSUSE 11.2 (not SLES11), you can also configure the filename + that will be uploaded. If you use the "magic" __MAC__ filename, the + filename will be the mac address of your machine like this + "01-08-00-27-79-49-ee". If the filename setting is missing, the IP + address will be used for the filename. </para> </section> </section> <section id="invoking_autoinst"> <title id="invoking_autoinst.title"> - Invoking the Auto-Installation process + Invoking the Auto-Installation Process </title> <section> - <title>Command line Options</title> + <title>Command Line Options</title> <para> - Adding the command line variable <emphasis>autoyast</emphasis> will make - <emphasis>linuxrc</emphasis> start in automated mode. - <command>Linuxrc</command> searches for a configuration file, which + Adding the command line variable <emphasis>autoyast</emphasis> causes + <emphasis>linuxrc</emphasis> to start in automated mode. + <command>linuxrc</command> searches for a configuration file<remark>emap 2011-11-07: Is this the profile? Better elaborate on this config file.</remark>, which should be distinguished from the main control file in the following places: </para> <itemizedlist> <listitem> - <para>In the root directory of the initial ram-disk used for booting - the system up</para> + <para>in the root directory of the initial RAM disk used for booting + the system,</para> </listitem> <listitem> - <para>In the root directory of the floppy</para> + <para>in the root directory of the floppy.</para> </listitem> </itemizedlist> <para> The configuration file used by <command>linuxrc</command> can have the - following keywords (for a detailed description of how linuxrc works and + following keywords (for a detailed description of how <command>linuxrc</command> works and other keywords, see <quote><xref linkend='appendix.linuxrc' endterm="appendix.linuxrc.title"></xref></quote> ): </para> @@ -272,20 +273,18 @@ <tbody> - <row><entry>netdevice</entry><entry>Which network device to use for - network setup (Device used for &bootp; / &dhcp; requests)</entry></row> - <row><entry>server</entry><entry>Which server to contact for source directory (NFS Server)</entry></row> + <row><entry>netdevice</entry><entry>Network device to use for + network setup (for &bootp; and &dhcp; requests)</entry></row> + <row><entry>server</entry><entry>Server (NFS) to contact for source directory</entry></row> <row><entry>serverdir</entry><entry>Directory on NFS Server </entry></row> <row><entry>hostip</entry><entry>When empty, client sends &bootp; request, otherwise client is configured with entered IP configuration.</entry></row> <row><entry>netmask</entry><entry>Netmask</entry></row> <row><entry>gateway</entry><entry>Gateway</entry></row> <row><entry>nameserver</entry><entry>Nameserver</entry></row> - <row><entry>insmod</entry><entry>Kernel modules to load.</entry></row> + <row><entry>insmod</entry><entry>Kernel modules to load</entry></row> <row> <entry>autoyast</entry> - <entry>Location of the the control file to be used for the - automatic installation, i.e - <emphasis>autoyast=http://192.168.2.1/profiles/</emphasis></entry> + <entry>Location of the the control file for automatic installation, i.e. <emphasis>autoyast=http://192.168.2.1/profiles/</emphasis></entry> </row> <row> @@ -294,13 +293,12 @@ </row> <row> <entry>instmode</entry> - <entry>Installation mode, i.e. nfs, http etc. (Not needed if + <entry>Installation mode, i.e. nfs, http etc. (not needed if <emphasis>install</emphasis> is set)</entry> </row> <row> <entry>y2confirm</entry> - <entry>even with <confirm>no</confirm> in the profile, the confirm proposal comes up. - This is available since SUSE Linux 10.1 / SLES10 + <entry>Even with <confirm>no</confirm> in the profile, the confirm proposal comes up (available since SUSE Linux 10.1/SLES10). </entry> </row> </tbody> @@ -311,36 +309,36 @@ <para> These variables and keywords will bring the system up to the point - where &yast2; can take over with the main control file. Currently, the + where &yast; can take over with the main control file. Currently, the source medium is automatically discovered, which in some cases makes it possible to initiate the auto-install process without giving any instructions to - linuxrc. + <command>linuxrc</command>. </para> <para> The traditional <command>linuxrc</command> configuration file (<filename>info</filename>) has the function of giving the client enough information about the installation server and - the location of the sources. In most cases this file is not needed; it is however - needed in special network environments where &dhcp; / &bootp; are not - used or when special kernel modules have to be loaded. + the location of the sources. In most cases, this file is not needed; it is however + needed in special network environments where &dhcp; and &bootp; are not + used or when special kernel modules have to be loaded. </para> <para> All linuxrc keywords can be passed to <command>linuxrc</command> using the kernel command - line. The command line can for example also be set when creating network boot-able + line. The command line can also be set when creating network bootable images or it can be passed to the kernel using a specially configured - &dhcp; server in combination with Etherboot or &pxe;. + &dhcp; server in combination with Etherboot or &pxe;.<remark>emap 2011-11-07:Obscure paragraph. What is set in the command line? And what is the 'it' that can be passed to the kernel? Probably not the command line itself.</remark> </para> <para> - The format of the special command line variable - <emphasis>autoyast</emphasis> can be used as described in table <quote><xref + The command line variable + <emphasis>autoyast</emphasis> can be used in the format described in table <quote><xref linkend="commandLineAutoYaST" endterm="commandLineAutoYaST.title"></xref></quote> </para> <table frame='top' id="commandLineAutoYaST"> - <title id="commandLineAutoYaST.title">Command line variables for AutoYaST</title> + <title id="commandLineAutoYaST.title">Command Line Variables for &ay;</title> <tgroup cols='2'> <thead> <row> @@ -350,27 +348,27 @@ </row> </thead> <tbody> - <row><entry>autoyast=default</entry><entry>Default auto-installation option </entry></row> + <row><entry>autoyast=default</entry><entry>Default auto-installation option.</entry></row> <row><entry>autoyast=file://<path></entry><entry>Looks for - control file in specified path (relative to source root + control file in specified path (relative to source root directory, i.e. <emphasis>file:///autoinst.xml</emphasis> if in - the top directory of a CD-ROM and you did an installation from CD)</entry></row> + the top directory of a CD-ROM and you did an installation from CD).</entry></row> <row> <entry> autoyast=device://<device>/<file></entry><entry>Looks - for control file on a storage device. (only device name needed - without full path, i.e. /dev/sda1 is wrong, instead use sda1). - Since openSUSE 11.2 (not SLES11) you can leave out the device to trigger - AutoYaST's search routine over all devices. (autoyast=device:///my.xml) + for control file on a storage device (only device name needed + without full path, i.e. /dev/sda1 is wrong, use only sda1 instead). + Since openSUSE 11.2 (not SLES11) you can omit specifying the device and trigger + &ay; to search all devices (autoyast=device:///my.xml). </entry> </row> <row> <entry>autoyast=floppy://<path></entry> - <entry>Looks for control file in the floppy (Useful when booting - from CD). Since SLES10 SP1 and later the fallback is looking on USB devices too</entry> + <entry>Looks for control file on a floppy (useful when booting + from CD). Since SLES10 SP1 and later the fallback is looking on USB devices.</entry><remark>emap 2011-11-07: Ah, here are USB devices. I think we could use more about this instead of floppies.</remark> </row> <row> <entry>autoyast=nfs://<server>/<path></entry> @@ -378,31 +376,31 @@ </row> <row> <entry>autoyast=http://[user:password@]<server>/<path></entry> - <entry>Retrieves the control file from a web server using the HTTP protocol.</entry> + <entry>Retrieves the control file from a web server using the HTTP protocol.</entry> </row> <row> <entry>autoyast=https://[user:password@]<server>/<path></entry> - <entry>Retrieves the control file from a web server using HTTPS (encrypted connection) protocol (possible since SL 10.1 and SLES10</entry> + <entry>Retrieves the control file from a web server using HTTPS (encrypted connection) protocol (possible since SL 10.1 and SLES10).</entry> </row> <row> <entry>autoyast=tftp://<server>/<path></entry> - <entry>Retrieve the control file with TFTP</entry> + <entry>Retrieve the control file via TFTP.</entry> </row> <row> <entry>autoyast=ftp://[user:password@]<server>/<path></entry> - <entry>Retrieve the control file with FTP</entry> + <entry>Retrieve the control file via FTP.</entry> </row> <row> <entry>autoyast=usb://<path> (since SLES10 SP1)</entry> - <entry>Retrieve the control file from USB devices (autoyast will search on all USB devices it can find)</entry> + <entry>Retrieve the control file from USB devices (&ay; will search all connected USB devices).</entry> </row> <row> <entry>autoyast=relurl://<path> (since openSUSE 11.0)</entry> - <entry>Retrieve the control file from the installation source (install=....)</entry> + <entry>Retrieve the control file from the installation source (install=....).</entry> </row> <row> <entry>autoyast=slp (since openSUSE 11.2, not SLES 11)</entry> - <entry>Query the location of the profile from an SLP server (service:autoyast:...). Since openSUSE 11.3 you can add a "description=" attribute so you can "translate" the URL into something more readable</entry> + <entry>Query the location of the profile from an SLP server (service:autoyast:...). Since openSUSE 11.3 you can add a "description=" attribute so you can "translate" the URL into something more readable.</entry> </row> <row> <entry>autoyast=cifs://<server>/<path> (since openSUSE 11.2, not SLES 11)</entry> @@ -410,49 +408,49 @@ </row> <row> <entry>autoyast=label://<label>/<path> (since openSUSE 11.3, not SLES 11)</entry> - <entry>Looks for control file on a device that has the label</entry> + <entry>Searches for control file on a device with the specified label</entry> </row> </tbody> </tgroup> </table> <para> Several scenarios for auto-installation are possible using different - types of infrastructure and source media. The simplest way is by using - the source media from the &company-suse; Box. In that case you have + types of infrastructure and source media. The simplest way is to use + the source media from &company-suse;. In that case you have either a DVD with all &company-suse; packages or a set of CD-ROMs. To initiate the auto-installation process however, the auto-installation command line variable should be entered at system boot-up and the control file should - be accessible to YaST2. The following list of scenarios explains how - the control file can be supplied and the setup needed for the - auto-installation process to be successful. + be accessible to &yast;. The following list of scenarios explains how + the control file can be supplied as well as the setup needed for the + auto-installation process to succeed. </para> <itemizedlist> <listitem> <para> - Using &company-suse; original CD-ROMs from &company-suse; Linux box: + Using original CD-ROMs from &company-suse;: </para> <para> To use the original CD-ROMs, you need a media with the control - file, the control file can reside on the following locations: + file. The control file can reside in the following locations: </para> <orderedlist> <listitem> <para> <emphasis>Floppy</emphasis>: Control file accessible via the - <emphasis>autoyast=floppy</emphasis> option. &yast2; also searches + <emphasis>autoyast=floppy</emphasis> option. &yast; also searches upon startup for a file named <filename>autoinst.xml</filename>. If such a file is found, YaST2 will switch into auto-installation mode even if no special command line variables were supplied. (See <quote><xref linkend="autoinstall.singlesystem" - endterm="autoinstall.singlesystem.title"></xref></quote> ) + endterm="autoinstall.singlesystem.title"></xref></quote>.) </para> </listitem> <listitem> <para> <emphasis>Network</emphasis>: Control file accessible via the <emphasis>autoyast=nfs://..</emphasis>, - <emphasis>autoyast=ftp://..</emphasis> + <emphasis>autoyast=ftp://..</emphasis>, <emphasis>autoyast=http://..</emphasis> or <emphasis>autoyast=tftp://..</emphasis> options. </para> @@ -471,22 +469,22 @@ original &company-suse; CD-ROMs. </para> <para> - Using CD-ROMs for autoinstallation, it is required to instruct the - installer to use the CD-ROM for installation and not try to find - the installation files on the network. This can be accomplished by - adding the <emphasis>instmode=cd</emphasis> option to the kernel - command line (this can be done by adding the option to the - isolinux.cfg file on the CD). + When using CD-ROMs for auto-installation, it is necessary to + instruct the installer to use the CD-ROM for installation and not + try to find the installation files on the network. This can be + accomplished by adding the <emphasis>instmode=cd</emphasis> option + to the kernel command line (this can be done by adding the option + to the isolinux.cfg file on the CD).<remark>emap 2011-11-07: A bit strange since an installation via network would have to be set up, first.</remark> </para> </listitem> <listitem> <para> - Using NFS and Floppy, Network or CD-ROM for system boot-up. + Using NFS and Floppy, Network or CD-ROM for system boot-up.<remark>emap 2011-11-07: Isn't this listitem already covered above? </remark> </para> <para> This option is the most important one due to the fact that installations of PC farms are normally done using NFS servers and other - network services like &bootp; / &dhcp; . The control file can reside in + network services like &bootp; and &dhcp;. The control file can reside in the following places: </para> <orderedlist> @@ -512,40 +510,40 @@ </itemizedlist> <note> - <title>Disabling network and DHCP</title> - <para>To disable network during installations where network is not - needed or not available, for example when auto-installing from - CD-ROMs use the linuxrc option <emphasis>netsetup</emphasis> to - set network configuration behavior. To disable network setup use - <emphasis>netsetup=0</emphasis> </para> + <title>Disabling Network and DHCP</title> + <para>To disable the network during installations where it is not + needed or unavailable, for example when auto-installing from + CD-ROMs, use the linuxrc option <emphasis>netsetup</emphasis> to + set the network configuration behavior. To disable network setup use + <emphasis>netsetup=0</emphasis>.</para> </note> <para> - If <emphasis>autoyast=default</emphasis> is defined, &yast2; will look + If <emphasis>autoyast=default</emphasis> is defined, &yast; will look for a file named <filename>autoinst.xml</filename> in the following three places: </para> <orderedlist> <listitem> <para> - The root directory of the floppy disk. + the root directory of the floppy disk, </para> </listitem> <listitem> <para> - The root directory of the installation medium. + the root directory of the installation medium, </para> </listitem> <listitem> <para> - The root directory of the initial ram disk used to boot the system. + the root directory of the initial RAM disk used to boot the system. </para> </listitem> </orderedlist> <para> - With all autoyast invocation options, excluding + With all &ay; invocation options, excluding <emphasis>default</emphasis>, it is possible to specify the location of the control file in the following ways: </para> @@ -561,7 +559,7 @@ </listitem> <listitem> <para> - Specify a directory where several control files are located + Specify a directory where several control files are located: </para> <screen> autoyast=http://192.168.1.1/control-files/ @@ -573,7 +571,7 @@ </listitem> </orderedlist> <para> - If only the path prefix variable is defined, &yast2; will fetch the + If only the path prefix variable is defined, &yast; will fetch the control file from the specified location in the following way: </para> <orderedlist numeration="arabic"> @@ -585,10 +583,10 @@ </listitem> <listitem> <para> - If that file is not found, it will remove one hex digit and try - again. This action is repeated till the file with the correct name - is found. Ultimately, it will try looking for a file with the MAC - address of the clients as the file name (mac should have the + If this file is not found, &yast; will remove one hex digit and try + again. This action is repeated until the file with the correct name + is found. Ultimately, it will try looking for a file with the MAC + address of the client as the file name (mac should have the following syntax: <emphasis>0080C8F6484C</emphasis>) and if not found a file named <filename>default</filename> (in lower case). @@ -636,14 +634,11 @@ Auto-installing a Single System </title> <para> - The easiest way to auto-install a system without any network connection - is by using the standard CD-ROMs that come in the &company-suse; Linux box. Using the - CD-ROMs in combination with a floppy disk lets you getting started with - &autoyast2; very fast and without spending much time configuring - installation server and network environments. + The easiest way to auto-install a system without any network + connection is to use the original &company-suse; CD-ROMs and a floppy + disk. You do o need to set up an installation server nor the network + environment. </para> - - <para> Create the control file and name it <filename>autoinst.xml</filename>. Copy the file @@ -654,15 +649,15 @@ mcopy autoinst.xml a: </screen> - </section> + </section><remark>emap 2011-11-07: This section should be merged with the previous one on auto-install with the original CDs and floppy, with all redundant information dropped.</remark> <section> - <title>Combining linuxrc <emphasis>info</emphasis> file with &yast2; control file</title> + <title>Combining linuxrc <emphasis>info</emphasis> file with &yast; control file</title> <para> If you choose to pass information to <emphasis>linuxrc</emphasis> using the <emphasis>info</emphasis> file, it is possible to integrate the - keywords in the XML control file. In the case the file has to be + keywords in the XML control file. In this case the file has to be accessible to linuxrc and has to be named <emphasis>info</emphasis>. </para> <para> @@ -707,10 +702,10 @@ </screen> </example> <para> - Note that the autoyast keyword must point to the same file, i.e. if it + Note that the "autoyast" keyword must point to the same file. If it is on a floppy, then the protocol <emphasis>floppy</emphasis> has to be - used. In other cases where the <emphasis>info</emphasis> file is stored - in the initial ram-disk, the <emphasis>file</emphasis> option has to be used. + used. If the <emphasis>info</emphasis> file is stored + in the initial RAM disk, the <emphasis>file</emphasis> option has to be used. </para> </section> </section> @@ -719,58 +714,55 @@ System Configuration </title> <para> - The system configuration during auto-installation can be seen as the - most important part of the whole process. Customizing a system to your - environment needs is what makes an auto-installation system attractive, - not the installation part. + The system configuration during auto-installation is the most important + part of the whole process. Customizing a system according to your + environment and needs is what makes an auto-installation system + attractive, not the installation part.<remark>emap 2011-11-07: Last sentence doesn't make sense. A system can be customized just as well via an interactive YaST installation.</remark> </para> <para> As you have seen in the previous chapters, almost anything can be configured automatically on the target system. In addition to the - pre-defined directives, you can always use post-scripts to change other - things in the system. Additionally you can change any system variables and - if required, copy complete configuration files into the target system. + pre-defined directives, you can always use post-scripts to change other + things in the system. Additionally you can change any system variables, + and if required, copy complete configuration files into the target + system. </para> <section> <title> Post-Install and System Configuration </title> <para> - The Post-Installation and the System Configuration are initiated directly after the last - package is installed in the target system and is continued after the - system has booted for the first time. + The post-installation and system configuration are initiated directly + after the last package is installed on the target system and continue + after the system has booted for the first time. </para> <para> - Before the system is booted for the first time, &yast2; writes all data - collected during installation into the system and finally it writes the - boot loader in the specified location. In addition to these regular - tasks, which are also done when performing a regular installation, YaST2 - executes the <emphasis>chroot-scripts</emphasis> as specified in the - control file. Note that these scripts are executed while the system is - still not mounted. + Before the system is booted for the first time, &ay; writes all data + collected during installation and writes the boot loader in the + specified location. In addition to these regular tasks, &ay; executes + the <emphasis>chroot-scripts</emphasis> as specified in the control + file. Note that these scripts are executed while the system is not yet + mounted. </para> <para> If a different kernel than the default is installed, a hard reboot will be required. A hard reboot can also be forced during auto-installation, - independent of the installed kernel. This can be accomplished using the + independent of the installed kernel. Use the <emphasis>reboot</emphasis> property of the - <emphasis>general</emphasis> resource. (See <link - linkend="CreateProfile.General">General Options</link>) + <emphasis>general</emphasis> resource (see <link + linkend="CreateProfile.General">General Options</link>). </para> </section> <section> <title>System Customization</title> <para> Most of the system customization is done in the second stage of the - installation. &yast2; provides most of the important resources needed to - bring up a system to a usable , general state. However, you may have - other requirements for the installed system. If the required - customizations can't be done using &yast2; resources, then the - post-install scripts can be used to accomplish this task. + installation. If you require customizations that cannot be done using + &ay; resources, use post-install scripts for further modifications. </para> <para> You can define an unlimited number of custom scripts in the control - file either by editing the control file or by using the configuration + file, either by editing the control file or by using the configuration system. </para> </section> -- To unsubscribe, e-mail: yast-commit+unsubscribe@opensuse.org For additional commands, e-mail: yast-commit+help@opensuse.org