LDP
/
LDP
mirror of https://github.com/tLDP/LDP
0
1
Fork 0
Code Releases Activity

linuxdoc validation improvement 

use terse format for table, which had all of the closing tags jammed at the
end of the </tabular>
correct nesting of <item> elements in many <enum> and <itemize> elements
fix a few <url> elements
remove the 50-car pileup of closing tags at the end of the document
all in order to quell validation errors
This commit is contained in:
Martin A. Brown 2016-01-17 14:07:36 -08:00
parent 863e0ea7c2
commit 740c3d37ef
1 changed files with 214 additions and 206 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

420
LDP/howto/linuxdoc/Network-Install-HOWTO.sgml
View File

@ -95,23 +95,23 @@ translator for it then please mail me.
You can always find the latest copy of this document at the <URL URL="http://www.tldp.org/" NAME="Linux Documentation Project"> homepage.
<TABLE LOC="h">
<TABULAR CA="lll">
<BF>V.</BF><COLSEP><BF>DATE</BF><COLSEP><BF>CHANGE</BF><ROWSEP><HLINE>
0.1<COLSEP>27th July 2002<COLSEP>Started writing the first draft<ROWSEP>
<COLSEP><COLSEP>Wrote the Introduction Section.<ROWSEP>
0.2<COLSEP>2nd August 2002<COLSEP>Finalised the document structure.<ROWSEP>
<COLSEP><COLSEP>Written the SuSE Server Setup.<ROWSEP>
0.3<COLSEP>20th August 2002<COLSEP>Tidied up source to work better with PDF docs<ROWSEP>
<COLSEP><COLSEP>Written SuSE Client Install<ROWSEP>
0.4<COLSEP>21st August 2002<COLSEP>Written Redhat Server Setup<ROWSEP>
0.5<COLSEP>22nd August 2002<COLSEP>Written Redhat Client Install<ROWSEP>
0.6<COLSEP>23rd August 2002<COLSEP>Written Debian Server Setup<ROWSEP>
0.7<COLSEP>30th August 2002<COLSEP>Written Debian Client Install<ROWSEP>
0.8<COLSEP>1st September 2002<COLSEP>Written Quick Install Section<ROWSEP>
0.9<COLSEP>2nd September 2002<COLSEP>Written Structure Section & Tidied up loose ends<ROWSEP>
1.0<COLSEP>12th September 2002<COLSEP>Proof read and made refinements<ROWSEP>
<COLSEP><COLSEP>Submit to the LDP<ROWSEP>
</ROWSEP></COLSEP></COLSEP></ROWSEP></COLSEP></COLSEP></ROWSEP></COLSEP></COLSEP></ROWSEP></COLSEP></COLSEP></ROWSEP></COLSEP></COLSEP></ROWSEP></COLSEP></COLSEP></ROWSEP></COLSEP></COLSEP></ROWSEP></COLSEP></COLSEP></ROWSEP></COLSEP></COLSEP></ROWSEP></COLSEP></COLSEP></ROWSEP></COLSEP></COLSEP></ROWSEP></COLSEP></COLSEP></ROWSEP></COLSEP></COLSEP></ROWSEP></COLSEP></COLSEP></HLINE></ROWSEP></COLSEP></COLSEP></TABULAR>
<TABULAR CA="lll">
<BF/VERSION/|<BF/DATE/ |<BF/CHANGE/@<hline>@
0.1 |27th July 2002 |Started writing the first draft@
| |Wrote the Introduction Section.@
0.2 |2nd August 2002 |Finalised the document structure.@
| |Written the SuSE Server Setup.@
0.3 |20th August 2002 |Tidied up source to work better with PDF docs@
| |Written SuSE Client Install@
0.4 |21st August 2002 |Written Redhat Server Setup@
0.5 |22nd August 2002 |Written Redhat Client Install@
0.6 |23rd August 2002 |Written Debian Server Setup@
0.7 |30th August 2002 |Written Debian Client Install@
0.8 |1st September 2002 |Written Quick Install Section@
0.9 |2nd September 2002 |Written Structure Section & Tidied up loose ends@
1.0 |12th September 2002 |Proof read and made refinements@
| |Submit to the LDP@
</TABULAR>
</TABLE>
@ -150,13 +150,13 @@ This is a rough list of points that you will need to follow in order to setup a
Linux machine as a network install server. The HOWTO sections on setting up
servers roughly adhere to this list:
<ENUM>
<ITEM>Install a machine with Linux to be a server machine
<ITEM>Check you have enough disk space free to serve Linux installs
<ITEM>Set up the filespace you want to use to serve the Linux installs
<ITEM>Copy the install media to your filespace
<ITEM>Enable one or more remote access methods to your filespace
<ITEM>Customise your server images
</ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ENUM>
<ITEM>Install a machine with Linux to be a server machine</ITEM>
<ITEM>Check you have enough disk space free to serve Linux installs</ITEM>
<ITEM>Set up the filespace you want to use to serve the Linux installs</ITEM>
<ITEM>Copy the install media to your filespace</ITEM>
<ITEM>Enable one or more remote access methods to your filespace</ITEM>
<ITEM>Customise your server images</ITEM>
</ENUM>
<SECT1>Client Install Structure <LABEL ID="client">
@ -166,16 +166,16 @@ This is a rough list of points that you will need to follow in order to install
a Linux distribution from a network install server. The HOWTO sections on
installing client machines roughly adhere to this list:
<ENUM>
<ITEM>Install config program on a machine
<ITEM>Use config program to create config files
<ITEM>Edit the config file to include customisable options
<ITEM>Create a bootable media
<ITEM>Provide access to the config file
<ITEM>Boot your machine and read the config file
<ITEM>Client contacts server machine
<ITEM>Manually supply any requested arguments
<ITEM>Client installs and reboots to new operating system
</ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ENUM>
<ITEM>Install config program on a machine</ITEM>
<ITEM>Use config program to create config files</ITEM>
<ITEM>Edit the config file to include customisable options</ITEM>
<ITEM>Create a bootable media</ITEM>
<ITEM>Provide access to the config file</ITEM>
<ITEM>Boot your machine and read the config file</ITEM>
<ITEM>Client contacts server machine</ITEM>
<ITEM>Manually supply any requested arguments</ITEM>
<ITEM>Client installs and reboots to new operating system</ITEM>
</ENUM>
<SECT1>Reading plan
@ -236,30 +236,30 @@ distributions of Linux. The list is in no specific order:
<SECT2>Advantages
<P>
<ITEMIZE>
<ITEM>Fastest installation (on a good network)
<ITEM>Automatic configuration available (unattended installation)
<ITEM>Very quick installation of many systems
<ITEM>No need for physical installation media
<ITEM>Customisable installation with packages not available from the standard distribution
<ITEM>Once the install system is setup and working installations are very simple
<ITEM>Multiple system configurations available for automatic installation with different config files
<ITEM>Simultaneous installation from a single source
<ITEM>No need for an install media library, space-saving
<ITEM>Very easy to update
<ITEM>No problems with reading install media
</ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEMIZE>
<ITEM>Fastest installation (on a good network)</ITEM>
<ITEM>Automatic configuration available (unattended installation)</ITEM>
<ITEM>Very quick installation of many systems</ITEM>
<ITEM>No need for physical installation media</ITEM>
<ITEM>Customisable installation with packages not available from the standard distribution</ITEM>
<ITEM>Once the install system is setup and working installations are very simple</ITEM>
<ITEM>Multiple system configurations available for automatic installation with different config files</ITEM>
<ITEM>Simultaneous installation from a single source</ITEM>
<ITEM>No need for an install media library, space-saving</ITEM>
<ITEM>Very easy to update</ITEM>
<ITEM>No problems with reading install media</ITEM>
</ITEMIZE>
<SECT2>Disadvantages
<P>
<ITEMIZE>
<ITEM>Slow installation (on a bad network)
<ITEM>Added complexity of installation
<ITEM>Time needed initially to set up an install server
<ITEM>Relies on network and connectivity
<ITEM>Uses network bandwidth
<ITEM>A server machine is required (expensive)
</ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEMIZE>
<ITEM>Slow installation (on a bad network)</ITEM>
<ITEM>Added complexity of installation</ITEM>
<ITEM>Time needed initially to set up an install server</ITEM>
<ITEM>Relies on network and connectivity</ITEM>
<ITEM>Uses network bandwidth</ITEM>
<ITEM>A server machine is required (expensive)</ITEM>
</ITEMIZE>
<SECT1>Automatic vs Manual Installation
@ -340,14 +340,14 @@ in either manual or automated mode. The basic requirements are:
<ENUM>
<ITEM>That you have a server machine available to you that has enough storage
space on it to hold the install image that you want to transfer over the
network.
network.</ITEM>
<ITEM>Ensure that this server is powerful enough to cope with the load that is
going to be placed upon it.
going to be placed upon it.</ITEM>
<ITEM>A network connection between your server and the client you want to
install.
install.</ITEM>
<ITEM>A client machine with the appropriate hardware for the installation that
you are intending to do.
</ITEM></ITEM></ITEM></ITEM></ENUM>
you are intending to do.</ITEM>
</ENUM>
Some examples where you might require specific hardware may be if you have a
specialised network or if you need to attach more storage to your server, for
@ -432,9 +432,9 @@ A guide for the amount of space that you will require will be the amount of
space on your install media that you are intending to copy from later. This
might be one of the following approximate examples:
<ITEMIZE>
<ITEM>Number of CDs x 650Mb
<ITEM>Number of ISO images x 650Mb
</ITEM></ITEM></ITEMIZE>
<ITEM>Number of CDs x 650Mb</ITEM>
<ITEM>Number of ISO images x 650Mb</ITEM>
</ITEMIZE>
<SECT3>How much space do you have?
@ -476,10 +476,10 @@ particular install server.
<P>
To install over NFS you need to meet certain conditions on the server:
<ITEMIZE>
<ITEM>Your install directory is exported
<ITEM>NFS is installed and running
<ITEM>Portmap is running
</ITEM></ITEM></ITEM></ITEMIZE>
<ITEM>Your install directory is exported</ITEM>
<ITEM>NFS is installed and running</ITEM>
<ITEM>Portmap is running</ITEM>
</ITEMIZE>
To export your install directory edit the <TT>/etc/exports</TT> file and add an
entry for your installation target directory to it. If you are not sure about
@ -605,28 +605,30 @@ is to use a floppy disk.
need to do this step once, when you have a boot floppy you can install as many
machines as you like with a single floppy):
<ITEMIZE>
<ITEM>Locate the floppy image that you need to use.
<ITEM>Locate the floppy image that you need to use.</ITEM>
<ITEM>Copy the image to your floppy disk (make sure you have one
inserted in the drive, but not mounted) using the following command:
<VERB>dd if=your-file.img of=/dev/fd0</VERB>
</ITEM></ITEM></ITEMIZE>
<VERB>dd if=your-file.img of=/dev/fd0</VERB></ITEM>
</ITEMIZE>
<ITEM>If you are doing an automated install (with the config file) then you
should follow this step (otherwise skip to next step):
<ITEMIZE>
<ITEM>Copy your config file to the root directory of the floppy
</ITEM></ITEMIZE>
<ITEM>Copy your config file to the root directory of the floppy</ITEM>
</ITEMIZE>
</ITEM>
<ITEM>Insert your floppy disk into the client machine that you want to install.
Make sure that the floppy disk is in the boot list of your BIOS and turn on your
machine to boot from the floppy.
machine to boot from the floppy.</ITEM>
<ITEM>At the boot prompt:
<ITEMIZE>
<ITEM>If you are doing an automated install then start the automated
process
process</ITEM>
<ITEM>If you're not using config files then press ENTER for the
default installation
</ITEM></ITEM></ITEMIZE>
<ITEM>Finish the installation.
</ITEM></ITEM></ITEM></ITEM></ITEM></ENUM>
default installation</ITEM>
</ITEMIZE>
</ITEM>
<ITEM>Finish the installation.</ITEM>
</ENUM>
Don't forget that some distributions will allow you to boot from other media as
well as floppy images to perform network installations. Also, each distribution
@ -676,10 +678,10 @@ space of install media that you are intending to copy from later. This might be
one of the following examples:
<ITEMIZE>
<ITEM>Number of CDs x 650Mb
<ITEM>Number of ISO images x 650Mb
<ITEM>One DVD which might be roughly 5Gb
</ITEM></ITEM></ITEM></ITEMIZE>
<ITEM>Number of CDs x 650Mb</ITEM>
<ITEM>Number of ISO images x 650Mb</ITEM>
<ITEM>One DVD which might be roughly 5Gb</ITEM>
</ITEMIZE>
<SECT2>How much space do you have?
@ -706,12 +708,12 @@ our install server will be setup and running: <VERB>/install</VERB>
Copy your install media to <TT>/install</TT>. The following example shows you how to do
this for copying your SuSE CD images to <TT>/install</TT>:
<ENUM>
<ITEM>Mount your CD<NEWLINE>e.g. <TT>mount /mnt/cdrom</TT>
<ITEM>Copy the data from CD<NEWLINE>e.g. <TT>cp -av /mnt/cdrom /install</TT>
<ITEM>Unmount the CD<NEWLINE>e.g. <TT>umount /mnt/cdrom</TT>
<ITEM>Now swap CDs and repeat from step 1 for each of your CDs you have.
<ITEM>Ensure that you have the dot files from the root directory of each CD copied over to <TT>/install</TT>
</ITEM></ITEM></NEWLINE></ITEM></NEWLINE></ITEM></NEWLINE></ITEM></ENUM>
<ITEM>Mount your CD<NEWLINE>e.g. <TT>mount /mnt/cdrom</TT></ITEM>
<ITEM>Copy the data from CD<NEWLINE>e.g. <TT>cp -av /mnt/cdrom /install</TT></ITEM>
<ITEM>Unmount the CD<NEWLINE>e.g. <TT>umount /mnt/cdrom</TT></ITEM>
<ITEM>Now swap CDs and repeat from step 1 for each of your CDs you have.</ITEM>
<ITEM>Ensure that you have the dot files from the root directory of each CD copied over to <TT>/install</TT></ITEM>
</ENUM>
Now you should have all you need in <TT>/install</TT> but if you have copied
from CD then as far as SuSE is concerned the <TT>/install</TT> directory still
@ -734,10 +736,10 @@ system updates may be applied over HTTP or FTP.
To install over NFS you need to meet certain conditions on the server:
<ITEMIZE>
<ITEM>Your install directory is exported
<ITEM>NFS is installed and running
<ITEM>Portmap is running
</ITEM></ITEM></ITEM></ITEMIZE>
<ITEM>Your install directory is exported</ITEM>
<ITEM>NFS is installed and running</ITEM>
<ITEM>Portmap is running</ITEM>
</ITEMIZE>
To export your install directory edit the <TT>/etc/exports</TT> file and add an
entry for <TT>/install</TT> to it. In our example, we would use the folowing
@ -801,10 +803,10 @@ In order to start creating your config files you will need to install the
AutoYaST module for YaST2 on your SuSE machine. You will need three RPMs for
this, all of which are on your SuSE source media e.g. CDs. The three RPMs are:
<ITEMIZE>
<ITEM>yast2-trans-autoinst
<ITEM>yast2-config-autoinst
<ITEM>yast2-module-autoinst
</ITEM></ITEM></ITEM></ITEMIZE>
<ITEM>yast2-trans-autoinst</ITEM>
<ITEM>yast2-config-autoinst</ITEM>
<ITEM>yast2-module-autoinst</ITEM>
</ITEMIZE>
Check to see if you already have them installed with the command: <VERB>rpm -q {rpm package name}</VERB>
@ -843,14 +845,14 @@ GUI from YaST2 you are ready to save out your configuration file to disk. <EM>
NOTE: it is outside the boundaries of this document to take you through each
configuration option for installation, we are just concerned with the principles
of network installs here. Please consult your SuSE documentation or
the <URL URL="http://www.suse.com" NAME="SuSE Website"> for this information.</URL></EM>
the <URL URL="http://www.suse.com" NAME="SuSE Website"> for this information.</EM>
When you save your configuration files they will be stored locally in two
different locations depending on what file you have created as follows:
<ITEMIZE>
<ITEM>Machine configuration files are stored in <TT>/var/lib/autoinstall/repository</TT>
<ITEM>Class definition files are stored in <TT>/var/lib/autoinstall/classes</TT>
</ITEM></ITEM></ITEMIZE>
<ITEM>Machine configuration files are stored in <TT>/var/lib/autoinstall/repository</TT></ITEM>
<ITEM>Class definition files are stored in <TT>/var/lib/autoinstall/classes</TT></ITEM>
</ITEMIZE>
<SECT2>Advanced Config File Setup
@ -926,29 +928,29 @@ this is the way in which you should boot your client machines.
BIOS, insert the CD. You should be faced with the normal boot menu of the SuSE
installation program. As an alternative to booting from CD, you can boot from
floppy images, from the network, or using whichever method you would normally
use to boot the installation program.
<ITEM>Select the "Manual Installation" option from the boot menu
use to boot the installation program.</ITEM>
<ITEM>Select the "Manual Installation" option from the boot menu</ITEM>
<ITEM>Your client should now boot the installation program and present you with
a new menu system for the installer
<ITEM>Load any network modules you will need in order to connect to your network
a new menu system for the installer</ITEM>
<ITEM>Load any network modules you will need in order to connect to your network</ITEM>
<ITEM>Load any other modules you might need for installation e.g. SCSI modules
if you are installing onto a SCSI type machine.
<ITEM>Select "Start Installation" from the menu
if you are installing onto a SCSI type machine.</ITEM>
<ITEM>Select "Start Installation" from the menu</ITEM>
<ITEM>Choose the NFS option and fill in the IP addresses when prompted for.
These should all be familiar to you i.e. the IP address of your server, and
perhaps your client and nameserver as well if you have not selected to use DHCP.
perhaps your client and nameserver as well if you have not selected to use DHCP.</ITEM>
<ITEM>The installation will now proceed to the configuration screens where you
can select the installation options you require for your client in the normal
way
way</ITEM>
<ITEM>Once you have configured all the installation options and selected to
start the installation process, instead of reading from the normal CD (or other)
media, the installation program will read all the information it needs from the
network.
network.</ITEM>
<ITEM>Don't forget to remove the CD (or other media) from the drive otherwise
you could end up with a recursive installation process.
you could end up with a recursive installation process.</ITEM>
<ITEM>Go grab a cup of something while you wait for your shiny new installation
to finish, no changing of installation media needed.
</ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ENUM>
to finish, no changing of installation media needed.</ITEM>
</ENUM>
<SECT2>Automatic Installation
@ -963,28 +965,28 @@ autoinst.xml. You can do this as follows:
Insert and mount a floppy disk
cp /var/lib/autoinstall/repository/Your-File /dev/fd0/autoinst.xml
Unmount the floppy disk
</VERB>
<ITEM>Put your floppy disk with the config file in your client machine
</VERB></ITEM>
<ITEM>Put your floppy disk with the config file in your client machine</ITEM>
<ITEM>Turn on your machine, ensure the CD drive is in the boot list of your
BIOS, insert the CD. You should be faced with the normal boot menu of the SuSE
installation program. As an alternative to booting from CD, you can boot from
floppy images, from the network, or using whichever method you would normally
use to boot the installation program.
use to boot the installation program.</ITEM>
<ITEM>At the boot menu leave the default line as Linux to do the standard boot,
but add the following parameters in order to read your configuration file from
the floppy disk:
<VERB>
linux autoyast=floppy
</VERB>
</VERB></ITEM>
<ITEM>Your client should now boot the installation program and it will try to
load appropriate modules and install the system with the information that you
have provided in the config file.
have provided in the config file.</ITEM>
<ITEM>If you are prompted to input any information for any reason then do so
e.g. if the installer cannot connect to your network.
e.g. if the installer cannot connect to your network.</ITEM>
<ITEM>Once the installation is running then you can remove the CD and the floppy
disk and grab a cup of something while you wait for your shiny new installation
to finish, no changing of installation media needed.
</ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ENUM>
to finish, no changing of installation media needed.</ITEM>
</ENUM>
<SECT3>Further Boot Options
@ -1003,20 +1005,20 @@ installer.
The list of keywords you can use is as follows:
<ITEMIZE>
<ITEM>autoyast - the location of your configuration file
<ITEM>gateway - the gateway your client should use (if any)
<ITEM>insmod - any special kernel modules you need to be loaded
<ITEM>install - a full path to your server installation directory
<ITEM>autoyast - the location of your configuration file</ITEM>
<ITEM>gateway - the gateway your client should use (if any)</ITEM>
<ITEM>insmod - any special kernel modules you need to be loaded</ITEM>
<ITEM>install - a full path to your server installation directory</ITEM>
<ITEM>ip - the address of your client machine. If this is blank then the
installer will try BOOTP/DHCP
<ITEM>nameserver - the nameserver address on your network
<ITEM>netdevice - the network adaptor you want to be used
<ITEM>netmask - your client's netmask
installer will try BOOTP/DHCP</ITEM>
<ITEM>nameserver - the nameserver address on your network</ITEM>
<ITEM>netdevice - the network adaptor you want to be used</ITEM>
<ITEM>netmask - your client's netmask</ITEM>
<ITEM>server - the hostname or IP address of the server you have set up i.e. the
machine you have your NFS exports from
machine you have your NFS exports from</ITEM>
<ITEM>serverdir - the directory on your server the installation should be taken
from
</ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEM></ITEMIZE>
from</ITEM>
</ITEMIZE>
Using the above keywords in an example info file, you <EM>might</EM> end up with
something looking a little bit like this:
@ -1075,9 +1077,9 @@ A guide for the amount of space that you will require will be the amount or
space of install media that you are intending to copy from later. This might be
one of the following examples:
<ITEMIZE>
<ITEM>Number of CDs x 650Mb
<ITEM>Number of ISO images x 650Mb
</ITEM></ITEM></ITEMIZE>
<ITEM>Number of CDs x 650Mb</ITEM>
<ITEM>Number of ISO images x 650Mb</ITEM>
</ITEMIZE>
<SECT2>How much space do you have?
@ -1104,11 +1106,11 @@ our install server will be setup and running: <VERB>/install</VERB>
Copy your install media to <TT>/install</TT>. The following example shows you how to do
this for copying your Redhat CD images to <TT>/install</TT>:
<ENUM>
<ITEM>Mount your CD<NEWLINE>e.g. <TT>mount /mnt/cdrom</TT>
<ITEM>Copy the data from CD<NEWLINE>e.g. <TT>cp -av /mnt/cdrom /install</TT>
<ITEM>Unmount the CD<NEWLINE>e.g. <TT>umount /mnt/cdrom</TT>
<ITEM>Now swap CDs and repeat from step 1 for each of your CDs you have.
</ITEM></NEWLINE></ITEM></NEWLINE></ITEM></NEWLINE></ITEM></ENUM>
<ITEM>Mount your CD<NEWLINE>e.g. <TT>mount /mnt/cdrom</TT></ITEM>
<ITEM>Copy the data from CD<NEWLINE>e.g. <TT>cp -av /mnt/cdrom /install</TT></ITEM>
<ITEM>Unmount the CD<NEWLINE>e.g. <TT>umount /mnt/cdrom</TT></ITEM>
<ITEM>Now swap CDs and repeat from step 1 for each of your CDs you have.</ITEM>
</ENUM>
<SECT1>Enable Remote Access
@ -1133,10 +1135,10 @@ this service on your server.
To install over NFS you need to meet certain conditions on the server:
<ITEMIZE>
<ITEM>Your install directory is exported
<ITEM>NFS is installed and running
<ITEM>Portmap is running
</ITEM></ITEM></ITEM></ITEMIZE>
<ITEM>Your install directory is exported</ITEM>
<ITEM>NFS is installed and running</ITEM>
<ITEM>Portmap is running</ITEM>
</ITEMIZE>
To export your install directory edit the <TT>/etc/exports</TT> file and add an
entry for <TT>/install</TT> to it. In our example, we would use the folowing
@ -1277,9 +1279,9 @@ Kickstart Configurator on your Linux machine. You will need one of two RPMS
for this depending on the version of Redhat you are using. These RPMS are
available on your Redhat install CDs as follows:
<ITEMIZE>
<ITEM><TT>redhat-config-kickstart</TT> - for versions 8.x and above
<ITEM><TT>ksconfig</TT> - for earlier versions
</ITEM></ITEM></ITEMIZE>
<ITEM><TT>redhat-config-kickstart</TT> - for versions 8.x and above</ITEM>
<ITEM><TT>ksconfig</TT> - for earlier versions</ITEM>
</ITEMIZE>
Check to see if you already have them installed with the command: <VERB>rpm -q {rpm package name}</VERB>
@ -1310,7 +1312,7 @@ boundaries of this document to take you through each configuration option for
installation, we are just concerned with the principles of network installs
here. Please consult your Redhat documentation or
the <URL URL="http://www.redhat.com" NAME="Redhat Website"> for this
information.</URL></EM> Click the "<TT>save</TT>" button and choose a location on
information.</EM> Click the "<TT>save</TT>" button and choose a location on
your system to store configuration files. If you are creating lots of different
configurations then it might be worthwhile creating your own configuration
repository - don't forget to name the files sensibly so you know which is which.
@ -1363,43 +1365,48 @@ need to do this step once, when you have a boot floppy you can install as many
machines as you like with a single floppy):
<ITEMIZE>
<ITEM>Locate the floppy image that you need to use. This is on the
first Redhat CD and is at <TT>images/bootnet.img</TT>
first Redhat CD and is at <TT>images/bootnet.img</TT></ITEM>
<ITEM>From the <TT>images</TT> directory on the CD copy the image to
your floppy disk (make sure you have one inserted in the drive, but not
mounted) using the following command:
<VERB>dd if=bootnet.img of=/dev/fd0</VERB>
</ITEM></ITEM></ITEMIZE>
<VERB>dd if=bootnet.img of=/dev/fd0</VERB></ITEM>
</ITEMIZE>
</ITEM>
<ITEM>If you are doing an automated install (with the config file) then you
should follow this step (otherwise skip to next step):
<ITEMIZE>
<ITEM>Mount your floppy disk <VERB>mount /mnt/floppy</VERB>
<ITEM>Mount your floppy disk <VERB>mount /mnt/floppy</VERB></ITEM>
<ITEM>Copy your config file to the root directory of the floppy with
the name <TT>ks.cfg</TT> <VERB>cp /path/to/file /mnt/floppy</VERB>
<ITEM>Umount your floppy disk <VERB>umount /mnt/floppy</VERB>
</ITEM></ITEM></ITEM></ITEMIZE>
the name <TT>ks.cfg</TT> <VERB>cp /path/to/file /mnt/floppy</VERB></ITEM>
<ITEM>Umount your floppy disk <VERB>umount /mnt/floppy</VERB></ITEM>
</ITEMIZE>
</ITEM>
<ITEM>Insert your floppy disk into the client machine that you want to install
Redhat on. Make sure that the floppy disk is in the boot list of your BIOS and
turn on your machine to boot from the floppy.
</ITEM>
<ITEM>At the boot prompt:
<ITEMIZE>
<ITEM>If you are doing an automated install:
<VERB>linux ks=floppy</VERB>
<VERB>linux ks=floppy</VERB></ITEM>
<ITEM>If you're not using config files then press ENTER for the
default installation
</ITEM></ITEM></ITEMIZE>
default installation</ITEM>
</ITEMIZE>
</ITEM>
<ITEM>Finish the installation:
<ITEMIZE>
<ITEM>If you are doing an automated install then you must complete any
parts of the configuration process that you have missed in the config
file. If you have a complete config file then you're done so go get
yourself a cup of something nice and wait for your install to finish.
yourself a cup of something nice and wait for your install to finish.</ITEM>
<ITEM>If you are doing a manual install then you must complete the
installation in the normal way, going through each menu of the Redhat
install program and selecting the options you require for your machine.
When you finish then it's time for a cup of something nice, no need to
swap install media here.
</ITEM></ITEM></ITEMIZE>
</ITEM></ITEM></ITEM></ITEM></ITEM></ENUM>
swap install media here.</ITEM>
</ITEMIZE>
</ITEM>
</ENUM>
<SECT2>Further Boot Options
@ -1415,25 +1422,26 @@ extra drivers for network cards. This can then be read on boot and the drivers
loaded for your card from there instead. This is done as follows:
<ENUM>
<ITEM>In the <TT>images</TT> directory on your CD you should find a file called
<TT>drvnet.img</TT>.
<TT>drvnet.img</TT>.</ITEM>
<ITEM>From the <TT>images</TT> directory on your CD, copy the file to a
<EM>different</EM> floppy disk with the command:
<VERB>dd if=drvnet.img of=/dev/fd0</VERB>
Again, make sure your floppy disk is not mounted when you run this command.
Again, make sure your floppy disk is not mounted when you run this command.</ITEM>
<ITEM>Now you have a network driver floppy disk. You should return to your
installation as described above but now add the keyword <TT>dd</TT> to your
command line.
<ITEMIZE>
<ITEM>So for automated intall we type:
<VERB>linux dd ks=floppy</VERB>
<VERB>linux dd ks=floppy</VERB></ITEM>
<ITEM>For manual install we type:
<VERB>linux dd</VERB>
</ITEM></ITEM></ITEMIZE>
<VERB>linux dd</VERB></ITEM>
</ITEMIZE>
</ITEM>
<ITEM>When prompted if you have a driver disk, select <TT>YES</TT>. Then swap
the boot disk for your driver disk and the extra drivers will load and detect
your network card.
<ITEM>You should now continue with the installation as described above.
</ITEM></ITEM></ITEM></ITEM></ITEM></ENUM>
your network card.</ITEM>
<ITEM>You should now continue with the installation as described above.</ITEM>
</ENUM>
<!--
@ -1576,10 +1584,10 @@ service should be used for your particular install server.
<P>
To install over NFS you need to meet certain conditions on the server:
<ITEMIZE>
<ITEM>Your install directory is exported
<ITEM>NFS is installed and running
<ITEM>Portmap is running
</ITEM></ITEM></ITEM></ITEMIZE>
<ITEM>Your install directory is exported</ITEM>
<ITEM>NFS is installed and running</ITEM>
<ITEM>Portmap is running</ITEM>
</ITEMIZE>
To export your install directory edit the <TT>/etc/exports</TT> file and add an
entry for directory you have copied your Debian archive to. In our examples
@ -1664,10 +1672,10 @@ in the directory specified rather than any of it's subdirectories.
Copy each floppy disk image that you have downloaded from the server to a
different floppy disk following the example below:
<ITEMIZE>
<ITEM>Insert a floppy disk
<ITEM><TT>dd if=/path/to/image of=/dev/fd0</TT>
<ITEM>Remove floppy disk.
</ITEM></ITEM></ITEM></ITEMIZE>
<ITEM>Insert a floppy disk</ITEM>
<ITEM><TT>dd if=/path/to/image of=/dev/fd0</TT></ITEM>
<ITEM>Remove floppy disk.</ITEM>
</ITEMIZE>
Do not mount the floppy disks when using this procedure to create floppy boot
disks. Also, don't forget to check that the floppy disks you are going to use
@ -1705,16 +1713,17 @@ information as well as show you how to solve a specific problem.
<SECT2>Generic
<P>
<ITEMIZE>
<ITEM><URL URL="http://www.tldp.org/HOWTO/Net-HOWTO/index.html" NAME="Net-HOWTO">
<ITEM><URL URL="http://www.tldp.org/HOWTO/Installation-HOWTO/index.html" NAME="Installation-HOWTO">
</URL></ITEM></URL></ITEM></ITEMIZE>
<ITEM><URL URL="http://www.tldp.org/HOWTO/Net-HOWTO/index.html" NAME="Net-HOWTO"></ITEM>
<ITEM><URL URL="http://www.tldp.org/HOWTO/Installation-HOWTO/index.html" NAME="Installation-HOWTO"></ITEM>
</ITEMIZE>
<SECT2>Redhat
<P>
<ITEMIZE>
<ITEM><URL URL="http://www.tldp.org/HOWTO/KickStart-HOWTO.html" NAME="Kickstart-HOWTO">
</URL></ITEM></ITEMIZE>
</ITEM>
</ITEMIZE>
<SECT1>Mini-HOWTO
@ -1726,16 +1735,16 @@ These are the smaller free text relatives to the HOWTOs above.
<SECT2>Generic
<P>
<ITEMIZE>
<ITEM><URL URL="http://www.tldp.org/HOWTO/mini/Pre-Installation-Checklist/index.html" NAME="Pre-Installation-Checklist">
<ITEM><URL URL="http://www.tldp.org/HOWTO/mini/Post-Installation-Checklist/index.html" NAME="Post-Installation-Checklist">
</URL></ITEM></URL></ITEM></ITEMIZE>
<ITEM><URL URL="http://www.tldp.org/HOWTO/mini/Pre-Installation-Checklist/index.html" NAME="Pre-Installation-Checklist"></ITEM>
<ITEM><URL URL="http://www.tldp.org/HOWTO/mini/Post-Installation-Checklist/index.html" NAME="Post-Installation-Checklist"></ITEM>
</ITEMIZE>
<SECT2>Debian
<P>
<ITEMIZE>
<ITEM><URL URL="http://www.tldp.org/HOWTO/mini/Debian-Jigdo/index.html" NAME="Debian-Jigdo">
</URL></ITEM></ITEMIZE>
</ITEM></ITEMIZE>
<SECT1>Web Pages
@ -1750,35 +1759,35 @@ possible but they may become outdated.
<ITEMIZE>
<ITEM><URL URL="http://www.tldp.org" NAME="Linux Documentation Project"> -
<EM>the</EM> Linux documentation reference site.
</URL></ITEM></ITEMIZE>
</ITEM></ITEMIZE>
<SECT2>SuSE
<P>
<ITEMIZE>
<ITEM><URL URL="http://www.suse.com" NAME="Main SuSE Website">
<ITEM><URL URL="http://www.suse.de/~nashif/autoinstall" NAME="Autoinstall Website">
</URL></ITEM></URL></ITEM></ITEMIZE>
<ITEM><URL URL="http://www.suse.com" NAME="Main SuSE Website"></ITEM>
<ITEM><URL URL="http://www.suse.de/~nashif/autoinstall" NAME="Autoinstall Website"></ITEM>
</ITEMIZE>
<SECT2>Redhat
<P>
<ITEMIZE>
<ITEM><URL URL="http://www.redhat.com" NAME="Main Redhat Website">
<ITEM><URL URL="http://www.redhat.com/docs" NAME="Documentation Page">
<ITEM><URL URL="http://www.redhat.com/apps/support/resources" NAME="Support/Resources Page">
</URL></ITEM></URL></ITEM></URL></ITEM></ITEMIZE>
<ITEM><URL URL="http://www.redhat.com" NAME="Main Redhat Website"></ITEM>
<ITEM><URL URL="http://www.redhat.com/docs" NAME="Documentation Page"></ITEM>
<ITEM><URL URL="http://www.redhat.com/apps/support/resources" NAME="Support/Resources Page"></ITEM>
</ITEMIZE>
<SECT2>Debian
<P>
<ITEMIZE>
<ITEM><URL URL="http://www.debian.org" NAME="Main Debian Website">
<ITEM><URL URL="http://www.debian.org/releases/stable/installmanual" NAME="Installation Manual">
<ITEM><URL URL="http://www.debian.org/mirrors/ftpmirror" NAME="Setting up your own Debian mirror">
<ITEM><URL URL="http://www.debian.org/misc/README.mirrors" NAME="List of mirrors">
<ITEM><URL URL="http://www.informatik.uni-koeln.de/fai" NAME="Debian Fully Automatic Installation">
</URL></ITEM></URL></ITEM></URL></ITEM></URL></ITEM></URL></ITEM></ITEMIZE>
<ITEM><URL URL="http://www.debian.org" NAME="Main Debian Website"></ITEM>
<ITEM><URL URL="http://www.debian.org/releases/stable/installmanual" NAME="Installation Manual"></ITEM>
<ITEM><URL URL="http://www.debian.org/mirrors/ftpmirror" NAME="Setting up your own Debian mirror"></ITEM>
<ITEM><URL URL="http://www.debian.org/misc/README.mirrors" NAME="List of mirrors"></ITEM>
<ITEM><URL URL="http://www.informatik.uni-koeln.de/fai" NAME="Debian Fully Automatic Installation"></ITEM>
</ITEMIZE>
<SECT1>Mailing Lists
@ -1791,7 +1800,7 @@ possible but they may become outdated.
<ITEM><BF>suse-autoinstall@suse.com</BF> is a mailing list specific to AutoYaST.
<NEWLINE>List archives are at <URL URL="http://lists.suse.com/archive/suse-autoinstall" NAME="http://lists.suse.com/archive/suse-autoinstall">
<NEWLINE>Subscribe address is <URL URL="mailto:suse-autoinstall-subscribe@suse.com" NAME="suse-autoinstall-subscribe@suse.com">
</URL></NEWLINE></URL></NEWLINE></ITEM></ITEMIZE>
</ITEM></ITEMIZE>
<SECT2>Redhat
@ -1799,18 +1808,18 @@ possible but they may become outdated.
<ITEMIZE>
<ITEM><BF>redhat-install-list@redhat.com</BF> is a mailing list for Redhat installation.
<NEWLINE>List archives are only available to list members
<NEWLINE>List information page is at <URL URL="https://listman.redhat.com/mailman/listinfo/redhat-install-list" NAME="https://listman.redhat.com/mailman/listinfo/redhat-install-list">
<NEWLINE>List information page is at <URL URL="https://listman.redhat.com/mailman/listinfo/redhat-install-list" NAME="https://listman.redhat.com/mailman/listinfo/redhat-install-list"></ITEM>
<ITEM><BF>Other Redhat Lists</BF> are also available on-line
<NEWLINE>Information page is at <URL URL="http://www.redhat.com/support/forums" NAME="http://www.redhat.com/support/forums">
</URL></NEWLINE></ITEM></URL></NEWLINE></NEWLINE></ITEM></ITEMIZE>
<NEWLINE>Information page is at <URL URL="http://www.redhat.com/support/forums" NAME="http://www.redhat.com/support/forums"></ITEM>
</ITEMIZE>
<SECT2>Debian
<P>
<ITEMIZE>
<ITEM><BF>Debian mailing lists</BF> can be found at <URL URL="http://www.debian.org/MailingLists" NAME="http://www.debian.org/MailingLists">
<ITEM>List archives can be found at <URL URL="http://lists.debian.org" NAME="http://lists.debian.org">
</URL></ITEM></URL></ITEM></ITEMIZE>
<ITEM><BF>Debian mailing lists</BF> can be found at <URL URL="http://www.debian.org/MailingLists" NAME="http://www.debian.org/MailingLists"></ITEM>
<ITEM>List archives can be found at <URL URL="http://lists.debian.org" NAME="http://lists.debian.org"></ITEM>
</ITEMIZE>
<SECT1>Local Resources
@ -1840,6 +1849,5 @@ this section then they will be particularly welcome.
<item><url url="news:comp.arch.storage" name="Storage">.
</itemize>-->
</P></SECT1></P></SECT1></P></SECT2></P></SECT2></P></SECT2></P></SECT1></P></SECT2></P></SECT2></P></SECT2></P></SECT2></P></SECT1></P></SECT2></P></SECT2></P></SECT1></P></SECT2></P></SECT2></P></SECT1></P></LABEL></SECT></REF></P></SECT1></REF></P></SECT></P></SECT2></P></SECT2></P></SECT2></P></SECT1></URL></P></SECT2></URL></P></SECT2></URL></P></SECT1></P></SECT2></URL></P></SECT2></P></SECT1></REF></P></SECT></P></SECT2></P></SECT1></REF></REF></P></SECT2></P></LABEL></SECT2></P></SECT2></P></SECT1></REF></P></SECT></P></SECT2></P></LABEL></SECT1></P></SECT2></P></SECT2></P></SECT2></P></SECT1></P></SECT1></P></SECT2></P></SECT2></P></SECT1></REF></P></SECT></P></SECT3></P></SECT2></P></SECT2></P></SECT1></REF></REF></REF></P></SECT2></P></LABEL></SECT2></P></SECT2></P></SECT1></REF></P></SECT></P></LABEL></SECT1></P></SECT2></P></SECT1></P></SECT1></P></SECT2></P></SECT2></P></SECT1></REF></P></SECT></P></SECT2></REF></P></SECT3></P></LABEL></SECT3></P></SECT3></P></SECT2></P></SECT1></P></SECT2></P></SECT3></P></SECT3></P></SECT3></P></SECT2></P></SECT2></P></SECT3></P></SECT3></P></SECT2></REF></P></SECT2></P></SECT1></P></SECT1></P></SECT1></P></SECT2></P></SECT2></P></SECT1></P></SECT2></P></SECT2></P></SECT1></P></LABEL></SECT></P></SECT1></P></LABEL></SECT1></P></LABEL></SECT1></REF></REF></P></SECT></URL></P></SECT1></P></SECT1></NEWLINE></NEWLINE></NEWLINE></P></SECT1></P></SECT1></P></SECT1></P></SECT></TOC></DATE></NEWLINE></AUTHOR></TITLE></ARTICLE>
</ARTICLE>