View | Details | Raw Unified | Return to bug 70485
Collapse All | Expand All

(-)release/doc/en_US.ISO8859-1/installation/common/install.sgml (-91 / +116 lines)
Lines 77-86 Link Here
77
77
78
<!-- i386/pc98 text starts here -->
78
<!-- i386/pc98 text starts here -->
79
79
80
    <para arch="i386,pc98">&os; for the &arch.print; requires a 386 or better
80
    <para arch="i386,pc98">&os; for the &arch.print; requires a 486 or better
81
    processor to run (sorry, there is no support for 286 processors)
81
    processor to install and run (although &os; can run on 386 processors with
82
    and at least 5 megs of RAM to install and 4 megs of RAM to
82
    a custom kernel) and at least 8 megs of RAM to install and 7 megs to
83
    run. You will need at least 100MB of free hard drive space for the
83
    run. You will need at least 150MB of free hard drive space for the
84
    most minimal installation.  See below for ways of shrinking
84
    most minimal installation.  See below for ways of shrinking
85
    existing DOS partitions in order to install &os;.</para>
85
    existing DOS partitions in order to install &os;.</para>
86
86
Lines 139-145 Link Here
139
  <title>Floppy Disk Image Instructions</title>
139
  <title>Floppy Disk Image Instructions</title>
140
140
141
  <para arch="i386,alpha,pc98">Depending on how you choose to install &os;, you may need to
141
  <para arch="i386,alpha,pc98">Depending on how you choose to install &os;, you may need to
142
  create a set of floppy disks (usually two) to begin the installation
142
  create a set of floppy disks (usually three) to begin the installation
143
  process.  This section briefly describes how to create these disks,
143
  process.  This section briefly describes how to create these disks,
144
  either from a CDROM installation or from the Internet.  Note that in
144
  either from a CDROM installation or from the Internet.  Note that in
145
  the common case of installing &os; from CDROM, on a machine that
145
  the common case of installing &os; from CDROM, on a machine that
Lines 148-170 Link Here
148
148
149
  <para arch="i386,alpha">For most CDROM or network installations, all you need to
149
  <para arch="i386,alpha">For most CDROM or network installations, all you need to
150
  copy onto actual floppies from the <filename>floppies/</filename> directory are the
150
  copy onto actual floppies from the <filename>floppies/</filename> directory are the
151
  <filename>kern.flp</filename> and <filename>mfsroot.flp</filename>
151
  <filename>boot.flp</filename> and <filename>kernX.flp</filename>
152
  images (for 1.44MB floppies).  Depending on your hardware, you may
152
  images (for 1.44MB floppies).</para>
153
  also need to make the third <filename>drivers.flp</filename> image
154
  to provide necessary device drivers.</para>
155
153
156
  <para arch="pc98">For a normal CDROM or network installation, all you need
154
  <para arch="pc98">For a normal CDROM or network installation, all you need
157
  to copy onto actual floppies from the <filename>floppies/</filename>
155
  to copy onto actual floppies from the <filename>floppies/</filename>
158
  directory are the <filename>kern.flp</filename> and <filename>mfsroot.flp</filename>
156
  directory are the <filename>boot.flp</filename> and <filename>kernX.flp</filename>
159
  images (for 1.44MB floppies) or <filename>kern-small.flp</filename> and
157
  images (for 1.44MB floppies) or <filename>boot-small.flp</filename> and
160
  <filename>mfsroot-small.flp</filename> images (for 1.2MB floppies).</para>
158
  <filename>kern-small.flp</filename> images (for 1.2MB floppies).</para>
161
159
162
  <para arch="i386,alpha,pc98">Getting these images over the network is easy.  Simply fetch
160
  <para arch="i386,alpha,pc98">Getting these images over the network is easy.  Simply fetch
163
  the
161
  the
164
  <replaceable>release</replaceable><filename>/floppies/kern.flp</filename>,
162
  <replaceable>release</replaceable><filename>/floppies/boot.flp</filename>,
165
  <replaceable>release</replaceable><filename>/floppies/mfsroot.flp</filename>,
163
  and all of the
166
  and
164
  <replaceable>release</replaceable><filename>/floppies/kernX.flp</filename>
