Document using the NT boot loader for 3.x systems.

PR:             docs/13207
Submitted by:   Mark Ovens <mark@ukug.uk.freebsd.org>

Update the "Memory limits" question.

PR:             docs/13403
Submitted by:   Stephen Roznowski <sjr@home.com>
This commit is contained in:
Nik Clayton 1999-09-26 00:05:28 +00:00
parent d298d96457
commit e06812d8fa
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=5730
2 changed files with 54 additions and 24 deletions

View file

@ -10,7 +10,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.11 1999/09/22 07:23:47 jkoshy Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.12 1999/09/23 08:43:54 wosch Exp $</pubdate>
<abstract><para> This is the FAQ for FreeBSD systems version 2.X All entries are
assumed to be relevant to FreeBSD 2.0.5 and later, unless otherwise noted.
@ -1543,10 +1543,14 @@ Your system should boot successfully.
<qandaentry><question>
<para>What are the limits for memory?</para></question><answer>
<para>For memory, the (theoretical) limit is 4 gigabytes. One gigabyte
has been tested; you generally can't buy i386 PCs that can support
much more than that.</para>
<para>For memory, the limit is 4 gigabytes. This configuration has
been tested, see <ulink
URL="ftp://ftp.cdrom.com/archive-info/configuration">wcarchive's
configuration</ulink> for more details. If you plan to install this
much memory into a machine, you need to be careful. You'll probably
want to use ECC memory and to reduce capacitive loading use 9 chip
memory modules vice 18 chip memory modules.</para>
</answer></qandaentry>
<qandaentry><question>
@ -3478,6 +3482,9 @@ information, see this tutorial by Mark Ovens at
<qandaentry><question>
<para>How can I use the NT loader to boot FreeBSD?</para></question><answer>
<para>This procedure is slightly different for 2.2.x and 3.x (with the
3-stage boot) systems.</para>
<para>The general idea is that you copy the first sector of your
native root FreeBSD partition into a file in the DOS/NT
partition. Assuming you name that file something like
@ -3496,7 +3503,7 @@ something like this:</para>
</literallayout>
</para>
<para>This procedure assumes that DOS, NT, FreeBSD, or whatever
<para>For 2.2.x systems this procedure assumes that DOS, NT, FreeBSD, or whatever
have been installed into their respective fdisk partitions on the
<emphasis remap=bf>same</emphasis> disk. In my case DOS &amp; NT are in the first fdisk
partition and FreeBSD is in the second. I also installed FreeBSD
@ -3529,8 +3536,16 @@ and/or the <filename>bootsect.lnx</filename> file from the floppy to
</para>
<para>If FreeBSD is booting from the MBR, restore it with the DOS
``<emphasis remap=tt>fdisk</emphasis>'' command after you reconfigure them to boot from their
``<command>fdisk</command>'' command after you reconfigure them to boot from their
native partitions.</para>
<para>For FreeBSD 3.x systems the procedure is somewhat simpler.</para>
<para>If FreeBSD is installed on the same disk as the NT boot partition
copy <filename>/boot/boot1</filename> to <filename>c:\bootsect.bsd</filename>
or if FreeBSD is installed on a different disk copy
<filename>/boot/boot0</filename> to <filename>c:\bootsect.bsd</filename>.
Then edit <filename>c:\bootsect.ini</filename> as described earlier.</para>
</answer></qandaentry>
@ -3544,23 +3559,23 @@ system. Very briefly, these are:</para>
<para>Boot Linux, and add the following lines to
<filename>/etc/lilo.conf</filename>:
<literallayout> other=/dev/hda2
<programlisting> other=/dev/hda2
table=/dev/hda
label=FreeBSD
</literallayout>
</programlisting>
(the above assumes that your FreeBSD slice is known to Linux as
<filename>/dev/hda2</filename>; tailor to suit your setup). Then,
run <emphasis remap=tt>lilo</emphasis> as root and you should be done.</para>
run <command>lilo</command> as root and you should be done.</para>
<para>If FreeBSD resides on another disk, you need to add
``<literal>loader=/boot/chain.b</literal>'' to the LILO entry.
For example:
<literallayout> other=/dev/dab4
<programlisting> other=/dev/dab4
table=/dev/dab
loader=/boot/chain.b
label=FreeBSD
</literallayout>
</programlisting>
</para>
<para>In some cases you may need to specify the BIOS drive number

