From 431577d47c148bc21bb3bb402bf92354832c65e1 Mon Sep 17 00:00:00 2001 From: ue Date: Thu, 18 Apr 2002 01:27:19 +0000 Subject: Whitespace fix after the restructuring, no content changes --- .../installation/sparc64/install.sgml | 658 +++++++++++---------- 1 file changed, 331 insertions(+), 327 deletions(-) (limited to 'release/doc') 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 1c71ded..6af1820 100644 --- a/release/doc/en_US.ISO8859-1/installation/sparc64/install.sgml +++ b/release/doc/en_US.ISO8859-1/installation/sparc64/install.sgml @@ -9,16 +9,18 @@ This file contains sparc64-specific installation instructions. Installing &os; - This text describes how to install and boot the &arch; - port. Users of this port are encouraged to subscribe to the + This text describes how to install and boot the &arch; port. + Users of this port are encouraged to subscribe to the &a.sparc;. - The kernel and userland binaries mentioned below are - highly experimental (for example, the kernel contains some ATA - changes and EEPROM handling code which could potentially be - dangerous). Unless you know what you are doing and are willing to - cope with any damage that might arise, you should probably not be - trying this. + + The kernel and userland binaries mentioned below are highly + experimental (for example, the kernel contains some ATA changes + and EEPROM handling code which could potentially be dangerous). + Unless you know what you are doing and are willing to cope with + any damage that might arise, you should probably not be trying + this. + Unlike &os;/i386 or &os;/alpha, there is no version of &man.sysinstall.8; for &os;/&arch;. The installation procedure @@ -29,100 +31,94 @@ This file contains sparc64-specific installation instructions. optionally to copy the &os; distribution to the local disk to make a stand-alone machine. - 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 - dependencies on any other computers. + 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 dependencies on + any other computers. - If installing from CDROM is impossible or undesirable, the - alternative is to install over the network. This requires - another machine, suitably configured, to serve the boot loader, - kernel, and root file system to the new machine, via a - combination of RARP, TFTP, and either BOOTP or DHCP. This - netboot server can be another &os; machine, but is not required - to be. + If installing from CDROM is impossible or undesirable, the + alternative is to install over the network. This requires another + machine, suitably configured, to serve the boot loader, kernel, + and root file system to the new machine, via a combination of + RARP, TFTP, and either BOOTP or DHCP. This netboot server can be + another &os; machine, but is not required to be. - You will need to decide which of these methods you want to - use for installation, as this will determine the set of files - you need to download (if any), as well as the steps required to - do the installation. + You will need to decide which of these methods you want to use + for installation, as this will determine the set of files you need + to download (if any), as well as the steps required to do the + installation. - - The URLs in this section are provisional and subject to - change. Please see the archives of the &a.sparc; for the - most recent locations of files. This notice will be removed - when more permanent URLs have been determined. - - - - 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). - - To do this, reboot the system, and wait until the boot - message appears. It depends on the model, but should look about - like: - Sun Blade 100 (UltraSPARC-IIe), Keyboard Present + + + The URLs in this section are provisional and subject to + change. Please see the archives of the &a.sparc; for the most + recent locations of files. This notice will be removed when + more permanent URLs have been determined. + + + + 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). + + To do this, reboot the system, and wait until the boot + message appears. It depends on the model, but should look about + like: + + Sun Blade 100 (UltraSPARC-IIe), Keyboard Present Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved. OpenBoot 4.2, 128 MB memory installed, Serial #51090132. Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. - If your system proceeds to boot from disk at this point, - you need to press - - L1 - A - - or - - 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 this: - - - - - - - - ok -ok {0} - - - - This is the prompt used on systems with just - one CPU. - - - - This is the prompt used on SMP systems, the digit - indicates the number of the active CPU. - - - + If your system proceeds to boot from disk at this point, you + need to press L1A + or StopA + 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 this: + + + + + + + + ok +ok {0} + + + + This is the prompt used on systems with just one + CPU. + + + + This is the prompt used on SMP systems, the digit + indicates the number of the active CPU. + + + 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. + 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 + described above. On the PROM prompt, type boot 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 Preparing for a Network Installation - 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. - - - 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 - . - + 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. + + + 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 . - + 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; - system to /etc/ethers on the netboot - server. An entry looks like: + + rarpd - 0:3:ba:b:92:d4 your.host.name + You need to add the Ethernet address of your &os;/&arch; + system to /etc/ethers on the netboot + server. An entry looks like: - The Ethernet address is usually displayed in the boot - message. + 0:3:ba:b:92:d4 your.host.name - 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. + The Ethernet address is usually displayed in the boot + message. - + 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. + - - tftpd + + tftpd - Activate &man.tftpd.8; in your &man.inetd.8; - configuration by uncommenting the following line in - /etc/inetd.conf: + 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 + 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 - 192.168.0.16: + 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 192.168.0.16: - lrwx------ 1 tmm users 9 Jul 24 17:05 /tftpboot/C0A80010 -> boot/loader + 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. - + 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. + - - Setting up bootpd/dhcpd - - You can use either BOOTP or DHCP (both not both) to - provide some parameters to the boot loader, such as a - machine's IP address. If you are using another &os; machine - as a netboot server, the BOOTP functionality is provided by - &man.bootpd.8;, which is a part of the &os; base system. - 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): - - .default:\ + + Setting up bootpd/dhcpd + + You can use either BOOTP or DHCP (both not both) to + provide some parameters to the boot loader, such as a + machine's IP address. If you are using another &os; machine + as a netboot server, the BOOTP functionality is provided by + &man.bootpd.8;, which is a part of the &os; base system. + 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): + + .default:\ :bf="kernel":dn=local:ds=name-server-ip-address:\ :gw=gateway-ip-address:ht=ether:hd="/tftpboot/boot/kernel":hn:\ :sa="tftp-server-ip-address":\ @@ -248,29 +247,30 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. name-of-the-entry:\ 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 - 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 - are booting using NFS, remove the bf - and hd settings (or change them to - specify the directory and file inside the NFS root hierarchy - 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: - - host name-of-entry { + 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 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 are booting using + NFS, remove the bf and + hd settings (or change them to specify the + directory and file inside the NFS root hierarchy 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: + + host name-of-entry { hardware ethernet sparc64-ethernet-address; option host-name "sparc64-fully-qualified-domain-name"; fixed-address sparc64-ip-address; @@ -279,18 +279,18 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. option root-path "tftp-server-ip-address:nfs-root-directory"; } - The filename option corresponds to - the concatenation of hd and - 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 - /etc/hosts, the - fixed-address specification can be omitted. + The filename option corresponds to the + concatenation of hd and + 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 /etc/hosts, the + fixed-address specification can be + omitted. @@ -300,35 +300,35 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. next step is to copy the kernel (obtained during the steps of ) to an appropriate directory. There are two ways of retrieving a kernel over the network: - TFTP and NFS. (You specified one of these two alternatives - by picking a loader.) + TFTP and NFS. (You specified one of these two alternatives by + picking a loader.) For both TFTP and NFS, the loader will use the parameters that it obtained via BOOTP or DHCP to find the kernel. - Loading the Kernel over TFTP + Loading the Kernel over TFTP - Place the kernel in the directory you specified using - bf and hd in the - /etc/bootptab or the - filename parameter to - dhcpd.conf. + Place the kernel in the directory you specified using + bf and hd in the + /etc/bootptab or the + filename parameter to + dhcpd.conf. - Loading the Kernel over NFS - - Export the directory that was specified by the - rp property in - /etc/bootptab or the - root-path parameter in - dhcpd.conf (see &man.exports.5;). - Copy the kernel to the directory you specified using - bf and hd in the - /etc/bootptab or the - filename parameter to - dhcpd.conf. + Loading the Kernel over NFS + + Export the directory that was specified by the + rp property in + /etc/bootptab or the + root-path parameter in + dhcpd.conf (see &man.exports.5;). Copy + the kernel to the directory you specified using + bf and hd in the + /etc/bootptab or the + filename parameter to + dhcpd.conf. @@ -347,33 +347,33 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. 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 - /etc/fstab and - /etc/rc.conf and set a - root password. + server, you probably will want to edit the &arch;'s + /etc/fstab and + /etc/rc.conf and set a + root password. 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 - proceed to execute the kernel. + 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. + 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. @@ -384,14 +384,14 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. label the disks you want to use with &os; from Solaris. &os; disk labels must currently be created by hand, as - &man.sysinstall.8; is not yet available on &os;/&arch;. Please + &man.sysinstall.8; is not yet available on &os;/&arch;. Please refer to the FreeBSD Handbook for more information about labels and special partitions. On &os;/&arch;, a Sun compatibility label is embedded in the - &os; label; this is needed for the PROM to boot from disk. This + &os; label; this is needed for the PROM to boot from disk. This imposes an additional restriction on the disk label format: partitions are required to start on a cylinder boundary. @@ -400,22 +400,21 @@ Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4. - Run -disklabel -w -r device auto - to create a basic disk label. The third argument you need - specify here is just the name of the device, not the complete - path to the device node (e.g. ad0 for - the first ATA disk). + Run disklabel -w -r + device auto to create a + basic disk label. The third argument you need specify here + is just the name of the device, not the complete path to the + device node (e.g. ad0 for the first + ATA disk). - - Use -disklabel -e device - to open an editor in which you can edit the disk - label. The information presented to you should look like: + Use disklabel -e + device to open an + editor in which you can edit the disk label. The + information presented to you should look like: -# /dev/ad6c: + # /dev/ad6c: type: unknown disk: amnesiac label: @@ -438,24 +437,28 @@ drivedata: 0 # size offset fstype [fsize bsize bps/cpg] c: 80418240 0 unused 0 0 # (Cyl. 0 - 79779) - You can now add new partitions in the same format as the already - present line. Using * in the offset field makes the procedure - easier; please refer to the &man.disklabel.8; manual page for more - information. - - To make sure the restriction mentioned above is met, the - size of each partition must be a multiple of the number of - 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. - - This procedure will overwrite any disk label that - may be already present on the disk. Any existing filesystems on - this disk must have their respective partition entries in the - old and new label match exactly, or they - will be lost. + You can now add new partitions in the same format as the + already present line. Using * in the + offset field makes the procedure easier; please refer to the + &man.disklabel.8; manual page for more information. + + To make sure the restriction mentioned above is met, the + size of each partition must be a multiple of the number of + 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.i 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 this disk must have their respective partition entries + in the old and new label match + exactly, or they will be + lost. + If you want to double-check that your partitions end on cylinder boundaries, run disklabel -e @@ -470,44 +473,45 @@ drivedata: 0 - Use disklabel -B if you want to make the - disk bootable for &os;/&arch;. - - Using disklabel -B on a disk - will overwrite any preexisting boot block, so it will likely - render any other operating system installed on the same disk - unbootable. - - If you do not want to overwrite the boot block, it is - possible to load the loader via TFTP - as described above, but have it boot the kernel from disk. This - requires a special loader binary, which is available at - - + Use disklabel -B if you want to make + the disk bootable for &os;/&arch;. + + + Using disklabel -B on a disk will + overwrite any preexisting boot block, so it will likely + render any other operating system installed on the same + disk unbootable. + + + If you do not want to overwrite the boot block, it is + possible to load the loader via + TFTP as described above, but have it boot the kernel from + disk. This requires a special loader binary, which is + available at - - + Creating the Root Fileystem - If you want to boot from a local disk, you will need - to create a root file system to hold the base system binaries and + If you want to boot from a local disk, you will need to + create a root file system to hold the base system binaries and configuration files (and optionally other file systems mounted in places such as /usr and /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 + 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 - permissions. + + Do not run Solaris + 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 @@ -517,23 +521,24 @@ drivedata: 0 root partition into /etc/fstab yet, you may need to specify your root partition on the mountroot prompt when booting (use a format like - ufs:diskpartition, 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: -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 - then boot into single-user mode. Once the root file system has - been entered into /etc/fstab, it should be - automatically mounted as / on the next + ufs:diskpartition, + 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: + + 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 then boot into single-user mode. Once the root file system + has been entered into /etc/fstab, it should + be automatically mounted as / on the next boot. If you are booting over the network (via NFS), the above BOOTP entries should suffice to have the kernel find and mount the root filesystem via NFS. - @@ -541,20 +546,19 @@ drivedata: 0 If you booted the kernel from the network, you downloaded a &man.tar.1; archive with the base system and exported it from - the netboot server via NFS. You can unpack this same archive - to your local disk to create a stand-alone system (remember to - copy the kernel over as well). + the netboot server via NFS. You can unpack this same archive to + your local disk to create a stand-alone system (remember to copy + the kernel over as well). If you booted from CDROM, the same archive is available in /root/ on the CDROM. - Before booting the system stand-alone, you will want to edit - /etc/fstab and - /etc/rc.conf and set a - root password. - - Note that some programs from the base system may not be - present in the archive, or may not work properly yet. - + Before booting the system stand-alone, you will want to edit + /etc/fstab and + /etc/rc.conf and set a + root password. + Note that some programs from the base system may not be + present in the archive, or may not work properly yet. + -- cgit v1.1