167
  <replaceable>release</replaceable><filename>/floppies/drivers.flp</filename>
168
  files from <ulink
165
  files from <ulink
169
  url="&release.url;"></ulink>
166
  url="&release.url;"></ulink>
170
  or one of the many mirrors listed at <ulink
167
  or one of the many mirrors listed at <ulink
Lines 173-188 Link Here
173
    <ulink url="http://mirrorlist.FreeBSD.org/"></ulink> Web pages.
170
    <ulink url="http://mirrorlist.FreeBSD.org/"></ulink> Web pages.
174
  </para>
171
  </para>
175
172
176
  <para arch="i386,alpha">Get two blank, freshly formatted floppies and image copy
173
  <para arch="i386,alpha">Get approximately three blank, freshly formatted floppies and image copy
177
  <filename>kern.flp</filename> onto one and <filename>mfsroot.flp</filename> onto the other.  These images are
174
  <filename>boot.flp</filename> onto one and the <filename>kernX.flp</filename> files 
175
  onto the others.  These images are
178
  <emphasis>not</emphasis> DOS files.  You cannot simply copy them to a DOS or UFS floppy
176
  <emphasis>not</emphasis> DOS files.  You cannot simply copy them to a DOS or UFS floppy
179
  as regular files, you need to <quote>image</quote> copy them to the floppy with
177
  as regular files, you need to <quote>image</quote> copy them to the floppy with
180
  <filename>fdimage.exe</filename> under DOS (see the
178
  <filename>fdimage.exe</filename> under DOS (see the
181
  <filename>tools</filename> directory on your CDROM or &os; FTP
179
  <filename>tools</filename> directory on your CDROM or &os; FTP
182
  mirror) or the &man.dd.1; command in UNIX.</para>
180
  mirror) or the &man.dd.1; command in UNIX.</para>
183
181
184
  <para arch="pc98">Get two blank, freshly formatted floppies and image copy
182
  <para arch="pc98">Get approximately three blank, freshly formatted floppies and image copy
185
  <filename>kern.flp</filename> onto one and <filename>mfsroot.flp</filename> onto the other.  These images are
183
  <filename>boot.flp</filename> onto one and the <filename>kernX.flp</filename> files
184
  onto the others.  These images are
186
  <emphasis>not</emphasis> DOS files.  You cannot simply copy them to a DOS or UFS floppy
185
  <emphasis>not</emphasis> DOS files.  You cannot simply copy them to a DOS or UFS floppy
187
  as regular files, you need to <quote>image</quote> copy them to the floppy with
186
  as regular files, you need to <quote>image</quote> copy them to the floppy with