View file

@ -10,7 +10,7 @@
</author>
</authorgroup>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.11 1999/09/22 07:23:47 jkoshy Exp $</pubdate>
<pubdate>$FreeBSD: doc/en_US.ISO_8859-1/books/faq/book.sgml,v 1.12 1999/09/23 08:43:54 wosch Exp $</pubdate>
<abstract><para> This is the FAQ for FreeBSD systems version 2.X All entries are
assumed to be relevant to FreeBSD 2.0.5 and later, unless otherwise noted.
@ -1543,10 +1543,14 @@ Your system should boot successfully.
<qandaentry><question>
<para>What are the limits for memory?</para></question><answer>
<para>For memory, the (theoretical) limit is 4 gigabytes. One gigabyte
has been tested; you generally can't buy i386 PCs that can support
much more than that.</para>
<para>For memory, the limit is 4 gigabytes. This configuration has
been tested, see <ulink
URL="ftp://ftp.cdrom.com/archive-info/configuration">wcarchive's
configuration</ulink> for more details. If you plan to install this
much memory into a machine, you need to be careful. You'll probably
want to use ECC memory and to reduce capacitive loading use 9 chip
memory modules vice 18 chip memory modules.</para>
</answer></qandaentry>
<qandaentry><question>
@ -3478,6 +3482,9 @@ information, see this tutorial by Mark Ovens at
<qandaentry><question>
<para>How can I use the NT loader to boot FreeBSD?</para></question><answer>
<para>This procedure is slightly different for 2.2.x and 3.x (with the
3-stage boot) systems.</para>
<para>The general idea is that you copy the first sector of your
native root FreeBSD partition into a file in the DOS/NT
partition. Assuming you name that file something like
@ -3496,7 +3503,7 @@ something like this:</para>
</literallayout>
</para>
<para>This procedure assumes that DOS, NT, FreeBSD, or whatever
<para>For 2.2.x systems this procedure assumes that DOS, NT, FreeBSD, or whatever
have been installed into their respective fdisk partitions on the
<emphasis remap=bf>same</emphasis> disk. In my case DOS &amp; NT are in the first fdisk
partition and FreeBSD is in the second. I also installed FreeBSD
@ -3529,8 +3536,16 @@ and/or the <filename>bootsect.lnx</filename> file from the floppy to
</para>
<para>If FreeBSD is booting from the MBR, restore it with the DOS
``<emphasis remap=tt>fdisk</emphasis>'' command after you reconfigure them to boot from their
``<command>fdisk</command>'' command after you reconfigure them to boot from their
native partitions.</para>
<para>For FreeBSD 3.x systems the procedure is somewhat simpler.</para>
<para>If FreeBSD is installed on the same disk as the NT boot partition
copy <filename>/boot/boot1</filename> to <filename>c:\bootsect.bsd</filename>
or if FreeBSD is installed on a different disk copy
<filename>/boot/boot0</filename> to <filename>c:\bootsect.bsd</filename>.
Then edit <filename>c:\bootsect.ini</filename> as described earlier.</para>
</answer></qandaentry>
@ -3544,23 +3559,23 @@ system. Very briefly, these are:</para>
<para>Boot Linux, and add the following lines to
<filename>/etc/lilo.conf</filename>:
<literallayout> other=/dev/hda2
<programlisting> other=/dev/hda2
table=/dev/hda
label=FreeBSD
</literallayout>
</programlisting>
(the above assumes that your FreeBSD slice is known to Linux as
<filename>/dev/hda2</filename>; tailor to suit your setup). Then,
run <emphasis remap=tt>lilo</emphasis> as root and you should be done.</para>
run <command>lilo</command> as root and you should be done.</para>
<para>If FreeBSD resides on another disk, you need to add
``<literal>loader=/boot/chain.b</literal>'' to the LILO entry.
For example:
<literallayout> other=/dev/dab4
<programlisting> other=/dev/dab4
table=/dev/dab
loader=/boot/chain.b
label=FreeBSD
</literallayout>
</programlisting>
</para>
<para>In some cases you may need to specify the BIOS drive number