Fix some typos. Also move things around so that "refer to previous
question" entries make sense again, unspam one of the entries and make headings fit on a single line again for the benefit of Lynx users.
This commit is contained in:
parent
f10114b093
commit
3ef7e4d140
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=2079
1 changed files with 44 additions and 41 deletions
85
FAQ/FAQ.sgml
85
FAQ/FAQ.sgml
|
@ -1,5 +1,5 @@
|
|||
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
|
||||
<!-- $Id: FAQ.sgml,v 1.86 1997-10-18 23:34:07 brian Exp $ -->
|
||||
<!-- $Id: FAQ.sgml,v 1.87 1997-10-19 13:35:27 jraynard Exp $ -->
|
||||
|
||||
<article>
|
||||
|
||||
|
@ -7,7 +7,7 @@
|
|||
|
||||
<author>Please send submissions to <tt><htmlurl url='mailto:faq@freebsd.org'
|
||||
name='<faq@freebsd.org>'></tt>
|
||||
<date>$Date: 1997-10-18 23:34:07 $</date>
|
||||
<date>$Date: 1997-10-19 13:35:27 $</date>
|
||||
|
||||
<abstract>
|
||||
This is the FAQ for FreeBSD systems version 2.X All entries are
|
||||
|
@ -127,13 +127,13 @@
|
|||
<p><url url="../handbook/current.html" name="FreeBSD-current"> is the
|
||||
development version of the operating system, which will in due
|
||||
course become 3.0-RELEASE. As such, it is really only of interest
|
||||
to developers working on the system and die-hard hobbiests.
|
||||
to developers working on the system and die-hard hobbyists.
|
||||
See the <url url="../handbook/current.html" name="relevant section">
|
||||
in the <url url="../handbook/handbook.html" name="handbook"> for
|
||||
details on running -current.
|
||||
|
||||
<p>If you are not familiar with the operating system or are not
|
||||
capable of identifying the differenece between a real problem and
|
||||
capable of identifying the difference between a real problem and
|
||||
a temporary problem, you should not use FreeBSD-current. This
|
||||
branch sometimes evolves quite quickly and can be un-buildable
|
||||
for a number of days at a time. People that use FreeBSD-current
|
||||
|
@ -211,7 +211,7 @@
|
|||
</verb>
|
||||
|
||||
<p>The -current branch is slowly progressing towards 3.0 and beyond,
|
||||
whereas the previous 2.1-stable branch was superseded by the
|
||||
whereas the previous 2.1-stable branch was superceded by the
|
||||
release of 2.2.0, the new "stability branch" aka 2.2-stable.
|
||||
3.0-current will continue to be where the active development takes
|
||||
place, up until the actual release of 3.0. At that point, 3.0 will
|
||||
|
@ -362,7 +362,7 @@
|
|||
|
||||
<sect1>
|
||||
<heading>
|
||||
Is there anything about FreeBSD on IRC (Internet Relay Chat) ?
|
||||
Are there FreeBSD IRC (Internet Relay Chat) channels?
|
||||
</heading>
|
||||
|
||||
<p>There are two channels about FreeBSD on IRC:
|
||||
|
@ -580,8 +580,7 @@
|
|||
|
||||
<sect1>
|
||||
<heading>
|
||||
I've got some other special requirements, can I make my own custom
|
||||
install floppy?
|
||||
How can I make my own custom install floppy?
|
||||
</heading>
|
||||
|
||||
<p>Currently there's no way to *just* make a custom install floppy.
|
||||
|
@ -663,8 +662,14 @@
|
|||
the bed for the last three years)?
|
||||
|
||||
<item>Did you download the floppy image in binary (or image) mode?
|
||||
(don't be embarrassed, even the best of us have made this
|
||||
mistake at least once when FTP'ing things!)
|
||||
(don't be embarrassed, even the best of us have accidentally
|
||||
downloaded a binary file in ASCII mode at least once!)
|
||||
|
||||
<item>If you're using one of these new-fangled operating systems
|
||||
like Windows95 or Windows NT, did you shut it down and restart
|
||||
the system in plain, honest DOS? It seems these OS's can
|
||||
interfere with programs that write directly to hardware, which
|
||||
the disk creation program does; even running it inside a DOS
|
||||
shell in the GUI can cause this problem.
|
||||
</enum>
|
||||
|
||||
|
@ -736,7 +741,7 @@
|
|||
into block references internally as well.
|
||||
|
||||
<p>All that matters is the <tt /logical/ geometry - the answer that the
|
||||
BIOS gets when it asks "what is your geometry" and then uses to access
|
||||
BIOS gets when it asks "what is your geometry?" and then uses to access
|
||||
the disk. As FreeBSD uses the BIOS when booting, it's very important
|
||||
to get this right. In particular, if you have more than one operating
|
||||
system on a disk, they must all agree on the geometry, otherwise you
|
||||
|
@ -785,7 +790,7 @@
|
|||
|
||||
<sect1>
|
||||
<heading>
|
||||
What about disk managers? My BIOS doesn't support large drives!
|
||||
What about disk managers? Or, I have a large drive!
|
||||
</heading>
|
||||
|
||||
<p>FreeBSD recognizes the Ontrack Disk Manager and makes allowances
|
||||
|
@ -1133,7 +1138,7 @@
|
|||
|
||||
<sect1>
|
||||
<heading>
|
||||
How do I use the mouse/trackball/touchpad/etc... on my laptop?
|
||||
How do I use the mouse/trackball/touchpad on my laptop?
|
||||
</heading>
|
||||
|
||||
<p>Please refer to <ref id="ps2mouse" name="the answer to the previous
|
||||
|
@ -1442,8 +1447,7 @@
|
|||
|
||||
<sect1>
|
||||
<heading>
|
||||
FreeBSD does not recognize my on-board AIC-7xxx EISA SCSI in an HP
|
||||
Netserver!
|
||||
My HP Netserver's SCSI controller is not detected!
|
||||
</heading>
|
||||
|
||||
<p>This is basically a known problem. The EISA on-board SCSI controller
|
||||
|
@ -1453,14 +1457,14 @@
|
|||
and FreeBSD's auto-configuration currently cannot handle this
|
||||
situation very well.
|
||||
|
||||
<p>So now, the best you can do is to pretend there were no address
|
||||
<p>So now, the best you can do is to pretend there is no address
|
||||
range clash :), by bumping the kernel option <tt/EISA_SLOTS/
|
||||
to a value of 12.
|
||||
Configure and compile a kernel, as described in the
|
||||
<url url="http://www.freebsd.org/handbook/kernelconfig.html"
|
||||
name="Handbook entry on configuring the kernel">.
|
||||
|
||||
<p>Of course, this does present you a chicken-and-egg problem when
|
||||
<p>Of course, this does present you with a chicken-and-egg problem when
|
||||
installing on such a machine. In order to work around this
|
||||
problem, a special hack is available inside <em>UserConfig</em>.
|
||||
Do not use the ``visual'' interface, but the plain command-line
|
||||
|
@ -1472,12 +1476,12 @@
|
|||
</verb>
|
||||
|
||||
<p>at the prompt, and install your system as usual. While it's
|
||||
recommendable to compile and install a custom kernel anyway,
|
||||
recommended you compile and install a custom kernel anyway,
|
||||
|
||||
<htmlurl url="http://www.freebsd.org/cgi/man.cgi?dset" name="dset">
|
||||
now also understands to save this value.
|
||||
|
||||
<p>Hopefully, future version will have a proper fix for this problem.
|
||||
<p>Hopefully, future versions will have a proper fix for this problem.
|
||||
|
||||
<p><tt/NOTE:/ You can not use a <bf/dangerously dedicated/ disk with
|
||||
an HP Netserver. See <ref id="dedicate" name="this note"> for
|
||||
|
@ -1900,6 +1904,13 @@
|
|||
at the <url url="ftp://ftp.freebsd.org/pub/FreeBSD/"
|
||||
name="ftp.freebsd.org"> master site.
|
||||
|
||||
<sect1>
|
||||
<heading>Where do I find libc.so.3.0?</heading>
|
||||
|
||||
<p>You are trying to run a package for 2.2/3.0 on a 2.1.x
|
||||
system. Please take a look at the previous section and get
|
||||
the correct port/package for your system.
|
||||
|
||||
<sect1>
|
||||
<heading>
|
||||
ghostscript gives lots of errors with my 386/486SX.<label id="emul">
|
||||
|
@ -1917,13 +1928,6 @@
|
|||
<p><bf/NOTE/ You will need to remove the <tt/MATH_EMULATE/
|
||||
option when you do this.
|
||||
|
||||
<sect1>
|
||||
<heading>Where do I find libc.so.3.0?</heading>
|
||||
|
||||
<p>You are trying to run a package for 2.2/3.0 on a 2.1.x
|
||||
system. Please take a look at the previous section and get
|
||||
the correct port/package for your system.
|
||||
|
||||
<sect1>
|
||||
<heading>
|
||||
When I run a SCO/iBCS2 application, it bombs on <tt/socksys/.
|
||||
|
@ -2547,7 +2551,7 @@ disk fd1 at fdc0 drive 1
|
|||
|
||||
<sect1>
|
||||
<heading>
|
||||
How about FreeBSD and Linux? How do I boot FreeBSD from LILO?
|
||||
How do I boot FreeBSD and Linux from LILO?
|
||||
</heading>
|
||||
|
||||
<p>Theoretically you should be able to boot FreeBSD from LILO by
|
||||
|
@ -3265,7 +3269,7 @@ disk fd1 at fdc0 drive 1
|
|||
<p><tt/xdm/ should be started without any arguments (i.e., as a
|
||||
daemon).
|
||||
|
||||
<p><bf/NOTE:/ A previos version of this FAQ told you to add the
|
||||
<p><bf/NOTE:/ A previous version of this FAQ told you to add the
|
||||
<tt/vt/ you want X to use to the
|
||||
<tt>/usr/X11R6/lib/X11/xdm/Xservers</tt> file. This is not necessary:
|
||||
X will use the first free <tt/vt/ it finds.
|
||||
|
@ -3370,16 +3374,6 @@ disk fd1 at fdc0 drive 1
|
|||
standard requirements for routers; however, it comes close enough
|
||||
for ordinary usage.
|
||||
|
||||
<sect1>
|
||||
<heading>
|
||||
I want to recompile the latest BIND from ISC. It blows up during the
|
||||
compilation on some types conflicts. What can I do?
|
||||
</heading>
|
||||
|
||||
<p>There is a conflict between the ``<tt/cdefs.h/'' file in the
|
||||
distribution and the one shipped with FreeBSD. Just remove
|
||||
<tt>compat/include/sys/cdefs.h</tt>.
|
||||
|
||||
<sect1>
|
||||
<heading>Can I connect my Win95 box to the Internet via FreeBSD?</heading>
|
||||
|
||||
|
@ -3404,6 +3398,15 @@ disk fd1 at fdc0 drive 1
|
|||
|
||||
<p>See also the section on <ref id="direct-at" name="natd">.
|
||||
|
||||
<sect1>
|
||||
<heading>
|
||||
Why does recompiling the latest BIND from ISC fail?
|
||||
</heading>
|
||||
|
||||
<p>There is a conflict between the ``<tt/cdefs.h/'' file in the
|
||||
distribution and the one shipped with FreeBSD. Just remove
|
||||
<tt>compat/include/sys/cdefs.h</tt>.
|
||||
|
||||
<sect1>
|
||||
<heading>Does FreeBSD support SLIP and PPP?</heading>
|
||||
|
||||
|
@ -3668,7 +3671,7 @@ default 10.0.0.2 UGSc 0 0 tun0
|
|||
also sees the NAK reflect (which also means ppp must change
|
||||
its magic). This produces a potentially enormous number of
|
||||
magic number changes, all of which are happily piling into
|
||||
the servers tty buffer. As soon as ppp starts on the server,
|
||||
the server's tty buffer. As soon as ppp starts on the server,
|
||||
it's flooded with magic number changes and almost immediately
|
||||
decides it's tried enough to negotiate LCP and gives up.
|
||||
Meanwhile, the client, who no longer sees the reflections,
|
||||
|
@ -4558,7 +4561,7 @@ vat_nv_record Recording tools for vat ftp.sics.se:archive/vat_nv_record.tar.Z
|
|||
|
||||
<sect1>
|
||||
<heading>
|
||||
What is FreeBSD's a.out executable format, and why not ELF?
|
||||
What is FreeBSD's a.out executable format and not ELF?
|
||||
</heading>
|
||||
|
||||
<p>To understand why FreeBSD uses the <tt>a.out</tt> format, you must
|
||||
|
@ -4753,7 +4756,7 @@ vat_nv_record Recording tools for vat ftp.sics.se:archive/vat_nv_record.tar.Z
|
|||
|
||||
<sect1>
|
||||
<heading>
|
||||
What's with all these SNAPshot, RELENG and RELEASE releases?
|
||||
What's with all these SNAP, RELENG and RELEASE releases?
|
||||
</heading>
|
||||
|
||||
<p>There are currently three active/semi-active branches in the FreeBSD
|
||||
|
|
Loading…
Reference in a new issue