installation-i386.txt

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

     otherwise fail to find it.

   Now create a boot floppy as described in Section 1.3 and proceed with the
   installation.

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

  1.5.5 Installing over a Network using FTP or NFS

   After making the boot floppies as described in the first section, you can
   load the rest of the installation over a network using one of 3 types of
   connections: serial port, parallel port, or Ethernet.

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

    1.5.5.1 Serial Port

   SLIP support is rather primitive, and is limited primarily to hard-wired
   links, such as a serial cable running between two computers. The link must
   be hard-wired because the SLIP installation doesn't currently offer a
   dialing capability. If you need to dial out with a modem or otherwise
   dialog with the link before connecting to it, then I recommend that the
   PPP utility be used instead.

   If you're using PPP, make sure that you have your Internet Service
   Provider's IP address and DNS information handy as you'll need to know it
   fairly early in the installation process. You may also need to know your
   own IP address, though PPP supports dynamic address negotiation and may be
   able to pick up this information directly from your ISP if they support
   it.

   You will also need to know how to use the various ``AT commands'' for
   dialing out with your particular brand of modem as the PPP dialer provides
   only a very simple terminal emulator.

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

    1.5.5.2 Parallel Port

   If a hard-wired connection to another FreeBSD or Linux machine is
   available, you might also consider installing over a ``laplink'' style
   parallel port cable. The data rate over the parallel port is much higher
   than what is typically possible over a serial line (up to 50k/sec), thus
   resulting in a quicker installation. It's not typically necessary to use
   ``real'' IP addresses when using a point-to-point parallel cable in this
   way and you can generally just use RFC 1918 style addresses for the ends
   of the link (e.g. 10.0.0.1, 10.0.0.2, etc).

     Important: If you use a Linux machine rather than a FreeBSD machine as
     your PLIP peer, you will also have to specify link0 in the TCP/IP setup
     screen's ``extra options for ifconfig'' field in order to be compatible
     with Linux's slightly different PLIP protocol.

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

    1.5.5.3 Ethernet

   FreeBSD supports many common Ethernet cards; a table of supported cards is
   provided as part of the FreeBSD Hardware Notes (see HARDWARE.TXT in the
   Documentation menu on the boot floppy or the top level directory of the
   CDROM). If you are using one of the supported PCMCIA Ethernet cards, also
   be sure that it's plugged in before the laptop is powered on. FreeBSD does
   not, unfortunately, currently support ``hot insertion'' of PCMCIA cards
   during installation.

   You will also need to know your IP address on the network, the netmask
   value for your subnet and the name of your machine. Your system
   administrator can tell you which values are appropriate to your particular
   network setup. If you will be referring to other hosts by name rather than
   IP address, you'll also need a name server and possibly the address of a
   gateway (if you're using PPP, it's your provider's IP address) to use in
   talking to it. If you want to install by FTP via an HTTP proxy (see
   below), you will also need the proxy's address.

   If you do not know the answers to these questions then you should really
   probably talk to your system administrator first before trying this type
   of installation. Using a randomly chosen IP address or netmask on a live
   network is almost guaranteed not to work, and will probably result in a
   lecture from said system administrator.

   Once you have a network connection of some sort working, the installation
   can continue over NFS or FTP.

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

    1.5.5.4 NFS installation tips

   NFS installation is fairly straight-forward: Simply copy the FreeBSD
   distribution files you want onto a server somewhere and then point the NFS
   media selection at it.

   If this server supports only ``privileged port'' access (this is generally
   the default for Sun and Linux workstations), you will need to set this
   option in the Options menu before installation can proceed.

   If you have a poor quality Ethernet card which suffers from very slow
   transfer rates, you may also wish to toggle the appropriate Options flag.

   In order for NFS installation to work, the server must also support
   ``subdir mounts'', e.g. if your FreeBSD distribution directory lives on
   wiggy:/usr/archive/stuff/FreeBSD, then wiggy will have to allow the direct
   mounting of /usr/archive/stuff/FreeBSD, not just /usr or
   /usr/archive/stuff.

   In FreeBSD's /etc/exports file this is controlled by the -alldirs option.
   Other NFS servers may have different conventions. If you are getting
   Permission Denied messages from the server then it's likely that you don't
   have this properly enabled.

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

    1.5.5.5 FTP Installation tips

   FTP installation may be done from any mirror site containing a reasonably
   up-to-date version of FreeBSD. A full menu of reasonable choices for
   almost any location in the world is provided in the FTP site menu during
   installation.

   If you are installing from some other FTP site not listed in this menu, or
   you are having troubles getting your name server configured properly, you
   can also specify your own URL by selecting the ``URL'' choice in that
   menu. A URL can contain a hostname or an IP address, so something like the
   following would work in the absence of a name server:

     ftp://216.66.64.162/pub/FreeBSD/releases/i386/4.2-RELEASE

   There are three FTP installation modes you can use:

     * FTP: This method uses the standard ``Active'' mode for transfers, in
       which the server initiates a connection to the client. This will not
       work through most firewalls but will often work best with older FTP
       servers that do not support passive mode. If your connection hangs
       with passive mode, try this one.

     * FTP Passive: This sets the FTP "Passive" mode which prevents the
       server from opening connections to the client. This option is best for
       users to pass through firewalls that do not allow incoming connections
       on random port addresses.

     * FTP via an HTTP proxy: This option instructs FreeBSD to use HTTP to
       connect to a proxy for all FTP operations. The proxy will translate
       the requests and send them to the FTP server. This allows the user to
       pass through firewalls that do not allow FTP at all, but offer an HTTP
       proxy. You must specify the hostname of the proxy in addition to the
       FTP server.

       In the rare case that you have an FTP proxy that does not go through
       HTTP, you can specify the URL as something like:

     ftp://foo.bar.com:port/pub/FreeBSD

       In the URL above, port is the port number of the proxy FTP server.

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

  1.5.6 Tips for Serial Console Users

   If you'd like to install FreeBSD on a machine using just a serial port
   (e.g. you don't have or wish to use a VGA card), please follow these
   steps:

    1. Connect some sort of ANSI (vt100) compatible terminal or terminal
       emulation program to the COM1 port of the PC you are installing
       FreeBSD onto.

    2. Unplug the keyboard (yes, that's correct!) and then try to boot from
       floppy or the installation CDROM, depending on the type of
       installation media you have, with the keyboard unplugged.

    3. If you don't get any output on your serial console, plug the keyboard
       in again and wait for some beeps. If you are booting from the CDROM,
       proceed to step 5 as soon as you hear the beep.

    4. For a floppy boot, the first beep means to remove the kern.flp floppy
       and insert the mfsroot.flp floppy, after which you should press Enter
       and wait for another beep.

    5. Hit the space bar, then enter

     boot -h

       and you should now definitely be seeing everything on the serial port.
       If that still doesn't work, check your serial cabling as well as the
       settings on your terminal emulation program or actual terminal device.
       It should be set for 9600 baud, 8 bits, no parity.

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

1.6 Question and Answer Section for IA-32 Architecture Users

   1.6.1. Help! I have no space! Do I need to delete everything first?

   1.6.2. Can I use compressed DOS filesystems from FreeBSD?

   1.6.3. Can I mount my DOS extended partitions?

   1.6.4. Can I run DOS binaries under FreeBSD?

   1.6.1. Help! I have no space! Do I need to delete everything first?

   If your machine is already running DOS and has little or no free space
   available for FreeBSD's installation, all is not lost! You may find the
   FIPS utility, provided in the tools/ subdirectory on the FreeBSD CDROM or
   on the various FreeBSD ftp sites, to be quite useful.

   FIPS allows you to split an existing DOS partition into two pieces,
   preserving the original partition and allowing you to install onto the
   second free piece. You first ``defrag'' your DOS partition, using the DOS
   6.xx DEFRAG utility or the Norton Disk Tools, then run FIPS. It will
   prompt you for the rest of the information it needs. Afterwards, you can
   reboot and install FreeBSD on the new partition. Also note that FIPS will
   create the second partition as a ``clone'' of the first, so you'll
   actually see that you now have two DOS Primary partitions where you
   formerly had one. Don't be alarmed! You can simply delete the extra DOS
   Primary partition (making sure it's the right one by examining its size).

   FIPS does NOT currently work with NTFS style partitions. To split up such
   a partition, you will need a commercial product such as Partition Magic.
   Sorry, but this is just the breaks if you've got a Windows partition
   hogging your whole disk and you don't want to reinstall from scratch.

   1.6.2. Can I use compressed DOS filesystems from FreeBSD?

   No. If you are using a utility such as Stacker(tm) or DoubleSpace(tm),
   FreeBSD will only be able to use whatever portion of the filesystem you
   leave uncompressed. The rest of the filesystem will show up as one large
   file (the stacked/dblspaced file!). Do not remove that file as you will
   probably regret it greatly!

   It is probably better to create another uncompressed DOS extended
   partition and use this for communications between DOS and FreeBSD if such
   is your desire.

   1.6.3. Can I mount my DOS extended partitions?

   Yes. DOS extended partitions are mapped in at the end of the other
   ``slices'' in FreeBSD, e.g. your D: drive might be /dev/da0s5, your E:
   drive /dev/da0s6, and so on. This example assumes, of course, that your
   extended partition is on SCSI drive 0. For IDE drives, substitute ad for
   da appropriately. You otherwise mount extended partitions exactly like you
   would mount any other DOS drive, e.g.:

     # mount -t msdos /dev/da0s5 /dos_d

   1.6.4. Can I run DOS binaries under FreeBSD?

   Ongoing work with BSDI's doscmd(1) utility will suffice in many cases,
   though it still has some rough edges. If you're interested in working on
   this, please send mail to the FreeBSD-emulation mailing list
   <[e-mail]> and indicate that you're interested in
   joining this ongoing effort!

   The emulators/pcemu port/package in the FreeBSD Ports Collection which
   emulates an 8088 and enough BIOS services to run DOS text mode
   applications. It requires the X Window System (XFree86) to operate.

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

                             2 Distribution Format

   A typical FreeBSD distribution directory looks something like this:

     ERRATA.HTM      README.TXT      compat1x        dict            manpages
     ERRATA.TXT      RELNOTES.HTM    compat20        doc             packages
     HARDWARE.HTM    RELNOTES.TXT    compat21        docbook.css     ports
     HARDWARE.TXT    XF86336         compat22        floppies        proflibs
     INSTALL.HTM     bin             compat3x        games           src
     INSTALL.TXT     catpages        compat4x        info            tools
     README.HTM      cdrom.inf       crypto          kernel

   If you want to do a CDROM, FTP or NFS installation from this distribution
   directory, all you need to do is make the 1.44MB boot floppies from the
   floppies directory (see Section 1.3 for instructions on how to do this),
   boot them and follow the instructions. The rest of the data needed during
   the installation will be obtained automatically based on your selections.
   If you've never installed FreeBSD before, you also want to read the
   entirety of this document (the installation instructions) file.

   If you're trying to do some other type of installation or are merely
   curious about how a distribution is organized, what follows is a more
   thorough description of each item in more detail:

    1. The *.TXT and *.HTM files contain documentation (for example, this
       document is contained in both INSTALL.TXT and INSTALL.HTM) and should
       be read before starting an installation. The *.TXT files are plain
       text, while the *.HTM files are HTML files that can be read by almost
       any Web browser. Some distributions may contain documentation in other
       formats as well, such as PDF or PostScript.

    2. docbook.css is a Cascading Style Sheet (CSS) file used by some Web
       browsers for formatting the HTML documentation.

    3. The XF86336 directory contains the XFree86 project's 3.3.6 release and
       consists of a series of gzip'd tar files which contain each component
       of the XFree86 distribution.

    4. The bin, catpages, crypto, dict, doc, games, info, manpages, proflibs,
       and src directories contain the primary distribution components of
       FreeBSD itself and are split into smaller files for easy packing onto
       floppies (should that be necessary).

    5. The compat1x, compat20, compat21, compat22, compat3x, and compat4x
       directories contain distributions for compatibility with older
       releases and are distributed as single gzip'd tar files - they can be
       installed during release time or later by running their install.sh
       scripts.

    6. The floppies/ subdirectory contains the floppy installation images;
       further information on using them can be found in Section 1.3.

    7. The packages and ports directories contain the FreeBSD Packages and
       Ports Collections. Packages may be installed from the packages