installation-sparc64.txt

标准模板库自修教程与参考手册 STL进行C++编程.我的代码发完了

             FreeBSD/sparc64 5.0-CURRENT Installation Instructions

  The FreeBSD Project

   Copyright (c) 2000, 2001, 2002 by The FreeBSD Documentation Project

     ----------------------------------------------------------------------

     This article gives some brief instructions on installing FreeBSD/sparc64
     5.0-CURRENT. Please keep in mind that this port is a work in progress,
     and as such, the installation procedure is much more involved than for
     FreeBSD/i386 or FreeBSD/alpha.

     ----------------------------------------------------------------------

                              1 Installing FreeBSD

   This text describes how to install and boot the sparc64 port. Users of
   this port are encouraged to subscribe to the FreeBSD SPARC porting mailing
   list <[e-mail]>.

     Warning: 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 FreeBSD/i386 or FreeBSD/alpha, there is no version of sysinstall(8)
   for FreeBSD/sparc64. The installation procedure consists of loading a
   kernel (either from CDROM or the network) onto the sparc64 machine, with a
   root filesystem on CDROM or exported via NFS. The utilities on the root
   filesystem can then be used to partition the local disk on the sparc64
   machine and optionally to copy the FreeBSD distribution to the local disk
   to make a stand-alone machine.

   Currently, there are two ways to install FreeBSD/sparc64 on a new machine.
   By far the easier of the two is to install from CDROM; this method allows
   you to install FreeBSD 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 FreeBSD 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.

     Important: The URLs in this section are provisional and subject to
     change. Please see the archives of the FreeBSD SPARC porting mailing
     list <[e-mail]> for the most recent locations of files.
     This notice will be removed when more permanent URLs have been
     determined.

     ----------------------------------------------------------------------

1.1 Getting to the PROM Prompt

   Most sparc64 systems are set up to boot automatically from disk. To
   install FreeBSD, 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 tip(1) or cu(1)) to get to the PROM prompt. It
   looks like this:

     ok         (1)
     ok {0}     (2)

   (1)
           This is the prompt used on systems with just one CPU.
   (2)
           This is the prompt used on SMP systems, the digit indicates the
           number of the active CPU.

     ----------------------------------------------------------------------

1.2 Preparing for a CDROM Installation

   If you want to do a CDROM installation, an ISO image with a snapshot of
   FreeBSD/sparc64 can be found at
   ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/. This file can be
   used to create a bootable CDROM which contains everything necessary to
   boot and load at least a minimal FreeBSD 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 now, and you can create the disk label and install the
   base system archive as described in Section 1.4 and Section 1.5.

     ----------------------------------------------------------------------

1.3 Preparing for a Network Installation

   A FreeBSD/sparc64 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 rarpd(8) and tftpd(8) (for the
   firmware) and 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.

     ----------------------------------------------------------------------

  1.3.1 Getting the Required Files

   For a network installation, you will need several files. First, you will
   need to download a FreeBSD/sparc64 loader for tftpd(8) to serve to your
   sparc64 client. The loader will use either TFTP or NFS to retrieve the
   FreeBSD 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:

     * ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-tftp.gz

     * ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-nfs.gz

   A network installation also requires a kernel to be served to the netboot
   client. A suitable kernel can be found at
   ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/.

   Finally, you will need a tar(1) archive which contains the binaries and
   configuration files from the base system. This file is available from
   ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/distrib.tar.gz.

     ----------------------------------------------------------------------

  1.3.2 rarpd

   You need to add the Ethernet address of your FreeBSD/sparc64 system to
   /etc/ethers on the netboot server. An entry looks like:

     0:3:ba:b:92:d4 your.host.name

   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 rarpd(8) on a network interface that is on the
   same subnet as the FreeBSD/sparc64 system.

     ----------------------------------------------------------------------

  1.3.3 tftpd

   Activate tftpd(8) in your 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
   FreeBSD/sparc64 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 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.

     ----------------------------------------------------------------------

  1.3.4 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 FreeBSD machine as a netboot server, the BOOTP functionality
   is provided by bootpd(8), which is a part of the FreeBSD base system.
   Several DHCP servers are provided in the FreeBSD Ports Collection.

   If you are going to use bootpd(8), create entries for your FreeBSD/sparc64
   system in the server's /etc/bootptab (see 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":\
       :rp="tftp-server-ip-address:nfs-root-directory":\
       :sm=ip-netmask
    
     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
   FreeBSD 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;
       always-reply-rfc1048 on;
       filename "kernel";
       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 rarpd(8) example above. options root-path