Changeset 17e6d48
- Timestamp:
- 05/30/2005 09:27:18 PM (19 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.1, 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, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 1065a91
- Parents:
- 5d5ced00
- Location:
- basicnet/netprogs
- Files:
-
- 9 edited
-
cvs.xml (modified) (5 diffs)
-
inetutils.xml (modified) (9 diffs)
-
ncftp.xml (modified) (5 diffs)
-
ncpfs.xml (modified) (9 diffs)
-
openssh-client.xml (modified) (1 diff)
-
portmap.xml (modified) (5 diffs)
-
rsync-client.xml (modified) (1 diff)
-
tcpwrappers.xml (modified) (13 diffs)
-
wget.xml (modified) (5 diffs)
Legend:
- Unmodified
- Added
- Removed
-
basicnet/netprogs/cvs.xml
r5d5ced00 r17e6d48 30 30 <title>Introduction to CVS</title> 31 31 32 <para><application>CVS</application> is the Concurrent Versioning System. 33 This is a version control system useful for projects using a central repository 34 to hold files and then track all changes made to those files. These instructions 35 install the client used to manipulate the repository, creation of a repository is 32 <para><application>CVS</application> is the Concurrent Versioning System. 33 This is a version control system useful for projects using a central repository 34 to hold files and then track all changes made to those files. These instructions 35 install the client used to manipulate the repository, creation of a repository is 36 36 covered at <xref linkend="cvsserver"/>.</para> 37 37 … … 69 69 70 70 <bridgehead renderas="sect4">Optional</bridgehead> 71 <para><xref linkend="gdbm"/>, 72 <xref linkend="tcsh"/>, 71 <para><xref linkend="gdbm"/>, 72 <xref linkend="tcsh"/>, 73 73 <ulink url="http://www.pdc.kth.se/kth-krb/">krb4</ulink>, 74 74 <xref linkend="mitkrb"/> or <xref linkend="heimdal"/> … … 91 91 <screen><userinput>patch -Np1 -i ../cvs-&cvs-version;-zlib-1.patch</userinput></screen> 92 92 93 <para>Install <application>cvs</application> by running 93 <para>Install <application>cvs</application> by running 94 94 the following commands:</para> 95 95 … … 140 140 diff -u</userinput> to their <filename>.cvsrc</filename> file.</para> 141 141 142 <para><filename>~/.cvswrappers</filename> specifies wrappers to be used in 142 <para><filename>~/.cvswrappers</filename> specifies wrappers to be used in 143 143 addition to those specified in the <filename>CVSROOT/cvswrappers</filename> 144 144 file in the repository.</para> … … 195 195 <term><command>rcs2log</command></term> 196 196 <listitem> 197 <para>is a symlink to the contributed RCS to Change Log 197 <para>is a symlink to the contributed RCS to Change Log 198 198 generator.</para> 199 199 <indexterm zone="cvs rcs2log"> -
basicnet/netprogs/inetutils.xml
r5d5ced00 r17e6d48 30 30 <title>Introduction to Inetutils</title> 31 31 32 <para>The <application>Inetutils</application> package contains network 32 <para>The <application>Inetutils</application> package contains network 33 33 clients and servers.</para> 34 34 … … 58 58 <itemizedlist spacing='compact'> 59 59 <listitem> 60 <para>Required Patch: <ulink 60 <para>Required Patch: <ulink 61 61 url="&patch-root;/inetutils-&inetutils-version;-kernel_headers-1.patch"/></para> 62 62 </listitem> 63 63 <listitem> 64 <para>Required Patch: <ulink 64 <para>Required Patch: <ulink 65 65 url="&patch-root;/inetutils-&inetutils-version;-daemon_fixes-1.patch"/></para> 66 66 </listitem> … … 70 70 71 71 <bridgehead renderas="sect4">Optional</bridgehead> 72 <para><xref linkend="Linux_PAM"/>, 73 <xref linkend="tcpwrappers"/>, 74 <ulink url="http://www.pdc.kth.se/kth-krb/">krb4</ulink>, and 72 <para><xref linkend="Linux_PAM"/>, 73 <xref linkend="tcpwrappers"/>, 74 <ulink url="http://www.pdc.kth.se/kth-krb/">krb4</ulink>, and 75 75 <xref linkend="heimdal"/> or <xref linkend="mitkrb"/></para> 76 76 … … 80 80 <title>Installation of Inetutils</title> 81 81 82 <para>Install <application>Inetutils</application> by running the following 82 <para>Install <application>Inetutils</application> by running the following 83 83 commands:</para> 84 84 … … 106 106 107 107 <para><parameter>--disable-syslogd</parameter>: This switch prevents 108 <application>Inetutils</application> installing a System Log Daemon, which is 108 <application>Inetutils</application> installing a System Log Daemon, which is 109 109 installed in the LFS Book.</para> 110 110 111 <para><option>--with-wrap</option>: This switch makes 112 <application>Inetutils</application> compile against 113 <application>tcp-wrappers</application>. Add this option if you want to 111 <para><option>--with-wrap</option>: This switch makes 112 <application>Inetutils</application> compile against 113 <application>tcp-wrappers</application>. Add this option if you want to 114 114 utilize <application>tcp-wrappers</application>.</para> 115 115 116 116 <para><option>--disable-whois</option>: This switch will prevent 117 <application>Inetutils</application> installing an outdated 118 <command>whois</command> client. Add this option if you plan on installing 117 <application>Inetutils</application> installing an outdated 118 <command>whois</command> client. Add this option if you plan on installing 119 119 <xref linkend="whois"/>.</para> 120 120 121 <para><option>--with-pam</option>: This switch makes 122 <application>Inetutils</application> link against 121 <para><option>--with-pam</option>: This switch makes 122 <application>Inetutils</application> link against 123 123 <application>Linux-PAM</application> libraries. 124 124 Add this option if you want to utilize PAM.</para> … … 134 134 <title>Contents</title> 135 135 136 <para>A list of the installed programs not included here, along with their 136 <para>A list of the installed programs not included here, along with their 137 137 short descriptions can be found at 138 138 <ulink url="&lfs-root;/chapter06/inetutils.html#contents-inetutils"/>.</para> … … 144 144 145 145 <seglistitem> 146 <seg>ftpd, inetd, rexecd, rlogind, rshd, talkd, telnetd, tftpd, uucpd and 146 <seg>ftpd, inetd, rexecd, rlogind, rshd, talkd, telnetd, tftpd, uucpd and 147 147 whois</seg> 148 148 <seg>None</seg> … … 240 240 <term><command>uucpd</command></term> 241 241 <listitem> 242 <para>is a server for supporting UUCP 242 <para>is a server for supporting UUCP 243 243 connections over networks.</para> 244 244 <indexterm zone="inetutils uucpd"> … … 251 251 <term><command>whois</command></term> 252 252 <listitem> 253 <para>is a client for the whois directory service. Note that the 253 <para>is a client for the whois directory service. Note that the 254 254 <xref linkend="whois"/> package provides a much better client.</para> 255 255 <indexterm zone="inetutils whois-inetutils"> -
basicnet/netprogs/ncftp.xml
r5d5ced00 r17e6d48 31 31 <title>Introduction to NcFTP</title> 32 32 33 <para>The <application>NcFTP</application> package contains 34 a powerful and flexible interface to the Internet standard File Transfer 35 Protocol. It is intended to replace or supplement the stock 33 <para>The <application>NcFTP</application> package contains 34 a powerful and flexible interface to the Internet standard File Transfer 35 Protocol. It is intended to replace or supplement the stock 36 36 <command>ftp</command> program.</para> 37 37 … … 64 64 65 65 <para>There are two ways to build <application>NcFTP</application>. 66 The first (and optimal) way builds most of the functionality as a shared library 67 and then builds and installs the program linked against this library. The 68 second method simply links all of the functionality into the binary statically. 66 The first (and optimal) way builds most of the functionality as a shared library 67 and then builds and installs the program linked against this library. The 68 second method simply links all of the functionality into the binary statically. 69 69 This doesn't make the dynamic library available for linking by other applications. 70 You need to choose which method best suits you. Note that the second method 71 does <emphasis>not</emphasis> create an entirely statically linked binary; 72 only the <filename class="libraryfile">libncftp</filename> parts are statically 73 linked in, in this case. Be aware that building and using the shared library is 74 covered by the Clarified Artistic License; however, developing applications that 70 You need to choose which method best suits you. Note that the second method 71 does <emphasis>not</emphasis> create an entirely statically linked binary; 72 only the <filename class="libraryfile">libncftp</filename> parts are statically 73 linked in, in this case. Be aware that building and using the shared library is 74 covered by the Clarified Artistic License; however, developing applications that 75 75 utilize the shared library is subject to a different license.</para> 76 76 77 <para>To install <application>NcFTP</application> using the 77 <para>To install <application>NcFTP</application> using the 78 78 first (and optimal) method, run the following commands:</para> 79 79 … … 84 84 make install</userinput></screen> 85 85 86 <para>To install <application>NcFTP</application> using the 86 <para>To install <application>NcFTP</application> using the 87 87 second method (with the <filename class="libraryfile">libncftp</filename> 88 88 functionality linked in statically) run the following commands:</para> … … 122 122 <title>Configuration Information</title> 123 123 124 <para>Most <application>NcFTP</application> configuration 125 is done while in the program, and the configuration files are dealt with 126 automatically. One exception to this is <filename>~/.ncftp/prefs_v3</filename>. 124 <para>Most <application>NcFTP</application> configuration 125 is done while in the program, and the configuration files are dealt with 126 automatically. One exception to this is <filename>~/.ncftp/prefs_v3</filename>. 127 127 There are various options to alter in there, including:</para> 128 128 … … 132 132 <application>NcFTPd</application> server.</para> 133 133 134 <para>There are other options in the <filename>prefs_v3</filename> file. Most 134 <para>There are other options in the <filename>prefs_v3</filename> file. Most 135 135 of these are self-explanatory.</para> 136 136 -
basicnet/netprogs/ncpfs.xml
r5d5ced00 r17e6d48 66 66 <title>Installation of NCPFS</title> 67 67 68 <para>Install <application>NCPFS</application> by running 68 <para>Install <application>NCPFS</application> by running 69 69 the following commands:</para> 70 70 … … 87 87 88 88 <para><parameter>--includedir=/usr/include</parameter>: Tells configure 89 to look in <filename class="directory">/usr/include</filename> for header 90 files. It also tells make to install <application>NCPFS</application>'s 89 to look in <filename class="directory">/usr/include</filename> for header 90 files. It also tells make to install <application>NCPFS</application>'s 91 91 headers here.</para> 92 92 … … 94 94 pages in the correct location.</para> 95 95 96 <para><parameter>--datadir=/usr/share</parameter>: correctly installs the 96 <para><parameter>--datadir=/usr/share</parameter>: correctly installs the 97 97 locale files to <filename class="directory">/usr/share</filename>.</para> 98 98 99 99 <note> 100 <para>If you do not need to use the IPX protocol, or you use a different 101 IPX package, you can optionally pass <option>--disable-ipx</option> and/or 100 <para>If you do not need to use the IPX protocol, or you use a different 101 IPX package, you can optionally pass <option>--disable-ipx</option> and/or 102 102 <option>--disable-ipx-tools</option> to the <command>configure</command> 103 103 script to disable these options.</para> … … 123 123 <title>Configuration Information</title> 124 124 125 <para>A config file <filename>~/.nwclient</filename> should be placed in the 126 home directory of each user that intends to use 127 <application>NCPFS</application>. The permissions on this file should be set 128 to 600, for obvious security reasons. The configuration file should contain 129 a single line per server that the user will use. Each line should contain 125 <para>A config file <filename>~/.nwclient</filename> should be placed in the 126 home directory of each user that intends to use 127 <application>NCPFS</application>. The permissions on this file should be set 128 to 600, for obvious security reasons. The configuration file should contain 129 a single line per server that the user will use. Each line should contain 130 130 the server name, the user name, and optionally the password. Below is a 131 131 sample <filename>.nwclient</filename> file.</para> … … 134 134 135 135 Server1/User1 Password 136 Server2/User1 136 Server2/User1 137 137 Server2/Guest1 - 138 138 … … 143 143 careful when creating or editing this file as the client utilities are 144 144 very picky about syntax. There should always be a space immediately 145 after the username. If this space is substituted by a tab or multiple 146 spaces, you will not get the expected results when attempting to use 147 the <application>NCPFS</application> tools. If no password is supplied, 148 the client utilities will ask for a password when it is needed. If no 149 password is needed, for instance when using a guest account, a single '-' 145 after the username. If this space is substituted by a tab or multiple 146 spaces, you will not get the expected results when attempting to use 147 the <application>NCPFS</application> tools. If no password is supplied, 148 the client utilities will ask for a password when it is needed. If no 149 password is needed, for instance when using a guest account, a single '-' 150 150 should be put in place of a password.</para> 151 151 152 152 <para>It should be noted that the <command>ncpmount</command> 153 is not intended to mount individual volumes because each mount point 154 creates a separate client connection to the Novell server. Mounting 155 each individual volume separately would be unwise, as mounting all 156 volumes on a server under one mount point uses only one client 153 is not intended to mount individual volumes because each mount point 154 creates a separate client connection to the Novell server. Mounting 155 each individual volume separately would be unwise, as mounting all 156 volumes on a server under one mount point uses only one client 157 157 connection.</para> 158 158 … … 164 164 <para>If you need to set up the IPX protocol at boot, you can install the 165 165 <filename>/etc/sysconfig/network-devices/services/ipx</filename> 166 network service script included with the 166 network service script included with the 167 167 <xref linkend="intro-important-bootscripts"/> package.</para> 168 168 … … 173 173 <screen><userinput>make install-service-ipx</userinput></screen> 174 174 175 <para>Next install the 175 <para>Next install the 176 176 <filename>/etc/sysconfig/network-devices/ifconfig.eth0/ipx</filename> 177 177 configuration file with the following commands:</para> … … 200 200 201 201 <seglistitem> 202 <seg>ncpmount, ncpumountt, nprintt, nsendt, nwpasswdt, 202 <seg>ncpmount, ncpumountt, nprintt, nsendt, nwpasswdt, 203 203 nwsfindt, pqlistt, pqrmt, pqstatt, and slist</seg> 204 <seg>ncopyt, nwbocreatet, nwbolst, nwbopropst, nwbormt, 205 nwbpaddt, nwbpcreatet, nwbprmt, nwbpsett, nwbpvaluest, 206 nwdirt, nwdpvaluest, nwfsctrlt, nwfsinfot, nwfstimet, nwgrantt, 207 nwpurget, nwrevoket, nwrightst, nwtrusteet, nwtrustee2t, 204 <seg>ncopyt, nwbocreatet, nwbolst, nwbopropst, nwbormt, 205 nwbpaddt, nwbpcreatet, nwbprmt, nwbpsett, nwbpvaluest, 206 nwdirt, nwdpvaluest, nwfsctrlt, nwfsinfot, nwfstimet, nwgrantt, 207 nwpurget, nwrevoket, nwrightst, nwtrusteet, nwtrustee2t, 208 208 nwuserlistt, and nwvolinfo</seg> 209 <seg>ipx_cmdt, ipx_configuret, ipx_interfacet, ipx_internal_nett, 209 <seg>ipx_cmdt, ipx_configuret, ipx_interfacet, ipx_internal_nett, 210 210 and ipx_route</seg> 211 211 <seg>ncpmap and nwauth</seg> -
basicnet/netprogs/openssh-client.xml
r5d5ced00 r17e6d48 16 16 <title>OpenSSH-&openssh-version; Client</title> 17 17 18 <para>The <command>ssh</command> client is a secure replacement for 19 <command>telnet</command>. If you want to install it, the instructions can be 20 found in Chapter 22 – <xref linkend="openssh"/>. Note that if you only 21 want to use the client, you do <emphasis>not</emphasis> need to run the server 22 and so do not need the startup script and links. In accordance with good 23 practice, only run the server if you actually need it (and if you don't know 18 <para>The <command>ssh</command> client is a secure replacement for 19 <command>telnet</command>. If you want to install it, the instructions can be 20 found in Chapter 22 – <xref linkend="openssh"/>. Note that if you only 21 want to use the client, you do <emphasis>not</emphasis> need to run the server 22 and so do not need the startup script and links. In accordance with good 23 practice, only run the server if you actually need it (and if you don't know 24 24 whether you need it or not, it's likely that you don't!).</para> 25 25 -
basicnet/netprogs/portmap.xml
r5d5ced00 r17e6d48 30 30 <title>Introduction to Portmap</title> 31 31 32 <para>The <application>portmap</application> package is a more secure 32 <para>The <application>portmap</application> package is a more secure 33 33 replacement for the original SUN <application>portmap</application> package. 34 <application>Portmap</application> is used to forward RPC requests to RPC 34 <application>Portmap</application> is used to forward RPC requests to RPC 35 35 daemons such as NFS and NIS.</para> 36 36 … … 60 60 <itemizedlist spacing='compact'> 61 61 <listitem> 62 <para>Required Patch: <ulink 62 <para>Required Patch: <ulink 63 63 url="&patch-root;/portmap-&portmap-version;-compilation_fixes-3.patch"/></para> 64 64 </listitem> 65 65 <listitem> 66 <para>Required Patch: <ulink 66 <para>Required Patch: <ulink 67 67 url="&patch-root;/portmap-&portmap-version;-glibc_errno_fix-1.patch"/></para> 68 68 </listitem> … … 79 79 <title>Installation of Portmap</title> 80 80 81 <para>Install <application>portmap</application> with the following 81 <para>Install <application>portmap</application> with the following 82 82 commands:</para> 83 83 … … 92 92 <note> 93 93 <para>The above installation places executable <command>portmap</command> 94 in <filename class="directory">/sbin</filename>. You may choose to move the 94 in <filename class="directory">/sbin</filename>. You may choose to move the 95 95 file to <filename class="directory">/usr/sbin</filename>. If you do, remember to 96 96 modify the bootscript also.</para> … … 105 105 <title>Boot Script</title> 106 106 107 <para>Install the <filename>/etc/rc.d/init.d/portmap</filename> init script 107 <para>Install the <filename>/etc/rc.d/init.d/portmap</filename> init script 108 108 included in the <xref linkend="intro-important-bootscripts"/> package.</para> 109 109 -
basicnet/netprogs/rsync-client.xml
r5d5ced00 r17e6d48 16 16 <title>Rsync-&rsync-version; Client</title> 17 17 18 <para><command>rsync</command> is a utility for fast incremental file 19 transfers. If you want to install it, the instructions can be found in Chapter 20 22 – <xref linkend="rsync"/>. Note that if you only want to use the 21 client, you do <emphasis>not</emphasis> need to run the server and so do not 22 need the startup script and links. In accordance with good practice, only run 23 the server if you actually need it (and if you don't know whether you need it 18 <para><command>rsync</command> is a utility for fast incremental file 19 transfers. If you want to install it, the instructions can be found in Chapter 20 22 – <xref linkend="rsync"/>. Note that if you only want to use the 21 client, you do <emphasis>not</emphasis> need to run the server and so do not 22 need the startup script and links. In accordance with good practice, only run 23 the server if you actually need it (and if you don't know whether you need it 24 24 or not, it's likely that you don't!).</para> 25 25 -
basicnet/netprogs/tcpwrappers.xml
r5d5ced00 r17e6d48 30 30 <title>Introduction to Tcpwrappers</title> 31 31 32 <para>The <application>tcpwrappers</application> package provides daemon 33 wrapper programs that report the name of the client requesting network 32 <para>The <application>tcpwrappers</application> package provides daemon 33 wrapper programs that report the name of the client requesting network 34 34 services and the requested service.</para> 35 35 … … 59 59 <itemizedlist spacing='compact'> 60 60 <listitem> 61 <para>Required Patch (Fixes some build issues and adds building of a 62 shared library): <ulink 61 <para>Required Patch (Fixes some build issues and adds building of a 62 shared library): <ulink 63 63 url="&patch-root;/tcp_wrappers-&tcpwrappers-version;-shared_lib_plus_plus-1.patch"/></para> 64 64 </listitem> … … 70 70 <title>Installation of Tcpwrappers</title> 71 71 72 <para>Install <application>tcpwrappers</application> with the following 72 <para>Install <application>tcpwrappers</application> with the following 73 73 commands:</para> 74 74 … … 86 86 <title>Command Explanations</title> 87 87 88 <para><command>sed -i -e ... scaffold.c</command>: This command removes an 89 obsolete C declaration which causes the build to fail if using 88 <para><command>sed -i -e ... scaffold.c</command>: This command removes an 89 obsolete C declaration which causes the build to fail if using 90 90 <application>GCC-3.4.x</application>.</para> 91 91 … … 98 98 <title>Config Files</title> 99 99 100 <para><filename>/etc/hosts.allow</filename> and 100 <para><filename>/etc/hosts.allow</filename> and 101 101 <filename>/etc/hosts.deny</filename></para> 102 102 … … 114 114 555). Do not install the wrapper set-uid.</para> 115 115 116 <para>As the <systemitem class="username">root</systemitem> user, 116 <para>As the <systemitem class="username">root</systemitem> user, 117 117 perform the following edits on the 118 118 <filename>/etc/inetd.conf</filename> configuration file:</para> … … 132 132 </note> 133 133 134 <para>Similar changes must be made if <application>xinetd</application> is 134 <para>Similar changes must be made if <application>xinetd</application> is 135 135 used, with the emphasis being on calling <command>/usr/sbin/tcpd</command> 136 instead of calling the service daemon directly, and passing the name of the 136 instead of calling the service daemon directly, and passing the name of the 137 137 service daemon to <command>tcpd</command>.</para> 138 138 … … 168 168 <term><command>tcpd</command></term> 169 169 <listitem> 170 <para>is the main access control daemon for all Internet services, 170 <para>is the main access control daemon for all Internet services, 171 171 which <command>inetd</command> or <command>xinetd</command> 172 172 will run instead of running the requested service daemon.</para> … … 180 180 <term><command>tcpdchk</command></term> 181 181 <listitem> 182 <para>is a tool to examine a <command>tcpd</command> wrapper 182 <para>is a tool to examine a <command>tcpd</command> wrapper 183 183 configuration and report problems with it.</para> 184 184 <indexterm zone="tcpwrappers tcpdchk"> … … 191 191 <term><command>tcpdmatch</command></term> 192 192 <listitem> 193 <para>is used to predict how the TCP wrapper 193 <para>is used to predict how the TCP wrapper 194 194 would handle a specific request for a service.</para> 195 195 <indexterm zone="tcpwrappers tcpdmatch"> … … 202 202 <term><command>try-from</command></term> 203 203 <listitem> 204 <para>can be called via a remote shell command to find out if the 204 <para>can be called via a remote shell command to find out if the 205 205 host name and address are properly recognized.</para> 206 206 <indexterm zone="tcpwrappers try-from"> … … 213 213 <term><command>safe_finger</command></term> 214 214 <listitem> 215 <para>is a wrapper for the <command>finger</command> utility, to 215 <para>is a wrapper for the <command>finger</command> utility, to 216 216 provide automatic reverse name lookups.</para> 217 217 <indexterm zone="tcpwrappers safe_finger"> … … 224 224 <term><filename class='libraryfile'>libwrap.[so,a]</filename></term> 225 225 <listitem> 226 <para>contains the API functions required by 227 the <application>tcpwrappers</application> programs as well as other programs 226 <para>contains the API functions required by 227 the <application>tcpwrappers</application> programs as well as other programs 228 228 to become <quote><application>tcpwrappers</application>-aware</quote>.</para> 229 229 <indexterm zone="tcpwrappers libwrap"> -
basicnet/netprogs/wget.xml
r5d5ced00 r17e6d48 30 30 <title>Introduction to Wget</title> 31 31 32 <para>The <application>Wget</application> package contains a utility useful for 32 <para>The <application>Wget</application> package contains a utility useful for 33 33 non-interactive downloading of files from the Web.</para> 34 34 … … 58 58 59 59 <bridgehead renderas="sect4">Optional</bridgehead> 60 <para><xref linkend="openssl"/> and 60 <para><xref linkend="openssl"/> and 61 61 <ulink url="http://www.inet.no/dante/">Dante</ulink></para> 62 62 … … 66 66 <title>Installation of Wget</title> 67 67 68 <para>Install <application>Wget</application> by running the following 68 <para>Install <application>Wget</application> by running the following 69 69 commands:</para> 70 70 … … 84 84 85 85 <para><parameter>--sysconfdir=/etc</parameter>: This relocates 86 the configuration file from <filename class="directory">/usr/etc</filename> to 86 the configuration file from <filename class="directory">/usr/etc</filename> to 87 87 <filename class="directory">/etc</filename>.</para> 88 88 … … 136 136 <listitem> 137 137 <para> retrieves files from the Web using the HTTP, HTTPS and 138 FTP protocols. It is designed to be non-interactive, for 138 FTP protocols. It is designed to be non-interactive, for 139 139 background or unattended operations.</para> 140 140 <indexterm zone="wget wget-prog">
Note:
See TracChangeset
for help on using the changeset viewer.
