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

Update to a more modern vintage.

Browse source 
e.g. sysctl instead of the GATEWAY option
     use a refer instead of an old file (options.info)
This commit is contained in:
Gary Clark II 1995-12-19 11:10:42 +00:00
parent 7644335c78
commit cef3470ee3
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=189
1 changed files with 9 additions and 23 deletions

32
handbook/slips.sgml
View file

@ -27,14 +27,11 @@ suggestions here.
This guide was originally written for SLIP Server services on a This guide was originally written for SLIP Server services on a
FreeBSD 1.x system. It has been modified to reflect changes in the FreeBSD 1.x system. It has been modified to reflect changes in the
pathnames and the removal of the SLIP interface compression flags in pathnames and the removal of the SLIP interface compression flags in
early versions of FreeBSD 2, which appear to be the only major early versions of FreeBSD 2.X, which appear to be the only major
changes between FreeBSD versions. If you do encounter mistakes in changes between FreeBSD versions. If you do encounter mistakes in
this document, please email the author with enough information to this document, please email the author with enough information to
help correct the problem. help correct the problem.
For FreeBSD 1.x users, all of the files referenced in the directory
<tt>/etc/sliphome</tt> are actually in the <tt>/etc</tt> directory.
<sect1><heading>Prerequisites<label id="slips:prereqs"></> <sect1><heading>Prerequisites<label id="slips:prereqs"></>
<p> <p>
@ -151,24 +148,14 @@ Internet RFC requirements for Internet hosts (see RFC's 1009
&lsqb;Requirements for Internet Hosts -- Communication Layers&rsqb;, &lsqb;Requirements for Internet Hosts -- Communication Layers&rsqb;,
and perhaps 1127 &lsqb;A Perspective on the Host Requirements and perhaps 1127 &lsqb;A Perspective on the Host Requirements
RFCs&rsqb;), so if you want your FreeBSD SLIP Server to act as a RFCs&rsqb;), so if you want your FreeBSD SLIP Server to act as a
router, you'll have to add the line <tt>options GATEWAY </tt> to your router, you'll have to add the line
machine's kernel configuration file and re-compile the kernel anyway. <verb>
(Trivia: ``Gateways'' are the Internet's old name for what are now sysctl -w net.inet.ip.forwarding = 0
usually called ``routers''.) </verb>
to your rc.local file.
Please see the BSD System Manager's Manual chapter on ``Building
Berkeley Kernels with Config'' &lsqb;the source for which is in
<tt>/usr/src/share/doc/smm</tt>&rsqb; and ``FreeBSD Configuration
Options'' &lsqb;in <tt>/sys/doc/options.doc</tt>&rsqb; for more
information on configuring and building kernels. You may have to
unpack the kernel source distribution if haven't installed the system
sources already (<tt>srcdist/srcsys.??</tt> in FreeBSD 1.1,
<tt>srcdist/sys.??</tt> in FreeBSD 1.1.5.1, or the entire source
distribution in FreeBSD 2.0) to be able to configure and build
kernels.
You'll notice that near the end of the default kernel configuration You'll notice that near the end of the default kernel configuration
file (<tt>/sys/i386/conf/GENERICAH</tt>) is a line that reads: file (<tt>/sys/i386/conf/GENERIC</tt>) is a line that reads:
<tscreen><verb> <tscreen><verb>
pseudo-device sl 2 pseudo-device sl 2
@ -178,9 +165,8 @@ which is the line that defines the number of SLIP devices available in
the kernel; the number at the end of the line is the maximum number of the kernel; the number at the end of the line is the maximum number of
SLIP connections that may be operating simultaneously. SLIP connections that may be operating simultaneously.
See the document ``Building Berkeley Kernels with Config'' and the Please refer to <ref id="kernelconfig" name="Configuring the FreeBSD Kernel">
manual page for <tt>config(8)</tt> to see how to configure and build for help in reconfiguring your kernel.
kernels.
<sect1><heading>Sliplogin Configuration</heading> <sect1><heading>Sliplogin Configuration</heading>