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 $
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="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/install.html"><quote>Installing
20 FreeBSD</quote></ulink>
22 url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/">FreeBSD
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 compatability 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="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/faq/">FAQ</ulink> and <ulink
45 url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/">Handbook</ulink> are also
46 available from the <ulink url="http://www.FreeBSD.org/">FreeBSD
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>
75 <title>Hardware Requirements</title>
77 <para arch="i386">&os; for the &arch.print; requires an 80386 or better
78 processor. The &man.sysinstall.8; installation program requires
79 16MB of RAM; after installation, &os; itself can be run in
80 4–8MB of RAM with a pared-down kernel.
81 You will need at least 100MB of free hard drive space for the
82 most minimal installation; a more realistic minimum is on the
83 order of 250–350MB. See below for ways of shrinking
84 existing DOS partitions in order to install &os;.</para>
86 <para arch="alpha">&os; for the &arch.print; supports the platforms
87 described in <filename>HARDWARE.TXT</filename>.</para>
89 <para arch="alpha">You will need a dedicated disk for
90 &os;/alpha. It is not possible to share a disk with another
91 operating system at this time. This disk will need to be attached
92 to a SCSI controller which is supported by the SRM firmware or an
93 IDE disk assuming the SRM in your machine supports booting from
96 <para arch="alpha">Your root filesystem MUST be the first
97 partition (partition <literal>a</literal>) on the disk to be
100 <para arch="alpha">You will need the SRM console firmware for your
101 platform. In some cases, it is possible to switch between
102 AlphaBIOS (or ARC) firmware and SRM. In others it will be
103 necessary to download new firmware from the vendor's Web
107 not familiar with configuring hardware for &os;, you should
108 be sure to read the <filename>HARDWARE.TXT</filename> file;
109 it contains important
110 information on what hardware is supported by &os;.</para>
113 <sect2 id="floppies">
114 <title>Floppy Disk Image Instructions</title>
116 <para>Depending on how you choose to install &os;, you may need to
117 create a set of floppy disks (usually two) to begin the installation
118 process. This section briefly describes how to create these disks,
119 either from a CDROM installation or from the Internet. Note that in
120 the common case of installing &os; from CDROM, on a machine that
121 supports bootable CDROMs, the steps outlined in this section will
122 not be needed and can be skipped.</para>
124 <para>For a normal CDROM or network installation, all you need to
125 copy onto actual floppies from the <filename>floppies/</filename> directory are the
126 <filename>kern.flp</filename> and <filename>mfsroot.flp</filename>
127 images (for 1.44MB floppies).</para>
129 <para>Getting these images over the network is easy. Simply fetch
131 <replaceable>release</replaceable><filename>/floppies/kern.flp</filename>
133 <replaceable>release</replaceable><filename>/floppies/mfsroot.flp</filename>
135 url="&release.url;"></ulink>
136 or one of the many mirrors listed at <ulink
137 url="http://www.FreeBSD.org/doc/en_US.ISO8859-1/books/handbook/mirrors-ftp.html">FTP
138 Sites</ulink> section of the Handbook, or on the
139 <ulink url="http://www.freebsdmirrors.org/"></ulink> Web pages.
142 <para>Get two blank, freshly formatted floppies and image copy
143 <filename>kern.flp</filename> onto one and <filename>mfsroot.flp</filename> onto the other. These images are
144 <emphasis>not</emphasis> DOS files. You cannot simply copy them to a DOS or UFS floppy
145 as regular files, you need to <quote>image</quote> copy them to the floppy with
146 <filename>fdimage.exe</filename> under DOS (see the
147 <filename>tools</filename> directory on your CDROM or &os; FTP
148 mirror) or the &man.dd.1; command in UNIX.</para>
150 <para>For example, to create the kernel floppy image from DOS, you'd
151 do something like this:</para>
153 <screen><prompt>C></prompt> <userinput>fdimage kern.flp a:</userinput></screen>
155 <para>Assuming that you'd copied <filename>fdimage.exe</filename> and <filename>kern.flp</filename> into a directory
156 somewhere. You would do the same for <filename>mfsroot.flp</filename>, of course.</para>
158 <para>If you're creating the boot floppy from a UNIX machine, you
159 may find that:</para>
161 <screen>&prompt.root; <userinput>dd if=floppies/kern.flp of=/dev/rfd0</userinput></screen>
165 <screen>&prompt.root; <userinput>dd if=floppies/kern.flp of=/dev/floppy</userinput></screen>
167 <para>work well, depending on your hardware and operating system
168 environment (different versions of UNIX have different names
169 for the floppy drive).</para>
171 <para arch="alpha">If you're on an alpha machine that can network-boot its
172 floppy images or you have a 2.88MB or LS-120 floppy capable of
173 taking a 2.88MB image on an x86 machine, you may wish to use
174 the single (but twice as large) <filename>boot.flp</filename> image.
175 It contains the contents of <filename>kern.flp</filename> and <filename>mfsroot.flp</filename> on
176 a single floppy. This file should also be used as the
177 boot file for those mastering <quote>El Torito</quote> bootable CD images. See
178 the &man.mkisofs.8; command for more information.</para>
181 <sect2 id="start-installation">
182 <title>Installing &os; from CDROM or the Internet</title>
184 <para arch="i386">The easiest type of installation is from
185 CDROM. If you have a supported CDROM drive and a &os;
186 installation CDROM, there are 2 ways of starting the
187 installation from it:
190 <para>If your system supports bootable CDROM media
191 (usually an option which can be selectively enabled in the
192 controller's setup menu or in the PC BIOS for some
193 systems) and you have it enabled, &os; supports the
194 <quote>El Torrito</quote> bootable CD standard. Simply
195 put the installation CD in your CDROM drive and boot the
196 system to begin installation.</para>
199 <para>Build a set of &os; boot floppies from the
200 <filename>floppies/</filename> directory in every &os;
201 distribution. Either simply use the
202 <filename>makeflp.bat</filename> script from DOS or read
203 <xref linkend="floppies"> for more information on creating
204 the bootable floppies under different operating systems.
205 Then you simply boot from the first floppy and you should
206 soon be in the &os; installation.</para>
211 <para arch="i386">If you don't have a CDROM (or your computer does not
212 support booting from CDROM) and would like to simply install
213 over the net using PPP, SLIP or a dedicated connection.
214 You should start the installation by building
215 a set of &os; boot floppies from the files
216 <filename>floppies/kern.flp</filename> and
217 <filename>floppies/mfsroot.flp</filename> using the instructions
218 found in <xref linkend="floppies">. Restart your computer using
219 the <filename>kern.flp</filename> disk; when prompted, insert
220 the <filename>mfsroot.flp</filename> disk. Then, please go to
221 <xref linkend="ftpnfs"> for additional tips on installing
222 via FTP or NFS.</para>
224 <para arch="alpha">The easiest type of installation is from
225 CDROM. If you have a supported CDROM drive and a &os;
226 installation CDROM, you can boot &os; directly from the
227 CDROM. Insert the CDROM into the drive and type the following
228 command to start the installation (substituting the name of the
229 appropriate CDROM drive if necessary):</para>
231 <screen arch="alpha">>>><userinput>boot dka0</userinput></screen>
233 <para arch="alpha">Alternatively you can boot the installation
234 from floppy disk. You should start the installation by building
235 a set of &os; boot floppies from the files
236 <filename>floppies/kern.flp</filename> and
237 <filename>floppies/mfsroot.flp</filename> using the instructions
238 found in <xref linkend="floppies">. From the SRM console prompt
239 (<literal>>>></literal>), just insert the
240 <filename>kern.flp</filename> floppy and type the following
241 command to start the installation:</para>
243 <screen arch="alpha">>>><userinput>boot dva0</userinput></screen>
245 <para arch="alpha">Insert the <filename>mfsroot.flp</filename>
246 floppy when prompted and you will end up at the first screen of
247 the install program.</para>
250 <title>Detail on various installation types</title>
252 <para>Once you've gotten yourself to the initial installation
253 screen somehow, you should be able to follow the various menu
254 prompts and go from there. If you've never used the &os;
255 installation before, you are also encouraged to read some of the
256 documentation in the Documentation submenu as well as the
257 general <quote>Usage</quote> instructions on the first menu.</para>
260 <para>If you get stuck at a screen, press the <keycap>F1</keycap> key for online
261 documentation relevant to that specific section.</para>
264 <para>If you've never installed &os; before, or even if you
265 have, the <quote>Standard</quote> installation mode is the most recommended
266 since it makes sure that you'll visit all the various important
267 checklist items along the way. If you're much more comfortable
268 with the &os; installation process and know <emphasis>exactly</emphasis> what you
269 want to do, use the <quote>Express</quote> or <quote>Custom</quote> installation options. If
270 you're upgrading an existing system, use the <quote>Upgrade</quote> option.</para>
272 <para>The &os; installer supports the direct use of floppy,
273 DOS, tape, CDROM, FTP, NFS and UFS partitions as installation
274 media; further tips on installing from each type of media are listed
277 <para arch="alpha">Once the install procedure has finished, you will be able
278 to start &os;/&arch; by typing something like this to the SRM
281 <screen arch="alpha">>>><userinput>boot dkc0</userinput></screen>
283 <para arch="alpha">This instructs the firmware to boot the specified disk. To
284 find the SRM names of disks in your machine, use the <literal>show
285 device</literal> command:</para>
287 <screen arch="alpha">>>><userinput>show device</userinput>
288 dka0.0.0.4.0 DKA0 TOSHIBA CD-ROM XM-57 3476
289 dkc0.0.0.1009.0 DKC0 RZ1BB-BS 0658
290 dkc100.1.0.1009.0 DKC100 SEAGATE ST34501W 0015
292 ewa0.0.0.3.0 EWA0 00-00-F8-75-6D-01
293 pkc0.7.0.1009.0 PKC0 SCSI Bus ID 7 5.27
294 pqa0.0.0.4.0 PQA0 PCI EIDE
295 pqb0.0.1.4.0 PQB0 PCI EIDE</screen>
297 <para arch="alpha">This example is from a Digital Personal Workstation 433au
298 and shows three disks attached to the machine. The first is a
299 CDROM called <devicename>dka0</devicename> and the other two are
300 disks and are called <devicename>dkc0</devicename> and
301 <devicename>dkc100</devicename> repectively.</para>
303 <para arch="alpha">You can specify which kernel file to load and what boot
304 options to use with the <option>-file</option> and
305 <option>-flags</option> options, for example:</para>
307 <screen arch="alpha"><prompt>>>></prompt> <userinput>boot -file kernel.old -flags s</userinput></screen>
309 <para arch="alpha">To make &os;/&arch; boot automatically, use these commands:</para>
311 <screen arch="alpha"><prompt>>>></prompt> <userinput>set boot_osflags a</userinput>
312 <prompt>>>></prompt> <userinput>set bootdef_dev dkc0</userinput>
313 <prompt>>>></prompt> <userinput>set auto_action BOOT</userinput></screen>
316 <title>Installing from a Network CDROM</title>
318 <para>If you simply wish to install from a local CDROM drive
319 then see <xref linkend="start-installation">. If you don't have a CDROM
320 drive on your system and wish to use a &os; distribution CD
321 in the CDROM drive of another system to which you have network
322 connectivity, there are also several ways of going about it:</para>
326 <para>If you would be able to FTP install &os; directly
327 from the CDROM drive in some &os; machine, it's quite
328 easy: You simply add the following line to the password file
329 (using the &man.vipw.8; command):</para>
331 <screen>ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin</screen>
333 <para>On the machine on which you are running the install,
334 go to the Options menu and set Release Name to
335 <literal>any</literal>. You may then choose a Media type of
336 <literal>FTP</literal> and type in
337 <filename>ftp://<replaceable>machine</replaceable></filename>
338 after picking <quote>URL</quote> in the ftp sites
342 <para>This may allow anyone on the local network (or Internet) to
343 make <quote>anonymous FTP</quote> connections to this
344 machine, which may not be desirable.</para>
349 <para>If you would rather use NFS to export the CDROM
350 directly to the machine(s) you'll be installing from, you
351 need to first add an entry to the
352 <filename>/etc/exports</filename> file (on the machine with
353 the CDROM drive). The example below allows the machine
354 <hostid role="hostname">ziggy.foo.com</hostid> to mount the
355 CDROM directly via NFS during installation:</para>
357 <screen>/cdrom -ro ziggy.foo.com</screen>
360 with the CDROM must also be configured as an NFS server, of
361 course, and if you're not sure how to do that then an NFS
362 installation is probably not the best choice for you unless
363 you're willing to read up on &man.rc.conf.5; and configure things
364 appropriately. Assuming that this part goes smoothly, you
365 should be able to enter: <filename><replaceable>cdrom-host</replaceable>:/cdrom</filename> as the path for
366 an NFS installation when the target machine is installed,
367 e.g. <filename>wiggy:/cdrom</filename>.</para>
373 <title>Installing from Floppies</title>
375 <para>If you must install from floppy disks, either due to
376 unsupported hardware or just because you enjoy doing things the
377 hard way, you must first prepare some floppies for the
380 <para>First, make your boot floppies as described in
381 <xref linkend="floppies">.</para>
383 <para>Second, peruse <xref linkend="layout"> and pay special attention
384 to the <quote>Distribution Format</quote> section since it describes which
385 files you're going to need to put onto floppy and which you can
388 <para>Next you will need, at minimum, as many 1.44MB floppies as
389 it takes to hold all files in the <filename>bin</filename>
390 (binary distribution) directory. If you're preparing these
391 floppies under DOS, then these floppies
392 <emphasis>must</emphasis> be formatted using the MS-DOS
393 <filename>FORMAT</filename> command. If you're using Windows,
394 use the Windows File Manager format command.</para>
397 <para>Frequently, floppy disks come <quote>factory
398 preformatted</quote>. While convenient,
399 many problems reported by users in the past have resulted
400 from the use of improperly formatted media.
401 Re-format them yourself, just to make sure.</para>
404 <para>If you're creating the floppies from another &os;
405 machine, a format is still not a bad idea though you don't need
406 to put a DOS filesystem on each floppy. You can use the
407 &man.disklabel.8; and &man.newfs.8; commands to put a UFS filesystem on a
408 floppy, as the following sequence of commands
411 <screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput>
412 &prompt.root; <userinput>disklabel -w -r fd0.1440 floppy3</userinput>
413 &prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</userinput></screen>
415 <para>After you've formatted the floppies for DOS or UFS, you'll
416 need to copy the files onto them. The distribution files are
417 split into chunks conveniently sized so that 5 of them will fit
418 on a conventional 1.44MB floppy. Go through all your floppies,
419 packing as many files as will fit on each one, until you've got
420 all the distributions you want packed up in this fashion. Each
421 distribution should go into its own subdirectory on the floppy,
422 e.g.: <filename>a:\bin\bin.inf</filename>, <filename>a:\bin\bin.aa</filename>, <filename>a:\bin\bin.ab</filename>, ...</para>
425 <para>The <filename>bin.inf</filename> file also needs to go on the first floppy of
426 the <filename>bin</filename> set since it is read by the installation program in
427 order to figure out how many additional pieces to look for
428 when fetching and concatenating the distribution. When
429 putting distributions onto floppies, the
430 <filename>distname.inf</filename> file <emphasis>must</emphasis> occupy the first
431 floppy of each distribution set. This is also covered in
432 <filename>README.TXT</filename>.</para>
435 <para>Once you come to the Media screen of the install, select
436 <quote>Floppy</quote> and you'll be prompted for the rest.</para>
440 <title>Installing from a DOS partition</title>
442 <para>To prepare for installation from an MS-DOS partition you
443 should simply copy the files from the distribution into a
444 directory called <filename>FREEBSD</filename> on the Primary DOS partition (<devicename>C:</devicename>). For example, to do a minimal installation of &os; from
445 DOS using files copied from the CDROM, you might do something
448 <screen><prompt>C:\></prompt> <userinput>MD C:\FREEBSD</userinput>
449 <prompt>C:\></prompt> <userinput>XCOPY /S E:\BIN C:\FREEBSD\BIN</userinput></screen>
451 <para>Assuming that <devicename>E:</devicename> was where your CD was mounted.</para>
453 <para>For as many distributions as you wish to install from DOS (and
454 you have free space for), install each one in a directory under
455 <filename>C:\FREEBSD</filename> - the <filename>BIN</filename> dist is only the minimal requirement.</para>
457 <para>Once you've copied the directories, you can simply launch
458 the installation from floppies as normal and select <quote>DOS</quote> as
459 your media type when the time comes.</para>
463 <title>Installing from QIC/SCSI Tape</title>
465 <para>When installing from tape, the installation program
466 expects the files to be simply tar'ed onto it, so after fetching
467 all of the files for the distributions you're interested in,
468 simply use &man.tar.1; to get them onto the tape with a command something like
471 <screen>&prompt.root; <userinput>cd <replaceable>/where/you/have/your/dists</replaceable></userinput>
472 &prompt.root; <userinput>tar cvf /dev/rsa0 <replaceable>dist1</replaceable> .. <replaceable>dist2</replaceable></userinput></screen>
474 <para>When you go to do the installation, you should also make
475 sure that you leave enough room in some temporary directory
476 (which you'll be allowed to choose) to accommodate the <emphasis>full</emphasis>
477 contents of the tape you've created. Due to the non-random
478 access nature of tapes, this method of installation requires
479 quite a bit of temporary storage. You should expect to require
480 as much temporary storage as you have stuff written on tape.</para>
483 <para>When going to do the installation, the tape must be in
484 the drive <emphasis>before</emphasis> booting from the boot floppies. The
485 installation <quote>probe</quote> may otherwise fail to find it.</para>
488 <para>Now create a boot floppy as described in <xref linkend="floppies"> and
489 proceed with the installation.</para>
493 <title>Installing over a Network using FTP or NFS</title>
495 <para>After making the boot floppies as described in the first
496 section, you can load the rest of the installation over a
497 network using one of 3 types of connections: serial port,
498 parallel port, or Ethernet.</para>
501 <title>Serial Port</title>
503 <para>SLIP support is rather primitive, and is limited
504 primarily to hard-wired links, such as a serial cable running
505 between two computers. The link must be hard-wired because
506 the SLIP installation doesn't currently offer a dialing
507 capability. If you need to dial out with a modem or otherwise
508 dialog with the link before connecting to it, then I recommend
509 that the PPP utility be used instead.</para>
511 <para>If you're using PPP, make sure that you have your
512 Internet Service Provider's IP address and DNS information
513 handy as you'll need to know it fairly early in the
514 installation process. You may also need to know your own IP
515 address, though PPP supports dynamic address negotiation and
516 may be able to pick up this information directly from your ISP
517 if they support it.</para>
519 <para>You will also need to know how to use the various <quote>AT
520 commands</quote> for dialing out with your particular brand of modem
521 as the PPP dialer provides only a very simple terminal
526 <title>Parallel Port</title>
528 <para>If a hard-wired connection to another &os; or Linux
529 machine is available, you might also consider installing over
530 a <quote>laplink</quote> style parallel port cable. The data rate over the
531 parallel port is much higher than what is typically possible
532 over a serial line (up to 50k/sec), thus resulting in a
533 quicker installation. It's not typically necessary to use
534 <quote>real</quote> IP addresses when using a point-to-point parallel cable
535 in this way and you can generally just use RFC 1918 style
536 addresses for the ends of the link (e.g. <hostid
537 role="ipaddr">10.0.0.1</hostid>, <hostid role="ipaddr">10.0.0.2</hostid>,
541 <para>If you use a Linux machine rather than a &os;
542 machine as your PLIP peer, you will also have to specify
543 <option>link0</option> in the TCP/IP setup screen's <quote>extra options for
544 ifconfig</quote> field in order to be compatible with Linux's
545 slightly different PLIP protocol.</para>
551 <title>Ethernet</title>
553 <para>&os; supports many common Ethernet cards; a table
554 of supported cards is
555 provided as part of the &os; Hardware Notes (see
556 <filename>HARDWARE.TXT</filename> in
557 the Documentation menu on the boot floppy or the top level
558 directory of the CDROM). If you are using one of the
559 supported PCMCIA Ethernet cards, also be sure that it's
560 plugged in <emphasis>before</emphasis> the laptop is powered on. &os; does
561 not, unfortunately, currently support <quote>hot insertion</quote> of
562 PCMCIA cards during installation.</para>
564 <para>You will also need to know your IP address on the
565 network, the <option>netmask</option> value for your subnet and the
566 name of your machine. Your system administrator can tell you
567 which values are appropriate to your particular network setup.
568 If you will be referring to other hosts by name rather than IP
569 address, you'll also need a name server and possibly the
570 address of a gateway (if you're using PPP, it's your
571 provider's IP address) to use in talking to it. If you want
572 to install by FTP via an HTTP proxy (see below), you will also
573 need the proxy's address.</para>
575 <para>If you do not know the answers to these questions then
576 you should really probably talk to your system administrator
577 <emphasis>first</emphasis> before trying this type of
578 installation. Using a randomly chosen IP address or netmask
579 on a live network is almost guaranteed not to work, and will
580 probably result in a lecture from said system administrator.</para>
582 <para>Once you have a network connection of some sort working, the
583 installation can continue over NFS or FTP.</para>
587 <title>NFS installation tips</title>
589 <para>NFS installation is fairly straight-forward: Simply copy
590 the &os; distribution files you want onto a server
591 somewhere and then point the NFS media selection at it.</para>
593 <para>If this server supports only <quote>privileged port</quote> access (this is
594 generally the default for Sun and Linux workstations), you
595 will need to set this option in the Options menu before
596 installation can proceed.</para>
598 <para>If you have a poor quality Ethernet card which suffers from very
599 slow transfer rates, you may also wish to toggle the appropriate
602 <para>In order for NFS installation to work, the server must
603 also support <quote>subdir mounts</quote>, e.g. if your &os;
604 distribution directory lives on
605 <filename>wiggy:/usr/archive/stuff/FreeBSD</filename>, then
606 <hostid role="hostname">wiggy</hostid> will have to allow
607 the direct mounting of <filename>/usr/archive/stuff/FreeBSD</filename>, not just
608 <filename>/usr</filename> or <filename>/usr/archive/stuff</filename>.</para>
610 <para>In &os;'s <filename>/etc/exports</filename> file this is controlled by the
611 <option>-alldirs</option> option. Other NFS servers may have different
612 conventions. If you are getting <literal>Permission Denied</literal> messages
613 from the server then it's likely that you don't have this
614 properly enabled.</para>
618 <title>FTP Installation tips</title>
620 <para>FTP installation may be done from any mirror site containing a
621 reasonably up-to-date version of &os;. A full menu of
622 reasonable choices for almost any location in the world is
623 provided in the FTP site menu during installation.</para>
625 <para>If you are installing from some other FTP site not listed in
626 this menu, or you are having troubles getting your name server
627 configured properly, you can also specify your own URL by
628 selecting the <quote>URL</quote> choice in that menu. A URL can
629 contain a hostname or an IP address, so something like the following would
630 work in the absence of a name server:</para>
632 <screen>ftp://216.66.64.162/pub/FreeBSD/releases/&arch;/4.2-RELEASE</screen>
634 <para>There are three FTP installation modes you can use:
637 <para>FTP: This method uses the standard
638 <quote>Active</quote> mode for transfers, in which the
639 server initiates a connection to the client. This will
640 not work through most firewalls but will often work best
641 with older FTP servers that do not support passive mode.
642 If your connection hangs with passive mode, try this
646 <para>FTP Passive: This sets the FTP "Passive" mode
647 which prevents the server from opening connections to
648 the client. This option is best for users to pass
649 through firewalls that do not allow incoming connections
650 on random port addresses.</para>
653 <para>FTP via an HTTP proxy: This option instructs &os;
654 to use HTTP to connect to a proxy for all FTP
655 operations. The proxy will translate the requests and
656 send them to the FTP server. This allows the user to
657 pass through firewalls that do not allow FTP at all, but
658 offer an HTTP proxy. You must specify the hostname of
659 the proxy in addition to the FTP server.</para>
661 <para>In the rare case that you have an FTP proxy that
662 does not go through HTTP, you can specify the URL as
663 something like:</para>
665 <screen><userinput>ftp://foo.bar.com:<replaceable>port</replaceable>/pub/FreeBSD</userinput></screen>
667 <para>In the URL above, <replaceable>port</replaceable>
668 is the port number of the proxy FTP server.</para>
675 <title>Tips for Serial Console Users</title>
677 <para>If you'd like to install &os; on a machine using just a
678 serial port (e.g. you don't have or wish to use a VGA card),
679 please follow these steps:</para>
683 <para>Connect some sort of ANSI (vt100) compatible terminal
684 or terminal emulation program to the <devicename>COM1</devicename> port of the PC you
685 are installing &os; onto.</para>
688 <para>Unplug the keyboard (yes, that's correct!) and then
689 try to boot from floppy or the installation CDROM, depending
690 on the type of installation media you have, with the
691 keyboard unplugged.</para>
694 <para>If you don't get any output on your serial console,
695 plug the keyboard in again and wait for some beeps. If you
696 are booting from the CDROM, proceed to <xref
697 linkend="hitspace"> as soon as you
698 hear the beep.</para>
701 <para>For a floppy boot, the first beep means to remove the
702 <filename>kern.flp</filename> floppy and insert the
703 <filename>mfsroot.flp</filename> floppy, after
704 which you should press <keycap>Enter</keycap> and wait for another beep.</para>
707 <para>Hit the space bar, then enter</para>
709 <screen><userinput>boot -h</userinput></screen>
711 <para>and you should now definitely be seeing everything on
712 the serial port. If that still doesn't work, check your
713 serial cabling as well as the settings on your terminal
714 emulation program or actual terminal device. It should be
715 set for 9600 baud, 8 bits, no parity.</para>
722 <title>Question and Answer Section for &arch.print; Architecture Users</title>
724 <qandaset arch="i386">
727 <para>Help! I have no space! Do I need to delete
728 everything first?</para>
731 <para>If your machine is already running DOS and has little
732 or no free space available for &os;'s installation, all is
733 not lost! You may find the <application>FIPS</application>
734 utility, provided in the <filename>tools/</filename>
735 subdirectory on the &os; CDROM or on the various &os; ftp
736 sites, to be quite useful.</para>
738 <para><application>FIPS</application> allows you to split an
739 existing DOS partition into two pieces, preserving the
740 original partition and allowing you to install onto the
741 second free piece. You first <quote>defrag</quote> your DOS
742 partition, using the DOS 6.xx <filename>DEFRAG</filename>
743 utility or the <application>Norton Disk Tools</application>,
744 then run FIPS. It will
745 prompt you for the rest of the information it needs.
746 Afterwards, you can reboot and install &os; on the new
747 partition. Also note that FIPS will create the second
748 partition as a <quote>clone</quote> of the first, so you'll
749 actually see that you now have two DOS Primary partitions
750 where you formerly had one. Don't be alarmed! You can
751 simply delete the extra DOS Primary partition (making sure
752 it's the right one by examining its size).</para>
754 <para><application>FIPS</application> does NOT currently
755 work with NTFS style partitions. To split up such a
756 partition, you will need a commercial product such as
757 <application>Partition Magic</application>. Sorry, but this
758 is just the breaks if you've got a Windows partition hogging
759 your whole disk and you don't want to reinstall from
767 <para>Can I use compressed DOS filesystems from
772 <para>No. If you are using a utility such as
773 <application>Stacker</application>(tm) or
774 <application>DoubleSpace</application>(tm), &os; will only
775 be able to use whatever portion of the filesystem you leave
776 uncompressed. The rest of the filesystem will show up as
777 one large file (the stacked/dblspaced file!). <emphasis>Do
778 not remove that file</emphasis> as you will probably regret
781 <para>It is probably better to create another uncompressed DOS
782 extended partition and use this for communications between
783 DOS and &os; if such is your desire.</para>
789 <para>Can I mount my DOS extended partitions?</para>
793 <para>Yes. DOS extended partitions are mapped in at the end
794 of the other <quote>slices</quote> in &os;, e.g. your <devicename>D:</devicename> drive might
795 be <filename>/dev/da0s5</filename>, your <devicename>E:</devicename> drive <filename>/dev/da0s6</filename>, and so on. This
796 example assumes, of course, that your extended partition is
797 on SCSI drive 0. For IDE drives, substitute <literal>ad</literal> for
798 <literal>da</literal> appropriately. You otherwise mount extended
799 partitions exactly like you would mount any other DOS drive,
802 <screen>&prompt.root; <userinput>mount -t msdos /dev/da0s5 /dos_d</userinput></screen>
808 <para>Can I run DOS binaries under &os;?</para>
812 <para>Ongoing work with BSDI's &man.doscmd.1; utility will
813 suffice in many cases, though
814 it still has some rough edges. If you're interested in
815 working on this, please send mail to the &a.emulation;
816 and indicate that you're interested in joining this ongoing
819 <para>The <filename role="package">emulators/pcemu</filename> port/package in the
820 &os; Ports Collection which emulates an 8088 and enough BIOS
821 services to run DOS text mode applications. It requires the
822 X Window System (XFree86) to operate.</para>
827 <qandaset arch="alpha">
830 <para>Can I boot from the ARC or Alpha BIOS Console?</para>
834 <para>No. &os;, like Compaq Tru64 and VMS, will only boot
835 from the SRM console.</para>
841 <para>Help! I have no space! Do I need to delete
842 everything first?</para>
846 <para>Unfortunately, yes.</para>
852 <para>Can I mount my Compaq Tru64 or VMS extended partitions?</para>
856 <para>No, not at this time.</para>
862 <para>What about support for Compaq Tru64 (OSF/1) binaries?</para>
866 <para>&os; can run Tru64 applications very well using the
867 <filename role="package">emulators/osf1_base</filename> port/package.</para>
873 <para>What about support for Linux binaries?</para>
877 <para>&os; can run AlphaLinux binaries with the assistance
878 of the <filename role="package">emulators/linux_base</filename>
885 <para>What about support for NT Alpha binaries?</para>
889 <para>&os; is not able to run NT applications natively,
890 although it has the ability to mount NT partitions.</para>