Changeset 6998c44a


Ignore:
Timestamp:
09/26/2003 02:04:06 AM (19 years ago)
Author:
Larry Lawrence <larry@…>
Branches:
10.0, 10.1, 11.0, 11.1, 6.0, 6.1, 6.2, 6.2.0, 6.2.0-rc1, 6.2.0-rc2, 6.3, 6.3-rc1, 6.3-rc2, 6.3-rc3, 7.10, 7.4, 7.5, 7.6, 7.6-blfs, 7.6-systemd, 7.7, 7.8, 7.9, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, gnome, kde5-13430, kde5-14269, kde5-14686, krejzi/svn, lazarus, nosym, perl-modules, qt5new, systemd-11177, systemd-13485, trunk, upgradedb, v5_0, v5_0-pre1, v5_1, v5_1-pre1, xry111/intltool, xry111/test-20220226
Children:
681ad68
Parents:
29f033a
Message:

chapter 19

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@1197 af4574ff-66df-0310-9fd7-8a98e5e911e0

Location:
basicnet
Files:
18 edited

Legend:

Unmodified
Added
Removed
  • basicnet/djb/daemontools/daemontools-desc.xml

    r29f033a r6998c44a  
    1919
    2020<sect3><title>svscanboot</title>
    21 <para><command>svscanboot</command> is simply a script that calls svscan and
    22 pipes its output to readproctitle.</para></sect3>
     21<para><command>svscanboot</command> is simply a script that calls
     22<command>svscan</command> and pipes its output to readproctitle.</para></sect3>
    2323
    2424<sect3><title>svscan</title>
    25 <para><command>svscan</command> checks the service directory for daemons to run
    26 and starts a <command>supervise</command> process for each run script that it
    27 finds.</para></sect3>
     25<para><command>svscan</command> checks the <filename>service</filename>
     26directory for daemons to run and starts a <command>supervise</command> process
     27for each run script that it finds.</para></sect3>
    2828
    2929<sect3><title>supervise</title>
     
    5555
    5656<sect3><title>readproctitle</title>
    57 <para><command>readproctitle</command> displays log entries in the output of ps.
     57<para><command>readproctitle</command> displays log entries in the output of
     58<command>ps</command>.
    5859</para></sect3>
    5960
  • basicnet/djb/daemontools/daemontools-exp.xml

    r29f033a r6998c44a  
    3636    -e 's|command|usr/sbin|' \
    3737    -e 's|/service|/etc/service|g' svscanboot &gt; svscanboot~ &amp;&amp;</command></screen>
    38 <para>Here various paths are adjusted in the svscanboot script. In our setup
    39 svscan will check the <filename>/etc/service</filename> directory instead of
     38<para>Here various paths are adjusted in the <command>svscanboot</command>
     39script. In our setup <command>svscan</command> will check the
     40<filename>/etc/service</filename> directory instead of
    4041the <filename>/service</filename> directory for daemons to run.</para>
    4142
     
    5051
    5152<para><command>mkdir /etc/service</command> : This command creates
    52 the daemontools control directory, which - even if empty - needs to exist for
     53the <application>daemontools</application> control directory, which - even if
     54empty - needs to exist for
    5355<application>daemontools</application> to run properly.</para>
    5456
  • basicnet/djb/djb.xml

    r29f033a r6998c44a  
    33<title>D.J. Bernstein's Utilities</title>
    44
    5 <para>This chapter includes applicatons needed for the qmail server.
     5<para>This chapter includes applications needed for the qmail server.
    66Their installation instructions are different than most packages in the
    77book because we want to support the <acronym>FHS</acronym> throughout
  • basicnet/djb/ucspi-tcp/ucspi-tcp-exp.xml

    r29f033a r6998c44a  
    22<title>Command explanations</title>
    33
    4 <para><screen><userinput>sed 's|/usr/local|/usr|' conf-home &gt; conf-home~
     4<para><screen><command>sed 's|/usr/local|/usr|' conf-home &gt; conf-home~
    55mv conf-home~ conf-home
    66sed 's/bin/sbin/' hier.c &gt; hier.c~
    7 mv hier.c~ hier.c</userinput></screen>
     7mv hier.c~ hier.c</command></screen>
    88These commands change the installation directory to
    99<filename>/usr/sbin</filename> from the default
     
    1414If you wish to make these available, then we would suggest installing as above,
    1515and then executing the following commands:
    16 <screen><userinput>cd /usr/sbin mv tcpclient *@ mconnect delcr addcr tcpcat /usr/bin</userinput></screen>
     16<screen><command>cd /usr/sbin mv tcpclient *@ mconnect delcr addcr tcpcat /usr/bin</command></screen>
    1717This will place the client related programs into <filename>/usr/bin</filename>
    1818for general use.</para>
  • basicnet/mailnews/fetchmail/fetchmail-intro.xml

    r29f033a r6998c44a  
    33
    44<para>The <application>Fetchmail</application> package contains the
    5 <command>fetchmail</command> program. &quot;It
     5a mail retrieval program. &quot;It
    66retrieves mail from remote mail servers and forwards it to your local
    77(client) machine's delivery system, so it can then be read by
  • basicnet/mailnews/mutt/mutt-config.xml

    r29f033a r6998c44a  
    1414man page for <filename>muttrc</filename> is a good starting place.</para>
    1515
    16 <para>In order to utilize gnupg, use the following command:
     16<para>In order to utilize <application>GnuPG</application>, use the following
     17command:
    1718<screen><userinput><command>cat /usr/share/doc/mutt/samples/gpg.rc &gt;&gt;
    1819~/.muttrc</command></userinput></screen></para>
  • basicnet/mailnews/mutt/mutt-desc.xml

    r29f033a r6998c44a  
    1717<sect3><title>flea</title>
    1818<para><command>flea</command> is a bug submitter for
    19 <application>mutt</application>.</para></sect3>
     19<application>Mutt</application>.</para></sect3>
    2020
    2121<sect3><title>muttbug</title>
  • basicnet/netutils/netutils.xml

    r29f033a r6998c44a  
    22<?dbhtml filename="netutils.html" dir="basicnet"?>
    33<title>Basic Networking Utilities</title>
     4
     5<para>This chapter contains some tools that come in handy when the
     6network need some investigating.</para>
    47
    58&traceroute;
  • basicnet/netutils/traceroute.xml

    r29f033a r6998c44a  
    1 <sect1 id="traceroute" xreflabel="traceroute">
     1<sect1 id="traceroute" xreflabel="Traceroute-&traceroute-version;">
    22<?dbhtml filename="traceroute.html" dir="basicnet"?>
    3 <title>traceroute-&traceroute-version;</title>
     3<title>Traceroute-&traceroute-version;</title>
    44
    55&traceroute-intro;
  • basicnet/netutils/traceroute/traceroute-desc.xml

    r29f033a r6998c44a  
    22<title>Contents</title>
    33
    4 <para>The traceroute package contains <userinput>traceroute</userinput>.</para>
     4<para>The <application>Traceroute</application> package contains <userinput>traceroute</userinput>.</para>
    55
    66</sect2>
     
    99
    1010<sect3><title>traceroute</title>
    11 <para>Traceroute does basically what it says: it traces the route your packets take from the host you are working on to another host on a network, showing all the intermediate steps (routers) along the way.</para></sect3>
     11<para><command>traceroute</command> does basically what it says: it traces the
     12route your packets take from the host you are working on to another host on a
     13network, showing all the intermediate steps (routers) along the way.</para>
     14</sect3>
    1215
    1316</sect2>
  • basicnet/netutils/traceroute/traceroute-exp.xml

    r29f033a r6998c44a  
    22<title>Command explanations</title>
    33
    4 <para><screen><userinput>sed 's/-o bin/-o root/'...</userinput></screen>
    5 Adjusts the Makefile so that the program is installed with user root instead
    6 of user bin (which doesn't exist on a default LFS system).</para>
     4<para><screen><command>sed 's/-o bin/-o root/'...</command></screen>
     5Adjusts the <filename>Makefile</filename> so that the program is installed
     6with user root instead of user bin (which doesn't exist on a default
     7<acronym>LFS</acronym> system).</para>
    78
    8 <para><userinput>make install</userinput> : Installs traceroute setuid root
    9 in the <filename>/usr/sbin</filename> directory. This makes it possible for all users to execute
    10 traceroute. For absolute security, turn off the setuid bit in traceroute's
    11 file permissions with the command:
    12 <screen><userinput>chmod 0755 /usr/sbin/traceroute</userinput></screen></para>
     9<para><command>make install</command> : Installs <command>traceroute</command>
     10setuid root in the <filename>/usr/sbin</filename> directory. This makes it
     11possible for all users to execute <command>traceroute</command>. For absolute
     12security, turn off the setuid bit in <command>traceroute</command>'s file
     13permissions with the command:
     14<screen><command>chmod 0755 /usr/sbin/traceroute</command></screen></para>
    1315
    1416<para>The risk is that if a security problem such as a buffer overflow were
    15 ever found in the traceroute code, a regular user on your system could gain
    16 root access if the program is setuid root. Removing the setuid permission
    17 of course also makes it impossible for users other than root to utilize
    18 traceroute, so decide what's right for your individual situation.</para>
     17ever found in the <application>Traceroute</application> code, a regular user
     18on your system could gain root access if the program is setuid root. Removing
     19the setuid permission of course also makes it impossible for users other than
     20root to utilize <command>traceroute</command>, so decide what's right for your
     21individual situation.</para>
    1922
    20 <para>Now, to be completely FHS compliant, as is our aim, if you do leave the
    21 traceroute binary setuid root, then you should move traceroute to
    22 <filename>/usr/bin</filename>
     23<para>Now, to be completely <acronym>FHS</acronym> compliant, as is our aim, if
     24you do leave the <command>traceroute</command> binary setuid root, then you
     25should move <filename>traceroute</filename> to <filename>/usr/bin</filename>
    2326with the following command:
    24 <screen><userinput>mv /usr/sbin/traceroute /usr/bin</userinput></screen></para>
     27<screen><command>mv /usr/sbin/traceroute /usr/bin</command></screen></para>
    2528
    2629<para>This ensures that the binary is in the path for non-root users.</para>
  • basicnet/netutils/traceroute/traceroute-inst.xml

    r29f033a r6998c44a  
    11<sect2>
    2 <title>Installation of traceroute</title>
     2<title>Installation of <application>Traceroute</application></title>
    33
    4 <para>Install traceroute by running the following commands:</para>
     4<para>Install <application>Traceroute</application> by running the following
     5commands:</para>
    56
    6 <para><screen><userinput>cp Makefile.in Makefile.in.bak &amp;&amp;
     7<screen><userinput><command>cp Makefile.in Makefile.in.bak &amp;&amp;
    78sed 's/-o bin/-o root/' Makefile.in.bak &gt; Makefile.in &amp;&amp;
    89./configure --prefix=/usr &amp;&amp;
    910make &amp;&amp;
    1011make install &amp;&amp;
    11 make install-man</userinput></screen></para>
     12make install-man</command></userinput></screen>
    1213
    1314</sect2>
  • basicnet/netutils/traceroute/traceroute-intro.xml

    r29f033a r6998c44a  
    11<sect2>
    2 <title>Introduction to traceroute</title>
     2<title>Introduction to <application>Traceroute</application></title>
    33
    4 <screen>Download location (HTTP):       <ulink url="&traceroute-download-http;"/>
    5 Download location (FTP):        <ulink url="&traceroute-download-ftp;"/>
    6 Version used:                   &traceroute-version;
    7 Package size:                   &traceroute-size;
    8 Estimated Disk space required:  &traceroute-buildsize;</screen>
     4<para>The <application>Traceroute</application> package contains a program
     5which is used to display the network route that packets take to reach a
     6specified host. This is a standard network troubleshooting tool. If you find
     7yourself unable to connect to another system, traceroute can help pinpoint
     8the problem.</para>
    99
    10 <para>The traceroute package contains the traceroute program, which is used
    11 to display the network route that packets take to reach a specified host. This
    12 is a standard network troubleshooting tool. If you find yourself unable to
    13 connect to another system, traceroute can help pinpoint the problem.</para>
     10<sect3><title>Package information</title>
     11<itemizedlist spacing='compact'>
     12<listitem><para>Download (HTTP): <ulink
     13url="&traceroute-download-http;"/></para></listitem>
     14<listitem><para>Download (FTP): <ulink
     15url="&traceroute-download-ftp;"/></para></listitem>
     16<listitem><para>Download size: &traceroute-size;</para></listitem>
     17<listitem><para>Estimated Disk space required:
     18&traceroute-buildsize;</para></listitem>
     19<listitem><para>Estimated build time:
     20&traceroute-time;</para></listitem></itemizedlist>
     21</sect3>
     22
    1423
    1524</sect2>
  • basicnet/netutils/traceroute/traceroute.ent

    r29f033a r6998c44a  
    99<!ENTITY traceroute-download-ftp "ftp://ftp.ee.lbl.gov/traceroute.tar.gz">
    1010<!ENTITY traceroute-size "35 KB">
     11<!ENTITY traceroute-time "">
  • basicnet/netutils/whois.xml

    r29f033a r6998c44a  
    1 <sect1 id="whois" xreflabel="whois">
     1<sect1 id="whois" xreflabel="Whois-&whois-version;">
    22<?dbhtml filename="whois.html" dir="basicnet"?>
    3 <title>whois-&whois-version;</title>
     3<title>Whois-&whois-version;</title>
    44
    55&whois-intro;
  • basicnet/netutils/whois/whois-desc.xml

    r29f033a r6998c44a  
    22<title>Contents</title>
    33
    4 <para>The whois package contains <command>whois</command>.</para>
     4<para>The <application>Whois</application> package contains <command>whois
     5</command>.</para>
    56
    67</sect2>
     
    910
    1011<sect3><title>whois</title>
    11 <para><command>whois</command> is a client-side application which queries the whois directory service for information pertaining to a particular domain name.</para></sect3>
     12<para><command>whois</command> is a client-side application which queries the
     13whois directory service for information pertaining to a particular domain name.
     14</para></sect3>
    1215
    1316</sect2>
  • basicnet/netutils/whois/whois-inst.xml

    r29f033a r6998c44a  
    11<sect2>
    2 <title>Installation of <application>whois</application></title>
     2<title>Installation of <application>Whois</application></title>
    33
    4 <para>Install <application>whois</application> by running the following commands:</para>
     4<para>Install <application>Whois</application> by running the following commands:</para>
    55
    66<para><screen><userinput><command>make &amp;&amp;
  • basicnet/netutils/whois/whois-intro.xml

    r29f033a r6998c44a  
    11<sect2>
    2 <title>Introduction to <application>whois</application></title>
     2<title>Introduction to <application>Whois</application></title>
    33
    4 <para>whois is a client-side application which queries the whois
    5 directory service for information pertaining to a particular domain
    6 name. <!--Note that you already have this program from your LFS
     4<para><application>Whois</application> is a client-side application which
     5queries the whois directory service for information pertaining to a particular
     6domain name. <!--Note that you already have this program from your LFS
    77installation, it can handle COM, NET and EDU queries. You will need
    88this application for any other domains. --></para>
Note: See TracChangeset for help on using the changeset viewer.