diff options
Diffstat (limited to 'en_US.ISO8859-1/books/handbook/install/chapter.sgml')
-rw-r--r-- | en_US.ISO8859-1/books/handbook/install/chapter.sgml | 1673 |
1 files changed, 0 insertions, 1673 deletions
diff --git a/en_US.ISO8859-1/books/handbook/install/chapter.sgml b/en_US.ISO8859-1/books/handbook/install/chapter.sgml deleted file mode 100644 index 0702dd8aae..0000000000 --- a/en_US.ISO8859-1/books/handbook/install/chapter.sgml +++ /dev/null @@ -1,1673 +0,0 @@ -<!-- - The FreeBSD Documentation Project - - $FreeBSD: doc/en_US.ISO_8859-1/books/handbook/install/chapter.sgml,v 1.44 2000/06/14 00:47:26 jim Exp $ ---> - -<chapter id="install"> - <title>Installing FreeBSD</title> - - <para><emphasis>Restructured, updated, and parts rewritten by &a.jim;, - January 2000.</emphasis></para> - - <sect1> - <title>Synopsis</title> - - <para>The following chapter will attempt to guide you through the - installation of FreeBSD on your system. It can be installed through a - variety of methods, including anonymous FTP (assuming you have - network connectivity via modem or local network), CDROM, floppy - disk, tape, an MS-DOS partition, or even NFS.</para> - - <para>No matter which method you choose, you will need to get started - by creating the <emphasis>installation disks</emphasis> as described - in the <link linkend="install-floppies">next section</link>. - Booting into the FreeBSD installer, even if you are not planning on - installing FreeBSD right away, will provide important information - about compatibility with your hardware. This information may - dictate which installation options are even possible for you. It - can also provide clues early-on in the process to potential problems - you may come across later.</para> - - <para>If you plan to install FreeBSD via anonymous FTP, the only - things you will need are the <link - linkend="install-floppies">installation floppies</link>. The - installation program itself will handle anything else that is - required.</para> - - <para>For more information about obtaining FreeBSD, see the <link - linkend="mirrors">Obtaining FreeBSD</link> section of the - Appendix.</para> - - <para>By now, you are probably wondering what exactly it is you need - to do. Continue on to the installation guide.</para> - </sect1> - - <sect1 id="install-guide"> - <title>Installation Guide</title> - - <para>The following sections will guide you through preparing for and - actually installing FreeBSD. If you find something missing, please - let us know about it by sending email to the &a.doc;.</para> - - <sect2 id="install-prepare"> - <title>Preparing for the Installation</title> - - <para>There are various things you should do in preparation for the - installation. The following describes what needs to be done prior to - each type of installation.</para> - - <para>The first thing to do is to make sure your hardware is - supported by FreeBSD. The list of <link - linkend="install-hw">supported hardware</link> should - come in handy here. ;-) It would also be a good idea to make a - list of any <quote>special</quote> cards you have installed, - such as SCSI controllers, ethernet cards, sound cards, etc.. - The list should include their IRQs and IO port addresses.</para> - - <sect3 id="install-floppies"> - <title>Creating the Boot Floppies</title> - - <para>Please read the <ulink - url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/README.TXT">installation - boot image information</ulink> before proceeding. To make the - installation boot disks from the image files, do the - following:</para> - - <para>Download the image - files. These can be retrieved from the <ulink - url="ftp://ftp.FreeBSD.org/pub/FreeBSD/releases/i386/&rel.current;-RELEASE/floppies/">floppies directory</ulink> - of the FreeBSD FTP site or your local mirror.</para> - - <itemizedlist> - <listitem> - <para>If you are installing from an MS-DOS partition, - download the <ulink - url="ftp://ftp.FreeBSD.org/pub/FreeBSD/tools/fdimage.exe">fdimage.exe</ulink> - program or get it from <filename>tools\fdimage.exe</filename> - on the CDROM and then run it like so:</para> - - <screen><prompt>E:\></prompt> <userinput>tools\fdimage floppies\kern.flp a:</userinput></screen> - - <para>The <emphasis>fdimage</emphasis> program will format - the <devicename>A:</devicename> drive and then copy - <filename>kern.flp</filename> to it (assuming that you are - at the top level of a FreeBSD distribution and the floppy - images live in a <filename>floppies</filename> - subdirectory, which is typically the case).</para> - </listitem> - - <listitem> - <para>If you are using a UNIX-based system to create the - boot floppies, do the following:</para> - - <screen>&prompt.root; <userinput>dd if=kern.flp of=<replaceable>disk_device</replaceable></userinput></screen> - - <para><replaceable>disk_device</replaceable> is the - <filename>/dev</filename> entry for the floppy drive. On - FreeBSD, this is <filename>/dev/rfd0</filename> for the - <devicename>A:</devicename> drive and - <filename>/dev/rfd1</filename> for the - <devicename>B:</devicename> drive.</para> - </listitem> - </itemizedlist> - - <para>With the <filename>kern.flp</filename> disk in your floppy - drive, reboot your computer. After a couple of minutes - (while the kernel loads from the floppy), you - will be prompted to insert - the <filename>mfsroot.flp</filename>, after which the - installation will proceed normally.</para> - </sect3> - - <sect3 id="install-cdrom"> - <title>Before Installing from CDROM</title> - - <para>If your CDROM is of an unsupported type, please skip ahead - to the <link linkend="install-msdos">MS-DOS Preparation</link> - section.</para> - - <para>There is not a whole lot of preparation needed if you are - installing from one of <ulink - url="http://www.wccdrom.com/">Walnut Creek CDROM's</ulink> - FreeBSD CDROMs (other CDROM distributions may work as well, - though we cannot say for certain as we have no hand or say in - how they created). You can either boot into the CD installation - directly from DOS using the <filename>install.bat</filename> or - you can make floppies with the <filename>makeflp.bat</filename> - command.</para> - - <para>If the CD has El Torito boot support and your system - supports booting directly from the CDROM drive (many older - systems do <emphasis>NOT</emphasis>), simply insert the first - CD of the set into the drive and reboot your system. You - will be put into the installation menu directly from the CD.</para> - - <para>If you are installing from an MS-DOS partition and have - the proper drivers to access your CD, run the - <filename>install.bat</filename> script provided on the CDROM. - This will attempt to boot the FreeBSD installation directly - from DOS.</para> - - <note> - <para>You must do this from actual DOS (i.e., boot in DOS - mode) and not from a DOS window under Windows.</para> - </note> - - <para>For the easiest interface of all (from DOS), type - <command>view</command>. This will bring up a DOS menu utility - that leads you through all of the available options.</para> - - <para>If you are creating the boot floppies from a UNIX machine, - see the <link linkend="install-floppies">Creating the Boot - Floppies</link> section of this guide for examples.</para> - - <para>Once you have booted from DOS or floppy, you should then be - able to select CDROM as the media type during the install - process and load the entire distribution from CDROM. No other - types of installation media should be required.</para> - - <para>After your system is fully installed and you have rebooted - (from the hard disk), you can mount the CDROM at any time by - typing:</para> - - <screen>&prompt.root; <userinput>mount /cdrom</userinput></screen> - - <para>Before removing the CD from the drive again, you must first - unmount it. This is done with the following command:</para> - - <screen>&prompt.root; <userinput>umount /cdrom</userinput></screen> - - <para>Do not just remove it from the drive!</para> - - <note> - <para>Before invoking the installation, be sure that the CDROM - is in the drive so that the install probe can find it. This - is also true if you wish the CDROM to be added to the default - system configuration automatically during the installation (whether - or not you actually use it as the installation media).</para> - </note> - - <para>Finally, if you would like people to be able to FTP install - FreeBSD directly from the CDROM in your machine, you will find - it quite easy. After the machine is fully installed, you simply - need to add the following line to the password file (using the - <command>vipw</command> command):</para> - - <programlisting> -ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent</programlisting> - - <para>Anyone with network connectivity to your machine can now - chose a media type of FTP and type in - <userinput>ftp://<replaceable>your machine</replaceable></userinput> - after picking <quote>Other</quote> in the FTP sites menu during - the install.</para> - - <note><para>If you choose to enable anonymous FTP during the - installation of your system, the installation program will do - the above for you.</para></note> - - </sect3> - - <sect3> - <title>Before installing from Floppies</title> - - <para>If you must install from floppy disk (which we suggest you - do <emphasis>NOT</emphasis> do), either due to unsupported - hardware or simply because you insist on doing things the hard - way, you must first prepare some floppies for the installation.</para> - - <para>At a minimum, you will need as many 1.44MB or 1.2MB floppies - as it takes to hold all the files in the - <filename>bin</filename> (binary distribution) directory. If - you are preparing the floppies from DOS, then they - <emphasis>MUST</emphasis> be formatted using the MS-DOS - <command>FORMAT</command> command. If you are using Windows, - use Explorer to format the disks (right-click on the - <devicename>A:</devicename> drive, and select "Format".</para> - - <para>Do <emphasis>NOT</emphasis> trust factory pre-formatted - floppies! Format them again yourself, just to be sure. Many - problems reported by our users in the past have resulted from - the use of improperly formatted media, which is why we are - making a point of it now.</para> - - <para>If you are creating the floppies on another FreeBSD machine, - a format is still not a bad idea, though you do not need to put - a DOS filesystem on each floppy. You can use the - <command>disklabel</command> and <command>newfs</command> - commands to put a UFS filesystem on them instead, as the - following sequence of commands (for a 3.5" 1.44MB floppy) - illustrates:</para> - - <screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput> -&prompt.root; <userinput>disklabel -w -r fd0.1440 floppy3</userinput> -&prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/rfd0</userinput></screen> - - <note> - <para>Use <literal>fd0.1200</literal> and - <literal>floppy5</literal> for 5.25" 1.2MB disks.</para> - </note> - - <para>Then you can mount and write to them like any other - filesystem.</para> - - <para>After you have formatted the floppies, you will need to copy - the files to them. The distribution files are split into chunks - conveniently sized so that 5 of them will fit on a conventional - 1.44MB floppy. Go through all your floppies, packing as many - files as will fit on each one, until you have all of the - distributions you want packed up in this fashion. Each - distribution should go into a subdirectory on the floppy, e.g.: - <filename>a:\bin\bin.aa</filename>, - <filename>a:\bin\bin.ab</filename>, and so on.</para> - - <para>Once you come to the Media screen during the install - process, select <quote>Floppy</quote> and you will be prompted - for the rest.</para> - </sect3> - - <sect3 id="install-msdos"> - <title>Before Installing from MS-DOS</title> - - <para>To prepare for an installation from an MS-DOS partition, - copy the files from the distribution into a directory named, - for example, <filename>c:\FreeBSD</filename>. The directory - structure of the CDROM or FTP site must be partially reproduced - within this directory, so we suggest using the DOS - <command>xcopy</command> command if you are copying it from a - CD. For example, to prepare for a minimal installation of - FreeBSD:</para> - - <screen><prompt>C:\></prompt> <userinput>md c:\FreeBSD</userinput> -<prompt>C:\></prompt> <userinput>xcopy /s e:\bin c:\FreeBSD\bin\</userinput> -<prompt>C:\></prompt> <userinput>xcopy /s e:\manpages c:\FreeBSD\manpages\</userinput></screen> - - <para>Assuming that <devicename>C:</devicename> is where you have - free space and <devicename>E:</devicename> is where your CDROM - is mounted.</para> - - <para>If you do not have a CDROM drive, you can download the - distribution from <ulink - url="ftp://ftp.FreeBSD.org/pub/FreeBSD/&rel.current;-RELEASE/"> - ftp.FreeBSD.org</ulink>. Each distribution is in its own directory; - for example, the <emphasis>bin</emphasis> distribution can be - found in the <ulink - url="ftp://ftp.FreeBSD.org/pub/FreeBSD/&rel.current;-RELEASE/bin">&rel.current;/bin</ulink> directory.</para> - - <para>For as many distributions you wish to install from an MS-DOS - partition (and you have the free space for), install each one - under <filename>c:\FreeBSD</filename> — the - <literal>BIN</literal> distribution is the only one required for - a minimum installation.</para> - </sect3> - - <sect3> - <title>Before Installing from QIC/SCSI Tape</title> - - <para>Installing from tape is probably the easiest method, short - of an online FTP install or CDROM install. The installation - program expects the files to be simply tarred onto the tape, so - after getting all of the distribution files you are interested - in, simply tar them onto the tape like so:</para> - - <screen>&prompt.root; <userinput>cd /freebsd/distdir</userinput> -&prompt.root; <userinput>tar cvf /dev/rwt0 dist1 ... dist2</userinput></screen> - - <para>When you go to do the installation, you should also make - sure that you leave enough room in some temporary directory - (which you will be allowed to choose) to accommodate the - <emphasis>full</emphasis> contents of the tape you have created. - Due to the non-random access nature of tapes, this method of - installation requires quite a bit of temporary storage. You - should expect to require as much temporary storage as you have - stuff written on tape.</para> - - <note> - <para>When starting the installation, the tape must be in the - drive <emphasis>before</emphasis> booting from the boot - floppy. The installation probe may otherwise fail to find - it.</para> - </note> - </sect3> - - <sect3> - <title>Before Installing over a Network</title> - - <para>There are three types of network installations you can do. - Serial port (SLIP or PPP), Parallel port (PLIP (laplink cable)), - or Ethernet (a standard ethernet controller (includes some - PCMCIA)).</para> - - <para>The SLIP support is rather primitive, and limited primarily - to hard-wired links, such as a serial cable running between a - laptop computer and another computer. The link should be - hard-wired as the SLIP installation does not currently offer a - dialing capability; that facility is provided with the PPP - utility, which should be used in preference to SLIP whenever - possible.</para> - - <para>If you are using a modem, then PPP is almost certainly - your only choice. Make sure that you have your service - provider's information handy as you will need to know it fairly - early in the installation process.</para> - <para>If you use PAP or CHAP to connect your ISP (in other - words, if you can connect to the ISP in Windows without - using a script), then all you will need to do is type in - <command>dial</command> at the - <application>ppp</application> prompt. Otherwise, - you will need to know - how to dial your ISP using the <quote>AT commands</quote> - specific to your modem, as the PPP dialer provides only a very - simple terminal emulator. Please - to the user-ppp <link linkend="userppp">handbook</link> and <ulink - url="../FAQ/ppp.html">FAQ</ulink> entries for further - information. If you have problems, logging can be directed to - the screen using the command <command>set log local - ...</command>.</para> - - <para>If a hard-wired connection to another FreeBSD (2.0-R or - later) machine is available, you might also consider installing - over a <quote>laplink</quote> parallel port cable. The data rate - over the parallel port is much higher than what is typically - possible over a serial line (up to 50kbytes/sec), thus resulting - in a quicker installation.</para> - - <para>Finally, for the fastest possible network installation, an - ethernet adapter is always a good choice! FreeBSD supports most - common PC ethernet cards; a table of supported cards (and their - required settings) is provided in the <link - linkend="install-hw">Supported Hardware</link> list. If you are - using one of the supported PCMCIA ethernet cards, also be sure - that it is plugged in <emphasis>before</emphasis> the laptop is - powered on! FreeBSD does not, unfortunately, currently support - hot insertion of PCMCIA cards during installation.</para> - - <para>You will also need to know your IP address on the network, - the netmask value for your address class, and the name of your - machine. If you are installing over a PPP connection and do not - have a static IP, fear not, the IP address can be dynamically - assigned by your ISP. Your system administrator can tell you - which values to use for your particular network setup. If you - will be referring to other hosts by name rather than IP address, - you will also need a name server and possibly the address of a - gateway (if you are using PPP, it is your provider's IP address) - to use in talking to it. If you do not know the answers to all - or most of these questions, then you should really probably talk - to your system administrator or ISP <emphasis>before</emphasis> trying - this type of installation.</para> - - <sect4> - <title>Before Installing via NFS</title> - - <para>The 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.</para> - - <para>If this server supports only <quote>privileged port</quote> - (as is generally the default for Sun workstations), you will - need to set this option in the Options menu before - installation can proceed.</para> - - <para>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.</para> - - <para>In order for NFS installation to work, the server must - support subdir mounts, e.g., if your FreeBSD 3.4 distribution - directory lives - on:<filename>ziggy:/usr/archive/stuff/FreeBSD</filename>, then - <hostid>ziggy</hostid> will have to allow the direct mounting - of <filename>/usr/archive/stuff/FreeBSD</filename>, not just - <filename>/usr</filename> or - <filename>/usr/archive/stuff</filename>.</para> - - <para>In FreeBSD's <filename>/etc/exports</filename> file, this - is controlled by the <option>-alldirs</option>. Other NFS - servers may have different conventions. If you are getting - <quote>permission denied</quote> messages from the server, then - it is likely that you do not have this enabled - properly.</para> - </sect4> - - <sect4> - <title>Before Installing via FTP</title> - - <para>FTP installation may be done from any FreeBSD mirror site - containing a reasonably up-to-date version of FreeBSD. A full - list of FTP mirrors located all over the world is provided - during the install process.</para> - - <para>If you are installing from an FTP site not listed in this - menu, or are having trouble getting your name server - configured properly, you can also specify a URL to use by - selecting the choice labeled <quote>Other</quote> in that menu. - You can also use the IP address of a machine you wish to - install from, so the following would work in the absence of a - name server:</para> - - <screen><userinput>ftp://209.55.82.20/pub/FreeBSD/&rel.current;-RELEASE</userinput></screen> - - <para>There are two FTP installation modes you can choose from: - active or passive FTP.</para> - - <variablelist> - <varlistentry> - <term>FTP Active</term> - - <listitem> - <para>This option will make all FTP transfers - use <quote>Active</quote> - mode. This will not work through firewalls, but will - often work with older FTP servers that do not support - passive mode. If your connection hangs with passive - mode (the default), try active!</para> - </listitem> - </varlistentry> - - <varlistentry> - <term>FTP Passive</term> - - <listitem> - <para>This option instructs FreeBSD to use - <quote>Passive</quote> mode for all FTP operations. - This allows the user to pass through firewalls - that do not allow incoming connections on random port - addresses.</para> - </listitem> - </varlistentry> - </variablelist> - - <note> - <para>Active and passive modes are not the same as a - <quote>proxy</quote> connection, where a proxy FTP server is - listening and forwarding FTP requests!</para> - </note> - - <para>For a proxy FTP server, you should usually give the name - of the server you really want as a part of the username, after - an <quote>@</quote> sign. The proxy server then - <quote>fakes</quote> the real server. For example, assuming - you want to install from <hostid - role="fqdn">ftp.FreeBSD.org</hostid>, using the proxy FTP - server <hostid role="fqdn">foo.bar.com</hostid>, listening on - port 1024.</para> - - <para>In this case, you go to the options menu, set the FTP - username to ftp@ftp.FreeBSD.org, and the password to your - email address. As your installation media, you specify FTP - (or passive FTP, if the proxy supports it), and the URL - <literal>ftp://foo.bar.com:1234/pub/FreeBSD</literal>.</para> - - <para>Since <filename>/pub/FreeBSD</filename> from <hostid - role="fqdn">ftp.FreeBSD.org</hostid> is proxied under <hostid - role="fqdn">foo.bar.com</hostid>, you are able to install from - <emphasis>that</emphasis> machine (which will fetch the files - from <hostid role="fqdn">ftp.FreeBSD.org</hostid> as your - installation requests them.</para> - </sect4> - </sect3> - - <sect3> - <title>Check your BIOS drive numbering</title> - - <para>If you have used features in your BIOS to renumber your disk - drives without recabling them then you should read <xref - linkend="disks-bios-numbering"> first to ensure you do not - confused.</para> - </sect3> - </sect2> - - <sect2 id="install-freebsd"> - <title>Installing FreeBSD</title> - - <para>Once you have completed the pre-installation step relevant to - your situation, you are ready to install FreeBSD!</para> - - <para>Although you should not experience any difficulty, there is - always the chance that you may, no matter how slight it is. If this - is the case in your situation, then you may wish to go back and - re-read the relevant preparation section or sections. Perhaps you - will come across something you missed the first time. If you are - having hardware problems, or FreeBSD refuses to boot at all, read - the Hardware Guide on the boot floppy for a list of possible - solutions.</para> - - <para>The FreeBSD boot floppies contain all of the online - documentation you should need to be able to navigate through an - installation. If it does not, please let us know what you found - to be the most confusing or most lacking. Send your comments to - the &a.doc;. It is the objective of the installation program - (sysinstall) to be self-documenting enough that painful - <quote>step-by-step</quote> guides are no longer necessary. It may - take us a little while to reach that objective, but nonetheless, - it is still our objective :-)</para> - - <para>Meanwhile, you may also find the following <quote>typical - installation sequence</quote> to be helpful:</para> - - <orderedlist> - <listitem> - <para>Boot the <filename>kern.flp</filename> floppy and when - asked, remove it and insert the - <filename>mfsroot.flp</filename> and hit return. After a - boot sequence which can take anywhere from 30 seconds to 3 - minutes, depending on your hardware, you should be presented - with a menu of initial choices. If the - <filename>kern.flp</filename> floppy does not boot at all or - the boot hangs at some stage, read the Q&A section of the - Hardware Guide on the floppy for possible causes.</para> - </listitem> - - <listitem> - <para>Press F1. You should see some basic usage instructions on - the menu screen and general navigation. If you have not used - this menu system before then <emphasis>please</emphasis> read - this thoroughly.</para> - </listitem> - - <listitem> - <para>Select the Options item and set any special preferences - you may have.</para> - </listitem> - - <listitem> - <para>Select a Standard, Express, or Custom install, depending on - whether or not you would like the installation to help you - through a typical installation, give you a high degree of - control over each step, or simply whiz through it (using - reasonable defaults when possible) as fast as possible. If - you have never used FreeBSD before, the Standard installation - method is most recommended.</para> - </listitem> - - <listitem> - <para>The final configuration menu choice allows you to further - configure your FreeBSD installation by giving you menu-driven - access to various system defaults. Some items, like - networking, may be especially important if you did a CDROM, - tape, or floppy install and have not yet configured your - network interfaces (assuming you have any). Properly - configuring such interfaces here will allow FreeBSD to come up - on the network when you first reboot from the hard - disk.</para> - </listitem> - </orderedlist> - </sect2> - </sect1> - - <sect1 id="install-hw"> - <title>Supported Hardware</title> - - <para>FreeBSD currently runs on a wide variety of ISA, VLB, EISA, and - PCI bus based PCs, ranging from the 386SX to Pentium class machines - (though the 386SX is not recommended). Support for generic IDE or - ESDI drive configurations, various SCSI controllers, and network and - serial cards is also provided.</para> - - <para>In order to run FreeBSD, a recommended minimum of eight - megabytes of RAM is suggested. Sixteen megabytes is the preferred - amount of RAM as you may have some trouble with anything less than - sixteen depending on your hardware.</para> - - <para>What follows is a list of hardware currently known to work with - FreeBSD. There may be other hardware that works as well, but we - have simply not received any confirmation of it.</para> - - <sect2> - <title>Disk Controllers</title> - - <itemizedlist> - <listitem> - <para>WD1003 (any generic MFM/RLL)</para> - </listitem> - - <listitem> - <para>WD1007 (any generic IDE/ESDI)</para> - </listitem> - - <listitem> - <para>IDE</para> - </listitem> - - <listitem> - <para>ATA</para> - </listitem> - - <listitem> - <para>Adaptec 1535 ISA SCSI controllers</para> - </listitem> - - <listitem> - <para>Adaptec 154X series ISA SCSI controllers</para> - </listitem> - - <listitem> - <para>Adaptec 174X series EISA SCSI controllers in standard and - enhanced mode</para> - </listitem> - - <listitem> - <para>Adaptec 274X/284X/2920C/294X/2950/3940/3950 - (Narrow/Wide/Twin) series EISA/VLB/PCI SCSI controllers</para> - </listitem> - - <listitem> - <para>Adaptec AIC-7850, AIC-7860, AIC-7880, AIC-789X on-board SCSI - controllers</para> - </listitem> - - <listitem> - <para>Adaptec 1510 series ISA SCSI controllers (not for bootable - devices)</para> - </listitem> - - <listitem> - <para>Adaptec 152X series ISA SCSI controllers</para> - </listitem> - - <listitem> - <para>Adaptec AIC-6260 and AIC-6360 based boards, which include - the AHA-152X and SoundBlaster SCSI cards</para> - </listitem> - - <listitem> - <para>AdvanSys SCSI controllers (all models)</para> - </listitem> - - <listitem> - <para>BusLogic MultiMaster <quote>W</quote> Series Host Adapters - including BT-948, BT-958, BT-9580</para> - </listitem> - - <listitem> - <para>BusLogic MultiMaster <quote>C</quote> Series Host Adapters - including BT-946C, BT-956C, BT-956CD, BT-445C, BT-747C, - BT-757C, BT-757CD, BT-545C, BT-540CF</para> - </listitem> - - <listitem> - <para>BusLogic MultiMaster <quote>S</quote> Series Host Adapters - including BT-445S, BT-747S, BT-747D, BT-757S, BT-757D, - BT-545S, BT-542D, BT-742A, BT-542B</para> - </listitem> - - <listitem> - <para>BusLogic MultiMaster <quote>A</quote> Series Host Adapters - including BT-742A, BT-542B</para> - </listitem> - - <listitem> - <para>AMI FastDisk controllers that are true BusLogic - MultiMaster clones are also supported.</para> - - <note> - <para>BusLogic/Mylex <quote>Flashpoint</quote> adapters are NOT - yet supported.</para> - </note> - </listitem> - - <listitem> - <para>DPT SmartCACHE Plus, SmartCACHE III, SmartRAID III, - SmartCACHE IV, and SmartRAID IV SCSI/RAID are supported. The - DPT SmartRAID/CACHE V is not yet supported.</para> - </listitem> - - <listitem> - <para>Compaq Intelligent Disk Array Controllers: IDA, IDA-2, IAES, - SMART, SMART-2/E, Smart-2/P, SMART-2SL, Integrated Array, and - Smart Arrays 3200, 3100ES, 221, 4200, 4200, 4250ES.</para> - </listitem> - - <listitem> - <para>SymBios (formerly NCR) 53C810, 53C810a, 53C815, 53C820, - 53C825a, 53C860, 53C875, 53C875j, 53C885, and 53C896 PCI SCSI - controllers including ASUS SC-200, Data Technology DTC3130 - (all variants), Diamond FirePort (all), NCR cards (all), - SymBios cards (all), Tekram DC390W, 390U, and 390F, and Tyan - S1365</para> - </listitem> - - <listitem> - <para>QLogic 1020, 1040, 1040B, and 2100 SCSI and Fibre - Channel Adapters</para> - </listitem> - - <listitem> - <para>DTC 3290 EISA SCSI controller in 1542 evaluation - mode</para> - </listitem> - </itemizedlist> - - <para>With all supported SCSI controllers, full support is provided - for SCSI-I and SCSI-II peripherals, including hard disks, optical - disks, tape drives (including DAT and 8mm Exabyte), medium - changers, processor target devices, and CDROM drives. WORM - devices that support CDROM commands are supported for read-only - access by the CDROM driver. WORM/CD-R/CD-RW writing support is - provided by cdrecord, which is in the ports tree.</para> - - <para>The following CD-ROM type systems are supported at this - time:</para> - - <itemizedlist> - <listitem> - <para><devicename>cd</devicename> - SCSI interface (includes - ProAudio Spectrum and SoundBlaster SCSI)</para> - </listitem> - - <listitem> - <para><devicename>matcd</devicename> - Matsushita/Panasonic - (Creative Soundblaster) proprietary interface (562/563 - models)</para> - </listitem> - - <listitem> - <para><devicename>scd</devicename> - Sony proprietary interface - (all models)</para> - </listitem> - - <listitem> - <para><devicename>acd</devicename> - ATAPI IDE interface</para> - </listitem> - </itemizedlist> - - <para>The following drivers were supported under the old SCSI - subsystem, but are NOT YET supported under the new CAM SCSI - subsystem:</para> - - <itemizedlist> - <listitem> - <para>NCR5380/NCR53400 (<quote>ProAudio Spectrum</quote>) SCSI - controller</para> - </listitem> - - <listitem> - <para>UltraStor 14F, 24F, and 34F SCSI controllers</para> - </listitem> - - <listitem> - <para>Seagate ST01/02 SCSI controllers</para> - </listitem> - - <listitem> - <para>Future Domain 8XX/950 series SCSI controllers</para> - </listitem> - - <listitem> - <para>WD7000 SCSI controller</para> - - <note> - <para>There is work-in-progress to port the UltraStor driver - to the new CAM framework, but no estimates on when or if it - will be completed.</para> - </note> - </listitem> - </itemizedlist> - - <para>Unmaintained drivers, which might or might not work for your - hardware:</para> - - <itemizedlist> - <listitem> - <para>Floppy tape interface (Colorado/Mountain/Insight)</para> - </listitem> - - <listitem> - <para><devicename>mcd</devicename> - Mitsumi proprietary CD-ROM - interface (all models)</para> - </listitem> - </itemizedlist> - </sect2> - - <sect2 id="install-nics"> - <title>Network Cards</title> - - <itemizedlist> - <listitem> - <para>Adaptec Duralink PCI fast ethernet adapters based on the - Adaptec AIC-6195 fast ethernet controller chip, including the - following:</para> - - <itemizedlist> - <listitem> - <para>ANA-62011 64-bit single port 10/100baseTX - adapter</para> - </listitem> - - <listitem> - <para>ANA-62022 64-bit dual port 10/100baseTX adapter</para> - </listitem> - - <listitem> - <para>ANA-62044 64-bit quad port 10/100baseTX adapter</para> - </listitem> - - <listitem> - <para>ANA-69011 32-bit single port 10/100baseTX - adapter</para> - </listitem> - - <listitem> - <para>ANA-62020 64-bit single port 100baseFX adapter</para> - </listitem> - </itemizedlist> - </listitem> - - <listitem> - <para>Allied-Telesyn AT1700 and RE2000 cards</para> - </listitem> - - <listitem> - <para>Alteon Networks PCI gigabit ethernet NICs based on the - Tigon 1 and Tigon 2 chipsets including the Alteon AceNIC - (Tigon 1 and 2), 3Com 3c985-SX (Tigon 1 and 2), Netgear GA620 - (Tigon 2), Silicon Graphics Gigabit Ethernet, DEC/Compaq - EtherWORKS 1000, NEC Gigabit Ethernet</para> - </listitem> - - <listitem> - <para>AMD PCnet/PCI (79c970 and 53c974 or 79c974)</para> - </listitem> - - <listitem> - <para>RealTek 8129/8139 fast ethernet NICs including the - following:</para> - - <itemizedlist> - <listitem> - <para>Allied-Telesyn AT2550</para> - </listitem> - - <listitem> - <para>Allied-Telesyn AT2500TX</para> - </listitem> - - <listitem> - <para>Genius GF100TXR (RTL8139)</para> - </listitem> - - <listitem> - <para>NDC Communications NE100TX-E</para> - </listitem> - - <listitem> - <para>OvisLink LEF-8129TX</para> - </listitem> - - <listitem> - <para>OvisLink LEF-8139TX</para> - </listitem> - - <listitem> - <para>Netronix Inc. EA-1210 NetEther 10/100</para> - </listitem> - - <listitem> - <para>KTX-9130TX 10/100 Fast Ethernet</para> - </listitem> - - <listitem> - <para>Accton <quote>Cheetah</quote> EN1027D (MPX 5030/5038; - RealTek 8139 clone?)</para> - </listitem> - - <listitem> - <para>SMC EZ Card 10/100 PCI 1211-TX</para> - </listitem> - </itemizedlist> - </listitem> - - <listitem> - <para>Lite-On 98713, 98713A, 98715, and 98725 fast ethernet - NICs, including the LinkSys EtherFast LNE100TX, NetGear - FA310-TX Rev. D1, Matrox FastNIC 10/100, Kingston - KNE110TX</para> - </listitem> - - <listitem> - <para>Macronix 98713, 98713A, 98715, 98715A, and 98725 fast - ethernet NICs including the NDC Communications SFA100A - (98713A), CNet Pro120A (98713 or 98713A), CNet Pro120B - (98715), SVEC PN102TX (98713)</para> - </listitem> - - <listitem> - <para>Macronix/Lite-On PNIC II LC82C115 fast ethernet NICs - including the LinkSys EtherFast LNE100TX version 2</para> - </listitem> - - <listitem> - <para>Winbond W89C840F fast ethernet NICs including the - Trendware TE100-PCIE</para> - </listitem> - - <listitem> - <para>VIA Technologies VT3043 <quote>Rhine I</quote> and - VT86C100A <quote>Rhine II</quote> fast ethernet NICs including - the Hawking Technologies PN102TX and D-Link DFE-530TX</para> - </listitem> - - <listitem> - <para>Silicon Integrated Systems SiS 900 and SiS 7016 PCI fast - ethernet NICs</para> - </listitem> - - <listitem> - <para>Sundance Technologies ST201 PCI fast ethernet NICs - including the D-Link DFE-550TX</para> - </listitem> - - <listitem> - <para>SysKonnect SK-984x PCI gigabit ethernet cards including - the SK-9841 1000baseLX (single mode fiber, single port), - the SK-9842 1000baseSX (multimode fiber, single port), the - SK-9843 1000baseLX (single mode fiber, dual port), and the - SK-9844 1000baseSX (multimode fiber, dual port).</para> - </listitem> - - <listitem> - <para>Texas Instruments ThunderLAN PCI NICs, including the - Compaq Netelligent 10, 10/100, 10/100 Proliant, 10/100 - Dual-Port, 10/100 TX Embedded UTP, 10 T PCI UTP/Coax, and - 10/100 TX UTP, the Compaq NetFlex 3P, 3P Integrated, and 3P - w/BNC, the Olicom OC-2135/2138, OC-2325, OC-2326 10/100 TX - UTP, and the Racore 8165 10/100baseTX and 8148 - 10baseT/100baseTX/100baseFX multi-personality cards</para> - </listitem> - - <listitem> - <para>ADMtek AL981-based and AN985-based PCI fast ethernet - NICs</para> - </listitem> - - <listitem> - <para>ASIX Electronics AX88140A PCI NICs including the Alfa Inc. - GFC2204 and CNet Pro110B</para> - </listitem> - - <listitem> - <para>DEC EtherWORKS III NICs (DE203, DE204, and DE205)</para> - </listitem> - - <listitem> - <para>DEC EtherWORKS II NICs (DE200, DE201, DE202, and - DE422)</para> - </listitem> - - <listitem> - <para>DEC DC21040, DC21041, or DC21140 based NICs (SMC - Etherpower 8432T, DE245, etc.)</para> - </listitem> - - <listitem> - <para>DEC FDDI (DEFPA/DEFEA) NICs</para> - </listitem> - - <listitem> - <para>Efficient ENI-155p ATM PCI</para> - </listitem> - - <listitem> - <para>FORE PCA-200E ATM PCI</para> - </listitem> - - <listitem> - <para>Fujitsu MB86960A/MB86965A</para> - </listitem> - - <listitem> - <para>HP PC Lan+ cards (model numbers: 27247B and 27252A)</para> - </listitem> - - <listitem> - <para>Intel EtherExpress (not recommended due to driver - instability)</para> - </listitem> - - <listitem> - <para>Intel EtherExpress Pro/10</para> - </listitem> - - <listitem> - <para>Intel EtherExpress Pro/100B PCI Fast Ethernet</para> - </listitem> - - <listitem> - <para>Isolan AT 4141-0 (16 bit)</para> - </listitem> - - <listitem> - <para>Isolink 4110 (8 bit)</para> - </listitem> - - <listitem> - <para>Novell NE1000, NE2000, and NE2100 Ethernet - interfaces</para> - </listitem> - - <listitem> - <para>PCI network cards emulating the NE2000, including the - RealTek 8029, NetVin 5000, Winbond W89C940, Surecom NE-34, VIA - VT86C926</para> - </listitem> - - <listitem> - <para>3Com 3C501, 3C503 Etherlink II, 3C505 Etherlink/+, 3C507 - Etherlink 16/TP, 3C509, 3C579, 3C589 (PCMCIA), - 3C590/592/595/900/905/905B/905C PCI and EISA (Fast) Etherlink - III / (Fast) Etherlink XL, 3C980/3C980B Fast Etherlink XL - server adapter, 3CSOHO100-TX OfficeConnect adapter</para> - </listitem> - - <listitem> - <para>Toshiba ethernet cards</para> - </listitem> - - <listitem> - <para>PCMCIA ethernet cards from IBM and National Semiconductor - are also supported</para> - </listitem> - </itemizedlist> - </sect2> - - <sect2 id="install-usb"> - <title>USB Peripherals</title> - - <para>A wide range of USB peripherals are supported. Owing to the - generic nature of most USB devices, with some exceptions any - device of a given class will be supported even if not explicitly - listed here.</para> - - <itemizedlist> - <listitem> - <para>USB keyboards</para> - </listitem> - - <listitem> - <para>USB mice</para> - </listitem> - - <listitem> - <para>USB printers and USB to parallel printer conversion - cables</para> - </listitem> - - <listitem> - <para>USB hubs</para> - </listitem> - </itemizedlist> - - <para>Motherboard chipsets:</para> - - <itemizedlist> - <listitem> - <para>ALi Aladdin-V</para> - </listitem> - - <listitem> - <para>Intel 82371SB (PIIX3) and 82371AB and EB (PIIX4) - chipsets</para> - </listitem> - - <listitem> - <para>NEC uPD 9210 Host Controller</para> - </listitem> - - <listitem> - <para>VIA 83C572 USB Host Controller</para> - - <para>and any other UHCI or OHCI compliant motherboard chipset - (no exceptions known).</para> - </listitem> - </itemizedlist> - - <para>PCI plug-in USB host controllers</para> - - <itemizedlist> - <listitem> - <para>ADS Electronics PCI plug-in card (2 ports)</para> - </listitem> - - <listitem> - <para>Entrega PCI plug-in card (4 ports)</para> - </listitem> - </itemizedlist> - - <para>Specific USB devices reported to be working:</para> - - <itemizedlist> - <listitem> - <para>Agiler Mouse 29UO</para> - </listitem> - - <listitem> - <para>Andromeda hub</para> - </listitem> - - <listitem> - <para>Apple iMac mouse and keyboard</para> - </listitem> - - <listitem> - <para>ATen parallel printer adapter</para> - </listitem> - - <listitem> - <para>Belkin F4U002 parallel printer adapter and Belkin - mouse</para> - </listitem> - - <listitem> - <para>BTC BTC7935 keyboard with mouse port</para> - </listitem> - - <listitem> - <para>Cherry G81-3504</para> - </listitem> - - <listitem> - <para>Chic mouse</para> - </listitem> - - <listitem> - <para>Cypress mouse</para> - </listitem> - - <listitem> - <para>Entrega USB-to-parallel printer adapter</para> - </listitem> - - <listitem> - <para>Genius Niche mouse</para> - </listitem> - - <listitem> - <para>Iomega USB Zip 100 MB</para> - </listitem> - - <listitem> - <para>Kensington Mouse-in-a-Box</para> - </listitem> - - <listitem> - <para>Logitech M2452 keyboard</para> - </listitem> - - <listitem> - <para>Logictech wheel mouse (3 buttons)</para> - </listitem> - - <listitem> - <para>Logitech PS/2 / USB mouse (3 buttons)</para> - </listitem> - - <listitem> - <para>MacAlly mouse (3 buttons)</para> - </listitem> - - <listitem> - <para>MacAlly self-powered hub (4 ports)</para> - </listitem> - - <listitem> - <para>Microsoft Intellimouse (3 buttons)</para> - </listitem> - - <listitem> - <para>Microsoft keyboard</para> - </listitem> - - <listitem> - <para>NEC hub</para> - </listitem> - - <listitem> - <para>Trust Ami Mouse (3 buttons)</para> - </listitem> - </itemizedlist> - </sect2> - - <sect2 id="install-isdn"> - <title>ISDN (European DSS1 [Q.921/Q.931] protocol)</title> - - <itemizedlist> - <listitem> - <para>Asuscom I-IN100-ST-DV (experimental, may work)</para> - </listitem> - - <listitem> - <para>Asuscom ISDNlink 128K</para> - </listitem> - - <listitem> - <para>AVM A1</para> - </listitem> - - <listitem> - <para>AVM Fritz!Card classic</para> - </listitem> - - <listitem> - <para>AVM Fritz!Card PCI</para> - </listitem> - - <listitem> - <para>AVM Fritz!Card PCMCIA (currently FreeBSD 3.x only)</para> - </listitem> - - <listitem> - <para>AVM Fritz!Card PnP (currently FreeBSD 3.x only)</para> - </listitem> - - <listitem> - <para>Creatix ISDN-S0/8</para> - </listitem> - - <listitem> - <para>Creatix ISDN-S0/16</para> - </listitem> - - <listitem> - <para>Creatix ISDN-S0 PnP</para> - </listitem> - - <listitem> - <para>Dr.Neuhaus Niccy 1008</para> - </listitem> - - <listitem> - <para>Dr.Neuhaus Niccy 1016</para> - </listitem> - - <listitem> - <para>Dr.Neuhaus Niccy GO@ (ISA PnP)</para> - </listitem> - - <listitem> - <para>Dynalink IS64PH (no longer maintained)</para> - </listitem> - - <listitem> - <para>ELSA 1000pro ISA</para> - </listitem> - - <listitem> - <para>ELSA 1000pro PCI</para> - </listitem> - - <listitem> - <para>ELSA PCC-16</para> - </listitem> - - <listitem> - <para>ITK ix1 micro (currently FreeBSD 3.x only)</para> - </listitem> - - <listitem> - <para>ITK ix1 micro V.3 (currently FreeBSD 3.x only)</para> - </listitem> - - <listitem> - <para>Sagem Cybermod (ISA PnP, may work)</para> - </listitem> - - <listitem> - <para>Sedlbauer Win Speed</para> - </listitem> - - <listitem> - <para>Siemens I-Surf 2.0</para> - </listitem> - - <listitem> - <para>Stollman Tina-pp (under development)</para> - </listitem> - - <listitem> - <para>Teles S0/8</para> - </listitem> - - <listitem> - <para>Teles S0/16</para> - </listitem> - - <listitem> - <para>Teles S0/16.3 (the <quote>c</quote> Versions - like 16.3c - - are unsupported!)</para> - </listitem> - - <listitem> - <para>Teles S0 PnP (experimental, may work)</para> - </listitem> - - <listitem> - <para>3Com/USRobotics Sportster ISDN TA intern (non-PnP - version)</para> - </listitem> - </itemizedlist> - </sect2> - - <sect2 id="install-misc"> - <title>Miscellaneous Devices</title> - - <itemizedlist> - <listitem> - <para>AST 4 port serial card using shared IRQ</para> - </listitem> - - <listitem> - <para>ARNET 8 port serial card using shared IRQ</para> - </listitem> - - <listitem> - <para>ARNET (now Digiboard) Sync 570/i high-speed serial</para> - </listitem> - - <listitem> - <para>Boca BB1004 4-Port serial card (Modems NOT - supported)</para> - </listitem> - - <listitem> - <para>Boca IOAT66 6-Port serial card (Modems supported)</para> - </listitem> - - <listitem> - <para>Boca BB1008 8-Port serial card (Modems NOT - supported)</para> - </listitem> - - <listitem> - <para>Boca BB2016 16-Port serial card (Modems supported)</para> - </listitem> - - <listitem> - <para>Cyclades Cyclom-y Serial Board</para> - </listitem> - - <listitem> - <para>Moxa SmartIO CI-104J 4-Port serial card</para> - </listitem> - - <listitem> - <para>STB 4 port card using shared IRQ</para> - </listitem> - - <listitem> - <para>SDL Communications RISCom/8 Serial Board</para> - </listitem> - - <listitem> - <para>SDL Communications RISCom/N2 and N2pci high-speed sync - serial boards</para> - </listitem> - - <listitem> - <para>Specialix SI/XIO/SX multiport serial cards, with both the - older SIHOST2.x and the new <quote>enhanced</quote> - (transputer based, aka JET) host cards; ISA, EISA and PCI are - supported</para> - </listitem> - - <listitem> - <para>Stallion multiport serial boards: EasyIO, EasyConnection - 8/32 & 8/64, ONboard 4/16 and Brumby</para> - </listitem> - - <listitem> - <para>Adlib, SoundBlaster, SoundBlaster Pro, ProAudioSpectrum, - Gravis UltraSound, and Roland MPU-401 sound cards</para> - </listitem> - - <listitem> - <para>Connectix QuickCam</para> - </listitem> - - <listitem> - <para>Matrox Meteor Video frame grabber</para> - </listitem> - - <listitem> - <para>Creative Labs Video Spigot frame grabber</para> - </listitem> - - <listitem> - <para>Cortex1 frame grabber</para> - </listitem> - - <listitem> - <para>Various frame grabbers based on the Brooktree Bt848 - and Bt878 chip</para> - </listitem> - - <listitem> - <para>HP4020, HP6020, Philips CDD2000/CDD2660 and Plasmon CD-R - drives</para> - </listitem> - - <listitem> - <para>Bus mice</para> - </listitem> - - <listitem> - <para>PS/2 mice</para> - </listitem> - - <listitem> - <para>Standard PC Joystick</para> - </listitem> - - <listitem> - <para>X-10 power controllers</para> - </listitem> - - <listitem> - <para>GPIB and Transputer drives</para> - </listitem> - - <listitem> - <para>Genius and Mustek hand scanners</para> - </listitem> - - <listitem> - <para>Floppy tape drives (some rather old models only, driver is - rather stale)</para> - </listitem> - - <listitem> - <para>Lucent Technologies WaveLAN/IEEE 802.11 PCMCIA and ISA - standard speed (2Mbps) and turbo speed (6Mbps) wireless - network adapters and workalikes (NCR WaveLAN/IEEE 802.11, - Cabletron RoamAbout 802.11 DS)</para> - - <note> - <para>The ISA versions of these adapters are actually PCMCIA - cards combined with an ISA to PCMCIA bridge card, so both - kinds of devices work with the same driver.</para> - </note> - </listitem> - </itemizedlist> - - <para>FreeBSD currently does NOT support IBM's microchannel (MCA) - bus.</para> - </sect2> - </sect1> - - <sect1 id="install-trouble"> - <title>Troubleshooting</title> - - <para>The following section covers basic installation troubleshooting, - such as common problems people have reported. There are also a few - questions and answers for people wishing to dual-boot FreeBSD with - MS-DOS.</para> - - <sect2> - <title>What to do if something goes wrong...</title> - - <para>Due to various limitations of the PC architecture, it is - impossible for probing to be 100% reliable, however, there are a - few things you can do if it fails.</para> - - <para>Check the <link linkend="install-hw">supported - hardware</link> list to make sure your hardware is - supported.</para> - - <para>If your hardware is supported and you still experience - lock-ups or other problems, reset your computer, and when the - visual kernel configuration option is given, choose it. This will - allow you to go through your hardware and supply information to the - system about it. The kernel on the boot disks is configured - assuming that most hardware devices are in their factory default - configuration in terms of IRQs, IO addresses, and DMA channels. If - your hardware has been reconfigured, you will most likely need to - use the configuration editor to tell FreeBSD where to find - things.</para> - - <para>It is also possible that a probe for a device not present will - cause a later probe for another device that is present to fail. In - that case, the probes for the conflicting driver(s) should be - disabled.</para> - - <warning> - <para>Do not disable any drivers you will need during the - installation, such as your screen (<devicename>sc0</devicename>). - If the installation wedges or fails mysteriously after leaving - the configuration editor, you have probably removed or changed - something you should not have. Reboot and try again.</para> - </warning> - - <para>In configuration mode, you can:</para> - - <itemizedlist> - <listitem> - <para>List the device drivers installed in the kernel.</para> - </listitem> - - <listitem> - <para>Change device drivers for hardware that is not present in - your system.</para> - </listitem> - - <listitem> - <para>Change IRQs, DRQs, and IO port addresses used by a device - driver.</para> - </listitem> - </itemizedlist> - - <para>After adjusting the kernel to match your hardware - configuration, type <command>Q</command> to boot with the new - settings. Once the installation has completed, any changes you - made in the configuration mode will be permanent so you do not have - to reconfigure every time you boot. It is still highly likely that - you will eventually want to build a <link - linkend="kernelconfig">custom kernel</link>.</para> - </sect2> - - <sect2> - <title>MS-DOS User's Questions and Answers</title> - - <para>Many users wish to install FreeBSD on PCs inhabited by MS-DOS. - Here are some commonly asked questions about installing FreeBSD on - such systems.</para> - - <qandaset> - <qandaentry> - <question> - <para>Help, I have no space! Do I need to delete everything - first?</para> - </question> - - <answer> - <para>If your machine is already running MS-DOS and has little - or no free space available for the FreeBSD installation, all - hope is not lost! You may find the FIPS utility, provided - in the <filename>tools</filename> directory on the FreeBSD - CDROM or various FreeBSD FTP sites to be quite - useful.</para> - - <para>FIPS allows you to split an existing MS-DOS partition - into two pieces, preserving the original partition and - allowing you to install onto the second free piece. You - first defragment your MS-DOS partition using the Windows - DEFRAG utility (go into Explorer, right-click on the - hard drive, and choose to defrag your - hard drive), or Norton Disk Tools. You then must run FIPS. It - will prompt you for the rest of the information it needs. - Afterwards, you can reboot and install FreeBSD on the new - free slice. See the <emphasis>Distributions</emphasis> menu - for an estimate of how much free space you will need for the - kind of installation you want.</para> - - <para>There is also a <emphasis>very</emphasis> useful - product from <ulink - url="http://www.powerquest.com/">PowerQuest</ulink> - called <application>Partition Magic</application>. This - application has far more functionality than FIPS, and is - highly recommended if you plan to often add/remove - operating systems (like me). However, it does cost - money, and if you plan to install FreeBSD once and then - leave it there, FIPS will probably be fine for you.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Can I use compressed MS-DOS filesystems from - FreeBSD?</para> - </question> - - <answer> - <para>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/double spaced file!). <emphasis>Do not remove that - file or you will probably regret it - greatly!</emphasis></para> - - <para>It is probably better to create another uncompressed - primary MS-DOS partition and use this for communications - between MS-DOS and FreeBSD.</para> - </answer> - </qandaentry> - - <qandaentry> - <question> - <para>Can I mount my extended MS-DOS partition?</para> - </question> - - <answer> - <para>Yes. DOS extended partitions are mapped in at the end - of the other <quote>slices</quote> in FreeBSD, e.g., your - <devicename>D:</devicename> drive might be - <filename>/dev/da0s5</filename>, your - <devicename>E:</devicename> drive, - <filename>/dev/da0s6</filename>, and so on. This example - assumes, of course, that your extended partition is on SCSI - drive 0. For IDE drives, substitute <filename>ad</filename> - for <filename>da</filename> appropriately if installing - 4.0-RELEASE or later, and substitute - <filename>wd</filename> for <filename>da</filename> if you - are installing a version of FreeBSD prior to 4.0. You otherwise - mount extended partitions exactly like you would any other - DOS drive, for example:</para> - - <screen>&prompt.root; <userinput>mount -t msdos /dev/ad0s5 /dos_d</userinput></screen> - </answer> - </qandaentry> - </qandaset> - </sect2> - </sect1> -</chapter> - -<!-- - Local Variables: - mode: sgml - sgml-declaration: "../chapter.decl" - sgml-indent-data: t - sgml-omittag: nil - sgml-always-quote-attributes: t - sgml-parent-document: ("../book.sgml" "part" "chapter") - End: ---> |