From 51bd1150a5d419c50eb4453bd0710d1f588c8b25 Mon Sep 17 00:00:00 2001 From: "Bruce A. Mah" Date: Thu, 14 Mar 2002 01:40:47 +0000 Subject: [PATCH] Whitespace, no content or markup changes. --- .../installation/sparc64/install.sgml | 186 ++++++++++-------- 1 file changed, 99 insertions(+), 87 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 6fda3ce61f47..615eae2f5008 100644 --- a/release/doc/en_US.ISO8859-1/installation/sparc64/install.sgml +++ b/release/doc/en_US.ISO8859-1/installation/sparc64/install.sgml @@ -70,9 +70,10 @@ This file contains sparc64-specific installation instructions. 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. + . This file can be used + to create a bootable CDROM which contains everything + necessary to boot and load at least a minimal &os; + installation. @@ -85,17 +86,19 @@ This file contains sparc64-specific installation instructions. 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: + 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 + A network installation also requires a kernel to be + served to the netboot client. A suitable kernel can be + found at . @@ -109,8 +112,9 @@ This file contains sparc64-specific installation instructions. 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 from - a CDROM, which requires you to break into the PROM (OpenFirmware). + disk. To install &os;, you need to boot over the network or + from a CDROM, which requires you to break into the PROM + (OpenFirmware). To do this, reboot the system, and wait until the boot message appears. It depends on the model, but should look about @@ -131,12 +135,12 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. Stop A + on the keyboard, or send a BREAK over the serial console (using for - example ~# in - &man.tip.1; or - &man.cu.1;) to get to the PROM prompt. It - looks like + example ~# in &man.tip.1; or &man.cu.1;) to + get to the PROM prompt. It looks like + ok or ok {0} @@ -151,19 +155,19 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. cdrom. The system should boot into single-user mode now, and you can create the disk label and install the base system archive as described in and . + linkend="creating-disk-label"> and . Installing over the Network Configuring the Netboot Server - A &os;/&arch; kernel is booted by having the firmware retrieve - and execute a loader, which in turn - fetches and executes the actual kernel. For this boot process, - you need to set up &man.rarpd.8; and - &man.tftpd.8; (for the firmware) and - &man.bootpd.8; (for the + A &os;/&arch; kernel is booted by having the firmware + retrieve and execute a loader, + which in turn fetches and executes the actual kernel. For + this boot process, you need to set up &man.rarpd.8; and + &man.tftpd.8; (for the firmware) and &man.bootpd.8; (for the loader) on another networked system. The loader can fetch a kernel using TFTP or NFS. All of this is covered in detail below. @@ -171,9 +175,9 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. rarpd - You need to add the Ethernet address of your &os;/&arch; system - to /etc/ethers on the netboot server. - An entry looks like: + You need to add the Ethernet address of your &os;/&arch; + system to /etc/ethers on the netboot + server. An entry looks like: 0:3:ba:b:92:d4 your.host.name @@ -182,36 +186,37 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. Make sure your.host.name is in /etc/hosts or has a valid DNS entry (or - use an IP address). Then, start &man.rarpd.8; on - a network interface that is on the same subnet as the - &os;/&arch; system. + use an IP address). Then, start &man.rarpd.8; on a network + interface that is on the same subnet as the &os;/&arch; + system. tftpd - Activate &man.tftpd.8; in your - &man.inetd.8; configuration by uncommenting - the following line in + Activate &man.tftpd.8; in your &man.inetd.8; + configuration by uncommenting the following line in /etc/inetd.conf: tftp dgram udp wait nobody /usr/libexec/tftpd tftpd /tftpboot Copy the unpacked loader to your - /tftpboot directory, and name it with the &os;/&arch; host's IP address in - upper-case hexadecimal notation without dots (or use appropriately-named symbolic links). For - example, your setup may look like this, for an IP address of + /tftpboot directory, and name it with + the &os;/&arch; host's IP address in upper-case hexadecimal + notation without dots (or use appropriately-named symbolic + links). For example, your setup may look like this, for an + IP address of 192.168.0.16: lrwx------ 1 tmm users 9 Jul 24 17:05 /tftpboot/C0A80010 -> boot/loader -rw-r--r-- 1 tmm users 1643021 Oct 20 18:04 /tftpboot/boot/loader If you have trouble booting, it is very helpful to use - &man.tcpdump.1; to monitor the TFTP - requests. This will 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. + &man.tcpdump.1; to monitor the TFTP requests. This will + 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. @@ -225,9 +230,10 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. Several DHCP servers are provided in the &os; Ports Collection. - If you are going to use - &man.bootpd.8;, create entries for your - &os;/&arch; system in the server's /etc/bootptab (see &man.bootptab.5; for more details): + If you are going to use &man.bootpd.8;, create entries + for your &os;/&arch; system in the server's + /etc/bootptab (see &man.bootptab.5; for + more details): .default:\ :bf="kernel":dn=local:ds=name-server-ip-address:\ @@ -240,11 +246,11 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. ha=sparc64-ethernet-address:ip=sparc64-ip-address:tc=.default The Ethernet address must be the same as the one in the - TFTP example above, but it is specified - hexadecimal notation without colons (for the example - above, this would be 0003ba0b92d4). NFS/TFTP specific - entries can be omitted if the given method is not used. The - strings given in the hd and + TFTP example above, but it is specified hexadecimal notation + without colons (for the example above, this would be + 0003ba0b92d4). NFS/TFTP specific entries + can be omitted if the given method is not used. The strings + given in the hd and bf properties are concatenated to give the boot file name. If your kernel is named differently or you use another directory, change these values as required. If you @@ -254,11 +260,12 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. in which the kernel will reside). The name of the host entry is conventionally the host name without the domain appended. - For a DHCP server, add an entry similar to the following to your dhcpd.conf file. An example entry for - ISC DHCP version 2 (available in - the &os; Ports Collection as net/isc-dhcp2) is shown - below: + For a DHCP server, add an entry similar to the following + to your dhcpd.conf file. An example + entry for ISC DHCP version 2 + (available in the &os; Ports Collection as net/isc-dhcp2) is shown + below: host name-of-entry { hardware ethernet sparc64-ethernet-address; @@ -271,13 +278,14 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. The filename option corresponds to the concatenation of hd and - bf in /etc/bootptab. The Ethernet address is + bf in + /etc/bootptab. The Ethernet address is specified in hexadecimal with colons, just like in the - &man.rarpd.8; example - above. options root-path corresponds to - rp in /etc/bootptab. If the name given in option - host-name is resolvable, i.e. has a DNS entry or is - associated with an address in + &man.rarpd.8; example above. options + root-path corresponds to rp in + /etc/bootptab. If the name given in + option host-name is resolvable, i.e. has + a DNS entry or is associated with an address in /etc/hosts, the fixed-address specification can be omitted. @@ -330,11 +338,11 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. rp option in /etc/bootptab or the root-path option in - dhcpd.conf. This directory tree will become - the &arch;'s root filesystem once the kernel is booted. - Besides providing a normal userland environment, it - also contains all of the necessary utilities for you to install - the distribution on the &arch; client's local disk. + dhcpd.conf. This directory tree will + become the &arch;'s root filesystem once the kernel is booted. + Besides providing a normal userland environment, it also + contains all of the necessary utilities for you to install the + distribution on the &arch; client's local disk. Using whatever editing tools you have on the netboot server, you probably will want to edit the &arch;'s @@ -346,22 +354,24 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. Booting - If all goes well, you can now boot the &os; on your &arch; machine - by dropping into the PROM prompt as described in . Now, just - type boot net and the system should - boot. Specifically, the loader is retrieved via TFTP, it - then does a BOOTP request and will proceed to load the - kernel (either using TFTP or NFS, depending on your choice of loader). Then, it should wait 10 seconds for user input and + If all goes well, you can now boot the &os; on your &arch; + machine by dropping into the PROM prompt as described in . Now, just type + boot net and the system should + boot. Specifically, the loader is retrieved via TFTP, it then + does a BOOTP request and will proceed to load the kernel + (either using TFTP or NFS, depending on your choice of + loader). Then, it should wait 10 seconds for user input and proceed to execute the kernel. If something does not work in between, and you suspect TFTP/NFS/BOOTP problems, Ethereal - (available in the &os; Ports Collection as - net/ethereal) - is usually helpful. The most common problems are related to bad file - permissions. Also note that &man.rarpd.8; - will not answer to packets under some circumstances, refer to - the manual page for details. + (available in the &os; Ports Collection as net/ethereal) is usually + helpful. The most common problems are related to bad file + permissions. Also note that &man.rarpd.8; will not answer to + packets under some circumstances, refer to the manual page for + details. @@ -373,7 +383,8 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. &os; disk labels must currently be created by hand, as &man.sysinstall.8; is not yet available on &os;/&arch;. Please - refer to the FreeBSD + refer to the FreeBSD Handbook for more information about labels and special partitions. @@ -432,8 +443,8 @@ drivedata: 0 sectors per cylinder as shown in the information that is presented in the editor (1008 in the example above). - When you are done, save your changes and quit the editor. This will cause the disk - label to be written. + When you are done, save your changes and quit the + editor. This will cause the disk label to be written. This procedure will overwrite any disk label that may be already present on the disk. Any existing filesystems on @@ -469,27 +480,28 @@ drivedata: 0 /var). The kernel contains support for Sun disklabels, so you can - use Solaris disks, which may even be prepared using newfs under - Solaris. NetBSD disk labels and file systems are also usable - from &os;. + use Solaris disks, which may even be prepared using + newfs under Solaris. NetBSD disk + labels and file systems are also usable from &os;. Do not run Solaris - fsck on file systems - modified by &os;. Doing so will damage the file + fsck on file systems modified by + &os;. Doing so will damage the file permissions. To create file systems and to install the base system, boot - from CDROM or via NFS and create a disk label as described - in . + from CDROM or via NFS and create a disk label as described in + . When booting the first time and you have not entered your root partition into /etc/fstab yet, you may - need to specify your root partition on the mountroot - prompt when booting (use a format like + need to specify your root partition on the mountroot prompt when + booting (use a format like ufs:<disk><partition>, i.e. leave the slice specification out). If the kernel does automatically - attempt to boot from another file system, press a key - other than Enter on the loader prompt: + attempt to boot from another file system, press a key other than + Enter on the loader + prompt: Hit [Enter] to boot immediately, or any other key for command prompt. Then, boot the kernel using boot -a -s, which will cause the kernel to ask you for the root partition and