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

More rc.conf vs sysconfig updates.

Browse source
This commit is contained in:
Jordan K. Hubbard 1997-07-11 08:04:00 +00:00
parent 3232f3568f
commit 0cb93f7b9d
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=1734
7 changed files with 30 additions and 21 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

4
handbook/kerberos.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: kerberos.sgml,v 1.10 1997-02-22 12:58:41 peter Exp $ -->
<!-- $Id: kerberos.sgml,v 1.11 1997-07-11 08:03:51 jkh Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>Kerberos<label id="kerberos"></heading>
@ -277,7 +277,7 @@ Principal name: <---- null entry here will cause an exit
<heading>Testing it all out</heading>
<p>First we have to start the Kerberos daemons. NOTE that if you have
correctly edited your <tt>/etc/sysconfig</tt> then this will happen
correctly edited your <tt>/etc/rc.conf</tt> then this will happen
automatically when you reboot. This is only necessary on the Kerberos
server. Kerberos clients will automagically get what they need from
the <tt>/etc/kerberosIV</tt> directory.

4
handbook/kerneldebug.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: kerneldebug.sgml,v 1.14 1997-04-06 23:03:27 dfr Exp $ -->
<!-- $Id: kerneldebug.sgml,v 1.15 1997-07-11 08:03:53 jkh Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Kernel Debugging<label id="kerneldebug"></heading>
@ -23,7 +23,7 @@
Use the <tt>dumpon(8)</tt> command to tell the kernel where to dump
to (note that this will have to be done after configuring the
partition in question as swap space via <tt>swapon(8)</tt>). This is
normally arranged via <tt>/etc/sysconfig</tt> and <tt>/etc/rc</tt>.
normally arranged via <tt>/etc/rc.conf</tt> and <tt>/etc/rc</tt>.
Alternatively, you can
hard-code the dump device via the `dump' clause in the `config' line
of your kernel config file. This is deprecated, use only if you

15
handbook/linuxemu.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: linuxemu.sgml,v 1.19 1997-03-19 03:24:50 obrien Exp $ -->
<!-- $Id: linuxemu.sgml,v 1.20 1997-07-11 08:03:54 jkh Exp $ -->
<!-- The FreeBSD Documentation Project -->
<chapt><heading>Linux Emulation<label id="linuxemu"></heading>
@ -106,7 +106,7 @@ EXEC 0 3 f0baf000 0018 f0bb4000 1 linux_emulator
</verb>
</tscreen>
You can cause the LKM to be loaded when the system boots in either of
two ways. On FreeBSD 2.2-RELEASE and 2.1-STABLE enable it in
two ways. In FreeBSD 2.2.1-RELEASE and 2.1-STABLE enable it in
/etc/sysconfig
<tscreen>
<verb>
@ -122,7 +122,7 @@ linux
</verb>
</tscreen>
<sect1><heading>Installing Linux Emulation in 2.2-RELEASE and later</heading>
<sect1><heading>Installing Linux Emulation in 2.2.2-RELEASE and later</heading>
<p>It is no longer necessary to specify ``options LINUX''
or ``options COMPAT_LINUX''. Linux emulation is done with an LKM
@ -130,19 +130,18 @@ or ``options COMPAT_LINUX''. Linux emulation is done with an LKM
having to reboot. You will need the following things in your startup files,
however:
<enum>
<item> In /etc/sysconfig, you need the following line:
<item> In /etc/rc.conf, you need the following line:
<tscreen>
<verb>
linux=YES
linux_enable=YES
</verb>
</tscreen>
<item> This, in turn, triggers the following action in /etc/rc.i386:
<tscreen>
<verb>
# Start the Linux binary emulation if requested.
if [ "X${linux}" = X"YES" ]; then
echo -n ' '; linux
# XXX BOGUS - Linux script shouldn't make any output on success
if [ "X${linux_enable}" = X"YES" ]; then
echo -n ' linux'; linux > /dev/null 2>&1
fi
</verb>
</tscreen>

