installation-sparc64.txt

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

   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.

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

  1.3.5 Loading the Kernel

   With the daemons on the netboot server configured, the next step is to
   copy the kernel (obtained during the steps of Section 1.3.1) 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.)

   For both TFTP and NFS, the loader will use the parameters that it obtained
   via BOOTP or DHCP to find the kernel.

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

    1.3.5.1 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.

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

    1.3.5.2 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 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.

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

  1.3.6 Loading the Base System to the Netboot Server

   You must extract the base system distribution image to the NFS root
   directory specified either by the rp option in /etc/bootptab or the
   root-path option in dhcpd.conf. This directory tree will become the
   sparc64'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 sparc64 client's
   local disk.

   Using whatever editing tools you have on the netboot server, you probably
   will want to edit the sparc64's /etc/fstab and /etc/rc.conf and set a root
   password.

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

  1.3.7 Booting

   If all goes well, you can now boot the FreeBSD on your sparc64 machine by
   dropping into the PROM prompt as described in Section 1.1. 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 FreeBSD Ports Collection as
   net/ethereal) is usually helpful. The most common problems are related to
   bad file permissions. Also note that rarpd(8) will not answer to packets
   under some circumstances, refer to the manual page for details.

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

1.4 Creating a Disk Label

   The kernel supports the Sun disk label format, so you can label the disks
   you want to use with FreeBSD from Solaris.

   FreeBSD disk labels must currently be created by hand, as sysinstall(8) is
   not yet available on FreeBSD/sparc64. Please refer to the FreeBSD Handbook
   for more information about labels and special partitions.

   On FreeBSD/sparc64, a Sun compatibility label is embedded in the FreeBSD
   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.

   To create a disk label, the following procedure is the easiest:

    1. 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).

    2. 

       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:
     type: unknown
     disk: amnesiac
     label:
     flags:
     bytes/sector: 512
     sectors/track: 63
     tracks/cylinder: 16
     sectors/cylinder: 1008
     cylinders: 79780
     sectors/unit: 80418240
     rpm: 3600
     interleave: 1
     trackskew: 0
     cylinderskew: 0
     headswitch: 0           # milliseconds
     track-to-track seek: 0  # milliseconds
     drivedata: 0
    
     8 partitions:
     #        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 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.

         Warning: 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 device again. The editor will display the
       cylinders used by a particular partition on the right hand side of the
       output. If any of the partitions you defined (i.e. anything except
       partition c) shows an * next to it, the partition does NOT start or
       end on a cylinder boundary. You MUST fix these or your system will not
       work.

    3. Use disklabel -B if you want to make the disk bootable for
       FreeBSD/sparc64.

         Warning: 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 ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/loader-ufs.gz

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

1.5 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 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
   labels and file systems are also usable from FreeBSD.

     Warning: Do not run Solaris fsck on file systems modified by FreeBSD.
     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 Section 1.4.

   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 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.

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

1.6 Installing the Base System

   If you booted the kernel from the network, you downloaded a 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).

   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.

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

     This file, and other release-related documents, can be downloaded from
            ftp://ftp.FreeBSD.org/pub/FreeBSD/development/sparc64/.

     For questions about FreeBSD, read the documentation before contacting
                            <[e-mail]>.

  All users of FreeBSD 5-CURRENT should subscribe to the <[e-mail]>
                                 mailing list.

       For questions about this documentation, e-mail <[e-mail]>.