188
  <filename>rawrite.exe</filename> under DOS (see the
187
  <filename>rawrite.exe</filename> under DOS (see the
Lines 192-230 Link Here
192
  <para arch="i386,alpha,pc98">For example, to create the kernel floppy image from DOS, you'd
191
  <para arch="i386,alpha,pc98">For example, to create the kernel floppy image from DOS, you'd
193
  do something like this:</para>
192
  do something like this:</para>
194
193
195
  <screen arch="i386,alpha"><prompt>C></prompt> <userinput>fdimage kern.flp a:</userinput></screen>
194
  <screen arch="i386,alpha"><prompt>C></prompt> <userinput>fdimage boot.flp a:</userinput></screen>
196
  <screen arch="pc98"><prompt>A></prompt> <userinput>rawrite</userinput></screen>
195
  <screen arch="pc98"><prompt>A></prompt> <userinput>rawrite</userinput></screen>
197
196
198
  <para arch="i386,alpha">Assuming that you'd copied <filename>fdimage.exe</filename> and <filename>kern.flp</filename> into a directory
197
  <para arch="i386,alpha">Assuming that you'd copied <filename>fdimage.exe</filename> and <filename>boot.flp</filename> into a directory
199
  somewhere.  You would do the same for <filename>mfsroot.flp</filename>, of course.</para>
198
  somewhere.  You would do the same for the <filename>kernX.flp</filename> files, of course.</para>
200
199
201
  <para arch="pc98">Assuming that you'd copied <filename>rawrite.exe</filename> and <filename>kern.flp</filename> into a directory
200
  <para arch="pc98">Assuming that you'd copied <filename>rawrite.exe</filename> and <filename>boot.flp</filename> into a directory
202
  somewhere.  You would do the same for <filename>mfsroot.flp</filename>, of course.</para>
201
  somewhere.  You would do the same for the <filename>kernX.flp</filename> files, of course.</para>
203
202
204
  <para arch="i386,alpha,pc98">If you're creating the boot floppy from a UNIX machine, you
203
  <para arch="i386,alpha,pc98">If you're creating the boot floppy from a UNIX machine, you
205
  may find that:</para>
204
  may find that:</para>
206
205
207
  <screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/kern.flp of=/dev/rfd0</userinput></screen>
206
  <screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/rfd0</userinput></screen>
208
  <screen arch="pc98">&prompt.root; <userinput>dd if=floppies/kern.flp of=/dev/rfd0.1440</userinput></screen>
207
  <screen arch="pc98">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/rfd0.1440</userinput></screen>
208
209
  <para arch="i386,alpha">or</para>
210
211
  <screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/fd0</userinput></screen>
209
212
210
  <para arch="i386,alpha,pc98">or</para>
213
  <para arch="i386,alpha,pc98">or</para>
211
214
212
  <screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/kern.flp of=/dev/floppy</userinput></screen>
215
  <screen arch="i386,alpha">&prompt.root; <userinput>dd if=floppies/boot.flp of=/dev/floppy</userinput></screen>
213
  <screen arch="pc98">&prompt.root; <userinput>dd if=floppies/kern-small.flp of=/dev/rfd0.1200</userinput></screen>
216
  <screen arch="pc98">&prompt.root; <userinput>dd if=floppies/boot-small.flp of=/dev/rfd0.1200</userinput></screen>
214
217
215
  <para arch="i386,alpha,pc98">work well, depending on your hardware and operating system
218
  <para arch="i386,alpha,pc98">work well, depending on your hardware and operating system
216
  environment (different versions of UNIX have different names
219
  environment (different versions of UNIX have different names
217
  for the floppy drive).</para>
220
  for the floppy drive).</para>
218
221
219
  <para arch="alpha">If you're on an alpha machine that can network-boot its
220
  floppy images or you have a 2.88MB or LS-120 floppy capable of
221
  taking a 2.88MB image on an x86 machine, you may wish to use
222
  the single (but twice as large) <filename>boot.flp</filename> image.
223
  It contains the contents of <filename>kern.flp</filename> and <filename>mfsroot.flp</filename> on
224
  a single floppy.  This file should also be used as the
225
  boot file for those mastering <quote>El Torito</quote> bootable CD images.  See
226
  the &man.mkisofs.8; command for more information.</para>
227
228
  <para arch="amd64">Floppy disk based install is not supported
222
  <para arch="amd64">Floppy disk based install is not supported
229
  on &os;/&arch;.</para>
223
  on &os;/&arch;.</para>
230
  </sect2>
224
  </sect2>
Lines 240-258 Link Here
240
      installation from it:
234
      installation from it:
241
        <itemizedlist>
235
        <itemizedlist>
242
          <listitem>
236
          <listitem>
243
            <para>If your system supports bootable CDROM media
237
            <para>If your system supports the <quote>CDBOOT</quote> standard for
244
            (usually an option which can be selectively enabled in the
238
            bootable CDROM media and you have booting from CD enabled,
245
            controller's setup menu or in the PC BIOS for some
239
            simply put the &os; installation CD in your CDROM drive and
246
            systems) and you have it enabled, &os; supports the
240
            boot the system to begin installation.</para>
247
            <quote>El Torito</quote> bootable CD standard.  Simply
248
            put the installation CD in your CDROM drive and boot the
249
            system to begin installation.</para>
250
	  </listitem>
241
	  </listitem>
251
	  <listitem>
242
	  <listitem>
252
	    <para>Build a set of &os; boot floppies from the
243
	    <para>Build a set of &os; boot floppies from the
253
            <filename>floppies/</filename> directory in every &os;
244
            <filename>floppies/</filename> directory in every &os;
254
            distribution.  Either simply use the
245
            distribution.  Read
255
            <filename>makeflp.bat</filename> script from DOS or read
256
            <xref linkend="floppies"> for more information on creating
246
            <xref linkend="floppies"> for more information on creating
257
            the bootable floppies under different operating systems.
247
            the bootable floppies under different operating systems.
258
            Then you simply boot from the first floppy and you should
248
            Then you simply boot from the first floppy and you should
Lines 280-305 Link Here
280
270
281
      <para arch="i386">If you don't have a CDROM (or your computer does not
271
      <para arch="i386">If you don't have a CDROM (or your computer does not
282
      support booting from CDROM) and would like to simply install
272
      support booting from CDROM) and would like to simply install
