7 This file has architecture-dependent installation instructions, culled
8 from {alpha,i386}/INSTALL.TXT.
13 <title>Installing &os;</title>
15 <para>This section documents the process of installing a new
16 distribution of &os;. These instructions pay particular emphasis to
17 the process of obtaining the &os; &release.current; distribution and
18 to beginning the installation procedure. The <ulink
19 url="&url.books.handbook;/install.html"><quote>Installing
22 url="&url.books.handbook;/">&os;
23 Handbook</ulink> provides more in-depth information about the
24 installation program itself, including a guided walkthrough with
27 <para>If you are upgrading from a previous release
28 of &os;, please see <xref linkend="upgrading"> for instructions on
31 <sect2 id="getting-started">
32 <title>Getting Started</title>
34 <para>Probably the most important pre-installation step that can
35 be taken is that of reading the various instruction documents
36 provided with &os;. A roadmap of documents pertaining to this
37 release of &os; can be found in <filename>README.TXT</filename>,
38 which can usually be found in the same location as this file; most
39 of these documents, such as the release notes and the hardware
40 compatibility list, are also accessible in the Documentation menu
41 of the installer.</para>
43 <para>Note that on-line versions of the &os; <ulink
44 url="&url.books.faq;/">FAQ</ulink> and <ulink
45 url="&url.books.handbook;/">Handbook</ulink> are also
46 available from the <ulink url="&url.base;/">&os;
47 Project Web site</ulink>, if you have an Internet
50 <para>This collection of documents may seem daunting, but the time
51 spent reading them will likely be saved many times over. Being
52 familiar with what resources are available can also be helpful in
53 the event of problems during installation.</para>
55 <para>The best laid plans sometimes go awry, so if you run into
56 trouble take a look at <xref linkend="trouble">, which contains
57 valuable troubleshooting information. You should also read
59 <filename>ERRATA.TXT</filename> before installing,
60 since this will alert you to
61 any problems which have reported in the interim for your
62 particular release.</para>
65 <para>While &os; does its best to safeguard against
66 accidental loss of data, it's still more than possible to
67 <emphasis>wipe out your entire disk</emphasis>
68 with this installation if you make a
69 mistake. Please do not proceed to the final &os;
70 installation menu unless you've adequately backed up any
71 important data first.</para>
76 <title>Hardware Requirements</title>
78 <!-- i386/pc98 text starts here -->
80 <para arch="i386,pc98">&os; for the &arch.print; requires a 486 or better
81 processor and at least 24 MB of RAM.
82 You will need at least 150MB of free hard drive space for the
83 most minimal installation. See below for ways of shrinking
84 existing DOS partitions in order to install &os;.</para>
86 <!-- alpha text starts here -->
88 <para arch="alpha">&os; for the &arch.print; supports the platforms
89 described in <filename>HARDWARE.TXT</filename>.</para>
91 <para arch="alpha">You will need a dedicated disk for
92 &os;/alpha. It is not possible to share a disk with another
93 operating system at this time. This disk will need to be attached
94 to a SCSI controller which is supported by the SRM firmware or an
95 IDE disk assuming the SRM in your machine supports booting from
98 <para arch="alpha">Your root filesystem MUST be the first
99 partition (partition <literal>a</literal>) on the disk to be
102 <para arch="alpha">You will need the SRM console firmware for your
103 platform. In some cases, it is possible to switch between
104 AlphaBIOS (or ARC) firmware and SRM. In others it will be
105 necessary to download new firmware from the vendor's Web
108 <!-- sparc64 text starts here -->
110 <para arch="sparc64">&os; for the &arch.print; supports the platforms
111 described in <filename>HARDWARE.TXT</filename>.</para>
113 <para arch="sparc64">You will need a dedicated disk for
114 &os;/sparc64. It is not possible to share a disk with another
115 operating system at this time.</para>
117 <!-- amd64 text starts here -->
118 <para arch="amd64">&os; for the &arch.print; requires an
119 Athlon64, Athlon64-FX, Opteron or better processor to run.</para>
121 <para arch="amd64">If you have an machine based on an
122 nVidia nForce3 Pro-150, you MUST use the BIOS setup to
123 disable the IO APIC. If you do not have an option
124 to do this, you will likely have to disable ACPI
125 instead. There are bugs in the Pro-150 chipset that
126 we have not found a workaround for yet.</para>
128 <!-- generic text starts here -->
131 not familiar with configuring hardware for &os;, you should
132 be sure to read the <filename>HARDWARE.TXT</filename> file;
133 it contains important
134 information on what hardware is supported by &os;.</para>
137 <sect2 id="floppies">
138 <title>Floppy Disk Image Instructions</title>
140 <para arch="i386,alpha,pc98">Depending on how you choose to install &os;, you may need to
141 create a set of floppy disks (usually three) to begin the installation
142 process. This section briefly describes how to create these disks,
143 either from a CDROM installation or from the Internet. Note that in
144 the common case of installing &os; from CDROM, on a machine that
145 supports bootable CDROMs, the steps outlined in this section will
146 not be needed and can be skipped.</para>
148 <para arch="i386,alpha">For most CDROM or network installations, all you need to
149 copy onto actual floppies from the <filename>floppies/</filename> directory are the
150 <filename>boot.flp</filename> and <filename>kern<replaceable>X</replaceable>.flp</filename>
151 images (for 1.44MB floppies).</para>
153 <para arch="pc98">For a normal CDROM or network installation, all you need
154 to copy onto actual floppies from the <filename>floppies/</filename>
155 directory are the <filename>boot.flp</filename> and <filename>kern<replaceable>X</replaceable>.flp</filename>
156 images (for 1.44MB floppies) or <filename>boot-small.flp</filename> and
157 <filename>kern-small.flp</filename> images (for 1.2MB floppies).</para>
159 <para arch="i386,alpha,pc98">Getting these images over the network is easy. Simply fetch
161 <replaceable>release</replaceable><filename>/floppies/boot.flp</filename>,
163 <replaceable>release</replaceable><filename>/floppies/kern<replaceable>X</replaceable>.flp</filename>
165 url="&release.url;"></ulink>
166 or one of the many mirrors listed at <ulink
167 url="&url.books.handbook;/mirrors-ftp.html">FTP
168 Sites</ulink> section of the Handbook, or on the
169 <ulink url="http://mirrorlist.FreeBSD.org/"></ulink> Web pages.
172 <para arch="i386,alpha">Get several blank, freshly formatted floppies and image copy
173 <filename>boot.flp</filename> onto one and the <filename>kern<replaceable>X</replaceable>.flp</filename> files
174 onto the others. These images are
175 <emphasis>not</emphasis> DOS files. You cannot simply copy them to a DOS or UFS floppy
176 as regular files, you need to <quote>image</quote> copy them to the floppy with
177 <filename>fdimage.exe</filename> under DOS (see the
178 <filename>tools</filename> directory on your CDROM or &os; FTP
179 mirror) or the &man.dd.1; command in UNIX.</para>
181 <para arch="pc98">Get several blank, freshly formatted floppies and image copy
182 <filename>boot.flp</filename> onto one and the <filename>kern<replaceable>X</replaceable>.flp</filename> files
183 onto the others. These images are
184 <emphasis>not</emphasis> DOS files. You cannot simply copy them to a DOS or UFS floppy
185 as regular files, you need to <quote>image</quote> copy them to the floppy with
186 <filename>rawrite.exe</filename> under DOS (see the
187 <filename>tools</filename> directory on your CDROM or &os; FTP
188 mirror) or the &man.dd.1; command in UNIX.</para>
190 <para arch="i386,alpha,pc98">For example, to create the kernel floppy image from DOS, you'd
191 do something like this:</para>
193 <screen arch="i386,alpha"><prompt>C></prompt> <userinput>fdimage boot.flp a:</userinput></screen>
194 <screen arch="pc98"><prompt>A></prompt> <userinput>rawrite</userinput></screen>
196 <para arch="i386,alpha">Assuming that you'd copied <filename>fdimage.exe</filename> and <filename>boot.flp</filename> into a directory
197 somewhere. You would do the same for the <filename>kern<replaceable>X</replaceable>.flp</filename> files, of course.</para>
199 <para arch="pc98">Assuming that you'd copied <filename>rawrite.exe</filename> and <filename>boot.flp</filename> into a directory
200 somewhere. You would do the same for the <filename>kern<replaceable>X</replaceable>.flp</filename> files, of course.</para>
202 <para arch="i386,alpha,pc98">If you're creating the boot floppy from a UNIX machine, you
203 may find that:</para>
205 <screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/rfd0</userinput></screen>
206 <screen arch="pc98">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/rfd0.1440</userinput></screen>
208 <para arch="i386,alpha">or</para>
210 <screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/fd0</userinput></screen>
212 <para arch="i386,alpha,pc98">or</para>
214 <screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/floppy</userinput></screen>
215 <screen arch="pc98">&prompt.root; <userinput>dd if=floppies/boot-small.flp of=/dev/rfd0.1200</userinput></screen>
217 <para arch="i386,alpha,pc98">work well, depending on your hardware and operating system
218 environment (different versions of UNIX have different names
219 for the floppy drive).</para>
221 <para arch="amd64,sparc64">Floppy disk based install is not supported
222 on &os;/&arch;.</para>
225 <sect2 id="start-installation">
226 <title>Installing &os; from CDROM or the Internet</title>
228 <!-- i386/pc98 text starts here -->
230 <para arch="i386,amd64">The easiest type of installation is from
231 CDROM. If you have a supported CDROM drive and a &os;
232 installation CDROM, there are 2 ways of starting the
233 installation from it:
236 <para>If your system supports the <quote>CDBOOT</quote> standard for
237 bootable CDROM media and you have booting from CD enabled,
238 simply put the &os; installation CD in your CDROM drive and
239 boot the system to begin installation.</para>
242 <para>Build a set of &os; boot floppies from the
243 <filename>floppies/</filename> directory in every &os;
245 <xref linkend="floppies"> for more information on creating
246 the bootable floppies under different operating systems.
247 Then you simply boot from the first floppy and you should
248 soon be in the &os; installation.</para>
253 <para arch="pc98">The easiest type of installation is from
254 CDROM. If you have a supported CDROM drive and a &os;
255 installation CDROM, there is a next way of starting the
256 installation from it:
259 <para>Build a set of &os; boot floppies from the
260 <filename>floppies/</filename> directory in every &os;
261 distribution. Read <xref linkend="floppies"> for more
262 information on creating the bootable floppies under
263 different operating systems. Then you simply boot from
264 the first floppy and you should soon be in the &os;
270 <para arch="i386">If you don't have a CDROM (or your computer does not
271 support booting from CDROM) and would like to simply install
272 over the net using PPP, SLIP or a dedicated connection,
273 you should start the installation by building
274 a set of &os; boot floppies from the files
275 <filename>floppies/boot.flp</filename> and
276 <filename>floppies/kern<replaceable>X</replaceable>.flp</filename> using the instructions
277 found in <xref linkend="floppies">. Restart your computer using
278 the <filename>boot.flp</filename> disk; when prompted, insert
279 the other disks as required. Then, please go to
280 <xref linkend="ftpnfs"> for additional tips on installing
281 via FTP or NFS.</para>
283 <para arch="pc98">If you don't have a CDROM and would like to
284 simply install over the net using PPP, SLIP or a dedicated connection,
285 you should start the installation by building
286 a set of &os; boot floppies from the files
287 <filename>floppies/boot.flp</filename> and
288 <filename>floppies/kern<replaceable>X</replaceable>.flp</filename> using the instructions
289 found in <xref linkend="floppies">. Restart your computer using
290 the <filename>boot.flp</filename> disk; when prompted, insert
291 the other disks as required. Then, please go to
292 <xref linkend="ftpnfs"> for additional tips on installing
293 via FTP or NFS.</para>
295 <!-- alpha text starts here -->
297 <para arch="alpha">The easiest type of installation is from
298 CDROM. If you have a supported CDROM drive and a &os;
299 installation CDROM, you can boot &os; directly from the
300 CDROM. Insert the CDROM into the drive and type the following
301 command to start the installation (substituting the name of the
302 appropriate CDROM drive if necessary):</para>
304 <screen arch="alpha">>>><userinput>boot dka0</userinput></screen>
306 <para arch="alpha">Alternatively you can boot the installation
307 from floppy disk. You should start the installation by building
308 a set of &os; boot floppies from the
309 <filename>floppies/boot.flp</filename> and
310 <filename>floppies/kern<replaceable>X</replaceable>.flp</filename> files using the instructions
311 found in <xref linkend="floppies">. From the SRM console prompt
312 (<literal>>>></literal>), just insert the
313 <filename>boot.flp</filename> floppy and type the following
314 command to start the installation:</para>
316 <screen arch="alpha">>>><userinput>boot dva0</userinput></screen>
318 <para arch="alpha">Insert the other floppies when prompted and
319 you will end up at the first screen of
320 the install program.</para>
322 <!-- sparc64 text starts here -->
324 <para arch="sparc64">Most &arch; systems are set up to boot automatically from
325 disk. To install &os;, you need to boot over the network or
326 from a CDROM, which requires you to break into the PROM
327 (OpenFirmware).</para>
329 <para arch="sparc64">To do this, reboot the system, and wait until the boot
330 message appears. It depends on the model, but should look about
333 <screen arch="sparc64">Sun Blade 100 (UltraSPARC-IIe), Keyboard Present
334 Copyright 1998-2001 Sun Microsystems, Inc. All rights reserved.
335 OpenBoot 4.2, 128 MB memory installed, Serial #51090132.
336 Ethernet address 0:3:ba:b:92:d4, Host ID: 830b92d4.</screen>
338 <para arch="sparc64">If your system proceeds to boot from disk at this point, you
339 need to press <keycombo
340 action="simul"><keycap>L1</keycap><keycap>A</keycap></keycombo>
342 action="simul"><keycap>Stop</keycap><keycap>A</keycap></keycombo>
343 on the keyboard, or send a <command>BREAK</command> over the
344 serial console (using for example <command>~#</command> in
345 &man.tip.1; or &man.cu.1;) to get to the PROM prompt. It looks
348 <screenco arch="sparc64">
350 <area id="prompt-single" coords="1 5">
351 <area id="prompt-smp" coords="2 5">
354 <screen><prompt>ok </prompt>
355 <prompt>ok {0} </prompt></screen>
358 <callout arearefs="prompt-single">
359 <para>This is the prompt used on systems with just one
363 <callout arearefs="prompt-smp">
364 <para>This is the prompt used on SMP systems, the digit
365 indicates the number of the active CPU.</para>
370 <para arch="sparc64">At this point, place the CDROM into your
371 drive, and from the PROM prompt, type <command>boot
372 cdrom</command>.</para>
376 <title>Detail on various installation types</title>
378 <para>Once you've gotten yourself to the initial installation
379 screen somehow, you should be able to follow the various menu
380 prompts and go from there. If you've never used the &os;
381 installation before, you are also encouraged to read some of the
382 documentation in the Documentation submenu as well as the
383 general <quote>Usage</quote> instructions on the first menu.</para>
386 <para>If you get stuck at a screen, press the <keycap>F1</keycap> key for online
387 documentation relevant to that specific section.</para>
390 <para>If you've never installed &os; before, or even if you
391 have, the <quote>Standard</quote> installation mode is the most recommended
392 since it makes sure that you'll visit all the various important
393 checklist items along the way. If you're much more comfortable
394 with the &os; installation process and know <emphasis>exactly</emphasis> what you
395 want to do, use the <quote>Express</quote> or <quote>Custom</quote> installation options. If
396 you're upgrading an existing system, use the <quote>Upgrade</quote> option.</para>
398 <para>The &os; installer supports the direct use of floppy,
399 DOS, tape, CDROM, FTP, NFS and UFS partitions as installation
400 media; further tips on installing from each type of media are listed
403 <para arch="alpha">Once the install procedure has finished, you will be able
404 to start &os;/&arch; by typing something like this to the SRM
407 <screen arch="alpha">>>><userinput>boot dkc0</userinput></screen>
409 <para arch="alpha">This instructs the firmware to boot the specified disk. To
410 find the SRM names of disks in your machine, use the <literal>show
411 device</literal> command:</para>
413 <screen arch="alpha">>>><userinput>show device</userinput>
414 dka0.0.0.4.0 DKA0 TOSHIBA CD-ROM XM-57 3476
415 dkc0.0.0.1009.0 DKC0 RZ1BB-BS 0658
416 dkc100.1.0.1009.0 DKC100 SEAGATE ST34501W 0015
418 ewa0.0.0.3.0 EWA0 00-00-F8-75-6D-01
419 pkc0.7.0.1009.0 PKC0 SCSI Bus ID 7 5.27
420 pqa0.0.0.4.0 PQA0 PCI EIDE
421 pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
423 <para arch="alpha">This example is from a Digital Personal Workstation 433au
424 and shows three disks attached to the machine. The first is a
425 CDROM called <devicename>dka0</devicename> and the other two are
426 disks and are called <devicename>dkc0</devicename> and
427 <devicename>dkc100</devicename> respectively.</para>
429 <para arch="alpha">You can specify which kernel file to load and what boot
430 options to use with the <option>-file</option> and
431 <option>-flags</option> options, for example:</para>
433 <screen arch="alpha"><prompt>>>></prompt> <userinput>boot -file kernel.old -flags s</userinput></screen>
435 <para arch="alpha">To make &os;/&arch; boot automatically, use these commands:</para>
437 <screen arch="alpha"><prompt>>>></prompt> <userinput>set boot_osflags a</userinput>
438 <prompt>>>></prompt> <userinput>set bootdef_dev dkc0</userinput>
439 <prompt>>>></prompt> <userinput>set auto_action BOOT</userinput></screen>
442 <title>Installing from a Network CDROM</title>
444 <para>If you simply wish to install from a local CDROM drive
445 then see <xref linkend="start-installation">. If you don't have a CDROM
446 drive on your system and wish to use a &os; distribution CD
447 in the CDROM drive of another system to which you have network
448 connectivity, there are also several ways of going about it:</para>
452 <para>If you would be able to FTP install &os; directly
453 from the CDROM drive in some &os; machine, it's quite
454 easy: You ensure an FTP server is running and then
455 simply add the following line to the password file
456 (using the &man.vipw.8; command):</para>
458 <screen>ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin</screen>
460 <para>On the machine on which you are running the install,
461 go to the Options menu and set Release Name to
462 <literal>any</literal>. You may then choose a Media type of
463 <literal>FTP</literal> and type in
464 <filename>ftp://<replaceable>machine</replaceable></filename>
465 after picking <quote>URL</quote> in the ftp sites
469 <para>This may allow anyone on the local network (or Internet) to
470 make <quote>anonymous FTP</quote> connections to this
471 machine, which may not be desirable.</para>
476 <para>If you would rather use NFS to export the CDROM
477 directly to the machine(s) you'll be installing from, you
478 need to first add an entry to the
479 <filename>/etc/exports</filename> file (on the machine with
480 the CDROM drive). The example below allows the machine
481 <hostid role="hostname">ziggy.foo.com</hostid> to mount the
482 CDROM directly via NFS during installation:</para>
484 <screen>/cdrom -ro ziggy.foo.com</screen>
487 with the CDROM must also be configured as an NFS server, of
488 course, and if you're not sure how to do that then an NFS
489 installation is probably not the best choice for you unless
490 you're willing to read up on &man.rc.conf.5; and configure things
491 appropriately. Assuming that this part goes smoothly, you
492 should be able to enter: <filename><replaceable>cdrom-host</replaceable>:/cdrom</filename> as the path for
493 an NFS installation when the target machine is installed,
494 e.g. <filename>wiggy:/cdrom</filename>.</para>
500 <title>Installing from Floppies</title>
502 <para>If you must install from floppy disks, either due to
503 unsupported hardware or just because you enjoy doing things the
504 hard way, you must first prepare some floppies for the
507 <para>First, make your boot floppies as described in
508 <xref linkend="floppies">.</para>
510 <para>Second, peruse <xref linkend="layout"> and pay special attention
511 to the <quote>Distribution Format</quote> section since it describes which
512 files you're going to need to put onto floppy and which you can
515 <para>Next you will need, at minimum, as many 1.44MB floppies as
516 it takes to hold all files in the <filename>bin</filename>
517 (binary distribution) directory. If you're preparing these
518 floppies under DOS, then these floppies
519 <emphasis>must</emphasis> be formatted using the MS-DOS
520 <filename>FORMAT</filename> command. If you're using Windows,
521 use the Windows File Manager format command.</para>
524 <para>Frequently, floppy disks come <quote>factory
525 preformatted</quote>. While convenient,
526 many problems reported by users in the past have resulted
527 from the use of improperly formatted media.
528 Re-format them yourself, just to make sure.</para>
531 <para>If you're creating the floppies from another &os;
532 machine, a format is still not a bad idea though you don't need
533 to put a DOS filesystem on each floppy. You can use the
534 &man.disklabel.8; and &man.newfs.8; commands to put a UFS filesystem on a
535 floppy, as the following sequence of commands
538 <screen>&prompt.root; <userinput>fdformat -f 1440 fd0</userinput>
539 &prompt.root; <userinput>disklabel -w fd0 floppy3</userinput>
540 &prompt.root; <userinput>newfs -i 65536 /dev/fd0</userinput></screen>
542 <para>After you've formatted the floppies for DOS or UFS, you'll
543 need to copy the files onto them.
544 The distribution files are sized so that a floppy disk will hold
546 Each distribution should go into its own subdirectory on the floppy,
547 e.g.: <filename>a:\bin\bin.inf</filename>, <filename>a:\bin\bin.aa</filename>, <filename>a:\bin\bin.ab</filename>, ...</para>
550 <para>The <filename>bin.inf</filename> file also needs to go on the first floppy of
551 the <filename>bin</filename> set since it is read by the installation program in
552 order to figure out how many additional pieces to look for
553 when fetching and concatenating the distribution. When
554 putting distributions onto floppies, the
555 <filename>distname.inf</filename> file <emphasis>must</emphasis> occupy the first
556 floppy of each distribution set.</para>
559 <para>Once you come to the Media screen of the install, select
560 <quote>Floppy</quote> and you'll be prompted for the rest.</para>
563 <sect3 arch="i386,pc98,amd64">
564 <title>Installing from a DOS partition</title>
566 <para arch="i386,amd64">To prepare for installation from an MS-DOS partition you
567 should simply copy the files from the distribution into a
568 directory called <filename>FREEBSD</filename> on the Primary DOS partition (<devicename>C:</devicename>). For example, to do a minimal installation of &os; from
569 DOS using files copied from the CDROM, you might do something
572 <para arch="pc98">To prepare for installation from an MS-DOS partition you
573 should simply copy the files from the distribution into a
574 directory called <filename>FREEBSD</filename> on the Primary DOS partition (<devicename>A:</devicename>). For example, to do a minimal installation of &os; from
575 DOS using files copied from the CDROM, you might do something
578 <screen arch="i386,amd64"><prompt>C:\></prompt> <userinput>MD C:\FREEBSD</userinput>
579 <prompt>C:\></prompt> <userinput>XCOPY /S E:\BASE C:\FREEBSD\BASE</userinput></screen>
580 <screen arch="pc98"><prompt>A:\></prompt> <userinput>MD A:\FREEBSD</userinput>
581 <prompt>A:\></prompt> <userinput>XCOPY /S E:\BASE A:\FREEBSD\BASE</userinput></screen>
583 <para>Assuming that <devicename>E:</devicename> was where your CD was mounted.</para>
585 <para arch="i386,amd64">For as many distributions as you wish to install from DOS (and
586 you have free space for), install each one in a directory under
587 <filename>C:\FREEBSD</filename> - the <filename>BIN</filename> dist is only the minimal requirement.</para>
589 <para arch="pc98">For as many distributions as you wish to install from DOS (and
590 you have free space for), install each one in a directory under
591 <filename>A:\FREEBSD</filename> - the <filename>BIN</filename> dist is only the minimal requirement.</para>
593 <para>Once you've copied the directories, you can simply launch
594 the installation from floppies as normal and select <quote>DOS</quote> as
595 your media type when the time comes.</para>
599 <title>Installing from QIC/SCSI Tape</title>
601 <para>When installing from tape, the installation program
602 expects the files to be simply tar'ed onto it, so after fetching
603 all of the files for the distributions you're interested in,
604 simply use &man.tar.1; to get them onto the tape with a command something like
607 <screen>&prompt.root; <userinput>cd <replaceable>/where/you/have/your/dists</replaceable></userinput>
608 &prompt.root; <userinput>tar cvf /dev/sa0 <replaceable>dist1</replaceable> .. <replaceable>dist2</replaceable></userinput></screen>
610 <para>When you go to do the installation, you should also make
611 sure that you leave enough room in some temporary directory
612 (which you'll be allowed to choose) to accommodate the <emphasis>full</emphasis>
613 contents of the tape you've created. Due to the non-random
614 access nature of tapes, this method of installation requires
615 quite a bit of temporary storage. You should expect to require
616 as much temporary storage as you have stuff written on tape.</para>
619 <para>When going to do the installation, the tape must be in
620 the drive <emphasis>before</emphasis> booting from the boot floppies. The
621 installation <quote>probe</quote> may otherwise fail to find it.</para>
624 <para>Now create a boot floppy as described in <xref linkend="floppies"> and
625 proceed with the installation.</para>
629 <title>Installing over a Network using FTP or NFS</title>
631 <para>After making the boot floppies as described in the first
632 section, you can load the rest of the installation over a
633 network using one of 3 types of connections: serial port,
634 parallel port, or Ethernet.</para>
637 <title>Serial Port</title>
639 <para>SLIP support is rather primitive, and is limited
640 primarily to hard-wired links, such as a serial cable running
641 between two computers. The link must be hard-wired because
642 the SLIP installation doesn't currently offer a dialing
643 capability. If you need to dial out with a modem or otherwise
644 dialog with the link before connecting to it, then the PPP
645 utility should be used instead.</para>
647 <para>If you're using PPP, make sure that you have your
648 Internet Service Provider's IP address and DNS information
649 handy as you'll need to know it fairly early in the
650 installation process. You may also need to know your own IP
651 address, though PPP supports dynamic address negotiation and
652 may be able to pick up this information directly from your ISP
653 if they support it.</para>
655 <para>You will also need to know how to use the various <quote>AT
656 commands</quote> for dialing out with your particular brand of modem
657 as the PPP dialer provides only a very simple terminal
662 <title>Parallel Port</title>
664 <para>If a hard-wired connection to another &os; or Linux
665 machine is available, you might also consider installing over
666 a <quote>laplink</quote> style parallel port cable. The data rate over the
667 parallel port is much higher than what is typically possible
668 over a serial line (up to 50k/sec), thus resulting in a
669 quicker installation. It's not typically necessary to use
670 <quote>real</quote> IP addresses when using a point-to-point parallel cable
671 in this way and you can generally just use RFC 1918 style
672 addresses for the ends of the link (e.g. <hostid
673 role="ipaddr">10.0.0.1</hostid>, <hostid role="ipaddr">10.0.0.2</hostid>,
677 <para>If you use a Linux machine rather than a &os;
678 machine as your PLIP peer, you will also have to specify
679 <option>link0</option> in the TCP/IP setup screen's <quote>extra options for
680 ifconfig</quote> field in order to be compatible with Linux's
681 slightly different PLIP protocol.</para>
687 <title>Ethernet</title>
689 <para>&os; supports most common Ethernet cards; a table
690 of supported cards is
691 provided as part of the &os; Hardware Notes (see
692 <filename>HARDWARE.TXT</filename> in
693 the Documentation menu on the boot floppy or the top level
694 directory of the CDROM). If you are using one of the
695 supported PCMCIA Ethernet cards, also be sure that it's
696 plugged in <emphasis>before</emphasis> the laptop is powered on. &os; does
697 not, unfortunately, currently support <quote>hot insertion</quote> of
698 PCMCIA cards during installation.</para>
700 <para>You will also need to know your IP address on the
701 network, the <option>netmask</option> value for your subnet and the
702 name of your machine. Your system administrator can tell you
703 which values are appropriate to your particular network setup.
704 If you will be referring to other hosts by name rather than IP
705 address, you'll also need a name server and possibly the
706 address of a gateway (if you're using PPP, it's your
707 provider's IP address) to use in talking to it. If you want
708 to install by FTP via an HTTP proxy (see below), you will also
709 need the proxy's address.</para>
711 <para>If you do not know the answers to these questions then
712 you should really probably talk to your system administrator
713 <emphasis>first</emphasis> before trying this type of
714 installation. Using a randomly chosen IP address or netmask
715 on a live network is almost guaranteed not to work, and will
716 probably result in a lecture from said system administrator.</para>
718 <para>Once you have a network connection of some sort working, the
719 installation can continue over NFS or FTP.</para>
723 <title>NFS installation tips</title>
725 <para>NFS installation is fairly straight-forward: Simply copy
726 the &os; distribution files you want onto a server
727 somewhere and then point the NFS media selection at it.</para>
729 <para>If this server supports only <quote>privileged port</quote> access (this is
730 generally the default for Sun and Linux workstations), you
731 may need to set this option in the Options menu before
732 installation can proceed.</para>
734 <para>If you have a poor quality Ethernet card which suffers from very
735 slow transfer rates, you may also wish to toggle the appropriate
738 <para>In order for NFS installation to work, the server must
739 also support <quote>subdir mounts</quote>, e.g. if your &os;
740 distribution directory lives on
741 <filename>wiggy:/usr/archive/stuff/FreeBSD</filename>, then
742 <hostid role="hostname">wiggy</hostid> will have to allow
743 the direct mounting of <filename>/usr/archive/stuff/FreeBSD</filename>, not just
744 <filename>/usr</filename> or <filename>/usr/archive/stuff</filename>.</para>
746 <para>In &os;'s <filename>/etc/exports</filename> file this is controlled by the
747 <option>-alldirs</option> option. Other NFS servers may have different
748 conventions. If you are getting <literal>Permission Denied</literal> messages
749 from the server then it's likely that you don't have this
750 properly enabled.</para>
754 <title>FTP Installation tips</title>
756 <para>FTP installation may be done from any mirror site containing a
757 reasonably up-to-date version of &os;. A full menu of
758 reasonable choices for almost any location in the world is
759 provided in the FTP site menu during installation.</para>
761 <para>If you are installing from some other FTP site not listed in
762 this menu, or you are having troubles getting your name server
763 configured properly, you can also specify your own URL by
764 selecting the <quote>URL</quote> choice in that menu. A URL can
765 contain a hostname or an IP address, so something like the following would
766 work in the absence of a name server:</para>
768 <screen>ftp://216.66.64.162/pub/FreeBSD/releases/&arch;/4.2-RELEASE</screen>
770 <para>There are three FTP installation modes you can use:
773 <para>FTP: This method uses the standard
774 <quote>Active</quote> mode for transfers, in which the
775 server initiates a connection to the client. This will
776 not work through most firewalls but will often work best
777 with older FTP servers that do not support passive mode.
778 If your connection hangs with passive mode, try this
782 <para>FTP Passive: This sets the FTP "Passive" mode
783 which prevents the server from opening connections to
784 the client. This option is best for users to pass
785 through firewalls that do not allow incoming connections
786 on random port addresses.</para>
789 <para>FTP via an HTTP proxy: This option instructs &os;
790 to use HTTP to connect to a proxy for all FTP
791 operations. The proxy will translate the requests and
792 send them to the FTP server. This allows the user to
793 pass through firewalls that do not allow FTP at all, but
794 offer an HTTP proxy. You must specify the hostname of
795 the proxy in addition to the FTP server.</para>
797 <para>In the rare case that you have an FTP proxy that
798 does not go through HTTP, you can specify the URL as
799 something like:</para>
801 <screen><userinput>ftp://foo.bar.com:<replaceable>port</replaceable>/pub/FreeBSD</userinput></screen>
803 <para>In the URL above, <replaceable>port</replaceable>
804 is the port number of the proxy FTP server.</para>
811 <sect3 arch="i386,alpha,amd64">
812 <title>Tips for Serial Console Users</title>
814 <para>If you'd like to install &os; on a machine using just a
815 serial port (e.g. you don't have or wish to use a VGA card),
816 please follow these steps:</para>
820 <para>Connect some sort of ANSI (vt100) compatible terminal
821 or terminal emulation program to the <devicename>COM1</devicename> port of the PC you
822 are installing &os; onto.</para>
825 <para>Unplug the keyboard (yes, that's correct!) and then
826 try to boot from floppy or the installation CDROM, depending
827 on the type of installation media you have, with the
828 keyboard unplugged.</para>
831 <para>If you don't get any output on your serial console,
832 plug the keyboard in again. If you are booting from the
833 CDROM, proceed to <xref linkend="hitspace"> as soon as you
834 hear the beep.</para>
837 <para>If booting from floppies, when access to the disk stops, insert
838 the first of the <filename>kern<replaceable>X</replaceable>.flp</filename> disks and press
839 <keycap>Enter</keycap>. When access to this disk finishes, insert
840 the next <filename>kern<replaceable>X</replaceable>.flp</filename> disk and press <keycap>Enter</keycap>,
841 and repeat until all <filename>kern<replaceable>X</replaceable>.flp</filename> disks have been
842 inserted. When disk activity finishes, reinsert the <filename>boot.flp</filename>
843 floppy disk and press <keycap>Enter</keycap>.</para>
846 <para>Once a beep is heard, hit the number <keycap>6</keycap>, then enter</para>
848 <screen><userinput>boot -h</userinput></screen>
850 <para>and you should now definitely be seeing everything on
851 the serial port. If that still doesn't work, check your
852 serial cabling as well as the settings on your terminal
853 emulation program or actual terminal device. It should be
854 set for 9600 baud, 8 bits, no parity.</para>
861 <title>Question and Answer Section for &arch.print; Architecture Users</title>
863 <qandaset arch="i386,amd64">
866 <para>Help! I have no space! Do I need to delete
867 everything first?</para>
870 <para>If your machine is already running DOS and has little
871 or no free space available for &os;'s installation, all is
872 not lost! You may find the <application>FIPS</application>
873 utility, provided in the <filename>tools/</filename>
874 subdirectory on the &os; CDROM or on the various &os; ftp
875 sites, to be quite useful.</para>
877 <para><application>FIPS</application> allows you to split an
878 existing DOS partition into two pieces, preserving the
879 original partition and allowing you to install onto the
880 second free piece. You first <quote>defrag</quote> your DOS
881 partition, using the DOS 6.xx <filename>DEFRAG</filename>
882 utility or the <application>Norton Disk Tools</application>,
883 then run FIPS. It will
884 prompt you for the rest of the information it needs.
885 Afterwards, you can reboot and install &os; on the new
886 partition. Also note that FIPS will create the second
887 partition as a <quote>clone</quote> of the first, so you'll
888 actually see that you now have two DOS Primary partitions
889 where you formerly had one. Don't be alarmed! You can
890 simply delete the extra DOS Primary partition (making sure
891 it's the right one by examining its size).</para>
893 <para><application>FIPS</application> does NOT currently
894 work with NTFS style partitions. To split up such a
895 partition, you will need a commercial product such as
896 <application>Partition Magic</application>. Sorry, but this
897 is just the breaks if you've got a Windows partition hogging
898 your whole disk and you don't want to reinstall from
901 <para><application>FIPS</application> does not work on
902 extended DOS partitions. Windows 95/98/ME FAT32 primary
903 partitions are supported.</para>
910 <para>Can I use compressed DOS filesystems from
915 <para>No. If you are using a utility such as
916 <application>Stacker</application>(tm) or
917 <application>DoubleSpace</application>(tm), &os; will only
918 be able to use whatever portion of the filesystem you leave
919 uncompressed. The rest of the filesystem will show up as
920 one large file (the stacked/dblspaced file!). <emphasis>Do
921 not remove that file</emphasis> as you will probably regret
924 <para>It is probably better to create another uncompressed DOS
925 extended partition and use this for communications between
926 DOS and &os; if such is your desire.</para>
932 <para>Can I mount my DOS extended partitions?</para>
936 <para>Yes. DOS extended partitions are mapped in at the end
937 of the other <quote>slices</quote> in &os;, e.g. your <devicename>D:</devicename> drive might
938 be <filename>/dev/da0s5</filename>, your <devicename>E:</devicename> drive <filename>/dev/da0s6</filename>, and so on. This
939 example assumes, of course, that your extended partition is
940 on SCSI drive 0. For IDE drives, substitute <literal>ad</literal> for
941 <literal>da</literal> appropriately. You otherwise mount extended
942 partitions exactly like you would mount any other DOS drive,
945 <screen>&prompt.root; <userinput>mount -t msdos /dev/da0s5 /dos_d</userinput></screen>
951 <para>Can I run DOS binaries under &os;?</para>
955 <para>Ongoing work with BSDI's &man.doscmd.1; utility will
956 suffice in many cases, though
957 it still has some rough edges. The
958 <filename role="package">emulators/doscmd</filename> port/package
959 can be found in the &os; Ports Collection.
960 If you're interested in
961 working on this, please send mail to the &a.emulation;
962 and indicate that you're interested in joining this ongoing
965 <para>The <filename role="package">emulators/pcemu</filename> port/package in the
966 &os; Ports Collection which emulates an 8088 and enough BIOS
967 services to run DOS text mode applications. It requires the
968 X Window System (XFree86) to operate.</para>
974 <para>Can I run µsoft.windows; applications under &os;?</para>
978 <para>There are several ports/packages in the &os; Ports Collection
979 which can enable the use of many &windows; applications.
980 The <filename role="package">emulators/wine</filename> port/package
981 provides a compatibility layer on top of &os; which allow many
982 &windows; applications to be run within X Windows (XFree86).
988 <para>Can I run other Operating Systems under &os;?</para>
992 <para>Again, there are several ports/packages in the &os; Ports Collection
993 which simulate "virtual machines" and allow other operating systems to run
995 The <filename role="package">emulators/bochs</filename> port/package
996 allows µsoft.windows;, Linux and even other copies of &os; to be run within a
997 window on the &os; desktop.
998 The <filename role="package">emulators/vmware2</filename> and
999 <filename role="package">emulators/vmware3</filename> ports/packages
1000 allow the commercial VMware virtual machine software to be run on &os;.</para>
1005 <qandaset arch="alpha">
1008 <para>Can I boot from the ARC or Alpha BIOS Console?</para>
1012 <para>No. &os;, like Compaq Tru64 and VMS, will only boot
1013 from the SRM console.</para>
1019 <para>Help! I have no space! Do I need to delete
1020 everything first?</para>
1024 <para>Unfortunately, yes.</para>
1030 <para>Can I mount my Compaq Tru64 or VMS extended partitions?</para>
1034 <para>No, not at this time.</para>
1040 <para>What about support for Compaq Tru64 (OSF/1) binaries?</para>
1044 <para>&os; can run Tru64 applications very well using the
1045 <filename role="package">emulators/osf1_base</filename> port/package.</para>
1051 <para>What about support for Linux binaries?</para>
1055 <para>&os; can run AlphaLinux binaries with the assistance
1056 of the <filename role="package">emulators/linux_base</filename>
1057 port/package.</para>
1063 <para>What about support for NT Alpha binaries?</para>
1067 <para>&os; is not able to run NT applications natively,
1068 although it has the ability to mount NT partitions.</para>