3 $FreeBSD: src/release/doc/en_US.ISO8859-1/installation/common/install.sgml,v 1.1.2.13 2003/02/15 00:36:58 bmah Exp $
4 $DragonFly: src/release/doc/en_US.ISO8859-1/installation/common/Attic/install.sgml,v 1.2 2003/06/17 04:27:19 dillon Exp $
8 This file has architecture-dependent installation instructions, culled
9 from {alpha,i386}/INSTALL.TXT.
14 <title>Installing &os;</title>
16 <para>This section documents the process of installing a new
17 distribution of &os;. These instructions pay particular emphasis to
18 the process of obtaining the &os; &release.current; distribution and
19 to beginning the installation procedure. The <ulink
20 url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html"><quote>Installing
21 FreeBSD</quote></ulink>
23 url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/">FreeBSD
24 Handbook</ulink> provides more in-depth information about the
25 installation program itself, including a guided walkthrough with
28 <para>If you are upgrading from a previous release
29 of &os;, please see <xref linkend="upgrading"> for instructions on
32 <sect2 id="getting-started">
33 <title>Getting Started</title>
35 <para>Probably the most important pre-installation step that can
36 be taken is that of reading the various instruction documents
37 provided with &os;. A roadmap of documents pertaining to this
38 release of &os; can be found in <filename>README.TXT</filename>,
39 which can usually be found in the same location as this file; most
40 of these documents, such as the release notes and the hardware
41 compatability list, are also accessible in the Documentation menu
42 of the installer.</para>
44 <para>Note that on-line versions of the &os; <ulink
45 url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/">FAQ</ulink> and <ulink
46 url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/">Handbook</ulink> are also
47 available from the <ulink url="http://www.FreeBSD.org/">FreeBSD
48 Project Web site</ulink>, if you have an Internet
51 <para>This collection of documents may seem daunting, but the time
52 spent reading them will likely be saved many times over. Being
53 familiar with what resources are available can also be helpful in
54 the event of problems during installation.</para>
56 <para>The best laid plans sometimes go awry, so if you run into
57 trouble take a look at <xref linkend="trouble">, which contains
58 valuable troubleshooting information. You should also read
60 <filename>ERRATA.TXT</filename> before installing,
61 since this will alert you to
62 any problems which have reported in the interim for your
63 particular release.</para>
66 <para>While &os; does its best to safeguard against
67 accidental loss of data, it's still more than possible to
68 <emphasis>wipe out your entire disk</emphasis>
69 with this installation if you make a
70 mistake. Please do not proceed to the final &os;
71 installation menu unless you've adequately backed up any
72 important data first.</para>
76 <title>Hardware Requirements</title>
78 <para arch="i386">&os; for the &arch.print; requires an 80386 or better
79 processor. The &man.sysinstall.8; installation program requires
80 16MB of RAM; after installation, &os; itself can be run in
81 4–8MB of RAM with a pared-down kernel.
82 You will need at least 100MB of free hard drive space for the
83 most minimal installation; a more realistic minimum is on the
84 order of 250–350MB. See below for ways of shrinking
85 existing DOS partitions in order to install &os;.</para>
87 <para arch="alpha">&os; for the &arch.print; supports the platforms
88 described in <filename>HARDWARE.TXT</filename>.</para>
90 <para arch="alpha">You will need a dedicated disk for
91 &os;/alpha. It is not possible to share a disk with another
92 operating system at this time. This disk will need to be attached
93 to a SCSI controller which is supported by the SRM firmware or an
94 IDE disk assuming the SRM in your machine supports booting from
97 <para arch="alpha">Your root filesystem MUST be the first
98 partition (partition <literal>a</literal>) on the disk to be
101 <para arch="alpha">You will need the SRM console firmware for your
102 platform. In some cases, it is possible to switch between
103 AlphaBIOS (or ARC) firmware and SRM. In others it will be
104 necessary to download new firmware from the vendor's Web
108 not familiar with configuring hardware for &os;, you should
109 be sure to read the <filename>HARDWARE.TXT</filename> file;
110 it contains important
111 information on what hardware is supported by &os;.</para>
114 <sect2 id="floppies">
115 <title>Floppy Disk Image Instructions</title>
117 <para>Depending on how you choose to install &os;, you may need to
118 create a set of floppy disks (usually two) to begin the installation
119 process. This section briefly describes how to create these disks,
120 either from a CDROM installation or from the Internet. Note that in
121 the common case of installing &os; from CDROM, on a machine that
122 supports bootable CDROMs, the steps outlined in this section will
123 not be needed and can be skipped.</para>
125 <para>For a normal CDROM or network installation, all you need to
126 copy onto actual floppies from the <filename>floppies/</filename> directory are the
127 <filename>kern.flp</filename> and <filename>mfsroot.flp</filename>
128 images (for 1.44MB floppies).</para>
130 <para>Getting these images over the network is easy. Simply fetch
132 <replaceable>release</replaceable><filename>/floppies/kern.flp</filename>
134 <replaceable>release</replaceable><filename>/floppies/mfsroot.flp</filename>
136 url="&release.url;"></ulink>
137 or one of the many mirrors listed at <ulink
138 url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html">FTP
139 Sites</ulink> section of the Handbook, or on the
140 <ulink url="http://www.freebsdmirrors.org/"></ulink> Web pages.
143 <para>Get two blank, freshly formatted floppies and image copy
144 <filename>kern.flp</filename> onto one and <filename>mfsroot.flp</filename> onto the other. These images are
145 <emphasis>not</emphasis> DOS files. You cannot simply copy them to a DOS or UFS floppy
146 as regular files, you need to <quote>image</quote> copy them to the floppy with
147 <filename>fdimage.exe</filename> under DOS (see the
148 <filename>tools</filename> directory on your CDROM or &os; FTP
149 mirror) or the &man.dd.1; command in UNIX.</para>
151 <para>For example, to create the kernel floppy image from DOS, you'd
152 do something like this:</para>
154 <screen><prompt>C></prompt> <userinput>fdimage kern.flp a:</userinput></screen>
156 <para>Assuming that you'd copied <filename>fdimage.exe</filename> and <filename>kern.flp</filename> into a directory
157 somewhere. You would do the same for <filename>mfsroot.flp</filename>, of course.</para>
159 <para>If you're creating the boot floppy from a UNIX machine, you
160 may find that:</para>
162 <screen>&prompt.root; <userinput>dd if=floppies/kern.flp of=/dev/rfd0</userinput></screen>
166 <screen>&prompt.root; <userinput>dd if=floppies/kern.flp of=/dev/floppy</userinput></screen>
168 <para>work well, depending on your hardware and operating system
169 environment (different versions of UNIX have different names
170 for the floppy drive).</para>
172 <para arch="alpha">If you're on an alpha machine that can network-boot its
173 floppy images or you have a 2.88MB or LS-120 floppy capable of
174 taking a 2.88MB image on an x86 machine, you may wish to use
175 the single (but twice as large) <filename>boot.flp</filename> image.
176 It contains the contents of <filename>kern.flp</filename> and <filename>mfsroot.flp</filename> on
177 a single floppy. This file should also be used as the
178 boot file for those mastering <quote>El Torito</quote> bootable CD images. See
179 the &man.mkisofs.8; command for more information.</para>
182 <sect2 id="start-installation">
183 <title>Installing &os; from CDROM or the Internet</title>
185 <para arch="i386">The easiest type of installation is from
186 CDROM. If you have a supported CDROM drive and a &os;
187 installation CDROM, there are 2 ways of starting the
188 installation from it:
191 <para>If your system supports bootable CDROM media
192 (usually an option which can be selectively enabled in the
193 controller's setup menu or in the PC BIOS for some
194 systems) and you have it enabled, &os; supports the
195 <quote>El Torrito</quote> bootable CD standard. Simply
196 put the installation CD in your CDROM drive and boot the
197 system to begin installation.</para>
200 <para>Build a set of &os; boot floppies from the
201 <filename>floppies/</filename> directory in every &os;
202 distribution. Either simply use the
203 <filename>makeflp.bat</filename> script from DOS or read
204 <xref linkend="floppies"> for more information on creating
205 the bootable floppies under different operating systems.
206 Then you simply boot from the first floppy and you should
207 soon be in the &os; installation.</para>
212 <para arch="i386">If you don't have a CDROM (or your computer does not
213 support booting from CDROM) and would like to simply install
214 over the net using PPP, SLIP or a dedicated connection.
215 You should start the installation by building
216 a set of &os; boot floppies from the files
217 <filename>floppies/kern.flp</filename> and
218 <filename>floppies/mfsroot.flp</filename> using the instructions
219 found in <xref linkend="floppies">. Restart your computer using
220 the <filename>kern.flp</filename> disk; when prompted, insert
221 the <filename>mfsroot.flp</filename> disk. Then, please go to
222 <xref linkend="ftpnfs"> for additional tips on installing
223 via FTP or NFS.</para>
225 <para arch="alpha">The easiest type of installation is from
226 CDROM. If you have a supported CDROM drive and a &os;
227 installation CDROM, you can boot &os; directly from the
228 CDROM. Insert the CDROM into the drive and type the following
229 command to start the installation (substituting the name of the
230 appropriate CDROM drive if necessary):</para>
232 <screen arch="alpha">>>><userinput>boot dka0</userinput></screen>
234 <para arch="alpha">Alternatively you can boot the installation
235 from floppy disk. You should start the installation by building
236 a set of &os; boot floppies from the files
237 <filename>floppies/kern.flp</filename> and
238 <filename>floppies/mfsroot.flp</filename> using the instructions
239 found in <xref linkend="floppies">. From the SRM console prompt
240 (<literal>>>></literal>), just insert the
241 <filename>kern.flp</filename> floppy and type the following
242 command to start the installation:</para>
244 <screen arch="alpha">>>><userinput>boot dva0</userinput></screen>
246 <para arch="alpha">Insert the <filename>mfsroot.flp</filename>
247 floppy when prompted and you will end up at the first screen of
248 the install program.</para>
251 <title>Detail on various installation types</title>
253 <para>Once you've gotten yourself to the initial installation
254 screen somehow, you should be able to follow the various menu
255 prompts and go from there. If you've never used the &os;
256 installation before, you are also encouraged to read some of the
257 documentation in the Documentation submenu as well as the
258 general <quote>Usage</quote> instructions on the first menu.</para>
261 <para>If you get stuck at a screen, press the <keycap>F1</keycap> key for online
262 documentation relevant to that specific section.</para>
265 <para>If you've never installed &os; before, or even if you
266 have, the <quote>Standard</quote> installation mode is the most recommended
267 since it makes sure that you'll visit all the various important
268 checklist items along the way. If you're much more comfortable
269 with the &os; installation process and know <emphasis>exactly</emphasis> what you
270 want to do, use the <quote>Express</quote> or <quote>Custom</quote> installation options. If
271 you're upgrading an existing system, use the <quote>Upgrade</quote> option.</para>
273 <para>The &os; installer supports the direct use of floppy,
274 DOS, tape, CDROM, FTP, NFS and UFS partitions as installation
275 media; further tips on installing from each type of media are listed
278 <para arch="alpha">Once the install procedure has finished, you will be able
279 to start &os;/&arch; by typing something like this to the SRM
282 <screen arch="alpha">>>><userinput>boot dkc0</userinput></screen>
284 <para arch="alpha">This instructs the firmware to boot the specified disk. To
285 find the SRM names of disks in your machine, use the <literal>show
286 device</literal> command:</para>
288 <screen arch="alpha">>>><userinput>show device</userinput>
289 dka0.0.0.4.0 DKA0 TOSHIBA CD-ROM XM-57 3476
290 dkc0.0.0.1009.0 DKC0 RZ1BB-BS 0658
291 dkc100.1.0.1009.0 DKC100 SEAGATE ST34501W 0015
293 ewa0.0.0.3.0 EWA0 00-00-F8-75-6D-01
294 pkc0.7.0.1009.0 PKC0 SCSI Bus ID 7 5.27
295 pqa0.0.0.4.0 PQA0 PCI EIDE
296 pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
298 <para arch="alpha">This example is from a Digital Personal Workstation 433au
299 and shows three disks attached to the machine. The first is a
300 CDROM called <devicename>dka0</devicename> and the other two are
301 disks and are called <devicename>dkc0</devicename> and
302 <devicename>dkc100</devicename> repectively.</para>
304 <para arch="alpha">You can specify which kernel file to load and what boot
305 options to use with the <option>-file</option> and
306 <option>-flags</option> options, for example:</para>
308 <screen arch="alpha"><prompt>>>></prompt> <userinput>boot -file kernel.old -flags s</userinput></screen>
310 <para arch="alpha">To make &os;/&arch; boot automatically, use these commands:</para>
312 <screen arch="alpha"><prompt>>>></prompt> <userinput>set boot_osflags a</userinput>
313 <prompt>>>></prompt> <userinput>set bootdef_dev dkc0</userinput>
314 <prompt>>>></prompt> <userinput>set auto_action BOOT</userinput></screen>
317 <title>Installing from a Network CDROM</title>
319 <para>If you simply wish to install from a local CDROM drive
320 then see <xref linkend="start-installation">. If you don't have a CDROM
321 drive on your system and wish to use a &os; distribution CD
322 in the CDROM drive of another system to which you have network
323 connectivity, there are also several ways of going about it:</para>
327 <para>If you would be able to FTP install &os; directly
328 from the CDROM drive in some &os; machine, it's quite
329 easy: You simply add the following line to the password file
330 (using the &man.vipw.8; command):</para>
332 <screen>ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin</screen>
334 <para>On the machine on which you are running the install,
335 go to the Options menu and set Release Name to
336 <literal>any</literal>. You may then choose a Media type of
337 <literal>FTP</literal> and type in
338 <filename>ftp://<replaceable>machine</replaceable></filename>
339 after picking <quote>URL</quote> in the ftp sites
343 <para>This may allow anyone on the local network (or Internet) to
344 make <quote>anonymous FTP</quote> connections to this
345 machine, which may not be desirable.</para>
350 <para>If you would rather use NFS to export the CDROM
351 directly to the machine(s) you'll be installing from, you
352 need to first add an entry to the
353 <filename>/etc/exports</filename> file (on the machine with
354 the CDROM drive). The example below allows the machine
355 <hostid role="hostname">ziggy.foo.com</hostid> to mount the
356 CDROM directly via NFS during installation:</para>
358 <screen>/cdrom -ro ziggy.foo.com</screen>
361 with the CDROM must also be configured as an NFS server, of
362 course, and if you're not sure how to do that then an NFS
363 installation is probably not the best choice for you unless
364 you're willing to read up on &man.rc.conf.5; and configure things
365 appropriately. Assuming that this part goes smoothly, you
366 should be able to enter: <filename><replaceable>cdrom-host</replaceable>:/cdrom</filename> as the path for
367 an NFS installation when the target machine is installed,
368 e.g. <filename>wiggy:/cdrom</filename>.</para>
374 <title>Installing from Floppies</title>
376 <para>If you must install from floppy disks, either due to
377 unsupported hardware or just because you enjoy doing things the
378 hard way, you must first prepare some floppies for the
381 <para>First, make your boot floppies as described in
382 <xref linkend="floppies">.</para>
384 <para>Second, peruse <xref linkend="layout"> and pay special attention
385 to the <quote>Distribution Format</quote> section since it describes which
386 files you're going to need to put onto floppy and which you can
389 <para>Next you will need, at minimum, as many 1.44MB floppies as
390 it takes to hold all files in the <filename>bin</filename>
391 (binary distribution) directory. If you're preparing these
392 floppies under DOS, then these floppies
393 <emphasis>must</emphasis> be formatted using the MS-DOS
394 <filename>FORMAT</filename> command. If you're using Windows,
395 use the Windows File Manager format command.</para>
398 <para>Frequently, floppy disks come <quote>factory
399 preformatted</quote>. While convenient,
400 many problems reported by users in the past have resulted
401 from the use of improperly formatted media.
402 Re-format them yourself, just to make sure.</para>
405 <para>If you're creating the floppies from another &os;
406 machine, a format is still not a bad idea though you don't need
407 to put a DOS filesystem on each floppy. You can use the
408 &man.disklabel.8; and &man.newfs.8; commands to put a UFS filesystem on a
409 floppy, as the following sequence of commands
412 <screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput>
413 &prompt.root; <userinput>disklabel -w -r fd0.1440 floppy3</userinput>
414 &prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</userinput></screen>
416 <para>After you've formatted the floppies for DOS or UFS, you'll
417 need to copy the files onto them. The distribution files are
418 split into chunks conveniently sized so that 5 of them will fit
419 on a conventional 1.44MB floppy. Go through all your floppies,
420 packing as many files as will fit on each one, until you've got
421 all the distributions you want packed up in this fashion. Each
422 distribution should go into its own subdirectory on the floppy,
423 e.g.: <filename>a:\bin\bin.inf</filename>, <filename>a:\bin\bin.aa</filename>, <filename>a:\bin\bin.ab</filename>, ...</para>
426 <para>The <filename>bin.inf</filename> file also needs to go on the first floppy of
427 the <filename>bin</filename> set since it is read by the installation program in
428 order to figure out how many additional pieces to look for
429 when fetching and concatenating the distribution. When
430 putting distributions onto floppies, the
431 <filename>distname.inf</filename> file <emphasis>must</emphasis> occupy the first
432 floppy of each distribution set. This is also covered in
433 <filename>README.TXT</filename>.</para>
436 <para>Once you come to the Media screen of the install, select
437 <quote>Floppy</quote> and you'll be prompted for the rest.</para>
441 <title>Installing from a DOS partition</title>
443 <para>To prepare for installation from an MS-DOS partition you
444 should simply copy the files from the distribution into a
445 directory called <filename>FREEBSD</filename> on the Primary DOS partition (<devicename>C:</devicename>). For example, to do a minimal installation of &os; from
446 DOS using files copied from the CDROM, you might do something
449 <screen><prompt>C:\></prompt> <userinput>MD C:\FREEBSD</userinput>
450 <prompt>C:\></prompt> <userinput>XCOPY /S E:\BIN C:\FREEBSD\BIN</userinput></screen>
452 <para>Assuming that <devicename>E:</devicename> was where your CD was mounted.</para>
454 <para>For as many distributions as you wish to install from DOS (and
455 you have free space for), install each one in a directory under
456 <filename>C:\FREEBSD</filename> - the <filename>BIN</filename> dist is only the minimal requirement.</para>
458 <para>Once you've copied the directories, you can simply launch
459 the installation from floppies as normal and select <quote>DOS</quote> as
460 your media type when the time comes.</para>
464 <title>Installing from QIC/SCSI Tape</title>
466 <para>When installing from tape, the installation program
467 expects the files to be simply tar'ed onto it, so after fetching
468 all of the files for the distributions you're interested in,
469 simply use &man.tar.1; to get them onto the tape with a command something like
472 <screen>&prompt.root; <userinput>cd <replaceable>/where/you/have/your/dists</replaceable></userinput>
473 &prompt.root; <userinput>tar cvf /dev/rsa0 <replaceable>dist1</replaceable> .. <replaceable>dist2</replaceable></userinput></screen>
475 <para>When you go to do the installation, you should also make
476 sure that you leave enough room in some temporary directory
477 (which you'll be allowed to choose) to accommodate the <emphasis>full</emphasis>
478 contents of the tape you've created. Due to the non-random
479 access nature of tapes, this method of installation requires
480 quite a bit of temporary storage. You should expect to require
481 as much temporary storage as you have stuff written on tape.</para>
484 <para>When going to do the installation, the tape must be in
485 the drive <emphasis>before</emphasis> booting from the boot floppies. The
486 installation <quote>probe</quote> may otherwise fail to find it.</para>
489 <para>Now create a boot floppy as described in <xref linkend="floppies"> and
490 proceed with the installation.</para>
494 <title>Installing over a Network using FTP or NFS</title>
496 <para>After making the boot floppies as described in the first
497 section, you can load the rest of the installation over a
498 network using one of 3 types of connections: serial port,
499 parallel port, or Ethernet.</para>
502 <title>Serial Port</title>
504 <para>SLIP support is rather primitive, and is limited
505 primarily to hard-wired links, such as a serial cable running
506 between two computers. The link must be hard-wired because
507 the SLIP installation doesn't currently offer a dialing
508 capability. If you need to dial out with a modem or otherwise
509 dialog with the link before connecting to it, then I recommend
510 that the PPP utility be used instead.</para>
512 <para>If you're using PPP, make sure that you have your
513 Internet Service Provider's IP address and DNS information
514 handy as you'll need to know it fairly early in the
515 installation process. You may also need to know your own IP
516 address, though PPP supports dynamic address negotiation and
517 may be able to pick up this information directly from your ISP
518 if they support it.</para>
520 <para>You will also need to know how to use the various <quote>AT
521 commands</quote> for dialing out with your particular brand of modem
522 as the PPP dialer provides only a very simple terminal
527 <title>Parallel Port</title>
529 <para>If a hard-wired connection to another &os; or Linux
530 machine is available, you might also consider installing over
531 a <quote>laplink</quote> style parallel port cable. The data rate over the
532 parallel port is much higher than what is typically possible
533 over a serial line (up to 50k/sec), thus resulting in a
534 quicker installation. It's not typically necessary to use
535 <quote>real</quote> IP addresses when using a point-to-point parallel cable
536 in this way and you can generally just use RFC 1918 style
537 addresses for the ends of the link (e.g. <hostid
538 role="ipaddr">10.0.0.1</hostid>, <hostid role="ipaddr">10.0.0.2</hostid>,
542 <para>If you use a Linux machine rather than a &os;
543 machine as your PLIP peer, you will also have to specify
544 <option>link0</option> in the TCP/IP setup screen's <quote>extra options for
545 ifconfig</quote> field in order to be compatible with Linux's
546 slightly different PLIP protocol.</para>
552 <title>Ethernet</title>
554 <para>&os; supports many common Ethernet cards; a table
555 of supported cards is
556 provided as part of the &os; Hardware Notes (see
557 <filename>HARDWARE.TXT</filename> in
558 the Documentation menu on the boot floppy or the top level
559 directory of the CDROM). If you are using one of the
560 supported PCMCIA Ethernet cards, also be sure that it's
561 plugged in <emphasis>before</emphasis> the laptop is powered on. &os; does
562 not, unfortunately, currently support <quote>hot insertion</quote> of
563 PCMCIA cards during installation.</para>
565 <para>You will also need to know your IP address on the
566 network, the <option>netmask</option> value for your subnet and the
567 name of your machine. Your system administrator can tell you
568 which values are appropriate to your particular network setup.
569 If you will be referring to other hosts by name rather than IP
570 address, you'll also need a name server and possibly the
571 address of a gateway (if you're using PPP, it's your
572 provider's IP address) to use in talking to it. If you want
573 to install by FTP via an HTTP proxy (see below), you will also
574 need the proxy's address.</para>
576 <para>If you do not know the answers to these questions then
577 you should really probably talk to your system administrator
578 <emphasis>first</emphasis> before trying this type of
579 installation. Using a randomly chosen IP address or netmask
580 on a live network is almost guaranteed not to work, and will
581 probably result in a lecture from said system administrator.</para>
583 <para>Once you have a network connection of some sort working, the
584 installation can continue over NFS or FTP.</para>
588 <title>NFS installation tips</title>
590 <para>NFS installation is fairly straight-forward: Simply copy
591 the &os; distribution files you want onto a server
592 somewhere and then point the NFS media selection at it.</para>
594 <para>If this server supports only <quote>privileged port</quote> access (this is
595 generally the default for Sun and Linux workstations), you
596 will need to set this option in the Options menu before
597 installation can proceed.</para>
599 <para>If you have a poor quality Ethernet card which suffers from very
600 slow transfer rates, you may also wish to toggle the appropriate
603 <para>In order for NFS installation to work, the server must
604 also support <quote>subdir mounts</quote>, e.g. if your &os;
605 distribution directory lives on
606 <filename>wiggy:/usr/archive/stuff/FreeBSD</filename>, then
607 <hostid role="hostname">wiggy</hostid> will have to allow
608 the direct mounting of <filename>/usr/archive/stuff/FreeBSD</filename>, not just
609 <filename>/usr</filename> or <filename>/usr/archive/stuff</filename>.</para>
611 <para>In &os;'s <filename>/etc/exports</filename> file this is controlled by the
612 <option>-alldirs</option> option. Other NFS servers may have different
613 conventions. If you are getting <literal>Permission Denied</literal> messages
614 from the server then it's likely that you don't have this
615 properly enabled.</para>
619 <title>FTP Installation tips</title>
621 <para>FTP installation may be done from any mirror site containing a
622 reasonably up-to-date version of &os;. A full menu of
623 reasonable choices for almost any location in the world is
624 provided in the FTP site menu during installation.</para>
626 <para>If you are installing from some other FTP site not listed in
627 this menu, or you are having troubles getting your name server
628 configured properly, you can also specify your own URL by
629 selecting the <quote>URL</quote> choice in that menu. A URL can
630 contain a hostname or an IP address, so something like the following would
631 work in the absence of a name server:</para>
633 <screen>ftp://216.66.64.162/pub/FreeBSD/releases/&arch;/4.2-RELEASE</screen>
635 <para>There are three FTP installation modes you can use:
638 <para>FTP: This method uses the standard
639 <quote>Active</quote> mode for transfers, in which the
640 server initiates a connection to the client. This will
641 not work through most firewalls but will often work best
642 with older FTP servers that do not support passive mode.
643 If your connection hangs with passive mode, try this
647 <para>FTP Passive: This sets the FTP "Passive" mode
648 which prevents the server from opening connections to
649 the client. This option is best for users to pass
650 through firewalls that do not allow incoming connections
651 on random port addresses.</para>
654 <para>FTP via an HTTP proxy: This option instructs &os;
655 to use HTTP to connect to a proxy for all FTP
656 operations. The proxy will translate the requests and
657 send them to the FTP server. This allows the user to
658 pass through firewalls that do not allow FTP at all, but
659 offer an HTTP proxy. You must specify the hostname of
660 the proxy in addition to the FTP server.</para>
662 <para>In the rare case that you have an FTP proxy that
663 does not go through HTTP, you can specify the URL as
664 something like:</para>
666 <screen><userinput>ftp://foo.bar.com:<replaceable>port</replaceable>/pub/FreeBSD</userinput></screen>
668 <para>In the URL above, <replaceable>port</replaceable>
669 is the port number of the proxy FTP server.</para>
676 <title>Tips for Serial Console Users</title>
678 <para>If you'd like to install &os; on a machine using just a
679 serial port (e.g. you don't have or wish to use a VGA card),
680 please follow these steps:</para>
684 <para>Connect some sort of ANSI (vt100) compatible terminal
685 or terminal emulation program to the <devicename>COM1</devicename> port of the PC you
686 are installing &os; onto.</para>
689 <para>Unplug the keyboard (yes, that's correct!) and then
690 try to boot from floppy or the installation CDROM, depending
691 on the type of installation media you have, with the
692 keyboard unplugged.</para>
695 <para>If you don't get any output on your serial console,
696 plug the keyboard in again and wait for some beeps. If you
697 are booting from the CDROM, proceed to <xref
698 linkend="hitspace"> as soon as you
699 hear the beep.</para>
702 <para>For a floppy boot, the first beep means to remove the
703 <filename>kern.flp</filename> floppy and insert the
704 <filename>mfsroot.flp</filename> floppy, after
705 which you should press <keycap>Enter</keycap> and wait for another beep.</para>
708 <para>Hit the space bar, then enter</para>
710 <screen><userinput>boot -h</userinput></screen>
712 <para>and you should now definitely be seeing everything on
713 the serial port. If that still doesn't work, check your
714 serial cabling as well as the settings on your terminal
715 emulation program or actual terminal device. It should be
716 set for 9600 baud, 8 bits, no parity.</para>
723 <title>Question and Answer Section for &arch.print; Architecture Users</title>
725 <qandaset arch="i386">
728 <para>Help! I have no space! Do I need to delete
729 everything first?</para>
732 <para>If your machine is already running DOS and has little
733 or no free space available for &os;'s installation, all is
734 not lost! You may find the <application>FIPS</application>
735 utility, provided in the <filename>tools/</filename>
736 subdirectory on the &os; CDROM or on the various &os; ftp
737 sites, to be quite useful.</para>
739 <para><application>FIPS</application> allows you to split an
740 existing DOS partition into two pieces, preserving the
741 original partition and allowing you to install onto the
742 second free piece. You first <quote>defrag</quote> your DOS
743 partition, using the DOS 6.xx <filename>DEFRAG</filename>
744 utility or the <application>Norton Disk Tools</application>,
745 then run FIPS. It will
746 prompt you for the rest of the information it needs.
747 Afterwards, you can reboot and install &os; on the new
748 partition. Also note that FIPS will create the second
749 partition as a <quote>clone</quote> of the first, so you'll
750 actually see that you now have two DOS Primary partitions
751 where you formerly had one. Don't be alarmed! You can
752 simply delete the extra DOS Primary partition (making sure
753 it's the right one by examining its size).</para>
755 <para><application>FIPS</application> does NOT currently
756 work with NTFS style partitions. To split up such a
757 partition, you will need a commercial product such as
758 <application>Partition Magic</application>. Sorry, but this
759 is just the breaks if you've got a Windows partition hogging
760 your whole disk and you don't want to reinstall from
768 <para>Can I use compressed DOS filesystems from
773 <para>No. If you are using a utility such as
774 <application>Stacker</application>(tm) or
775 <application>DoubleSpace</application>(tm), &os; will only
776 be able to use whatever portion of the filesystem you leave
777 uncompressed. The rest of the filesystem will show up as
778 one large file (the stacked/dblspaced file!). <emphasis>Do
779 not remove that file</emphasis> as you will probably regret
782 <para>It is probably better to create another uncompressed DOS
783 extended partition and use this for communications between
784 DOS and &os; if such is your desire.</para>
790 <para>Can I mount my DOS extended partitions?</para>
794 <para>Yes. DOS extended partitions are mapped in at the end
795 of the other <quote>slices</quote> in &os;, e.g. your <devicename>D:</devicename> drive might
796 be <filename>/dev/da0s5</filename>, your <devicename>E:</devicename> drive <filename>/dev/da0s6</filename>, and so on. This
797 example assumes, of course, that your extended partition is
798 on SCSI drive 0. For IDE drives, substitute <literal>ad</literal> for
799 <literal>da</literal> appropriately. You otherwise mount extended
800 partitions exactly like you would mount any other DOS drive,
803 <screen>&prompt.root; <userinput>mount -t msdos /dev/da0s5 /dos_d</userinput></screen>
809 <para>Can I run DOS binaries under &os;?</para>
813 <para>Ongoing work with BSDI's &man.doscmd.1; utility will
814 suffice in many cases, though
815 it still has some rough edges. If you're interested in
816 working on this, please send mail to the &a.emulation;
817 and indicate that you're interested in joining this ongoing
820 <para>The <filename role="package">emulators/pcemu</filename> port/package in the
821 &os; Ports Collection which emulates an 8088 and enough BIOS
822 services to run DOS text mode applications. It requires the
823 X Window System (XFree86) to operate.</para>
828 <qandaset arch="alpha">
831 <para>Can I boot from the ARC or Alpha BIOS Console?</para>
835 <para>No. &os;, like Compaq Tru64 and VMS, will only boot
836 from the SRM console.</para>
842 <para>Help! I have no space! Do I need to delete
843 everything first?</para>
847 <para>Unfortunately, yes.</para>
853 <para>Can I mount my Compaq Tru64 or VMS extended partitions?</para>
857 <para>No, not at this time.</para>
863 <para>What about support for Compaq Tru64 (OSF/1) binaries?</para>
867 <para>&os; can run Tru64 applications very well using the
868 <filename role="package">emulators/osf1_base</filename> port/package.</para>
874 <para>What about support for Linux binaries?</para>
878 <para>&os; can run AlphaLinux binaries with the assistance
879 of the <filename role="package">emulators/linux_base</filename>
886 <para>What about support for NT Alpha binaries?</para>
890 <para>&os; is not able to run NT applications natively,
891 although it has the ability to mount NT partitions.</para>