283
      over the net using PPP, SLIP or a dedicated connection.
273
      over the net using PPP, SLIP or a dedicated connection,
284
      You should start the installation by building
274
      you should start the installation by building
285
      a set of &os; boot floppies from the files
275
      a set of &os; boot floppies from the files
286
      <filename>floppies/kern.flp</filename> and
276
      <filename>floppies/boot.flp</filename> and
287
      <filename>floppies/mfsroot.flp</filename> using the instructions
277
      <filename>floppies/kernX.flp</filename> using the instructions
288
      found in <xref linkend="floppies">.  Restart your computer using
278
      found in <xref linkend="floppies">.  Restart your computer using
289
      the <filename>kern.flp</filename> disk; when prompted, insert
279
      the <filename>boot.flp</filename> disk; when prompted, insert
290
      the <filename>mfsroot.flp</filename> disk.  Then, please go to
280
      the other disks as required.  Then, please go to
291
      <xref linkend="ftpnfs"> for additional tips on installing
281
      <xref linkend="ftpnfs"> for additional tips on installing
292
      via FTP or NFS.</para>
282
      via FTP or NFS.</para>
293
283
294
      <para arch="pc98">If you don't have a CDROM and would like to
284
      <para arch="pc98">If you don't have a CDROM and would like to
295
      simply install over the net using PPP, SLIP or a dedicated connection.
285
      simply install over the net using PPP, SLIP or a dedicated connection,
296
      You should start the installation by building
286
      you should start the installation by building
297
      a set of &os; boot floppies from the files
287
      a set of &os; boot floppies from the files
298
      <filename>floppies/kern.flp</filename> and
288
      <filename>floppies/boot.flp</filename> and
299
      <filename>floppies/mfsroot.flp</filename> using the instructions
289
      <filename>floppies/kernX.flp</filename> using the instructions
300
      found in <xref linkend="floppies">.  Restart your computer using
290
      found in <xref linkend="floppies">.  Restart your computer using
301
      the <filename>kern.flp</filename> disk; when prompted, insert
291
      the <filename>boot.flp</filename> disk; when prompted, insert
302
      the <filename>mfsroot.flp</filename> disk.  Then, please go to
292
      the other disks as required.  Then, please go to
303
      <xref linkend="ftpnfs"> for additional tips on installing
293
      <xref linkend="ftpnfs"> for additional tips on installing
304
      via FTP or NFS.</para>
294
      via FTP or NFS.</para>
305
295
Lines 316-333 Link Here
316
306
317
      <para arch="alpha">Alternatively you can boot the installation
307
      <para arch="alpha">Alternatively you can boot the installation
318
      from floppy disk. You should start the installation by building
308
      from floppy disk. You should start the installation by building
319
      a set of &os; boot floppies from the files
309
      a set of &os; boot floppies from the
320
      <filename>floppies/kern.flp</filename> and
310
      <filename>floppies/boot.flp</filename> and
321
      <filename>floppies/mfsroot.flp</filename> using the instructions
311
      <filename>floppies/kernX.flp</filename> files using the instructions
322
      found in <xref linkend="floppies">. From the SRM console prompt
312
      found in <xref linkend="floppies">. From the SRM console prompt
323
      (<literal>&gt;&gt;&gt;</literal>), just insert the
313
      (<literal>&gt;&gt;&gt;</literal>), just insert the
324
      <filename>kern.flp</filename> floppy and type the following
