From 7316f95396198d32b1b30c51d5648217b0006a5b Mon Sep 17 00:00:00 2001 From: ue Date: Thu, 18 Apr 2002 01:07:25 +0000 Subject: Restructure the Sparc installation instructions to - get rid of the 4th level headings - seperate the actions required to prepare the installation (getting the CD, settings up the various daemons, ...) from the actual installation Translation teams: This patch moves some paragraphs around and changes a lot of headers, but does not contain any content changes in the strict sense of the word (i.e. I did not rewrite paragraphs yet). There were no changes to the indentation, either. Reviewed by: bmah, -sparc, -doc --- .../installation/sparc64/install.sgml | 125 +++++++++------------ 1 file changed, 55 insertions(+), 70 deletions(-) diff --git a/release/doc/en_US.ISO8859-1/installation/sparc64/install.sgml b/release/doc/en_US.ISO8859-1/installation/sparc64/install.sgml index 98a54bc..1c71ded 100644 --- a/release/doc/en_US.ISO8859-1/installation/sparc64/install.sgml +++ b/release/doc/en_US.ISO8859-1/installation/sparc64/install.sgml @@ -29,9 +29,6 @@ This file contains sparc64-specific installation instructions. optionally to copy the &os; distribution to the local disk to make a stand-alone machine. - - Preparation - Currently, there are two ways to install &os;/&arch; on a new machine. By far the easier of the two is to install from CDROM; this method allows you to install &os; without any @@ -50,14 +47,7 @@ This file contains sparc64-specific installation instructions. you need to download (if any), as well as the steps required to do the installation. - - Downloading Required Files - - This section describes the files you will need for a - &os;/&arch; installation. The links in this document point to - the main &os; FTP server. Please use a mirror site instead if - possible. - + The URLs in this section are provisional and subject to change. Please see the archives of the &a.sparc; for the @@ -65,51 +55,7 @@ This file contains sparc64-specific installation instructions. when more permanent URLs have been determined. - - Required Files for CDROM Installation - - If you want to do a CDROM installation, an ISO - image with a snapshot of &os;/&arch; can be found at - . This file can be used - to create a bootable CDROM which contains everything - necessary to boot and load at least a minimal &os; - installation. - - - - - - - Required Files for Network Installation - - For a network installation, you will need several files. - First, you will need to download a &os;/&arch; loader for - &man.tftpd.8; to serve to your &arch; client. The loader - will use either TFTP or NFS to retrieve the &os; kernel from - the netboot server. There is a separate loader for each of - these methods (i.e. a loader for TFTP and a loader for NFS). - You should download one of the following files, as - appropriate: - - - - - - - A network installation also requires a kernel to be - served to the netboot client. A suitable kernel can be - found at - . - - - - Finally, you will need a &man.tar.1; archive which - contains the binaries and configuration files from the base - system. This file is available from . - - - + Getting to the PROM Prompt Most &arch; systems are set up to boot automatically from disk. To install &os;, you need to boot over the network or @@ -162,11 +108,19 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. - - - - Installing from CDROM + + + Preparing for a CDROM Installation + + If you want to do a CDROM installation, an ISO + image with a snapshot of &os;/&arch; can be found at + . This file can be used + to create a bootable CDROM which contains everything + necessary to boot and load at least a minimal &os; + installation. + + Place the CDROM into your drive, and break into the PROM as described above. On the PROM prompt, type boot cdrom. The system should boot into single-user mode @@ -175,10 +129,9 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. linkend="creating-disk-label"> and . - - Installing over the Network - - Configuring the Netboot Server + + + Preparing for a Network Installation A &os;/&arch; kernel is booted by having the firmware retrieve and execute a loader, @@ -189,7 +142,38 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. system. The loader can fetch a kernel using TFTP or NFS. All of this is covered in detail below. - + + Getting the Required Files + + For a network installation, you will need several files. + First, you will need to download a &os;/&arch; loader for + &man.tftpd.8; to serve to your &arch; client. The loader + will use either TFTP or NFS to retrieve the &os; kernel from + the netboot server. There is a separate loader for each of + these methods (i.e. a loader for TFTP and a loader for NFS). + You should download one of the following files, as + appropriate: + + + + + + + A network installation also requires a kernel to be + served to the netboot client. A suitable kernel can be + found at + . + + + + Finally, you will need a &man.tar.1; archive which + contains the binaries and configuration files from the base + system. This file is available from . + + + + rarpd You need to add the Ethernet address of your &os;/&arch; @@ -207,9 +191,10 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. interface that is on the same subnet as the &os;/&arch; system. - + - + + tftpd Activate &man.tftpd.8; in your &man.inetd.8; @@ -234,9 +219,10 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. allow you to see the file name you need to use for the loader. Error replies by the TFTP server are most often due to incorrect file permissions. - + - + + Setting up bootpd/dhcpd You can use either BOOTP or DHCP (both not both) to @@ -305,7 +291,6 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. a DNS entry or is associated with an address in /etc/hosts, the fixed-address specification can be omitted. - -- cgit v1.1