installation-i386.txt

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

       directory by running the command:

     #/stand/sysinstall configPackages

       Packages can also be installed by feeding individual filenames in
       packages/ to the pkg_add(1) command.

       The Ports Collection may be installed like any other distribution and
       requires about 100MB unpacked. More information on the ports
       collection may be obtained from http://www.FreeBSD.org/ports/ or
       locally from /usr/share/doc/handbook if you've installed the doc
       distribution.

    8. Last of all, the tools directory contains various DOS tools for
       discovering disk geometries, installing boot managers and the like. It
       is purely optional and provided only for user convenience.

   A typical distribution directory (for example, the info distribution)
   looks like this internally:

     CHECKSUM.MD5    info.ab         info.ad         info.inf        install.sh
     info.aa         info.ac         info.ae         info.mtree

   The CHECKSUM.MD5 file contains MD5 signatures for each file, should data
   corruption be suspected, and is purely for reference. It is not used by
   the actual installation and does not need to be copied with the rest of
   the distribution files. The info.a* files are split, gzip'd tar files, the
   contents of which can be viewed by doing:

     # cat info.a* | tar tvzf -

   During installation, they are automatically concatenated and extracted by
   the installation procedure.

   The info.inf file is also necessary since it is read by the installation
   program in order to figure out how many pieces to look for when fetching
   and concatenating the distribution. When putting distributions onto
   floppies, the .inf file must occupy the first floppy of each distribution
   set!

   The info.mtree file is another non-essential file which is provided for
   user reference. It contains the MD5 signatures of the unpacked
   distribution files and can be later used with the mtree(8) program to
   verify the installation permissions and checksums against any possible
   modifications to the file. When used with the bin distribution, this can
   be an excellent way of detecting trojan horse attacks on your system.

   Finally, the install.sh file is for use by those who want to install the
   distribution after installation time. To install the info distribution
   from CDROM after a system was installed, for example, you'd do:

     # cd /cdrom/info
     # sh install.sh

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

                              3 Upgrading FreeBSD

   These instructions describe a procedure for doing a binary upgrade from an
   older version of FreeBSD.

     Warning: While the FreeBSD upgrade procedure does its best to safeguard
     against accidental loss of data, it is still more than possible to wipe
     out your entire disk with this installation! Please do not accept the
     final confirmation request unless you have adequately backed up any
     important data files.

     Important: These notes assume that you are using the version of
     sysinstall(8) supplied with the version of FreeBSD to which you intend
     to upgrade. Using a mismatched version of sysinstall(8) is almost
     guaranteed to cause problems and has been known to leave systems in an
     unusable state. The most commonly made mistake in this regard is the use
     of an old copy of sysinstall(8) from an existing installation to upgrade
     to a newer version of FreeBSD. This is not recommended.

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

3.1 Introduction

   The upgrade procedure replaces distributions selected by the user with
   those corresponding to the new FreeBSD release. It preserves standard
   system configuration data, as well as user data, installed packages and
   other software.

   Administrators contemplating an upgrade are encouraged to study this
   section in its entirety before commencing an upgrade. Failure to do so may
   result in a failed upgrade or loss of data.

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

  3.1.1 Upgrade Overview

   Upgrading of a distribution is performed by extracting the new version of
   the component over the top of the previous version. Files belonging to the
   old distribution are not deleted.

   System configuration is preserved by retaining and restoring the previous
   version of the following files:

   Xaccel.ini, XF86Config, adduser.conf, aliases, aliases.db, amd.map,
   crontab, csh.cshrc, csh.login, csh.logout, cvsupfile, dhclient.conf,
   disktab, dm.conf, dumpdates, exports, fbtab, fstab, ftpusers, gettytab,
   gnats, group, hosts, hosts.allow, hosts.equiv, hosts.lpd, inetd.conf,
   kerberosIV, localtime, login.access, login.conf, mail, mail.rc, make.conf,
   manpath.config, master.passwd, modems, motd, namedb, networks,
   newsyslog.conf, nsmb.conf, nsswitch.conf, pam.conf, passwd, periodic, ppp,
   printcap, profile, pwd.db, rc.conf, rc.conf.local, rc.firewall, rc.local,
   remote, resolv.conf, rmt, sendmail.cf, sendmail.cw, services, shells,
   skeykeys, spwd.db, ssh, syslog.conf, ttys, uucp

   The versions of these files which correspond to the new version are moved
   to /etc/upgrade/. The system administrator may peruse these new versions
   and merge components as desired. Note that many of these files are
   interdependent, and the best merge procedure is to copy all site-specific
   data from the current files into the new.

   During the upgrade procedure, the administrator is prompted for a location
   into which all files from /etc/ are saved. In the event that local
   modifications have been made to other files, they may be subsequently
   retrieved from this location.

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