314
      <filename>boot.flp</filename> floppy and type the following
325
      command to start the installation:</para>
315
      command to start the installation:</para>
326
316
327
      <screen arch="alpha">&gt;&gt;&gt;<userinput>boot dva0</userinput></screen>
317
      <screen arch="alpha">&gt;&gt;&gt;<userinput>boot dva0</userinput></screen>
328
318
329
      <para arch="alpha">Insert the <filename>mfsroot.flp</filename>
319
      <para arch="alpha">Insert the other floppies when prompted and
330
      floppy when prompted and you will end up at the first screen of
320
      you will end up at the first screen of
331
      the install program.</para>
321
      the install program.</para>
332
322
333
<!-- sparc64 text starts here -->
323
<!-- sparc64 text starts here -->
Lines 462-468 Link Here
462
        <listitem>
452
        <listitem>
463
          <para>If you would be able to FTP install &os; directly
453
          <para>If you would be able to FTP install &os; directly
464
          from the CDROM drive in some &os; machine, it's quite
454
          from the CDROM drive in some &os; machine, it's quite
465
          easy: You simply add the following line to the password file
455
          easy: You ensure an FTP server is running and then
456
          simply add the following line to the password file
466
          (using the &man.vipw.8; command):</para>
457
          (using the &man.vipw.8; command):</para>
467
458
468
          <screen>ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin</screen>
459
          <screen>ftp:*:99:99::0:0:FTP:/cdrom:/sbin/nologin</screen>
Lines 545-561 Link Here
545
      floppy, as the following sequence of commands
536
      floppy, as the following sequence of commands
546
      illustrates:</para>
537
      illustrates:</para>
547
538
548
      <screen>&prompt.root; <userinput>fdformat -f 1440 fd0.1440</userinput>
539
      <screen>&prompt.root; <userinput>fdformat -f 1440 fd0</userinput>
549
&prompt.root; <userinput>disklabel -w -r fd0.1440 floppy3</userinput>
540
&prompt.root; <userinput>disklabel -w fd0 floppy3</userinput>
550
&prompt.root; <userinput>newfs -t 2 -u 18 -l 1 -i 65536 /dev/fd0</userinput></screen>
541
&prompt.root; <userinput>newfs -i 65536 /dev/fd0</userinput></screen>
551
542
552
      <para>After you've formatted the floppies for DOS or UFS, you'll
543
      <para>After you've formatted the floppies for DOS or UFS, you'll
553
      need to copy the files onto them.  The distribution files are
544
      need to copy the files onto them.
554
      split into chunks conveniently sized so that 5 of them will fit
545
      The distribution files are sized so that a floppy disk will hold
555
      on a conventional 1.44MB floppy.  Go through all your floppies,
546
      a single file.
556
      packing as many files as will fit on each one, until you've got
547
      Each distribution should go into its own subdirectory on the floppy,
557
      all the distributions you want packed up in this fashion.  Each
558
      distribution should go into its own subdirectory on the floppy,
559
      e.g.: <filename>a:\bin\bin.inf</filename>, <filename>a:\bin\bin.aa</filename>, <filename>a:\bin\bin.ab</filename>, ...</para>
548
      e.g.: <filename>a:\bin\bin.inf</filename>, <filename>a:\bin\bin.aa</filename>, <filename>a:\bin\bin.ab</filename>, ...</para>
560
549
561
      <important>
550
      <important>
Lines 565-572 Link Here
565
        when fetching and concatenating the distribution.  When
554
        when fetching and concatenating the distribution.  When
566
        putting distributions onto floppies, the
555
        putting distributions onto floppies, the
567
        <filename>distname.inf</filename> file <emphasis>must</emphasis> occupy the first
556
        <filename>distname.inf</filename> file <emphasis>must</emphasis> occupy the first
568
        floppy of each distribution set.  This is also covered in
557
        floppy of each distribution set.</para>
569
        <filename>README.TXT</filename>.</para>
570
      </important>
558
      </important>
571
559
572
      <para>Once you come to the Media screen of the install, select
560
      <para>Once you come to the Media screen of the install, select
Lines 618-624 Link Here
618
      this:</para>
606
      this:</para>
