os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Use 4.X, 3.X, etc... instead of 4.x, 3.x, etc...

Browse source 
While i'm there, the same can be done for XFree86 versions

PR:		docs/38776
Submitted by:	blackend
This commit is contained in:
Marc Fonvieille 2002-07-16 20:08:25 +00:00
parent 305e27587e
commit 718345a7e7
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=13650
1 changed files with 25 additions and 25 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

50
en_US.ISO8859-1/books/faq/book.sgml
View file

@ -399,7 +399,7 @@
| (May 1999) (Sep 1999) (Dec 1999) (June 2000) (July 2000)
|
| [4.0-STABLE]
*BRANCH* 4.0 (Mar 2000) -> 4.1 -> 4.1.1 -> 4.2 -> 4.3 -> 4.4 -> ... future 4.x releases ...
*BRANCH* 4.0 (Mar 2000) -> 4.1 -> 4.1.1 -> 4.2 -> 4.3 -> 4.4 -> ... future 4.X releases ...
|
| (July 2000) (Sep 2000) (Nov 2000)
\|/
@ -1082,7 +1082,7 @@ File: +DESC (ignored)</screen>
install FreeBSD, namely <filename>floppies/boot.flp</filename>.
However, since release 3.1 the Project has added out-of-the-box
support for a wide variety of hardware, which takes up more
space. For 3.x and later you need two floppy images:
space. For 3.X and later you need two floppy images:
<filename>floppies/kernel.flp</filename> and
<filename>floppies/mfsroot.flp</filename>. These images need to
be copied onto floppies by tools like
@ -1500,7 +1500,7 @@ File: +DESC (ignored)</screen>
themselves, <command>bad144</command> has been removed from the
FreeBSD source tree. If you wish to install FreeBSD 3.0 or
later, we strongly suggest you purchase a newer disk drive. If
you do not wish to do this, you must run FreeBSD 2.x.</para>
you do not wish to do this, you must run FreeBSD 2.X.</para>
<para>If you are seeing bad block errors with a modern IDE
drive, chances are the drive is going to die very soon (the
drive's internal remapping functions are no longer sufficient
@ -2556,7 +2556,7 @@ usbd_flags=""</programlisting>
at boot time.</para>
<para>If you are running a previous but relatively recent version
of FreeBSD (2.1.x or better) then you can simply enable it in
of FreeBSD (2.1.X or better) then you can simply enable it in
the kernel configuration menu at installation time, otherwise
later with <option>-c</option> at the <command>boot:</command>
prompt. It is disabled by default, so you will need to enable
@ -3935,7 +3935,7 @@ quit</programlisting>
</question>
<answer>
<para>This occurs in FreeBSD 3.x with PCI sound cards. The
<para>This occurs in FreeBSD 3.X with PCI sound cards. The
<devicename>pcm0</devicename> device is reserved exclusively for
ISA-based cards so, if you have a PCI card, then you will see
this error, and your card will appear as <devicename>pcm1</devicename>.
@ -3956,7 +3956,7 @@ quit</programlisting>
<screen>&prompt.root; <userinput>cd /dev</userinput>
&prompt.root; <userinput>./MAKEDEV snd1</userinput></screen>
<para>This situation does not arise in FreeBSD 4.x as a lot
<para>This situation does not arise in FreeBSD 4.X as a lot
of work has been done to make it more
<emphasis>PnP-centric</emphasis> and the
<devicename>pcm0</devicename> device is no longer reserved
@ -3967,29 +3967,29 @@ quit</programlisting>
<qandaentry>
<question id="pnp-not-found">
<para>Why is my PnP card no longer found (or found as
<literal>unknown</literal>) since upgrading to FreeBSD 4.x?</para>
<literal>unknown</literal>) since upgrading to FreeBSD 4.X?</para>
</question>
<answer>
<para>FreeBSD 4.x is now much more <emphasis>PnP-centric</emphasis>
<para>FreeBSD 4.X is now much more <emphasis>PnP-centric</emphasis>
and this has had the side effect of some PnP devices (e.g. sound
cards and internal modems) not working even though they worked
under FreeBSD 3.x.</para>
under FreeBSD 3.X.</para>
<para>The reasons for this behavior are explained by the following
e-mail, posted to the freebsd-questions mailing list by Peter
Wemm, in answer to a question about an internal modem that was
no longer found after an upgrade to FreeBSD 4.x (the comments
no longer found after an upgrade to FreeBSD 4.X (the comments
in <literal>[]</literal> have been added to clarify the
context.</para>
<blockquote>
<para>The PNP bios preconfigured it [the modem] and left it
laying around in port space, so [in 3.x] the old-style ISA
laying around in port space, so [in 3.X] the old-style ISA
probes <quote>found</quote> it there.</para>
<para>Under 4.0, the ISA code is much more PnP-centric. It was
possible [in 3.x] for an ISA probe to find a
possible [in 3.X] for an ISA probe to find a
<quote>stray</quote> device and then for the PNP device id to
match and then fail due to resource conflicts. So, it
disables the programmable cards first so this double probing
@ -4066,7 +4066,7 @@ IO range check 0x00 activate 0x01</screen>
<para>Add the hexadecimal Vendor ID for your device in the
correct place, save the file, rebuild your kernel, and reboot.
Your device should now be found as an <literal>sio</literal>
device as it was under FreeBSD 3.x</para>
device as it was under FreeBSD 3.X</para>
</answer>
</qandaentry>
@ -4721,8 +4721,8 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
linkend="mailing">mailing list</link> for periodic updates on
new entries.</para>
<para>Most ports should be available for the 2.2, 3.x and 4.x
branches, and many of them should work on 2.1.x systems as
<para>Most ports should be available for the 2.2, 3.X and 4.X
branches, and many of them should work on 2.1.X systems as
well. Each time a FreeBSD release is made, a snapshot of the
ports tree at the time of release in also included in the
<filename>ports/</filename> directory.</para>
@ -4803,7 +4803,7 @@ kern.timecounter.hardware: TSC -&gt; i8254</screen>
<answer>
<para>You are trying to run a package built on 2.2 and later on
a 2.1.x system. Please take a look at the previous section and
a 2.1.X system. Please take a look at the previous section and
get the correct port/package for your system.</para>
</answer>
</qandaentry>
@ -5662,7 +5662,7 @@ use "disklabel -r" to install initial label</screen>
</question>
<answer>
<para>This procedure is slightly different for 2.2.x and 3.x
<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
@ -5681,7 +5681,7 @@ multi(0)disk(0)rdisk(0)partition(1)\WINDOWS="Windows NT"
C:\BOOTSECT.BSD="FreeBSD"
C:\="DOS"</programlisting>
<para>For 2.2.x systems this procedure assumes that DOS, NT,
<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>same</emphasis>
disk. This example was tested on a system where DOS &amp; NT
@ -5713,7 +5713,7 @@ C:\="DOS"</programlisting>
<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
<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
@ -8069,12 +8069,12 @@ UserConfig&gt; <userinput>quit</userinput></screen>
<qandaentry>
<question id="xfree86-version">
<para>An X app I am building depends on XFree86 3.3.x, but I
have XFree86 4.x installed. What should I do?</para>
<para>An X app I am building depends on XFree86 3.3.X, but I
have XFree86 4.X installed. What should I do?</para>
</question>
<answer>
<para>To tell the port build to link to the XFree86 4.x libraries,
<para>To tell the port build to link to the XFree86 4.X libraries,
add the following to <filename>/etc/make.conf</filename>, (if you
do not have this file, create it):</para>
@ -8340,7 +8340,7 @@ Key F15 A A Menu Workplace Nop</programlisting>
to access the Internet from the Windows95 box through the
FreeBSD box. This is really just a special case of the previous
question.</para> <para>... and the answer is yes! In FreeBSD
3.x, user-mode &man.ppp.8; contains a <option>-nat</option> option. If
3.X, user-mode &man.ppp.8; contains a <option>-nat</option> option. If
you run &man.ppp.8; with the <option>-nat</option>,
set <literal>gateway_enable</literal> to
<emphasis>YES</emphasis> in <filename>/etc/rc.conf</filename>,
@ -10936,7 +10936,7 @@ raisechar=^^</programlisting>
formats for Unix:</para>
<note>
<para>Prior to FreeBSD 3.x, FreeBSD used the a.out
<para>Prior to FreeBSD 3.X, FreeBSD used the a.out
format.</para>
</note>
@ -12340,7 +12340,7 @@ Cc: current@FreeBSD.org</programlisting>
<answer>
<para>By default, the kernel address space is 256 MB on
FreeBSD 3.x and 1 GB on FreeBSD 4.x. If you run a
FreeBSD 3.X and 1 GB on FreeBSD 4.X. If you run a
network-intensive server (e.g. a large FTP or HTTP server),
you might find that 256 MB is not enough.</para>