Clean up assorted formatting glitches. Mostly associated with missing
<header> tags.
This commit is contained in:
John Fieber
parent
918bad6d52
commit
1279901cec
@ -3,7 +3,7 @@
|
||||
|
||||
This conversion has been made by Ollivier Robert.
|
||||
|
||||
$Id: booting.sgml,v 1.3 1995/06/14 18:38:50 jfieber Exp $
|
||||
$Id: booting.sgml,v 1.4 1995/06/30 17:37:31 jfieber Exp $
|
||||
|
||||
|
||||
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
|
||||
@ -30,28 +30,25 @@
|
||||
determine the root filesystem and initialize user-land things. This
|
||||
leads to some interesting possibilities shown below.
|
||||
|
||||
<sect>Loading a kernel
|
||||
<sect><heading>Loading a kernel</heading>
|
||||
<p>
|
||||
We presently have three basic mechanisms for loading the kernel:
|
||||
<enum>
|
||||
<item>biosboot
|
||||
<item>dosboot
|
||||
<item>netboot
|
||||
</enum>
|
||||
Each will be described in detail below. They all pass some
|
||||
We presently have three basic mechanisms for loading the
|
||||
kernel as described below:
|
||||
They all pass some
|
||||
information to the kernel to help the kernel decide what to do
|
||||
next.
|
||||
|
||||
<sect1>Biosboot
|
||||
<p>
|
||||
<descrip>
|
||||
<tag>Biosboot</tag>
|
||||
|
||||
Biosboot is our ``bootblocks'', it consists of two files, which
|
||||
will be installed in the first 8Kbytes of the floppy or hard-disk
|
||||
slice to be booted from.
|
||||
|
||||
Biosboot can load a kernel from a FreeBSD filesystem.
|
||||
|
||||
<sect1>Dosboot
|
||||
<p>
|
||||
<tag>Dosboot</tag>
|
||||
|
||||
Dosboot was written by DI. Christian Gusenbauer, and is
|
||||
unfortunately at this time one of the few pieces of code that
|
||||
isn't compilable under FreeBSD itself because it is written for
|
||||
@ -63,53 +60,51 @@
|
||||
high memory on MS/DOS systems and usually wins them for it's
|
||||
case.
|
||||
|
||||
<sect1>Netboot
|
||||
<p>
|
||||
<tag>Netboot</tag>
|
||||
|
||||
Netboot will try to find a supported ethernet card, and use
|
||||
BOOTP, TFTP and NFS to find a kernel file to boot.
|
||||
</descrip>
|
||||
|
||||
<sect>Determine the root filesystem
|
||||
|
||||
<sect><heading>Determine the root filesystem</heading>
|
||||
<p>
|
||||
Once the kernel is loaded and the boot-code jumps to it, the kernel
|
||||
will initialize itself, trying to determine what hardware is
|
||||
present and so on, and then it needs to find a root filesystem.
|
||||
|
||||
Presently we support the following types of rootfilesystems:
|
||||
<itemize>
|
||||
<item>UFS
|
||||
<item>MSDOS
|
||||
<item>MFS
|
||||
<item>CD9660
|
||||
<item>NFS
|
||||
</itemize>
|
||||
|
||||
<sect1>UFS
|
||||
<p>
|
||||
<descrip>
|
||||
<tag>UFS</tag>
|
||||
|
||||
This is the most normal type of root filesystem. It can reside on
|
||||
a floppy or on harddisk.
|
||||
|
||||
<sect1>MSDOS
|
||||
<p>
|
||||
<tag>MSDOS</tag>
|
||||
|
||||
While this is technically possible, it isn't particular useful,
|
||||
because of ``FAT'' filesystems inability to make links, device
|
||||
nodes and such ``UNIXisms''.
|
||||
|
||||
<sect1>MFS
|
||||
<p>
|
||||
<tag>MFS</tag>
|
||||
|
||||
This is actually a UFS filesystem which has been compiled into
|
||||
the kernel. That means that the kernel does not really need any
|
||||
disks/floppies or other HW to function.
|
||||
|
||||
<sect1>CD9660
|
||||
<p>
|
||||
<tag>CD9660</tag>
|
||||
|
||||
This is for using a CD-ROM as root filesystem.
|
||||
|
||||
<sect1>NFS
|
||||
<p>
|
||||
<tag>NFS</tag>
|
||||
|
||||
This is for using a fileserver as root filesystem, basically
|
||||
making it a diskless machine.
|
||||
</descrip>
|
||||
|
||||
<sect>Initialize user-land things
|
||||
|
||||
<sect><heading>Initialize user-land things</heading>
|
||||
<p>
|
||||
To get the user-land going, when the kernel has finished
|
||||
initialization, it will create a with ``<tt/pid == 1/'' and execute
|
||||
@ -124,7 +119,7 @@
|
||||
1/''.
|
||||
|
||||
|
||||
<sect>Interesting combinations
|
||||
<sect><heading>Interesting combinations</heading>
|
||||
<p>
|
||||
Boot a kernel with a MFS in it with a special <tt>/sbin/init</tt>
|
||||
which...
|
||||
|
||||
@ -1,9 +1,9 @@
|
||||
<!-- $Id: contrib.sgml,v 1.8 1995/08/26 07:54:44 asami Exp $ -->
|
||||
<!-- $Id: contrib.sgml,v 1.9 1995/08/28 21:53:12 mpp Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<chapt>FreeBSD contributor list<label id="contrib">
|
||||
<chapt><heading>FreeBSD contributor list<label id="contrib"></heading>
|
||||
|
||||
<sect>Derived software contributors
|
||||
<sect><heading>Derived software contributors</heading>
|
||||
|
||||
<p>This software was originally derived from William
|
||||
F. Jolitz's 386BSD release 0.1, though almost none of the
|
||||
@ -21,7 +21,7 @@
|
||||
BSD based operating systems on people's computers! We wish
|
||||
the NetBSD group every success in their endevors.
|
||||
|
||||
<sect>Hardware contributors
|
||||
<sect><heading>Hardware contributors</heading>
|
||||
|
||||
<p>A special thank-you to Walnut Creek CDROM for providing
|
||||
the Pentium P5-90 and 486/DX2-66 EISA/VL systems that are
|
||||
@ -42,7 +42,7 @@
|
||||
contributing his floppy tape streamer for experimental
|
||||
work.
|
||||
|
||||
<sect>The FreeBSD core team<label id="contrib:core">
|
||||
<sect><heading>The FreeBSD core team<label id="contrib:core"></heading>
|
||||
|
||||
<p>(in alphabetical order by first name):
|
||||
|
||||
@ -64,7 +64,7 @@
|
||||
<item>Søren Schmidt <sos@FreeBSD.org>
|
||||
</itemize>
|
||||
|
||||
<sect>Who is responsible for what
|
||||
<sect><heading>Who is responsible for what</heading>
|
||||
|
||||
<p><descrip>
|
||||
<tag/President/ Jordan K. Hubbard <jkh@FreeBSD.org>
|
||||
@ -82,7 +82,7 @@
|
||||
<rich@FreeBSD.org>
|
||||
</descrip>
|
||||
|
||||
<sect>Additional FreeBSD contributors
|
||||
<sect><heading>Additional FreeBSD contributors</heading>
|
||||
|
||||
<p>(in alphabetical order by first name):
|
||||
|
||||
@ -196,7 +196,7 @@
|
||||
<item>Yves Fonk <yves@cpcoup5.tn.tudelft.nl>
|
||||
</itemize>
|
||||
|
||||
<sect>386BSD Patch kit patch contributors
|
||||
<sect><heading>386BSD Patch kit patch contributors</heading>
|
||||
|
||||
<p>(in alphabetical order by first name):
|
||||
|
||||
|
||||
@ -3,7 +3,7 @@
|
||||
#
|
||||
# Converted by Ollivier RObert <roberto@FreeBSD.ORG>
|
||||
#
|
||||
# $Id: ctm.sgml,v 1.2 1995/06/30 17:37:32 jfieber Exp $
|
||||
# $Id: ctm.sgml,v 1.3 1995/07/06 14:24:56 jfieber Exp $
|
||||
#
|
||||
# ----------------------------------------------------------------------------
|
||||
# "THE BEER-WARE LICENSE" (Revision 42):
|
||||
@ -25,7 +25,7 @@
|
||||
this time on the process of creating deltas, so talk to &a.phk;
|
||||
for more information should you wish to use <tt/CTM/ for other things.
|
||||
|
||||
<sect1>Why should I use <tt/CTM/ ?
|
||||
<sect1><heading>Why should I use <tt/CTM/?</heading>
|
||||
<p><tt/CTM/ will give you a local copy of the ``FreeBSD-current''
|
||||
sources. If you are an active developer on FreeBSD, but have lousy
|
||||
or non-existent TCP/IP connectivity, <tt/CTM/ was made for you.
|
||||
@ -39,7 +39,7 @@
|
||||
running ``current'' sources, and for this it is recommended that
|
||||
you read <ref id="current" name="Staying current with FreeBSD">.
|
||||
|
||||
<sect1>What do I need to use <tt/CTM/?
|
||||
<sect1><heading>What do I need to use <tt/CTM/?</heading>
|
||||
|
||||
<p>You will need two things: The ``<tt/CTM/'' program and the initial
|
||||
deltas to feed it (to get up to ``current'' levels).
|
||||
@ -82,7 +82,7 @@
|
||||
posted. Send an email to <tt/majordomo@freebsd.org/ with a single
|
||||
line of ``<tt/subscribe ctm-announce/'' to get added to the list.
|
||||
|
||||
<sect1>Starting off with <tt/CTM/ for the first time:
|
||||
<sect1><heading>Starting off with <tt/CTM/ for the first time</heading>
|
||||
<p>Before you can start using <tt/CTM/ deltas, you will need to get a
|
||||
special ``base'' delta that provides a starting point for all
|
||||
deltas produced subsequently to it.
|
||||
@ -100,7 +100,7 @@
|
||||
Once you've picked a base delta to start from, you will also need
|
||||
all deltas with higher numbers following it.
|
||||
|
||||
<sect1>Using <tt/CTM/ in your daily life:
|
||||
<sect1><heading>Using <tt/CTM/ in your daily life</heading>
|
||||
<p>To apply the deltas, simply say
|
||||
<verb>
|
||||
cd /where/ever/you/want/the/stuff
|
||||
@ -130,7 +130,7 @@
|
||||
make a copy.
|
||||
|
||||
|
||||
<sect1>Future plans for <tt/CTM/
|
||||
<sect1><heading>Future plans for <tt/CTM/</heading>
|
||||
<p>
|
||||
Tons of them:
|
||||
<itemize>
|
||||
@ -155,7 +155,7 @@
|
||||
The bad news is that I am very busy, so any help in doing this will
|
||||
be most welcome. And don't forget to tell me what you want also...
|
||||
|
||||
<sect1>Miscellaneous stuff
|
||||
<sect1><heading>Miscellaneous stuff</heading>
|
||||
<p>
|
||||
All the ``DES infected'' (e.g. export controlled) source is not
|
||||
included. You will get the ``international'' version only. If
|
||||
@ -178,7 +178,7 @@
|
||||
for details.
|
||||
|
||||
|
||||
<sect1>Thanks!
|
||||
<sect1><heading>Thanks!</heading>
|
||||
<p>
|
||||
<descrip>
|
||||
<tag/Bruce Evans/
|
||||
|
||||
@ -1,6 +1,6 @@
|
||||
<!-- This is an SGML document in the linuxdoc DTD of the Tutorial for
|
||||
Configuring a FreeBSD for Dialup Services by Guy Helmer.
|
||||
$Id: dialup.sgml,v 1.1.1.1 1995/04/28 16:19:59 jfieber Exp $
|
||||
$Id: dialup.sgml,v 1.2 1995/06/30 17:37:34 jfieber Exp $
|
||||
|
||||
<!DOCTYPE linuxdoc PUBLIC "-//Linux//DTD linuxdoc//EN">
|
||||
|
||||
@ -37,7 +37,7 @@ in a UNIX-like environment, and how to look up manual pages on the
|
||||
system. As discussed below, you'll need certain versions of FreeBSD,
|
||||
and knowledge of some terminology & modem and cabling.
|
||||
|
||||
<sect2>FreeBSD Version
|
||||
<sect2><heading>FreeBSD Version</heading>
|
||||
<p>
|
||||
|
||||
First, it is assumed that you are using FreeBSD version 1.1 or higher
|
||||
@ -47,7 +47,7 @@ device driver (<tt/sio/) has improved in every release of FreeBSD, so
|
||||
more recent versions of FreeBSD are assumed to have better and more
|
||||
efficient drivers than earlier versions.
|
||||
|
||||
<sect2>Terminology
|
||||
<sect2><heading>Terminology</heading>
|
||||
<p>
|
||||
|
||||
A quick rundown of terminology:
|
||||
@ -74,7 +74,7 @@ transitions that may be made in a period of time, while <bf/bps/ (bits
|
||||
per second) is the ``correct'' term to use (at least it doesn't seem
|
||||
to bother the curmudgeons quite a much).
|
||||
|
||||
<sect2>External vs. Internal Modems
|
||||
<sect2><heading>External vs. Internal Modems</heading>
|
||||
<p>
|
||||
|
||||
External modems seem to be more convenient for dialup, because
|
||||
@ -89,7 +89,7 @@ may be limited only to setting DIP switches. If your internal modem
|
||||
has any signal indicator lights, it is probably difficult to view the
|
||||
lights when the system's cover is in place.
|
||||
|
||||
<sect2>Modems and Cables
|
||||
<sect2><heading>Modems and Cables</heading>
|
||||
<p>
|
||||
|
||||
A background knowledge of these items is assumed
|
||||
@ -149,7 +149,7 @@ watching for status reports from the modem. If you are familiar with
|
||||
connecting modems to PC-based bulletin board systems, this may seem
|
||||
awkward.
|
||||
|
||||
<sect2>Serial Interface Considerations
|
||||
<sect2><heading>Serial Interface Considerations</heading>
|
||||
<p>
|
||||
|
||||
FreeBSD supports NS8250-, NS16450-, NS16550-, and NS16550A-based EIA
|
||||
@ -163,7 +163,7 @@ devices, 16550A-based serial interface cards are much prefered. If
|
||||
the system has many active serial ports or will have a heavy load,
|
||||
16550A-based cards are better for low-error-rate communications.
|
||||
|
||||
<sect1>Quick Overview
|
||||
<sect1><heading>Quick Overview</heading>
|
||||
<p>
|
||||
|
||||
Here is the process that FreeBSD follows to accept dialup logins. A
|
||||
@ -192,7 +192,7 @@ by asking for the user's password and then starting the user's shell.
|
||||
|
||||
Let's dive into the configuration...
|
||||
|
||||
<sect1>Kernel Configuration
|
||||
<sect1><heading>Kernel Configuration</heading>
|
||||
<p>
|
||||
|
||||
FreeBSD kernels typically come prepared to search for four serial
|
||||
@ -278,7 +278,7 @@ program <tt/config/ as documented in ``Building Berkeley Kernels with
|
||||
Config'' and the <tt/config(8)/ manual page to prepare a kernel
|
||||
building directory, then build, install, and test the new kernel.
|
||||
|
||||
<sect1>Device Special Files
|
||||
<sect1><heading>Device Special Files</heading>
|
||||
<p>
|
||||
|
||||
Most devices in the kernel are accessed through ``device special
|
||||
@ -297,7 +297,7 @@ and <tt/stty(1)/ for information on the terminal settings, locking
|
||||
& initializing devices, and setting terminal options,
|
||||
respectively.
|
||||
|
||||
<sect2>Making Device Special Files
|
||||
<sect2><heading>Making Device Special Files</heading>
|
||||
<p>
|
||||
|
||||
A shell script called <tt/MAKEDEV/ in the <tt>/dev</tt> directory
|
||||
@ -330,7 +330,7 @@ crw-rw---- 1 uucp dialer 28, 193 Feb 15 14:38 /dev/cual01
|
||||
These permissions allow the user <tt/uucp/ and users in the group
|
||||
<tt/dialer/ to use the call-out devices.
|
||||
|
||||
<sect1>Configuration Files
|
||||
<sect1><heading>Configuration Files</heading>
|
||||
<p>
|
||||
|
||||
There are three system configuration files in the <tt>/etc</tt>
|
||||
@ -376,7 +376,7 @@ The author will try to give balanced configuration information, but is
|
||||
biased towards having the modem's data rate follow the connection
|
||||
rate.
|
||||
|
||||
<sect2>/etc/gettytab
|
||||
<sect2><heading>/etc/gettytab</heading>
|
||||
<p>
|
||||
|
||||
<tt>/etc/gettytab</tt> is a <tt/termcap(5)/-style file of
|
||||
@ -384,14 +384,14 @@ configuration information for <tt/getty(8)/. Please see the
|
||||
<tt/gettytab(4)/ manual page for complete information on the format of
|
||||
the file and the list of capabilities.
|
||||
|
||||
<sect3>Locked-Speed Config
|
||||
<sect3><heading>Locked-Speed Config</heading>
|
||||
<p>
|
||||
|
||||
If you are locking your modem's data communications rate at a
|
||||
particular speed, you probably won't need to make any changes to
|
||||
<tt>/etc/gettytab</tt>.
|
||||
|
||||
<sect3>Matching-Speed Config
|
||||
<sect3><heading>Matching-Speed Config</heading>
|
||||
<p>
|
||||
|
||||
You'll need to setup an entry in <tt>/etc/gettytab</tt> to give
|
||||
@ -472,7 +472,7 @@ If you have a slow CPU or a heavily loaded system and you don't have
|
||||
16550A-based serial ports, you may receive sio ``silo'' errors at 57.6
|
||||
Kbps.
|
||||
|
||||
<sect2>/etc/ttys
|
||||
<sect2><heading>/etc/ttys</heading>
|
||||
<p>
|
||||
|
||||
<tt>/etc/ttys</tt> is the list of <tt/ttys/ for <tt/init/ to monitor.
|
||||
@ -521,7 +521,7 @@ to send the signal. If this is your first time setting up the system,
|
||||
though, you may want to wait until your modem(s) are properly
|
||||
configured and connected before signalling <tt/init/.
|
||||
|
||||
<sect3>Locked-Speed Config
|
||||
<sect3><heading>Locked-Speed Config</heading>
|
||||
<p>
|
||||
|
||||
For a locked-speed configuration, your <tt/ttys/ entry needs to
|
||||
@ -537,7 +537,7 @@ If your modem is locked at a different data rate, substitute the
|
||||
appropriate name for the <tt>std.<em/speed/</tt> entry for
|
||||
<tt/std.19200/ from <tt>/etc/gettytab</tt> for your modem's data rate.
|
||||
|
||||
<sect3>Matching-Speed Config
|
||||
<sect3><heading>Matching-Speed Config</heading>
|
||||
<p>
|
||||
|
||||
In a matching-speed configuration, your <tt/ttys/ entry needs to
|
||||
@ -551,7 +551,7 @@ entry for a matching-speed modem that starts at 19.2 Kbps (the
|
||||
ttyd0 "/usr/libexec/getty V19200" dialup on
|
||||
</verb></tscreen>
|
||||
|
||||
<sect2>/etc/rc.serial or /etc/rc.local
|
||||
<sect2><heading>/etc/rc.serial or /etc/rc.local</heading>
|
||||
<p>
|
||||
|
||||
High-speed modems, like V.32, V.32bis, and V.34 modems, need to use
|
||||
@ -590,7 +590,7 @@ Since there isn't an initialization device special file on FreeBSD
|
||||
1.1, one has to just set the flags on the sole device special file and
|
||||
hope the flags aren't cleared by a miscreant.
|
||||
|
||||
<sect1>Modem Settings
|
||||
<sect1><heading>Modem Settings</heading>
|
||||
<p>
|
||||
|
||||
If you have a modem whose parameters may be permanently set in
|
||||
@ -664,7 +664,7 @@ prompt to a modem that is in command mode and the modem echoes the
|
||||
command or returns a result code. I've heard this sequence can result
|
||||
in a extended, silly conversation between <tt/getty/ and the modem.
|
||||
|
||||
<sect2>Locked-speed Config
|
||||
<sect2><heading>Locked-speed Config</heading>
|
||||
<p>
|
||||
|
||||
For a locked-speed configuration, you'll need to configure the modem
|
||||
@ -678,7 +678,7 @@ ATZ
|
||||
AT&B1&W
|
||||
</verb></tscreen>
|
||||
|
||||
<sect2>Matching-speed Config
|
||||
<sect2><heading>Matching-speed Config</heading>
|
||||
<p>
|
||||
|
||||
For a variable-speed configuration, you'll need to configure your
|
||||
@ -693,7 +693,7 @@ ATZ
|
||||
AT&B2&W
|
||||
</verb></tscreen>
|
||||
|
||||
<sect2>Checking the Modem's Configuration
|
||||
<sect2><heading>Checking the Modem's Configuration</heading>
|
||||
<p>
|
||||
|
||||
Most high-speed modems provide commands to view the modem's current
|
||||
@ -706,13 +706,13 @@ switch settings), use the commands <tt/ATZ/ and then <tt/ATI4/.
|
||||
If you have a different brand of modem, check your modem's manual to
|
||||
see how to double-check your modem's configuration parameters.
|
||||
|
||||
<sect1>Troubleshooting
|
||||
<sect1><heading>Troubleshooting</heading>
|
||||
<p>
|
||||
|
||||
Here are a few steps you can follow to check out the dialup modem on
|
||||
your system.
|
||||
|
||||
<sect2>Checking out the FreeBSD system
|
||||
<sect2><heading>Checking out the FreeBSD system</heading>
|
||||
<p>
|
||||
|
||||
Hook up your modem to your FreeBSD system, boot the system, and, if
|
||||
@ -755,7 +755,7 @@ messages, triple-check the configuration files <tt>/etc/ttys</tt> and
|
||||
files <tt>/dev/ttyd?</tt>, for any mistakes, missing entries, or
|
||||
missing device special files.
|
||||
|
||||
<sect2>Try Dialing In
|
||||
<sect2><heading>Try Dialing In</heading>
|
||||
<p>
|
||||
|
||||
Try dialing into the system; be sure to use 8 bits, no parity, 1 stop
|
||||
@ -794,7 +794,7 @@ perhaps you can send an electronic mail message to
|
||||
<tt>FreeBSD-Questions@freebsd.org</tt> describing your modem and your
|
||||
problem, and the good folks on the list will try to help.
|
||||
|
||||
<sect1>Acknowledgements
|
||||
<sect1><heading>Acknowledgements</heading>
|
||||
<p>
|
||||
|
||||
Thanks to these people for comments and advice:
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: hw.sgml,v 1.3 1995/08/25 22:14:30 jfieber Exp $ -->
|
||||
<!-- $Id: hw.sgml,v 1.4 1995/08/27 02:44:20 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
@ -104,7 +104,7 @@
|
||||
cards are supported as well. See the <tt>sio(4)</tt>
|
||||
manual page for detailed technical documentation.
|
||||
|
||||
<sect2>Digiboard PC/8
|
||||
<sect2><heading>Digiboard PC/8</heading>
|
||||
|
||||
<p><em>Contributed by &a.awebster;.<newline>26 August
|
||||
1995.</em>
|
||||
@ -130,7 +130,7 @@ device sio11 at isa? port 0x138 tty flags 0xb05 irq 9 vector siointr
|
||||
flags represent the last SIO port, in this case 11 so
|
||||
flags are 0xb05.
|
||||
|
||||
<sect2>Boca 16
|
||||
<sect2><heading>Boca 16</heading>
|
||||
|
||||
<p><em>Contributed by &a.whiteside;.<newline>26 August
|
||||
1995.</em>
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: install.sgml,v 1.7 1995/08/25 23:51:08 jfieber Exp $ -->
|
||||
<!-- $Id: install.sgml,v 1.8 1995/08/26 03:09:12 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
@ -6,7 +6,7 @@
|
||||
-->
|
||||
<chapt><heading>Installing FreeBSD<label id="install"></heading>
|
||||
|
||||
<sect>MS-DOS user's Questions and Answers
|
||||
<sect><heading>MS-DOS user's Questions and Answers</heading>
|
||||
|
||||
<p><bf>Help! I have no space! Do I need to delete
|
||||
everything first?</bf>
|
||||
@ -63,7 +63,7 @@
|
||||
|
||||
|
||||
|
||||
<sect>Supported Configurations<label id="install:hw">
|
||||
<sect><heading>Supported Configurations<label id="install:hw"></heading>
|
||||
|
||||
<p>FreeBSD currently runs on a wide variety of ISA, VLB,
|
||||
EISA and PCI bus based PC's, ranging from 386sx to
|
||||
@ -81,7 +81,7 @@
|
||||
configurations may very well work, and we have simply not
|
||||
received any indication of this.
|
||||
|
||||
<sect1>Disk Controllers
|
||||
<sect1><heading>Disk Controllers</heading>
|
||||
|
||||
<p>
|
||||
<itemize>
|
||||
@ -171,7 +171,7 @@
|
||||
difficulty.
|
||||
|
||||
|
||||
<sect1>Ethernet cards
|
||||
<sect1><heading>Ethernet cards</heading>
|
||||
|
||||
<p>
|
||||
<itemize>
|
||||
@ -211,7 +211,7 @@
|
||||
Semiconductor are also supported.
|
||||
</itemize>
|
||||
|
||||
<sect1>Misc
|
||||
<sect1><heading>Miscellaneous devices</heading>
|
||||
|
||||
<p>
|
||||
<itemize>
|
||||
@ -246,13 +246,13 @@
|
||||
materializing. Details will be posted as the situation
|
||||
develops.
|
||||
|
||||
<sect>Preparing for the installation</heading>
|
||||
<sect><heading>Preparing for the installation</heading>
|
||||
|
||||
<p>There are a number of different methods by which FreeBSD
|
||||
can be installed. The following describes what
|
||||
preparation needs to be done for each type.
|
||||
|
||||
<sect1>Before installing from CDROM
|
||||
<sect1><heading>Before installing from CDROM</heading>
|
||||
|
||||
<p>If your CDROM is of an unsupported type, such as an
|
||||
IDE CDROM, then please skip to section 2.3: MS-DOS
|
||||
@ -297,7 +297,7 @@
|
||||
on a more writable media!
|
||||
|
||||
|
||||
<sect1>Before installing from Floppy</heading>
|
||||
<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
|
||||
@ -339,7 +339,7 @@
|
||||
that.
|
||||
|
||||
|
||||
<sect1>Before installing from a MS-DOS partition</heading>
|
||||
<sect1><heading>Before installing from a MS-DOS partition</heading>
|
||||
|
||||
<p>To prepare for installation from an MS-DOS partition,
|
||||
copy the files from the distribution into a directory
|
||||
@ -371,7 +371,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
|
||||
which would copy all the subdirectories of
|
||||
<tt>E:\DISTS</tt> to <tt>C:\FREEBSD</tt>.
|
||||
|
||||
<sect1>Before installing from QIC/SCSI Tape</heading>
|
||||
<sect1><heading>Before installing from QIC/SCSI Tape</heading>
|
||||
|
||||
<p>Installing from tape is probably the easiest method,
|
||||
short of an on-line install using FTP or a CDROM
|
||||
@ -398,7 +398,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
|
||||
tape.
|
||||
|
||||
|
||||
<sect1>Before installing over a network</heading>
|
||||
<sect1><heading>Before installing over a network</heading>
|
||||
|
||||
<p>You can do network installations over 3 types of
|
||||
communications links:
|
||||
@ -462,7 +462,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
|
||||
Once you have a network link of some sort working, the
|
||||
installation can continue over NFS or FTP.
|
||||
|
||||
<sect2>Preparing for NFS installation
|
||||
<sect2><heading>Preparing for NFS installation</heading>
|
||||
|
||||
<p>NFS installation is fairly straight-forward: Simply
|
||||
copy the FreeBSD distribution files you're interested
|
||||
@ -494,7 +494,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
|
||||
properly!
|
||||
|
||||
|
||||
<sect2>Preparing for FTP Installation
|
||||
<sect2><heading>Preparing for FTP Installation</heading>
|
||||
|
||||
<p>FTP installation may be done from any mirror site
|
||||
containing a reasonably up-to-date version of FreeBSD
|
||||
@ -521,7 +521,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
|
||||
the Options menu to select Active mode transfers.
|
||||
|
||||
|
||||
<sect>Installing FreeBSD
|
||||
<sect><heading>Installing FreeBSD</heading>
|
||||
|
||||
<p>Once you've taken note of the appropriate
|
||||
preinstallation steps, you should be able to install
|
||||
@ -577,7 +577,7 @@ C> XCOPY /S E:\DISTS C:\FREEBSD\
|
||||
|
||||
</enum>
|
||||
|
||||
<sect1>The installation menu
|
||||
<sect1><heading>The installation menu</heading>
|
||||
|
||||
<p>You can do anything you like in this menu without
|
||||
altering your system <em>except</em> for "Commit",
|
||||
|
||||
@ -1,11 +1,11 @@
|
||||
<!-- $Id: relnotes.sgml,v 1.2 1995/06/22 13:47:09 jfieber Exp $ -->
|
||||
<!-- $Id: relnotes.sgml,v 1.3 1995/06/30 17:37:47 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
<!DOCTYPE linuxdoc PUBLIC '-//FreeBSD//DTD linuxdoc//EN'>
|
||||
<linuxdoc><book><chapt>foo
|
||||
-->
|
||||
<sect>About this release<label id="relnotes">
|
||||
<sect><heading>About this release<label id="relnotes"></heading>
|
||||
|
||||
<p>Since our first release of FreeBSD 1.0 nearly two
|
||||
years ago, FreeBSD has changed dramatically. Since
|
||||
@ -88,7 +88,7 @@
|
||||
work and many thousands of man hours put in by an
|
||||
international development team. We hope you enjoy it!
|
||||
|
||||
<sect1>New feature highlights
|
||||
<sect1><heading>New feature highlights</heading>
|
||||
|
||||
<p>The following features were added or substantially
|
||||
improved between the release of 2.0 and this 2.0.5
|
||||
@ -98,7 +98,7 @@
|
||||
regarding the new functionality should be directed to
|
||||
them first.
|
||||
|
||||
<sect2>Kernel
|
||||
<sect2><heading>Kernel</heading>
|
||||
|
||||
<p>
|
||||
<descrip>
|
||||
@ -197,9 +197,9 @@
|
||||
|
||||
</descrip>
|
||||
|
||||
<sect2>New device support
|
||||
<sect2><heading>New device support</heading>
|
||||
|
||||
<sect3>SCSI and CDROM devices
|
||||
<sect3><heading>SCSI and CDROM devices</heading>
|
||||
|
||||
<p><descrip>
|
||||
|
||||
@ -251,7 +251,7 @@
|
||||
|
||||
</descrip>
|
||||
|
||||
<sect3>Serial devices
|
||||
<sect3><heading>Serial devices</heading>
|
||||
|
||||
<p><descrip>
|
||||
|
||||
@ -281,7 +281,7 @@
|
||||
|
||||
</descrip>
|
||||
|
||||
<sect2>Networking
|
||||
<sect2><heading>Networking</heading>
|
||||
|
||||
<p><descrip>
|
||||
|
||||
@ -366,7 +366,7 @@
|
||||
|
||||
</descrip>
|
||||
|
||||
<sect2>Miscellaneous drivers
|
||||
<sect2><heading>Miscellaneous drivers</heading>
|
||||
|
||||
<p><descrip>
|
||||
|
||||
@ -427,7 +427,7 @@
|
||||
|
||||
</descrip>
|
||||
|
||||
<sect1>Experimental features
|
||||
<sect1><heading>Experimental features</heading>
|
||||
|
||||
<p><descrip>
|
||||
|
||||
@ -457,7 +457,7 @@
|
||||
|
||||
</descrip>
|
||||
<!--
|
||||
<sect1>Reporting problems, making suggestions, submitting code
|
||||
<sect1><heading>Reporting problems, making suggestions, submitting code</heading>
|
||||
|
||||
<p>Your suggestions, bug reports and contributions of code
|
||||
are always valued - please do not hesitate to report any
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: scsi.sgml,v 1.1.1.1 1995/04/28 16:19:59 jfieber Exp $ -->
|
||||
<!-- $Id: scsi.sgml,v 1.2 1995/06/30 17:37:48 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<!--
|
||||
@ -87,9 +87,9 @@
|
||||
QIC tape unit, a SCSI-1 helical scan tape unit and 2 SCSI-1 disks
|
||||
work together quite happily.
|
||||
|
||||
<sect1>Concepts of SCSI
|
||||
<sect1><heading>Concepts of SCSI</heading>
|
||||
<p>
|
||||
<sect2>A <it>smart</it> interface
|
||||
<sect2><heading>A <it>smart</it> interface</heading>
|
||||
<p>
|
||||
As said before, SCSI devices are smart. The idea is to put the
|
||||
knowledge about intimate hardware details onto the SCSI device
|
||||
@ -104,7 +104,7 @@
|
||||
there is no longer a need to change (and qualify!) drivers for
|
||||
every odd new device that is introduced.
|
||||
|
||||
<sect2>Do's and don't's on interconnections
|
||||
<sect2><heading>Do's and don't's on interconnections</heading>
|
||||
<p>
|
||||
For cabling and connectors there is a golden rule: get good
|
||||
stuff. With bus speeds going up all the time you will save
|
||||
@ -116,7 +116,7 @@
|
||||
hunting down a problem with a flaky machine only to discover that
|
||||
shortening the SCSI bus with 1 meter solved the problem. And the
|
||||
original bus length was well within the SCSI specification.
|
||||
<sect2>SCSI bus types
|
||||
<sect2><heading>SCSI bus types</heading>
|
||||
<p>
|
||||
From an electrical point of view, there are two Incompatible bus
|
||||
types: single-ended and differential. This means that there are
|
||||
@ -156,7 +156,7 @@
|
||||
between the devices. You have to watch your device addressing
|
||||
closely when mixing wide and narrow.
|
||||
|
||||
<sect3>Single ended buses
|
||||
<sect3><heading>Single ended buses</heading>
|
||||
<p>
|
||||
A single-ended SCSI bus uses signals that are either 5 Volts or
|
||||
0 Volts (indeed, TTL levels) and are relative to a COMMON
|
||||
@ -190,7 +190,7 @@
|
||||
is a bad idea, you better stick to 50 pins cabling
|
||||
in accordance with the SCSI standard.
|
||||
|
||||
<sect3>Differential buses
|
||||
<sect3><heading>Differential buses</heading>
|
||||
<p>
|
||||
A differential SCSI bus has a maximum length of 25
|
||||
meters. Quite a difference from the 3 meters for a single-ended
|
||||
@ -216,7 +216,7 @@
|
||||
AH1740 as a single ended board, whereas the AH1744 was differential.
|
||||
The software interface to the host is identical for both.
|
||||
|
||||
<sect3>Terminators
|
||||
<sect3><heading>Terminators</heading>
|
||||
<p>
|
||||
Terminators in SCSI terminology are resistor networks that are
|
||||
used to get a correct impedance matching. Impedance matching
|
||||
@ -277,7 +277,7 @@
|
||||
for the internal flat cable connectors. This makes
|
||||
reconfiguration much easier.
|
||||
|
||||
<sect3>Terminator power
|
||||
<sect3><heading>Terminator power</heading>
|
||||
<p>
|
||||
The terminators discussed in the previous chapter need power to
|
||||
operate properly. On the SCSI bus, a line is dedicated to this
|
||||
@ -317,7 +317,7 @@
|
||||
configurable, using some sort of setup tool. Consult you
|
||||
documentation!
|
||||
|
||||
<sect3>Device addressing
|
||||
<sect3><heading>Device addressing</heading>
|
||||
<p>
|
||||
Because the SCSI bus is, ehh, a bus there must be a way to
|
||||
distinguish or address the different devices connected to it.
|
||||
@ -349,7 +349,7 @@
|
||||
tapechanger. In this way, the host system can address each of
|
||||
the parts of the tape unit as desired.
|
||||
|
||||
<sect3>Bus layout
|
||||
<sect3><heading>Bus layout</heading>
|
||||
<p>
|
||||
SCSI buses are linear. So, not shaped like Y-junctions, star
|
||||
topologies, cobwebbs or whatever else people might want to
|
||||
@ -364,9 +364,9 @@
|
||||
|
||||
<bf>Stick to the linear bus rule!</bf>
|
||||
|
||||
<sect1>Using SCSI with FreeBSD
|
||||
<sect1><heading>Using SCSI with FreeBSD</heading>
|
||||
<p>
|
||||
<sect2>About translations, BIOSes and magic..
|
||||
<sect2><heading>About translations, BIOSes and magic..</heading>
|
||||
<p>
|
||||
As stated before, you should first make sure that you have a
|
||||
electrically sound bus.
|
||||
@ -445,7 +445,7 @@ Feb 9 19:33:46 yedi /386bsd: sd0: 636MB (1303250 total sec), 1632 cyl, 15 head,
|
||||
the value reported by the drive when inquiring about the geometry
|
||||
now becomes fake.
|
||||
|
||||
<sect2>SCSI subsystem design
|
||||
<sect2><heading>SCSI subsystem design</heading>
|
||||
<p>
|
||||
FreeBSD uses a sort of layered SCSI subsystem. For each different
|
||||
controller card a so called device driver is written. This driver
|
||||
@ -465,7 +465,7 @@ Feb 9 19:33:46 yedi /386bsd: sd0: 636MB (1303250 total sec), 1632 cyl, 15 head,
|
||||
banging and more high level stuff. Adding support for another
|
||||
piece of hardware is a much more managable problem.
|
||||
|
||||
<sect2>Kernel configuration
|
||||
<sect2><heading>Kernel configuration</heading>
|
||||
<p>
|
||||
Dependent on your hardware, the kernel configuration file must
|
||||
contain a line which describes your hostadapter. This includes
|
||||
@ -514,7 +514,7 @@ device cd0 #Only need one of these, the code dynamically grows &lsq
|
||||
subsystem. For more detailed info on hostadapter drivers use eg
|
||||
<tt>man 4 aha</tt> for info on the Adaptec 154x driver.
|
||||
|
||||
<sect2>Tuning your SCSI kernel setup
|
||||
<sect2><heading>Tuning your SCSI kernel setup</heading>
|
||||
<p>
|
||||
Experience has shown that some devices are slow to respond to INQUIRY
|
||||
commands after a SCSI bus reset. An INQUIRY command is sent by the kernel
|
||||
@ -534,7 +534,7 @@ options "SCSI_DELAY=15" #Be pessimistic about Joe SCSI device
|
||||
with device recognition. If this helps, tune it back until it just stays
|
||||
working.
|
||||
|
||||
<sect2>Rogue SCSI devices
|
||||
<sect2><heading>Rogue SCSI devices</heading>
|
||||
<p>
|
||||
Although the SCSI standard tries to be complete and concise, it is
|
||||
a complex standard and implementing things correctly is no easy task.
|
||||
@ -570,7 +570,7 @@ Mar 29 21:16:37 yedi /386bsd: st1: Archive Viper 150 is a known rogue
|
||||
to connect your bogus Mumbletech SCSI cdrom you might be the one
|
||||
that has to define which workaround is needed.
|
||||
|
||||
<sect2>Busmaster host adapters
|
||||
<sect2><heading>Busmaster host adapters</heading>
|
||||
<p>
|
||||
Most, but not all, SCSI host adapters are bus mastering controllers.
|
||||
This means that they can do I/O on their own without putting load onto
|
||||
@ -601,7 +601,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed
|
||||
Check the man pages for the host adapter that you use. Or better
|
||||
still, use the ultimate documentation (read: driver source).
|
||||
|
||||
<sect1>Tracking down problems
|
||||
<sect1><heading>Tracking down problems</heading>
|
||||
<p>
|
||||
The following list is an attempt to give a guideline for the most
|
||||
common SCSI problems and their solutions. It is by no means
|
||||
@ -627,7 +627,7 @@ options "TUNE_1542" #dynamic tune of bus DMA speed
|
||||
If possible, configure your hostadapter to use slow bus speeds.
|
||||
</itemize>
|
||||
|
||||
<sect1><heading>Further reading<label id="scsi:further-reading"></>
|
||||
<sect1><heading>Further reading<label id="scsi:further-reading"></heading>
|
||||
<p>
|
||||
If you intend to do some serious SCSI hacking, you might want to
|
||||
have the official standard at hand:
|
||||
|
||||
@ -64,7 +64,7 @@ modems, and perhaps <tt/stty(1)/ for information on setting serial
|
||||
port parameters [such as <tt/clocal/ for directly-connected
|
||||
serial interfaces].
|
||||
|
||||
<sect1>Quick Overview
|
||||
<sect1><heading>Quick Overview</heading>
|
||||
<p>
|
||||
|
||||
In its typical configuration, using FreeBSD as a SLIP server works as
|
||||
@ -76,7 +76,7 @@ the special user, and if it finds a match, connects the serial line to
|
||||
an available SLIP interface and then runs the shell script
|
||||
<tt>/etc/sliphome/slip.login</tt> to configure the SLIP interface.
|
||||
|
||||
<sect2>An Example of a SLIP Server Login
|
||||
<sect2><heading>An Example of a SLIP Server Login</heading>
|
||||
<p>
|
||||
|
||||
For example, if a SLIP user ID were <tt>Shelmerg</tt>, <tt/Shelmerg/'s
|
||||
@ -121,7 +121,7 @@ logging).
|
||||
|
||||
OK, enough of the examples -- let's dive into setting up the system.
|
||||
|
||||
<sect1>Kernel Configuration
|
||||
<sect1><heading>Kernel Configuration</heading>
|
||||
<p>
|
||||
FreeBSD's default kernels usually come with two SLIP interfaces
|
||||
defined (<tt>sl0</tt> and <tt>sl1</tt>); you can use <tt>netstat
|
||||
@ -182,7 +182,7 @@ See the document ``Building Berkeley Kernels with Config'' and the
|
||||
manual page for <tt>config(8)</tt> to see how to configure and build
|
||||
kernels.
|
||||
|
||||
<sect1>Sliplogin Configuration
|
||||
<sect1><heading>Sliplogin Configuration</heading>
|
||||
|
||||
<p>
|
||||
|
||||
@ -196,7 +196,7 @@ and (optionally) <tt>slip.logout</tt>, which undoes
|
||||
<tt>slip.login</tt>'s effects when the serial connection is
|
||||
terminated.
|
||||
|
||||
<sect2>slip.hosts Configuration
|
||||
<sect2><heading>slip.hosts Configuration</heading>
|
||||
|
||||
<p>
|
||||
|
||||
@ -268,7 +268,7 @@ Ethernet subnet, and you'll also need to adjust your
|
||||
<tt>/etc/sliphome/slip.logout</tt> scripts to use <tt>arp(8)</tt> to
|
||||
manage the proxy-ARP entries in the SLIP server's ARP table.
|
||||
|
||||
<sect2>slip.login Configuration
|
||||
<sect2><heading>slip.login Configuration</heading>
|
||||
|
||||
<p>
|
||||
The typical <tt>/etc/sliphome/slip.login</tt> file looks like this:
|
||||
@ -347,7 +347,7 @@ Note that when you create <tt>/etc/sliphome/slip.login</tt> and
|
||||
/etc/sliphome/slip.logout</tt>) must be set, or <tt>sliplogin</tt>
|
||||
will be unable to execute it.
|
||||
|
||||
<sect2>slip.logout Configuration
|
||||
<sect2><heading>slip.logout Configuration</heading>
|
||||
|
||||
<p>
|
||||
|
||||
@ -400,7 +400,7 @@ It bears repeating: make sure <tt>/etc/sliphome/slip.logout</tt> has
|
||||
the execute bit set for after you create it (ie, <tt>chmod 755
|
||||
/etc/sliphome/slip.logout</tt>).
|
||||
|
||||
<sect1>Routing Considerations
|
||||
<sect1><heading>Routing Considerations</heading>
|
||||
|
||||
<p>
|
||||
If you are not using the ``proxy ARP'' method for routing packets
|
||||
@ -411,7 +411,7 @@ your SLIP server, or you will probably need to install and configure
|
||||
<tt>gated</tt> on your FreeBSD SLIP server so that it will tell your
|
||||
routers via appropriate routing protocols about your SLIP subnet.
|
||||
|
||||
<sect2>Static Routes
|
||||
<sect2><heading>Static Routes</heading>
|
||||
|
||||
<p>
|
||||
Adding static routes to your nearest default routers can be
|
||||
@ -423,7 +423,7 @@ which static routes to tell other routers about, so some expertise and
|
||||
troubleshooting/tweaking may be necessary to get static-route-based
|
||||
routing to work.
|
||||
|
||||
<sect2>Running gated
|
||||
<sect2><heading>Running gated</heading>
|
||||
|
||||
<p>
|
||||
An alternative to the headaches of static routes is to install
|
||||
@ -503,7 +503,7 @@ appropriate for your system. Please see the manual page for
|
||||
<tt>gated</tt> for information on <tt>gated</tt>'s command-line
|
||||
parameters.
|
||||
|
||||
<sect1>Acknowledgements
|
||||
<sect1><heading>Acknowledgements</heading>
|
||||
|
||||
<p>
|
||||
Thanks to these people for comments and advice regarding this tutorial:
|
||||
|
||||
@ -1,4 +1,4 @@
|
||||
<!-- $Id: userppp.sgml,v 1.1 1995/07/29 13:08:02 jfieber Exp $ -->
|
||||
<!-- $Id: userppp.sgml,v 1.2 1995/08/19 22:16:06 jfieber Exp $ -->
|
||||
<!-- The FreeBSD Documentation Project -->
|
||||
|
||||
<sect>Setting up user PPP<label id="userppp">
|
||||
@ -48,7 +48,7 @@
|
||||
Thanks to Rob Snow <rsnow@txdirect.net> who proved to be a mine of
|
||||
useful information when I was first experimenting with user ppp.
|
||||
|
||||
<sect1>Before you start
|
||||
<sect1><heading>Before you start</heading>
|
||||
|
||||
<p>This document assumes you're in roughly this position:
|
||||
|
||||
@ -80,7 +80,7 @@
|
||||
In addition, I've assumed that because your connection to the Internet is
|
||||
not full time you are not running a name server (<tt>named(8)</tt>).
|
||||
|
||||
<sect1>Building a ppp ready kernel
|
||||
<sect1><heading>Building a ppp ready kernel</heading>
|
||||
|
||||
<p>As the description states, ``ppp'' uses the kernel ``tun'' device. It is
|
||||
necessary to make sure that your kernel has support for this device compiled
|
||||
@ -97,7 +97,7 @@ pseudo-device tun 1
|
||||
should add the line, re-compile and then re-install the kernel. Boot from
|
||||
this new kernel.
|
||||
|
||||
<sect1>Check the tun device
|
||||
<sect1><heading>Check the tun device</heading>
|
||||
|
||||
<p>My experiences with ppp have only been with one ``tun'' device (tun0). If
|
||||
you have used more (i.e., a number other than `1' in the pseudo-device line
|
||||
@ -111,7 +111,7 @@ pseudo-device tun 1
|
||||
# ./MAKEDEV tun0
|
||||
</verb></tscreen>
|
||||
|
||||
<sect1>PPP Configuration
|
||||
<sect1><heading>PPP Configuration</heading>
|
||||
|
||||
<p>The meat of the problem.
|
||||
|
||||
@ -134,7 +134,7 @@ pseudo-device tun 1
|
||||
whether you are using static or dynamic IP addresses.
|
||||
|
||||
|
||||
<sect2>Configure the resolver(5)
|
||||
<sect2><heading>Configure the resolver(5)</heading>
|
||||
|
||||
<p>The resolver is the part of the networking system that turns IP addresses
|
||||
into hostnames. It can be configured to look for maps that describe IP to
|
||||
@ -165,7 +165,7 @@ bind
|
||||
namedflags="NO"
|
||||
</verb></tscreen>
|
||||
|
||||
<sect2>Create the /etc/hosts(5) file
|
||||
<sect2><heading>Create the /etc/hosts(5) file</heading>
|
||||
|
||||
<p>This file should contain the IP addresses and names of machines on your
|
||||
network. At a bare minimum it should contain entries for the machine
|
||||
@ -186,7 +186,7 @@ namedflags="NO"
|
||||
<!-- XXX <em>(* What should they do if they are
|
||||
allocated an IP address dynamically?)</em> -->
|
||||
|
||||
<sect2>Create the /etc/resolv.conf file
|
||||
<sect2><heading>Create the /etc/resolv.conf file</heading>
|
||||
|
||||
<p>/etc/resolv.conf contains some extra information required when you are
|
||||
not running a nameserver. It points the resolver routines at real
|
||||
@ -202,7 +202,7 @@ nameserver 158.152.1.65
|
||||
Which are Demon Internet's two nameservers. Add as many ``nameserver''
|
||||
lines as your ISP provides nameservers.
|
||||
|
||||
<sect1>PPP and static IP addresses
|
||||
<sect1><heading>PPP and static IP addresses</heading>
|
||||
|
||||
<p>Probably the easiest to configure for. You will need to create three files
|
||||
in the /etc/ppp directory.
|
||||
@ -283,7 +283,7 @@ x.x.x.x:
|
||||
may or may not want to do this, depending on how many people have access
|
||||
to your ppp system.
|
||||
|
||||
<sect1>PPP and Dynamic IP configuration
|
||||
<sect1><heading>PPP and Dynamic IP configuration</heading>
|
||||
|
||||
<!-- XXX -->
|
||||
<p>If you service provider does not assign static IP numbers,
|
||||
@ -294,7 +294,7 @@ set ifaddr 0 0
|
||||
</verb></tscreen>
|
||||
See the <tt>ppp(8)</tt> manual page for more detailed information.
|
||||
|
||||
<sect1>Final system configuration
|
||||
<sect1><heading>Final system configuration</heading>
|
||||
|
||||
<p>You now have PPP configured, but there's a few more things to do before
|
||||
it's ready to work. They all involve editing the /etc/sysconfig file.
|
||||
|
||||
Loading…
Reference in New Issue
Block a user