619
607
620
      <screen>&prompt.root; <userinput>cd <replaceable>/where/you/have/your/dists</replaceable></userinput>
608
      <screen>&prompt.root; <userinput>cd <replaceable>/where/you/have/your/dists</replaceable></userinput>
621
&prompt.root; <userinput>tar cvf /dev/rsa0 <replaceable>dist1</replaceable> .. <replaceable>dist2</replaceable></userinput></screen>
609
&prompt.root; <userinput>tar cvf /dev/sa0 <replaceable>dist1</replaceable> .. <replaceable>dist2</replaceable></userinput></screen>
622
610
623
      <para>When you go to do the installation, you should also make
611
      <para>When you go to do the installation, you should also make
624
      sure that you leave enough room in some temporary directory
612
      sure that you leave enough room in some temporary directory
Lines 654-661 Link Here
654
        between two computers.  The link must be hard-wired because
642
        between two computers.  The link must be hard-wired because
655
        the SLIP installation doesn't currently offer a dialing
643
        the SLIP installation doesn't currently offer a dialing
656
        capability.  If you need to dial out with a modem or otherwise
644
        capability.  If you need to dial out with a modem or otherwise
657
        dialog with the link before connecting to it, then I recommend
645
        dialog with the link before connecting to it, then the PPP
658
        that the PPP utility be used instead.</para>
646
        utility should be used instead.</para>
659
647
660
        <para>If you're using PPP, make sure that you have your
648
        <para>If you're using PPP, make sure that you have your
661
        Internet Service Provider's IP address and DNS information
649
        Internet Service Provider's IP address and DNS information
Lines 699-705 Link Here
699
      <sect4>
687
      <sect4>
700
        <title>Ethernet</title>
688
        <title>Ethernet</title>
701
689
702
	<para>&os; supports many common Ethernet cards; a table
690
	<para>&os; supports most common Ethernet cards; a table
703
        of supported cards is
691
        of supported cards is