3.2 Procedure

   This section details the upgrade procedure. Particular attention is given
   to items which substantially differ from a normal installation.

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

  3.2.1 Backup

   User data and system configuration should be backed up before upgrading.
   While the upgrade procedure does its best to prevent accidental mistakes,
   it is possible to partially or completely destroy data and configuration
   information.

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

  3.2.2 Mount Filesystems

   The disklabel editor is entered with the nominated disk's filesystem
   devices listed. Prior to commencing the upgrade, the administrator should
   make a note of the device names and corresponding mountpoints. These
   mountpoints should be entered here. Do notset the ``newfs flag'' for any
   filesystems, as this will cause data loss.

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

  3.2.3 Select Distributions

   When selecting distributions, there are no constraints on which must be
   selected. As a general rule, the bin distribution should be selected for
   an update, and the man distribution if manpages are already installed.
   Other distributions may be selected beyond those originally installed if
   the administrator wishes to add additional functionality.

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

  3.2.4 After Installation

   Once the installation procedure has completed, the administrator is
   prompted to examine the new configuration files. At this point, checks
   should be made to ensure that the system configuration is valid. In
   particular, the /etc/rc.conf and /etc/fstab files should be checked.

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

3.3 Upgrading from Source Code

   Those interested in an upgrade method that allows more flexibility and
   sophistication should take a look at The Cutting Edge in the FreeBSD
   Handbook. This procedure involves rebuilding all of FreeBSD from source
   code. It requires reliable network connectivity, extra disk space, and
   time, but has advantages for networks and other more complex
   installations. This is roughly the same procedure as is used for track the
   -STABLE or -CURRENT development branches.

   /usr/src/UPDATING contains important information on updating a FreeBSD
   system from source code. It lists various issues resulting from changes in
   FreeBSD that may affect an upgrade.

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

                               4 Troubleshooting

4.1 Repairing an Existing FreeBSD Installation

   FreeBSD features a ``Fixit'' option in the top menu of the boot floppy. To
   use it, you will also need either a fixit.flp image floppy, generated in
   the same fashion as the boot floppy, or the ``live filesystem'' CDROM;
   typically the second CDROM in a multi-disc FreeBSD distribution.

   To invoke fixit, simply boot the kern.flp floppy, choose the ``Fixit''
   item and insert the fixit floppy or CDROM when asked. You will then be
   placed into a shell with a wide variety of commands available (in the
   /stand and /mnt2/stand directories) for checking, repairing and examining
   file systems and their contents. Some UNIX administration experience is
   required to use the fixit option.

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