7
handbook/mail.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: mail.sgml,v 1.10 1997-05-24 21:14:03 joerg Exp $
<!-- $Id: mail.sgml,v 1.11 1997-07-11 08:03:56 jkh Exp $
The FreeBSD Documentation Project
<!DOCTYPE linuxdoc PUBLIC "-//FreeBSD//DTD linuxdoc//EN">
@ -33,7 +33,8 @@ A <tt/mailhost/ is a server that is responsible for delivering and receiving all
<p> This is a program like <tt /elm, pine, mail/ , or something more sophisticated like a WWW browser. This program will simply pass off all e-mail transactions to the local <tt/mailhost/ , either by calling <tt>sendmail</tt> or delivering it over TCP.
<sect1><heading>Mailhost Server Daemon</heading>
<p> Usually this program is <tt /sendmail or smail/ running in the background. Turn it off or change the command line options in <tt> /etc/sysconfig </tt>. It is best to leave it on, unless you have a specific reason to want it off. Example: You are building a <ref name="Firewall" id="firewalls">.
<p> Usually this program is <tt /sendmail or smail/ running in the background. Turn it off or change the command line options in <tt>/etc/rc.conf</tt>
(or, prior to FreeBSD 2.2.2, <tt>/etc/sysconfig</tt>). It is best to leave it on, unless you have a specific reason to want it off. Example: You are building a <ref name="Firewall" id="firewalls">.
<p>You should be aware that <tt>sendmail</tt> is a potential weak link in a secure site. Some versions of <tt>sendmail</tt> have known security problems.
@ -394,7 +395,7 @@ bigco.com. MX 10 bigco.com.
Only one host should be specified as the final recipient ( add ``Cw bigco.com'' in <tt>/etc/sendmail.cf</tt> on bigco.com).
When the senders sendmail is trying to deliver the mail it will try to connect to you over the modem link. It will most likely time out because you are not online. Sendmail will automatically deliver it to the secondary MX site, ie your Internet provider. The secondary MX site will try every (<tt>sendmail_flags = "-bd -q15m"</tt> in <tt>/etc/sysconfig</tt> ) 15 minutes to connect to your host to deliver the mail to the primary MX site.
When the senders sendmail is trying to deliver the mail it will try to connect to you over the modem link. It will most likely time out because you are not online. Sendmail will automatically deliver it to the secondary MX site, ie your Internet provider. The secondary MX site will try every (<tt>sendmail_flags = "-bd -q15m"</tt> in <tt>/etc/rc.conf</tt> ) 15 minutes to connect to your host to deliver the mail to the primary MX site.
You might wat to use something like this as a login script.
<verb>

8
handbook/quotas.sgml
View file

@ -1,7 +1,7 @@
<!-- This is an SGML document in the linuxdoc DTD describing
disk quotas under FreeBSD. By Mike Pritchard, 1996.
$Id: quotas.sgml,v 1.6 1997-02-24 23:20:49 mpp Exp $
$Id: quotas.sgml,v 1.7 1997-07-11 08:03:57 jkh Exp $
The FreeBSD Documentation Project
@ -52,6 +52,12 @@ quotas=NO
to:
<verb>
quotas=YES
</verb>
<p>If you are running FreeBSD 2.2.2 or later, the configuration file
will be <tt>/etc/rc.conf</tt> instead and the variable name changed to
<verb>
check_quotas=YES
</verb>
<p>Finally you will need to edit <tt>/etc/fstab</tt> to enable

6
handbook/slipc.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: slipc.sgml,v 1.9 1997-02-22 12:59:25 peter Exp $ -->
<!-- $Id: slipc.sgml,v 1.10 1997-07-11 08:03:59 jkh Exp $ -->
<!-- The FreeBSD Documentation Project -->
<sect><heading>Setting up a SLIP client<label id="slipc"></heading>
@ -48,13 +48,15 @@ so this will not be a problem unless you deleted it.
<item>Make sure you have "hosts" before "bind" in your <tt>/etc/host.conf</tt>.
Otherwise, funny things may happen.
<item>Edit the file <tt>/etc/sysconfig</tt>.
<item>Edit the file <tt>/etc/rc.conf</tt>.
<enum>
<item>Set your hostname by editing the line that says:
<verb>
hostname=myname.my.domain
</verb>
You should give it your full Internet hostname.
In versions of FreeBSD previous to 2.2.2, this information
is actually in <tt>/etc/sysconfig</tt>
<item>Add sl0 to the list of network interfaces by changing the line
that says:

7
handbook/slips.sgml
View file

@ -1,4 +1,4 @@
<!-- $Id: slips.sgml,v 1.13 1997-02-22 12:59:26 peter Exp $
<!-- $Id: slips.sgml,v 1.14 1997-07-11 08:04:00 jkh Exp $
This is an SGML version in the linuxdoc DTD of the SLIP Server
FAQ by Guy Helmer.
@ -149,9 +149,10 @@ Internet RFC requirements for Internet hosts (see RFC's 1009
&lsqb;Requirements for Internet Hosts -- Communication Layers&rsqb;,
and perhaps 1127 &lsqb;A Perspective on the Host Requirements
RFCs&rsqb;), so if you want your FreeBSD SLIP Server to act as a
router, you will have to edit the <tt>/etc/sysconfig</tt> file and change
router, you will have to edit the <tt>/etc/rc.conf</tt> file (called
<tt>/etc/sysconfig</tt> in FreeBSD releases prior to 2.2.2) and change
the setting of the <bf>gateway</bf> variable to <tt>YES</tt>. If you
have an older system which does not have the <tt>/etc/sysconfig</tt>
have an older system which predates even the <tt>/etc/sysconfig</tt>
file, then add the following command:
<verb>
sysctl -w net.inet.ip.forwarding = 1