704
        provided as part of the &os; Hardware Notes (see
692
        provided as part of the &os; Hardware Notes (see
705
        <filename>HARDWARE.TXT</filename> in
693
        <filename>HARDWARE.TXT</filename> in
Lines 741-747 Link Here
741
729
742
        <para>If this server supports only <quote>privileged port</quote> access (this is
730
        <para>If this server supports only <quote>privileged port</quote> access (this is
743
        generally the default for Sun and Linux workstations), you
731
        generally the default for Sun and Linux workstations), you
744
        will need to set this option in the Options menu before
732
        may need to set this option in the Options menu before
745
        installation can proceed.</para>
733
        installation can proceed.</para>
746
734
747
        <para>If you have a poor quality Ethernet card which suffers from very
735
        <para>If you have a poor quality Ethernet card which suffers from very
Lines 842-860 Link Here
842
	</step>
830
	</step>
843
	<step>
831
	<step>
844
	  <para>If you don't get any output on your serial console,
832
	  <para>If you don't get any output on your serial console,
845
	  plug the keyboard in again and wait for some beeps.  If you
833
	  plug the keyboard in again.  If you are booting from the
846
	  are booting from the CDROM, proceed to <xref
834
	  CDROM, proceed to <xref linkend="hitspace"> as soon as you
847
	  linkend="hitspace"> as soon as you
848
	  hear the beep.</para>
835
	  hear the beep.</para>
849
	</step>
836
	</step>
850
	<step>
837
	<step>
851
	  <para>For a floppy boot, the first beep means to remove the
838
	  <para>If booting from floppies, when access to the disk stops, insert
852
	  <filename>kern.flp</filename> floppy and insert the
839
	  the first of the <filename>kernX.flp</filename> disks and press
853
	  <filename>mfsroot.flp</filename> floppy, after
840
	  <keycap>Enter</keycap>.  When access to this disk finishes, insert
854
	  which you should press <keycap>Enter</keycap> and wait for another beep.</para>
841
	  the next <filename>kernX.flp</filename> disk and press <keycap>Enter</keycap>,
842
	  and repeat until all <filename>kernX.flp</filename> disks have been
843
	  inserted.  When disk activity finishes, reinsert the <filename>boot.flp</filename>
844
	  floppy disk and press <keycap>Enter</keycap>.</para>
855
	</step>
845
	</step>
856
	<step id="hitspace">
846
	<step id="hitspace">
857
	  <para>Hit the space bar, then enter</para>
847
	  <para>Once a beep is heard, hit the number <keycap>6</keycap>, then enter</para>
858
848
859
	  <screen><userinput>boot -h</userinput></screen>
849
	  <screen><userinput>boot -h</userinput></screen>
860
850
Lines 965-971 Link Here
965
	<answer>
955
	<answer>
966
	  <para>Ongoing work with BSDI's &man.doscmd.1; utility will
956
	  <para>Ongoing work with BSDI's &man.doscmd.1; utility will
967
	  suffice in many cases, though
957
	  suffice in many cases, though
968
	  it still has some rough edges.  If you're interested in
958
	  it still has some rough edges.  The
959
	  <filename role="package">emulators/doscmd</filename> port/package
960
	  can be found in the &os; Ports Collection.
961
          If you're interested in
969
	  working on this, please send mail to the &a.emulation;
962
	  working on this, please send mail to the &a.emulation;
970
	  and indicate that you're interested in joining this ongoing
963
	  and indicate that you're interested in joining this ongoing
971
	  effort!</para>
964
	  effort!</para>
Lines 976-981 Link Here
976
	  X Window System (XFree86) to operate.</para>
969
	  X Window System (XFree86) to operate.</para>
977
	</answer>
970
	</answer>
978
      </qandaentry>
971
      </qandaentry>
972
973
      <qandaentry>
974
        <question>
975
	  <para>Can I run &microsoft.windows; applications under &os;?</para>
976
	</question>
977
978
	<answer>
979
	  <para>There are several ports/packages in the &os; Ports Collection
980
	  which can enable the use of many &windows; applications.
981
	  The <filename role="package">emulators/wine</filename> port/package
982
	  provides a compatibility layer on top of &os; which allow many
983
	  &windows; applications to be run within X Windows (XFree86).
984
	</answer>
985
      </qandaentry>
986
987
      <qandaentry>
988
        <question>
989
	  <para>Can I run other Operating Systems under &os;?</para>
990
	</question>
991
992
	<answer>
993
	  <para>Again, there are several ports/packages in the &os; Ports Collection
994
	  which simulate "virtual machines" and allow other operating systems to run
995
	  on top of &os;.
996
	  The <filename role="package">emulators/bochs</filename> port/package
997
	  allows &microsoft.windows;, Linux and even other copies of &os; to be run within a
998
	  window on the &os; desktop.
999
	  The <filename role="package">emulators/vmware2</filename> and
1000
	  <filename role="package">emulators/vmware3</filename> ports/packages
1001
	  allow the commercial VMware virtual machine software to be run on &os;.</para>
1002
	</answer>
1003
      </qandaentry>
979
    </qandaset>
1004
    </qandaset>
980
1005
981
    <qandaset arch="alpha">
1006
    <qandaset arch="alpha">
(-)release/doc/en_US.ISO8859-1/installation/common/layout.sgml (-1 / +1 lines)
Lines 93-99 Link Here
93
	filenames in <filename>packages</filename>/ to the &man.pkg.add.1; command.</para>
93
	filenames in <filename>packages</filename>/ to the &man.pkg.add.1; command.</para>
94
94
95
	<para>The Ports Collection may be installed like any other
95
	<para>The Ports Collection may be installed like any other
96
	distribution and requires about 100MB unpacked.  More
96
	distribution and requires about 190MB unpacked.  More
97
	information on the ports collection may be obtained from
97
	information on the ports collection may be obtained from
98
	<ulink url="http://www.FreeBSD.org/ports/">http://www.FreeBSD.org/ports/</ulink> or locally from
98
	<ulink url="http://www.FreeBSD.org/ports/">http://www.FreeBSD.org/ports/</ulink> or locally from
99
	<filename>/usr/share/doc/handbook</filename> if you've installed the <filename>doc</filename>
99
	<filename>/usr/share/doc/handbook</filename> if you've installed the <filename>doc</filename>

Return to bug 70485