4.2 Common Installation Problems, Q&A

   4.2.1. I go to boot from the hard disk for the first time after installing
   FreeBSD, the kernel loads and probes my hardware, but stops with messages
   like:

   4.2.2. I go to boot from the hard disk for the first time after installing
   FreeBSD, but the Boot Manager prompt just prints F? at the boot menu each
   time but the boot won't go any further.

   4.2.1. I go to boot from the hard disk for the first time after installing
   FreeBSD, the kernel loads and probes my hardware, but stops with messages
   like:

     changing root device to wd1s1a panic: cannot mount root

   What is wrong? What can I do?

   What is this bios_drive:interface(unit,partition)kernel_name thing that is
   displayed with the boot help?

   There is a longstanding problem in the case where the boot disk is not the
   first disk in the system. The BIOS uses a different numbering scheme to
   FreeBSD, and working out which numbers correspond to which is difficult to
   get right.

   In the case where the boot disk is not the first disk in the system,
   FreeBSD can need some help finding it. There are two common situations
   here, and in both of these cases, you need to tell FreeBSD where the root
   filesystem is. You do this by specifying the BIOS disk number, the disk
   type and the FreeBSD disk number for that type.

   The first situation is where you have two IDE disks, each configured as
   the master on their respective IDE busses, and wish to boot FreeBSD from
   the second disk. The BIOS sees these as disk 0 and disk 1, while FreeBSD
   sees them as wd0 and wd2.

   FreeBSD is on BIOS disk 1, of type wd and the FreeBSD disk number is 2, so
   you would say:

     1:wd(2,a)kernel

   Note that if you have a slave on the primary bus, the above is not
   necessary (and is effectively wrong).

   The second situation involves booting from a SCSI disk when you have one
   or more IDE disks in the system. In this case, the FreeBSD disk number is
   lower than the BIOS disk number. If you have two IDE disks as well as the
   SCSI disk, the SCSI disk is BIOS disk 2, type da and FreeBSD disk number
   0, so you would say:

     2:da(0,a)kernel

   To tell FreeBSD that you want to boot from BIOS disk 2, which is the first
   SCSI disk in the system. If you only had one IDE disk, you would use '1:'
   instead.

   Once you have determined the correct values to use, you can put the
   command exactly as you would have typed it in the /boot.config file using
   a standard text editor. Unless instructed otherwise, FreeBSD will use the
   contents of this file as the default response to the boot: prompt.

   4.2.2. I go to boot from the hard disk for the first time after installing
   FreeBSD, but the Boot Manager prompt just prints F? at the boot menu each
   time but the boot won't go any further.

   The hard disk geometry was set incorrectly in the Partition editor when
   you installed FreeBSD. Go back into the partition editor and specify the
   actual geometry of your hard disk. You must reinstall FreeBSD again from
   the beginning with the correct geometry.

   If you are failing entirely in figuring out the correct geometry for your
   machine, here's a tip: Install a small DOS partition at the beginning of
   the disk and install FreeBSD after that. The install program will see the
   DOS partition and try to infer the correct geometry from it, which usually
   works.

   The following tip is no longer recommended, but is left here for
   reference:

     If you are setting up a truly dedicated FreeBSD server or workstation
     where you don't care for (future) compatibility with DOS, Linux or
     another operating system, you've also got the option to use the entire
     disk (`A' in the partition editor), selecting the non-standard option
     where FreeBSD occupies the entire disk from the very first to the very
     last sector. This will leave all geometry considerations aside, but is
     somewhat limiting unless you're never going to run anything other than
     FreeBSD on a disk.

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

4.3 Known Hardware Problems, Q&A

     Note: Please send hardware tips for this section to Jordan K. Hubbard
     <[e-mail]>.

   4.3.1. The mcd(4) driver keeps thinking that it has found a device and
   this stops my Intel EtherExpress card from working.

   4.3.2. FreeBSD claims to support the 3Com PCMCIA card, but my card isn't
   recognized when it's plugged into my laptop.

   4.3.3. FreeBSD finds my PCMCIA network card, but no packets appear to be
   sent even though it claims to be working.

   4.3.4. The system finds my ed(4) network card, but I keep getting device
   timeout errors.

   4.3.5. I have a Matsushita/Panasonic drive but it isn't recognized by the
   system.