Make some long-overdue updates in the install document, add

freebsd-emulation list to entities.
This commit is contained in:
Jordan K. Hubbard 1996-05-16 20:20:57 +00:00
parent 743b6f12fe
commit a34162e6e8
2 changed files with 59 additions and 119 deletions

View File

@ -1,4 +1,4 @@
<!-- $Id: authors.sgml,v 1.20 1996/05/09 23:04:30 mpp Exp $ -->
<!-- $Id: authors.sgml,v 1.21 1996/05/14 20:31:50 rich Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
@ -25,6 +25,10 @@ and double quotes.
<tt><htmlurl url='mailto:freebsd-current@FreeBSD.ORG'
name='&lt;freebsd-current@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.emulation "FreeBSD-emulation mailing list
<tt><htmlurl url='mailto:freebsd-emulation@FreeBSD.ORG'
name='&lt;freebsd-emulation@FreeBSD.ORG&gt;'></tt>">
<!ENTITY a.fs "FreeBSD filesystem project mailing list
<tt><htmlurl url='mailto:freebsd-fs@FreeBSD.ORG'
name='&lt;freebsd-fs@FreeBSD.ORG&gt;'></tt>">

View File

@ -1,4 +1,4 @@
<!-- $Id: install.sgml,v 1.26 1996/05/09 23:04:45 mpp Exp $ -->
<!-- $Id: install.sgml,v 1.27 1996/05/16 20:01:26 jkh Exp $ -->
<!-- The FreeBSD Documentation Project -->
<!--
@ -156,7 +156,7 @@ Boot:
configurations, various SCSI controller, network and
serial cards is also provided.
A minimum of five megabytes of RAM is required to run FreeBSD.
A minimum of four megabytes of RAM is required to run FreeBSD.
To run the X-window system, eight megabytes of RAM is the
recommended minimum.
@ -181,6 +181,7 @@ Boot:
<item>Adaptec 274x/284x/2940/3940
(Narrow/Wide/Twin)
series EISA/VLB/PCI SCSI controllers
<item>Adaptec AIC7850 on-board SCSI controllers
<item>Adaptec
<!-- AIC-6260 and - actually not working, joerg -->
AIC-6360 based boards,
@ -274,9 +275,11 @@ Boot:
<item>Fujitsu FMV-181 and FMV-182
<item>Fujitsu MB86960A/MB86965A
<item>Intel EtherExpress
<item>Intel EtherExpress Pro 100Mbit.
<item>Intel EtherExpress Pro/100B 100Mbit.
<item>Isolan AT 4141-0 (16 bit)
<item>Isolink 4110 (8 bit)
@ -293,7 +296,7 @@ Boot:
<item>3Com 3C509, 3C579, 3C589 (PCMCIA) Etherlink III
<item>3Com 3C590, 3C595
<item>3Com 3C590, 3C595 Etherlink III
<item>Toshiba ethernet cards
@ -351,8 +354,9 @@ Boot:
as we have no hand or say in how they're created). You can either
boot into the CD installation directly from DOS using Walnut Creek's
supplied ``install.bat'' batch file or you can make a boot floppy with
the ``makeflp.bat'' command [NOTE: If you're using an IDE CDROM, use
the inst&lowbar;ide.bat or atapiflp.bat batch files instead].
the ``makeflp.bat'' command. [NOTE: If you're running
FreeBSD 2.1-RELEASE and have an IDE CDROM, use the
inst&lowbar;ide.bat or atapiflp.bat batch files instead].
For the easiest interface of all (from DOS), type
``view''. This will bring up a DOS menu utility that
@ -402,7 +406,7 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent
<sect1><heading>Before installing from Floppy</heading>
<p>If you must install from floppy disks, either due to
unsupported hardware or just because you enjoy doing
unsupported hardware or simply because you enjoy doing
things the hard way, you must first prepare some
floppies for the install.
@ -434,22 +438,27 @@ ftp:*:99:99::0:0:FTP:/cdrom:/nonexistent
a format is still not a bad idea though you don't need to put
a DOS filesystem on each floppy. You can use the `disklabel'
and `newfs' commands to put a UFS filesystem on them instead,
like so:
as the following sequence of commands (for a 3.5" 1.44MB floppy
disk) illustrates:
<tscreen><verb>
disklabel -w -r fd0 floppy3 (use floppy5 for 1.2MB disks)
newfs /dev/rfd0
fdformat -f 1440 fd0.1440
disklabel -w -r fd0.1440 floppy3
newfs -t 2 -u 18 -l 1 -i 65536 /dev/rfd0
(Use "fd0.1200" and "floppy5" for 5.25" 1.2MB disks).
</verb></tscreen>
Then you can mount and write to them like any other file
system.
After you have DOS formatted the floppies, you will
need to copy the files onto them. The distribution
files are split into chunks conveniently sized so that
5 of them will fit on a conventional 1.44MB floppy. Go
through all your floppies, packing as many files as
will fit on each one, until you have got all the
distributions you want packed up in this fashion. Each
distribution should go into a subdirectory on the
After you have formatted the floppies, you will need to copy
the files onto them. The distribution files are split into
chunks conveniently sized so that 5 of them will fit on a
conventional 1.44MB floppy. Go through all your floppies,
packing as many files as will fit on each one, until you have
got all the distributions you want packed up in this fashion.
Each distribution should go into a subdirectory on the
floppy, e.g.: <bf>a:&bsol;bin&bsol;bin.aa</bf>,
<bf>a:&bsol;bin&bsol;bin.ab</bf>, and so on.
@ -716,15 +725,16 @@ ftp://foo.bar.com:1234/pub/FreeBSD
<item>Select the Options item and set any special
preferences you may have.
<item>Select a Custom or Express install, depending on
whether or not you would like the installation to give
you a high degree of control over each step of the
installation or simply lead you through it, choosing
reasonable defaults when possible. See details on
both installation types below.
<item>Select a Novice, Custom or Express install, depending on
whether or not you would like the installation to help
you through a typical installation, give you a high degree of
control over each step of the installation or simply whizz
through it (using reasonable defaults when possible) as fast
as possible. If you've never used FreeBSD before then the
Novice installation method is most recommended.
<item>The Configure menu choice allows you to further
configure your FreeBSD installation by giving you
<item>The final configuration menu choice allows you to
further configure your FreeBSD installation by giving you
menu-driven access to various system defaults. Some
items, like networking, may be especially important
if you did a CDROM/Tape/Floppy installation and have
@ -734,82 +744,6 @@ ftp://foo.bar.com:1234/pub/FreeBSD
when you first reboot from the hard disk.
</enum>
<sect1><heading>Express installation</heading>
<p>The express installation is not too much different than
the Custom one except that it leads you through the
required stages in the proper order and presents you
with various helpful prompts along the way.
<enum>
<item>The first step is the `Partition Editor', which
allows you to chose how your drives will be used
for FreeBSD. If you are dedicating an entire drive
to FreeBSD, the `A' command is probably all you
need to type here.
<item>Next, with the `Label Editor', you can specify
how the space in any allocated FreeBSD partitions
should be used by FreeBSD, or where to mount a
non-FreeBSD partition (such as DOS). If you want
the standard layout, simply type `A' here.
<item>Next, the `Distributions' menu allows you to
specify which parts of FreeBSD you wish to load. A
good choice is ``User'' for a small system or
``Developer'' for someone wanting a bit more out of
FreeBSD. If none of the existing collections sound
applicable, select Custom.
<item>Next, the `Media' menu allows you to specify
what kind of media you wish to install from. If a
desired media choice is found and configured
automatically then this menu will simply return,
otherwise you will be asked for additional details on
the media device type.
<item>Finally, you will be prompted to commit all of
these actions at once (nothing has been written to
your disk so far, nor will it until you give the
final confirmation). All new or changed partition
information will be written out, file systems will
be created and/or non-destructively labeled
(depending on how you set their newfs flags in the
Label Editor) and all selected distributions will
be extracted.
</enum>
At this point, you are generally done with the
sysinstall utility and can select the final `Quit'. If
you are running it as an installer (e.g., before the
system is all the way up) then the system will now
reboot after you press return one last time. If you
selected the boot manager option, you will see a small
boot menu with an `F?' prompt. Press the function key
for BSD (it will be shown) and you should boot up into
FreeBSD off the hard disk.
If this fails to happen for some reason, see the Q&amp;A
section of the Hardware Guide for possible clues!
<sect1><heading>Custom installation</heading>
<p>You can do anything you like in this menu without
altering your system <em>except</em> for ``Commit'',
which will perform any requests to alter your system
you may have made. Some of the menu options will also
have direct `Write' commands available for committing an
operation immediately, but they should only be used if
you are absolutely sure it is necessary. It is generally
better to make your changes and then commit them all at
once so that you are left with the option of changing
your mind up to the very last minute.
If you are confused at any point, the F1 key usually
pulls up the right information for the screen you are
in.
<sect><heading>MS-DOS user's Questions and Answers</heading>
<p>Many FreeBSD users wish to install FreeBSD on PCs inhabited
@ -853,28 +787,30 @@ ftp://foo.bar.com:1234/pub/FreeBSD
between MS-DOS and FreeBSD.
<!-- XXX Status???
<bf>Can I mount my MS-DOS extended partitions?</bf>
This feature is not in FreeBSD 2.0.5 but should be in 2.1.
We have laid all the groundwork for making this happen, now
we just need to do the last 1 percent of the work involved.
-->
Yes. DOS extended partitions are mapped in at the end of the other
``slices'' in FreeBSD, e.g. your D: drive might be /dev/sd0s5,
your E: drive /dev/sd0s6, and so on. This example assumes, of
course, that your extended partition is on SCSI drive 0. For IDE drives,
substitute ``wd'' for ``sd'' appropriately. You otherwise mount extended
partitions exactly like you would mount any other DOS drive, e.g.:
<tscreen><verb>
mount -t msdos /dev/sd0s5 /dos_d
</verb></tscreen>
<bf>Can I run MS-DOS binaries under FreeBSD?</bf>
Not yet! We would like to add support for this someday, but
are still lacking anyone to actually do the work.
Ongoing work with Linux's DOSEMU utility may bring this
much closer to being a reality sometime soon. Send mail
to the &a.hackers
if you're interested in joining
are still lacking anyone to actually do the work. BSDI has
also donated their DOS emulator to the BSD world and this is slowly
being ported to FreeBSD-current.
Send mail to the &a.emulation if you're interested in joining
this effort!
However, there is a nice application available in the
<ref id="ports" name="The Ports Collection"> called pcemu,
that allows you to run many basic MS-DOS text-mode binaries
In the interim, there is a nice application available in the
<ref id="ports" name="The Ports Collection"> called pcemu
which allows you to run many basic MS-DOS text-mode binaries
by entirely emulating an 8088 CPU.