Changeset b51fe6e
- Timestamp:
- 03/22/2020 03:52:07 PM (4 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, kea, ken/inkscape-core-mods, lazarus, lxqt, plabs/python-mods, qt5new, trunk, upgradedb, xry111/intltool, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- 254bc90d
- Parents:
- dcee7a56
- Location:
- networking/netprogs
- Files:
-
- 16 edited
Legend:
- Unmodified
- Added
- Removed
-
networking/netprogs/bridgeutils.xml
rdcee7a56 rb51fe6e 30 30 <title>Introduction to bridge-utils</title> 31 31 32 <para>The <application>bridge-utils</application> package contains a utility 33 needed to create and manage bridge devices. This is useful in setting up 34 networks for a hosted virtual machine (VM).</para> 32 <para> 33 The <application>bridge-utils</application> package contains a utility 34 needed to create and manage bridge devices. This is useful in setting up 35 networks for a hosted virtual machine (VM). 36 </para> 35 37 36 38 &lfs91_checked; … … 39 41 <itemizedlist spacing="compact"> 40 42 <listitem> 41 <para>Download (HTTP): <ulink url="&bridge-download-http;"/></para> 42 </listitem> 43 <listitem> 44 <para>Download (FTP): <ulink url="&bridge-download-ftp;"/></para> 45 </listitem> 46 <listitem> 47 <para>Download MD5 sum: &bridge-md5sum;</para> 48 </listitem> 49 <listitem> 50 <para>Download size: &bridge-size;</para> 51 </listitem> 52 <listitem> 53 <para>Estimated disk space required: &bridge-buildsize;</para> 54 </listitem> 55 <listitem> 56 <para>Estimated build time: &bridge-time;</para> 43 <para> 44 Download (HTTP): <ulink url="&bridge-download-http;"/> 45 </para> 46 </listitem> 47 <listitem> 48 <para> 49 Download (FTP): <ulink url="&bridge-download-ftp;"/> 50 </para> 51 </listitem> 52 <listitem> 53 <para> 54 Download MD5 sum: &bridge-md5sum; 55 </para> 56 </listitem> 57 <listitem> 58 <para> 59 Download size: &bridge-size; 60 </para> 61 </listitem> 62 <listitem> 63 <para> 64 Estimated disk space required: &bridge-buildsize; 65 </para> 66 </listitem> 67 <listitem> 68 <para> 69 Estimated build time: &bridge-time; 70 </para> 57 71 </listitem> 58 72 </itemizedlist> … … 73 87 <title>Kernel Configuration</title> 74 88 75 <para>Enable the following options in the kernel configuration 76 and recompile the kernel if necessary:</para> 89 <para> 90 Enable the following options in the kernel configuration 91 and recompile the kernel if necessary: 92 </para> 77 93 78 94 <screen><literal>[*] Networking support ---> [CONFIG_NET] … … 89 105 <title>Installation of bridge-utils</title> 90 106 91 <para>Install <application>bridge-utils</application> by running the following 92 commands:</para> 107 <para> 108 Install <application>bridge-utils</application> by running the following 109 commands: 110 </para> 93 111 94 112 <screen><userinput>autoconf && … … 96 114 make</userinput></screen> 97 115 98 <para>Testing the results requires running the six shell scripts in 99 the <filename class='directory'>tools/</filename> directory. 100 Two of the tests require two ethernet ports. Some tests 101 will not preserve the current network configuration. See 102 <filename>tests/README</filename> for details.</para> 103 104 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 116 <para> 117 Testing the results requires running the six shell scripts in 118 the <filename class='directory'>tools/</filename> directory. 119 Two of the tests require two ethernet ports. Some tests 120 will not preserve the current network configuration. See 121 <filename>tests/README</filename> for details. 122 </para> 123 124 <para> 125 Now, as the <systemitem class="username">root</systemitem> user: 126 </para> 105 127 106 128 <screen role="root"><userinput>make install</userinput></screen> … … 114 136 <title>Configuration Information</title> 115 137 116 <para>To automate bridge creation and configuration, 117 install the <filename>/lib/services/etc/bridge</filename> 118 service script included in the <xref linkend="bootscripts"/> 119 package.</para> 138 <para> 139 To automate bridge creation and configuration, 140 install the <filename>/lib/services/etc/bridge</filename> 141 service script included in the <xref linkend="bootscripts"/> 142 package. 143 </para> 120 144 121 145 <indexterm zone="bridgeutils bridgeutils-init"> … … 125 149 <screen role="root"><userinput>make install-service-bridge</userinput></screen> 126 150 127 <note><para>The <filename>bridge</filename> script depends 128 on the commands <command>/sbin/ifup</command> and 129 <command>/sbin/ifdown</command> and the service script 130 <emphasis>ipv4-static</emphasis> from the <emphasis>LFS</emphasis> 131 bootscripts dated January 27, 2012 or later.</para></note> 132 133 <para>The following configuration file will create a bridge device at 134 boot time and attach the eth0 device to it. If more than one device is 135 desired, use a space separated list of INTERFACE_COMPONENTS. This 136 configuration is useful when planning to run a virtual machine such as 137 kvm/qemu.</para> 138 139 <para>Other SERVICE combinations are possible, for example, 140 SERVICES="bridge dhcp". In that case, the address parameters 141 are not needed, but do not interfere if present. The 142 bridge service may also be used alone, but will require 143 additional subsequent configuration.</para> 144 145 <caution><para>Do not run a parallel configuration for a device in the 146 INTERFACE_COMPONENTS list. For instance, in the example below, do not 147 configure <filename>/etc/sysconfig/ifconfig.eth0</filename> to run at 148 boot time. The command <command>ifdown br0</command> followed by 149 command <command>ifup eth0</command> will work, but don't try to have 150 both up at the same time.</para></caution> 151 <note> 152 <para> 153 The <filename>bridge</filename> script depends 154 on the commands <command>/sbin/ifup</command> and 155 <command>/sbin/ifdown</command> and the service script 156 <emphasis>ipv4-static</emphasis> from the <emphasis>LFS</emphasis> 157 bootscripts dated January 27, 2012 or later. 158 </para> 159 </note> 160 161 <para> 162 The following configuration file will create a bridge device at 163 boot time and attach the eth0 device to it. If more than one device is 164 desired, use a space separated list of INTERFACE_COMPONENTS. This 165 configuration is useful when planning to run a virtual machine such as 166 kvm/qemu. 167 </para> 168 169 <para> 170 Other SERVICE combinations are possible, for example, 171 SERVICES="bridge dhcp". In that case, the address parameters 172 are not needed, but do not interfere if present. The 173 bridge service may also be used alone, but will require 174 additional subsequent configuration. 175 </para> 176 177 <caution> 178 <para> 179 Do not run a parallel configuration for a device in the 180 INTERFACE_COMPONENTS list. For instance, in the example below, do not 181 configure <filename>/etc/sysconfig/ifconfig.eth0</filename> to run at 182 boot time. The command <command>ifdown br0</command> followed by 183 command <command>ifup eth0</command> will work, but don't try to have 184 both up at the same time. 185 </para> 186 </caution> 151 187 152 188 <screen role="root"><userinput>cat > /etc/sysconfig/ifconfig.br0 << "EOF" … … 165 201 EOF</userinput></screen> 166 202 167 <para>All addresses should be changed to meet your circumstance.</para> 203 <para> 204 All addresses should be changed to meet your circumstance. 205 </para> 168 206 169 207 </sect3> … … 171 209 <sect3 id='bridgeutils-init-systemd' revision="systemd"> 172 210 <title>Configuration Information</title> 173 <para>TBA</para> 211 <para> 212 TBA 213 </para> 174 214 </sect3> 175 215 … … 200 240 <term><command>brctl</command></term> 201 241 <listitem> 202 <para>is a program used to set up, maintain, and inspect the 203 ethernet bridge configuration in the linux kernel. </para> 242 <para> 243 is a program used to set up, maintain, and inspect the 244 ethernet bridge configuration in the linux kernel. 245 </para> 204 246 <indexterm zone="bridgeutils brctl"> 205 247 <primary sortas="b-brctl">brctl</primary> -
networking/netprogs/cifsutils.xml
rdcee7a56 rb51fe6e 30 30 <title>Introduction to cifs-utils</title> 31 31 32 <para>The <application>cifs-utils</application> provides a means for 33 mounting SMB/CIFS shares on a Linux system.</para> 32 <para> 33 The <application>cifs-utils</application> provides a means for 34 mounting SMB/CIFS shares on a Linux system. 35 </para> 34 36 35 37 &lfs91_checked; … … 38 40 <itemizedlist spacing="compact"> 39 41 <listitem> 40 <para>Download (HTTP): <ulink url="&cifsutils-download-http;"/></para> 41 </listitem> 42 <listitem> 43 <para>Download (FTP): <ulink url="&cifsutils-download-ftp;"/></para> 44 </listitem> 45 <listitem> 46 <para>Download MD5 sum: &cifsutils-md5sum;</para> 47 </listitem> 48 <listitem> 49 <para>Download size: &cifsutils-size;</para> 50 </listitem> 51 <listitem> 52 <para>Estimated disk space required: &cifsutils-buildsize;</para> 53 </listitem> 54 <listitem> 55 <para>Estimated build time: &cifsutils-time;</para> 42 <para> 43 Download (HTTP): <ulink url="&cifsutils-download-http;"/> 44 </para> 45 </listitem> 46 <listitem> 47 <para> 48 Download (FTP): <ulink url="&cifsutils-download-ftp;"/> 49 </para> 50 </listitem> 51 <listitem> 52 <para> 53 Download MD5 sum: &cifsutils-md5sum; 54 </para> 55 </listitem> 56 <listitem> 57 <para> 58 Download size: &cifsutils-size; 59 </para> 60 </listitem> 61 <listitem> 62 <para> 63 Estimated disk space required: &cifsutils-buildsize; 64 </para> 65 </listitem> 66 <listitem> 67 <para> 68 Estimated build time: &cifsutils-time; 69 </para> 56 70 </listitem> 57 71 </itemizedlist> … … 70 84 <xref linkend="mitkrb"/>, 71 85 <xref linkend="samba"/>, and 72 <ulink url="http://people.redhat.com/sgrubb/libcap-ng/">libcap-ng</ulink> or 73 <xref linkend="libcap-pam"/> 86 <xref linkend="libcap-pam"/> or 87 <ulink url="http://people.redhat.com/sgrubb/libcap-ng/"> 88 libcap-ng 89 </ulink> 74 90 </para> 75 91 … … 105 121 <title>Installation of cifs-utils</title> 106 122 107 <para>Install <application>cifs-utils</application> by running the following 108 commands:</para> 123 <para> 124 Install <application>cifs-utils</application> by running the following 125 commands: 126 </para> 109 127 110 128 <screen revision="sysv"><userinput>autoreconf -fiv && … … 119 137 make</userinput></screen> 120 138 121 <para>This package does not come with a test suite.</para> 122 123 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 139 <para> 140 This package does not come with a test suite. 141 </para> 142 143 <para> 144 Now, as the <systemitem class="username">root</systemitem> user: 145 </para> 124 146 125 147 <!-- Note to editors: You need to define ROOTSBINDIR and man8dir, like this: … … 134 156 135 157 <sect2 role="commands"> 136 <title>Command Explanations</title> 137 138 <para><parameter>--disable-pam</parameter>: Do not build PAM support. 139 Remove it and use <option>--with-pamdir</option> (see below), 140 if <xref linkend="linux-pam"/> is installed and you wish 141 PAM support.</para> 142 143 <para revision="sysv"><parameter>--disable-systemd</parameter>: 144 Disable systemd specific behavior for 145 <command>mount.cifs</command>. Remove it for systems running with 146 systemd.</para> 147 148 <para><option>--with-pamdir=/lib/security</option>: Install the PAM 149 module in 150 <filename class="directory">/lib/security</filename>.</para> 158 <title>Command Explanations</title> 159 160 <para> 161 <parameter>--disable-pam</parameter>: Do not build PAM support. 162 Remove it and use <option>--with-pamdir</option> (see below), 163 if <xref linkend="linux-pam"/> is installed and you wish 164 PAM support. 165 </para> 166 167 <para revision="sysv"> 168 <parameter>--disable-systemd</parameter>: Disable systemd specific 169 behavior for <command>mount.cifs</command>. 170 </para> 171 172 <para> 173 <option>--with-pamdir=/lib/security</option>: Install the PAM 174 module in <filename class="directory">/lib/security</filename>. 175 </para> 151 176 152 177 </sect2> … … 177 202 <term><command>cifs.idmap</command></term> 178 203 <listitem> 179 <para>is a userspace helper program for the linux CIFS client 180 filesystem. There are a number of activities that the kernel cannot 181 easily do itself. This program is a callout program that does these 182 things for the kernel and then returns the result. It is not intended 183 to be run from the command-line.</para> 204 <para> 205 is a userspace helper program for the linux CIFS client filesystem. 206 There are a number of activities that the kernel cannot easily do 207 itself. This program is a callout program that does these 208 things for the kernel and then returns the result. It is not 209 intended to be run from the command-line. 210 </para> 184 211 <indexterm zone="cifsutils cifs.idmap"> 185 212 <primary sortas="b-cifs.idmap">cifs.idmap</primary> … … 191 218 <term><command>cifs.upcall</command></term> 192 219 <listitem> 193 <para>is a userspace helper program for the linux CIFS client 194 filesystem. It is intended to be run when the kernel calls 195 request-key for a particular key type. It is not intended to be 196 run from the command-line.</para> 220 <para> 221 is a userspace helper program for the linux CIFS client 222 filesystem. It is intended to be run when the kernel calls 223 request-key for a particular key type. It is not intended to be 224 run from the command-line. 225 </para> 197 226 <indexterm zone="cifsutils cifs.upcall"> 198 227 <primary sortas="b-cifs.upcall">cifs.upcall</primary> … … 204 233 <term><command>cifscreds</command></term> 205 234 <listitem> 206 <para>is a tool for managing credentials (username and password) 207 for the purpose of establishing sessions in multiuser mounts.</para> 235 <para> 236 is a tool for managing credentials (username and password) 237 for the purpose of establishing sessions in multiuser mounts. 238 </para> 208 239 <indexterm zone="cifsutils cifscreds"> 209 240 <primary sortas="b-cifscreds">cifscreds</primary> … … 215 246 <term><command>getcifsacl</command></term> 216 247 <listitem> 217 <para>is a userspace helper to display an ACL in a security 218 descriptor for Common Internet File System (CIFS).</para> 248 <para> 249 is a userspace helper to display an ACL in a security 250 descriptor for Common Internet File System (CIFS). 251 </para> 219 252 <indexterm zone="cifsutils getcifsacl"> 220 253 <primary sortas="b-getcifsacl">getcifsacl</primary> … … 226 259 <term><command>mount.cifs</command></term> 227 260 <listitem> 228 <para>mounts a Linux CIFS filesystem. It is usually invoked 229 indirectly by the mount(8) command when using the "-t cifs" option. 261 <para> 262 mounts a Linux CIFS filesystem. It is usually invoked 263 indirectly by the mount(8) command when using the "-t cifs" option. 230 264 </para> 231 265 <indexterm zone="cifsutils mount.cifs"> … … 238 272 <term><command>mount.smb3</command></term> 239 273 <listitem> 240 <para>mounts a SMB3-based filesystem. It is usually invoked 241 indirectly by the mount(8) command when using the "-t smb3" option. 274 <para> 275 mounts a SMB3-based filesystem. It is usually invoked 276 indirectly by the mount(8) command when using the "-t smb3" option. 242 277 </para> 243 278 <indexterm zone="cifsutils mount.smb3"> … … 250 285 <term><command>setcifsacl</command></term> 251 286 <listitem> 252 <para>is intended to alter an ACL of a security descriptor for a file 253 system object.</para> 287 <para> 288 is intended to alter an ACL of a security descriptor for a file 289 system object. 290 </para> 254 291 <indexterm zone="cifsutils setcifsacl"> 255 292 <primary sortas="b-setcifsacl">setcifsacl</primary> … … 261 298 <term><command>smb3-quota</command></term> 262 299 <listitem> 263 <para>displays quota information for a SMB filesystem.</para> 300 <para> 301 displays quota information for a SMB filesystem. 302 </para> 264 303 <indexterm zone="cifsutils smb2-quota"> 265 304 <primary sortas="b-smb2-quota">smb2-quota</primary> … … 271 310 <term><command>smbinfo</command></term> 272 311 <listitem> 273 <para>displays SMB-specific file information, such as security 274 descriptors and quotas.</para> 312 <para> 313 displays SMB-specific file information, such as security 314 descriptors and quotas. 315 </para> 275 316 <indexterm zone="cifsutils smbinfo"> 276 317 <primary sortas="b-smbinfo">smbinfo</primary> -
networking/netprogs/iw.xml
rdcee7a56 rb51fe6e 30 30 <title>Introduction to iw</title> 31 31 32 <para>iw is a new nl80211 based CLI configuration utility for wireless 33 devices. It supports all new drivers that have been added to the kernel 34 recently. The old tool iwconfig, which uses Wireless Extensions interface, 35 is deprecated and it's strongly recommended to switch to iw and nl80211. 32 <para> 33 <application>iw</application> is a new nl80211 based CLI configuration 34 utility for wireless devices. It supports all new drivers that have been 35 added to the kernel recently. The old tool 36 <application>iwconfig</application>, which uses Wireless Extensions 37 interface, is deprecated and it's strongly recommended to switch to 38 <application>iw</application> and nl80211. 36 39 </para> 37 40 … … 41 44 <itemizedlist spacing='compact'> 42 45 <listitem> 43 <para>Download (HTTP): <ulink url="&iw-download-http;"/></para> 46 <para> 47 Download (HTTP): <ulink url="&iw-download-http;"/> 48 </para> 44 49 </listitem> 45 50 <listitem> 46 <para>Download (FTP): <ulink url="&iw-download-ftp;"/></para> 51 <para> 52 Download (FTP): <ulink url="&iw-download-ftp;"/> 53 </para> 47 54 </listitem> 48 55 <listitem> 49 <para>Download MD5 sum: &iw-md5sum;</para> 56 <para> 57 Download MD5 sum: &iw-md5sum; 58 </para> 50 59 </listitem> 51 60 <listitem> 52 <para>Download size: &iw-size;</para> 61 <para> 62 Download size: &iw-size; 63 </para> 53 64 </listitem> 54 65 <listitem> 55 <para>Estimated disk space required: &iw-buildsize;</para> 66 <para> 67 Estimated disk space required: &iw-buildsize; 68 </para> 56 69 </listitem> 57 70 <listitem> 58 <para>Estimated build time: &iw-time;</para> 71 <para> 72 Estimated build time: &iw-time; 73 </para> 59 74 </listitem> 60 75 </itemizedlist> … … 79 94 </indexterm> 80 95 81 <para>To use <application>iw</application>, the kernel must 82 have the appropriate drivers and other support available. The appropriate 83 bus must also be available. For older laptops, the PCMCIA bus 84 (CONFIG_PCCARD) needs to be built. In some cases, this bus support will 85 also need to be built for embedded iw cards. The appropriate bridge 86 support also needs to be built. For many modern laptops, the CardBus host 87 bridge (CONFIG_YENTA) will be needed.</para> 96 <para> 97 To use <application>iw</application>, the kernel must have the 98 appropriate drivers and other support available. The appropriate bus 99 must also be available. For older laptops, the PCMCIA bus 100 (CONFIG_PCCARD) needs to be built. In some cases, this bus support will 101 also need to be built for embedded iw cards. The appropriate bridge 102 support also needs to be built. For many modern laptops, the CardBus host 103 bridge (CONFIG_YENTA) will be needed. 104 </para> 88 105 89 <para>In addition to the bus, the actual driver for the specific wireless 90 card must also be available. There are many wireless cards and they don't 91 all work with Linux. The first place to look for card support is the kernel. 92 The drivers are located in Device Drivers → Network Device Support 93 → Wireless LAN (non-hamradio). There are also external drivers 94 available for some very common cards. For more information, look 95 at the user notes.</para> 106 <para> 107 In addition to the bus, the actual driver for the specific wireless 108 card must also be available. There are many wireless cards and they 109 don't all work with Linux. The first place to look for card support is 110 the kernel. The drivers are located in Device Drivers → Network 111 Device Support → Wireless LAN (non-hamradio). There are also 112 external drivers available for some very common cards. For more 113 information, look at the user notes. 114 </para> 96 115 97 <para>After the correct drivers are loaded, the interface will 98 appear in <filename>/proc/net/wireless</filename>.</para> 116 <para> 117 After the correct drivers are loaded, the interface will 118 appear in <filename>/proc/net/wireless</filename>. 119 </para> 99 120 100 121 </sect2> … … 103 124 <title>Installation of iw</title> 104 125 105 <para>To install <application>iw</application>, 106 use the following commands:</para> 126 <para> 127 To install <application>iw</application>, 128 use the following commands: 129 </para> 107 130 108 131 <screen><userinput>sed -i "/INSTALL.*gz/s/.gz//" Makefile && 109 132 make</userinput></screen> 110 133 111 <para>This package does not come with a test suite.</para> 134 <para> 135 This package does not come with a test suite. 136 </para> 112 137 113 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 138 <para> 139 Now, as the <systemitem class="username">root</systemitem> user: 140 </para> 114 141 115 142 <screen role="root"><userinput>make SBINDIR=/sbin install</userinput></screen> … … 120 147 <title>Command Explanations</title> 121 148 122 <para><command>sed ...</command>: Install uncompressed manual pages 123 in accordance with other man pages.</para> 149 <para> 150 <command>sed ...</command>: Install uncompressed manual pages 151 in accordance with other man pages. 152 </para> 124 153 125 154 </sect2> … … 148 177 <term><command>iw</command></term> 149 178 <listitem> 150 <para>show / manipulate wireless devices and their configuration</para> 179 <para> 180 shows / manipulates wireless devices and their configuration. 181 </para> 151 182 <indexterm zone="iw iw-prog"> 152 183 <primary sortas="b-iw">iw</primary> -
networking/netprogs/ncftp.xml
rdcee7a56 rb51fe6e 30 30 <title>Introduction to NcFTP</title> 31 31 32 <para>The <application>NcFTP</application> package contains 33 a powerful and flexible interface to the Internet standard File Transfer 34 Protocol. It is intended to replace or supplement the stock 35 <command>ftp</command> program.</para> 32 <para> 33 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 <command>ftp</command> program. 37 </para> 36 38 37 39 &lfs91_checked; … … 40 42 <itemizedlist spacing="compact"> 41 43 <listitem> 42 <para>Download (HTTP): <ulink url="&ncftp-download-http;"/></para> 43 </listitem> 44 <listitem> 45 <para>Download (FTP): <ulink url="&ncftp-download-ftp;"/></para> 46 </listitem> 47 <listitem> 48 <para>Download MD5 sum: &ncftp-md5sum;</para> 49 </listitem> 50 <listitem> 51 <para>Download size: &ncftp-size;</para> 52 </listitem> 53 <listitem> 54 <para>Estimated disk space required: &ncftp-buildsize;</para> 55 </listitem> 56 <listitem> 57 <para>Estimated build time: &ncftp-time;</para> 44 <para> 45 Download (HTTP): <ulink url="&ncftp-download-http;"/> 46 </para> 47 </listitem> 48 <listitem> 49 <para> 50 Download (FTP): <ulink url="&ncftp-download-ftp;"/> 51 </para> 52 </listitem> 53 <listitem> 54 <para> 55 Download MD5 sum: &ncftp-md5sum; 56 </para> 57 </listitem> 58 <listitem> 59 <para> 60 Download size: &ncftp-size; 61 </para> 62 </listitem> 63 <listitem> 64 <para> 65 Estimated disk space required: &ncftp-buildsize; 66 </para> 67 </listitem> 68 <listitem> 69 <para> 70 Estimated build time: &ncftp-time; 71 </para> 58 72 </listitem> 59 73 </itemizedlist> … … 74 88 <title>Installation of NcFTP</title> 75 89 76 <para>There are two ways to build <application>NcFTP</application>. 77 The first (and optimal) way builds most of the functionality as a shared library 78 and then builds and installs the program linked against this library. The 79 second method simply links all of the functionality into the binary statically. 80 This doesn't make the dynamic library available for linking by other applications. 81 You need to choose which method best suits you. Note that the second method 82 does <emphasis>not</emphasis> create an entirely statically linked binary; 83 only the <filename class="libraryfile">libncftp</filename> parts are statically 84 linked in, in this case. Be aware that building and using the shared library is 85 covered by the Clarified Artistic License; however, developing applications that 86 utilize the shared library is subject to a different license.</para> 87 88 <para>To install <application>NcFTP</application> using the 89 first (and optimal) method, run the following commands:</para> 90 <para> 91 There are two ways to build <application>NcFTP</application>. The first 92 (and optimal) way builds most of the functionality as a shared library 93 and then builds and installs the program linked against this library. 94 The second method simply links all of the functionality into the binary 95 statically. This doesn't make the dynamic library available for linking 96 by other applications. You need to choose which method best suits you. 97 Note that the second method does <emphasis>not</emphasis> create an 98 entirely statically linked binary; only the <filename 99 class="libraryfile">libncftp</filename> parts are statically linked in, 100 in this case. Be aware that building and using the shared library is 101 covered by the Clarified Artistic License; however, developing 102 applications that utilize the shared library is subject to a different 103 license. 104 </para> 105 106 <para> 107 To install <application>NcFTP</application> using the 108 first (and optimal) method, run the following commands: 109 </para> 90 110 91 111 <screen><userinput>./configure --prefix=/usr --sysconfdir=/etc && … … 93 113 make</userinput></screen> 94 114 95 <para>This package does not come with a test suite.</para> 96 97 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 115 <para> 116 This package does not come with a test suite. 117 </para> 118 119 <para> 120 Now, as the <systemitem class="username">root</systemitem> user: 121 </para> 98 122 99 123 <screen role='root'><userinput>make -C libncftp soinstall && 100 124 make install</userinput></screen> 101 125 102 <para>To install <application>NcFTP</application> using the 103 second method (with the <filename class="libraryfile">libncftp</filename> 104 functionality linked in statically) run the following commands:</para> 126 <para> 127 To install <application>NcFTP</application> using the 128 second method (with the <filename class="libraryfile">libncftp</filename> 129 functionality linked in statically) run the following commands: 130 </para> 105 131 106 132 <screen role="nodump"><userinput>./configure --prefix=/usr --sysconfdir=/etc && 107 133 make</userinput></screen> 108 134 109 <para>This package does not come with a test suite.</para> 110 111 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 135 <para> 136 This package does not come with a test suite. 137 </para> 138 139 <para> 140 Now, as the <systemitem class="username">root</systemitem> user: 141 </para> 112 142 113 143 <screen role="nodump"><userinput>make install</userinput></screen> … … 118 148 <title>Command Explanations</title> 119 149 120 <para><command>make -C ... && make -C ...</command>: 121 These commands make and install the dynamic library <filename 122 class="libraryfile">libncftp</filename> which is then used to link 123 against when compiling the main program.</para> 150 <para> 151 <command>make -C ... && make -C ...</command>: 152 These commands make and install the dynamic library <filename 153 class="libraryfile">libncftp</filename> which is then used to link 154 against when compiling the main program. 155 </para> 124 156 125 157 </sect2> … … 131 163 <title>Config Files</title> 132 164 133 <para><filename>/etc/ncftp.*</filename> and 134 <filename>~/.ncftp/*</filename>; especially 135 <filename>/etc/ncftp.prefs_v3</filename> and 136 <filename>~/.ncftp/prefs_v3</filename></para> 165 <para> 166 <filename>/etc/ncftp.*</filename> and 167 <filename>~/.ncftp/*</filename>; especially 168 <filename>/etc/ncftp.prefs_v3</filename> and 169 <filename>~/.ncftp/prefs_v3</filename> 170 </para> 137 171 138 172 <indexterm zone="ncftp ncftp-config"> … … 149 183 <title>Configuration Information</title> 150 184 151 <para>Most <application>NcFTP</application> configuration 152 is done while in the program, and the configuration files are dealt with 153 automatically. One exception to this is <filename>~/.ncftp/prefs_v3</filename>. 154 There are various options to alter in there, including:</para> 185 <para> 186 Most <application>NcFTP</application> configuration is done while in 187 the program, and the configuration files are dealt with automatically. 188 One exception to this is <filename>~/.ncftp/prefs_v3</filename>. There 189 are various options to alter in there, including: 190 </para> 155 191 156 192 <screen><literal>yes-i-know-about-NcFTPd=yes</literal></screen> 157 193 158 <para>This disables the splash screen advertising the 159 <application>NcFTPd</application> server.</para> 160 161 <para>There are other options in the <filename>prefs_v3</filename> file. 162 Most of these are self-explanatory. Global defaults can be set in 163 <filename>/etc/ncftp.prefs_v3</filename>.</para> 194 <para> 195 This disables the splash screen advertising the 196 <application>NcFTPd</application> server. 197 </para> 198 199 <para> 200 There are other options in the <filename>prefs_v3</filename> file. 201 Most of these are self-explanatory. Global defaults can be set in 202 <filename>/etc/ncftp.prefs_v3</filename>. 203 </para> 164 204 165 205 </sect3> … … 191 231 <term><command>ncftp</command></term> 192 232 <listitem> 193 <para>is a browser program for File Transfer Protocol.</para> 233 <para> 234 is a browser program for File Transfer Protocol. 235 </para> 194 236 <indexterm zone="ncftp ncftp-prog"> 195 237 <primary sortas="b-ncftp">ncftp</primary> … … 201 243 <term><command>ncftpbatch</command></term> 202 244 <listitem> 203 <para>is an individual batch FTP job processor.</para> 245 <para> 246 is an individual batch FTP job processor. 247 </para> 204 248 <indexterm zone="ncftp ncftpbatch"> 205 249 <primary sortas="b-ncftpbatch">ncftpbatch</primary> … … 211 255 <term><command>ncftpbookmarks</command></term> 212 256 <listitem> 213 <para>is the <application>NcFTP</application> Bookmark Editor 214 (<application>NCurses</application>-based).</para> 257 <para> 258 is the <application>NcFTP</application> Bookmark Editor 259 (<application>NCurses</application>-based). 260 </para> 215 261 <indexterm zone="ncftp ncftpbookmarks"> 216 262 <primary sortas="b-ncftpbookmarks">ncftpbookmarks</primary> … … 222 268 <term><command>ncftpget</command></term> 223 269 <listitem> 224 <para>is an internet file transfer program for scripts used to 225 retrieve files.</para> 270 <para> 271 is an internet file transfer program for scripts used to 272 retrieve files. 273 </para> 226 274 <indexterm zone="ncftp ncftpget"> 227 275 <primary sortas="b-ncftpget">ncftpget</primary> … … 233 281 <term><command>ncftpls</command></term> 234 282 <listitem> 235 <para>is an internet file transfer program for scripts used to 236 list files.</para> 283 <para> 284 is an internet file transfer program for scripts used to 285 list files. 286 </para> 237 287 <indexterm zone="ncftp ncftpls"> 238 288 <primary sortas="b-ncftpls">ncftpls</primary> … … 244 294 <term><command>ncftpput</command></term> 245 295 <listitem> 246 <para>is an internet file transfer program for scripts used to 247 transfer files.</para> 296 <para> 297 is an internet file transfer program for scripts used to 298 transfer files. 299 </para> 248 300 <indexterm zone="ncftp ncftpput"> 249 301 <primary sortas="b-ncftpput">ncftpput</primary> … … 255 307 <term><command>ncftpspooler</command></term> 256 308 <listitem> 257 <para>is a global batch FTP job processor daemon.</para> 309 <para> 310 is a global batch FTP job processor daemon. 311 </para> 258 312 <indexterm zone="ncftp ncftpspooler"> 259 313 <primary sortas="b-ncftpspooler">ncftpspooler</primary> -
networking/netprogs/net-tools.xml
rdcee7a56 rb51fe6e 30 30 <title>Introduction to Net-tools</title> 31 31 32 <para>The <application>Net-tools</application> package is a collection 33 of programs for controlling the network subsystem of the Linux 34 kernel.</para> 32 <para> 33 The <application>Net-tools</application> package is a collection 34 of programs for controlling the network subsystem of the Linux kernel. 35 </para> 35 36 36 37 &lfs91_checked; … … 39 40 <itemizedlist spacing="compact"> 40 41 <listitem> 41 <para>Download (HTTP): <ulink url="&net-tools-download-http;"/></para> 42 </listitem> 43 <listitem> 44 <para>Download (FTP): <ulink url="&net-tools-download-ftp;"/></para> 45 </listitem> 46 <listitem> 47 <para>Download MD5 sum: &net-tools-md5sum;</para> 48 </listitem> 49 <listitem> 50 <para>Download size: &net-tools-size;</para> 51 </listitem> 52 <listitem> 53 <para>Estimated disk space required: &net-tools-buildsize;</para> 54 </listitem> 55 <listitem> 56 <para>Estimated build time: &net-tools-time;</para> 42 <para> 43 Download (HTTP): <ulink url="&net-tools-download-http;"/> 44 </para> 45 </listitem> 46 <listitem> 47 <para> 48 Download (FTP): <ulink url="&net-tools-download-ftp;"/> 49 </para> 50 </listitem> 51 <listitem> 52 <para> 53 Download MD5 sum: &net-tools-md5sum; 54 </para> 55 </listitem> 56 <listitem> 57 <para> 58 Download size: &net-tools-size; 59 </para> 60 </listitem> 61 <listitem> 62 <para> 63 Estimated disk space required: &net-tools-buildsize; 64 </para> 65 </listitem> 66 <listitem> 67 <para> 68 Estimated build time: &net-tools-time; 69 </para> 57 70 </listitem> 58 71 </itemizedlist> … … 77 90 <title>Installation of Net-tools</title> 78 91 79 <para id="net-tools-automate-example" xreflabel="Net-tools">The 80 instructions below automate the configuration process by piping 81 <command>yes</command> to the <command>make config</command> command. If 82 you wish to run the interactive configuration process (by changing the 83 instruction to just <command>make config</command>), but you are not sure 84 how to answer all the questions, then just accept the defaults. This will 85 be just fine in the majority of cases. What you're asked here is a bunch of 86 questions about which network protocols you've enabled in your kernel. The 87 default answers will enable the tools from this package to work with the 88 most common protocols: TCP, PPP, and several others. You still need to 89 actually enable these protocols in the kernel—what you do here is 90 merely tell the package to include support for those protocols in its 91 programs, but it's up to the kernel to make the protocols available.</para> 92 93 <note><para>This package has several unneeded protocols and hardware device 94 specific functions that are obsolete. To only build the minimum needed for 95 your system, skip the <command>yes</command> command and answer each 96 question interactively. The minimum needed options are 'UNIX protocol 97 family' and 'INET (TCP/IP) protocol family'.</para></note> 98 99 <para>The patch below cleans up the installation so that it does not 100 overwrite the <application>ifconfig</application> and 101 <application>hostname</application> programs that were installed in LFS.</para> 102 103 <para>Install <application>Net-tools</application> by running the 104 following commands:</para> 92 <para id="net-tools-automate-example" xreflabel="Net-tools"> 93 The instructions below automate the configuration process by piping 94 <command>yes</command> to the <command>make config</command> command. 95 If you wish to run the interactive configuration process (by changing 96 the instruction to just <command>make config</command>), but you are 97 not sure how to answer all the questions, then just accept the defaults. 98 This will be just fine in the majority of cases. What you're asked here 99 is a bunch of questions about which network protocols you've enabled 100 in your kernel. The default answers will enable the tools from this 101 package to work with the most common protocols: TCP, PPP, and several 102 others. You still need to actually enable these protocols in the 103 kernel—what you do here is merely tell the package to include 104 support for those protocols in its programs, but it's up to the kernel 105 to make the protocols available. 106 </para> 107 108 <note> 109 <para> 110 This package has several unneeded protocols and hardware device 111 specific functions that are obsolete. To only build the minimum needed 112 for your system, skip the <command>yes</command> command and answer 113 each question interactively. The minimum needed options are 'UNIX 114 protocol family' and 'INET (TCP/IP) protocol family'. 115 </para> 116 </note> 117 118 <para> 119 The patch below cleans up the installation so that it does not 120 overwrite the <application>ifconfig</application> and 121 <application>hostname</application> programs that were installed in LFS. 122 </para> 123 124 <para> 125 Install <application>Net-tools</application> by running the 126 following commands: 127 </para> 105 128 106 129 <screen><userinput>patch -Np1 -i ../net-tools-&net-tools-version;-remove_dups-1.patch && … … 110 133 make</userinput></screen> 111 134 112 <para>This package does not come with a test suite.</para> 113 114 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 135 <para> 136 This package does not come with a test suite. 137 </para> 138 139 <para> 140 Now, as the <systemitem class="username">root</systemitem> user: 141 </para> 115 142 116 143 <screen role='root'><userinput>make update</userinput></screen> … … 121 148 <title>Command Explanations</title> 122 149 123 <para><command>sed -i '/#include <netinet\/ip.h>/d' iptunnel.c</command>: 124 This fixes build breakage with linux-4.8 headers.</para> 150 <para> 151 <command>sed -i '/#include <netinet\/ip.h>/d' iptunnel.c</command>: 152 This fixes build breakage with linux-4.8 headers. 153 </para> 125 154 <!-- 126 <para><command>sed -i -e '/Token/s/y$/n/' config.in</command>: Change the 127 default for building obsolete token ring support to no. This is a 128 simpler change than changing the location for the token ring headers. 129 </para> 130 131 <para><command>sed -i -e '/HAVE_HWSTRIP/s/y$/n/' config.in</command>: 132 Removes obsolete Metricom radio support that requires a header no longer 133 included in the kernel. </para> 155 <para> 156 <command>sed -i -e '/Token/s/y$/n/' config.in</command>: Change the 157 default for building obsolete token ring support to no. This is a 158 simpler change than changing the location for the token ring headers. 159 </para> 160 161 <para> 162 <command>sed -i -e '/HAVE_HWSTRIP/s/y$/n/' config.in</command>: 163 Removes obsolete Metricom radio support that requires a header no longer 164 included in the kernel. 165 </para> 134 166 --> 135 <para><command>yes "" | make config</command>: Piping <command>yes</command> 136 to <command>make config</command> skips the interactive configuration and 137 accepts the defaults.</para> 167 <para> 168 <command>yes "" | make config</command>: Piping <command>yes</command> 169 to <command>make config</command> skips the interactive configuration and 170 accepts the defaults. 171 </para> 138 172 139 173 </sect2> … … 165 199 <term><command>arp</command></term> 166 200 <listitem> 167 <para>is used to manipulate the kernel's ARP cache, usually 168 to add or delete an entry, or to dump the entire cache.</para> 201 <para> 202 is used to manipulate the kernel's ARP cache, usually 203 to add or delete an entry, or to dump the entire cache. 204 </para> 169 205 <indexterm zone="net-tools arp"> 170 206 <primary sortas="b-arp">arp</primary> … … 176 212 <term><command>dnsdomainname</command></term> 177 213 <listitem> 178 <para>reports the system's DNS domain name.</para> 214 <para> 215 reports the system's DNS domain name. 216 </para> 179 217 <indexterm zone="net-tools dnsdomainname"> 180 218 <primary sortas="b-dnsdomainname">dnsdomainname</primary> … … 186 224 <term><command>domainname</command></term> 187 225 <listitem> 188 <para>reports or sets the system's NIS/YP domain name.</para> 226 <para> 227 reports or sets the system's NIS/YP domain name. 228 </para> 189 229 <indexterm zone="net-tools domainname"> 190 230 <primary sortas="b-domainname">domainname</primary> … … 196 236 <term><command>hostname</command></term> 197 237 <listitem> 198 <para>reports or sets the name of the current host system.</para> 238 <para> 239 reports or sets the name of the current host system. 240 </para> 199 241 <indexterm zone="net-tools hostname"> 200 242 <primary sortas="b-hostname">hostname</primary> … … 206 248 <term><command>ifconfig</command></term> 207 249 <listitem> 208 <para>is the main utility for configuring network interfaces.</para> 250 <para> 251 is the main utility for configuring network interfaces. 252 </para> 209 253 <indexterm zone="net-tools ifconfig"> 210 254 <primary sortas="b-ifconfig">ifconfig</primary> … … 216 260 <term><command>ipmaddr</command></term> 217 261 <listitem> 218 <para>adds, deletes and shows an interface's multicast addresses.</para> 262 <para> 263 adds, deletes and shows an interface's multicast addresses. 264 </para> 219 265 <indexterm zone="net-tools ipmaddr"> 220 266 <primary sortas="b-ipmaddr">ipmaddr</primary> … … 226 272 <term><command>iptunnel</command></term> 227 273 <listitem> 228 <para>adds, changes, deletes and shows an interface's tunnels.</para> 274 <para> 275 adds, changes, deletes and shows an interface's tunnels. 276 </para> 229 277 <indexterm zone="net-tools iptunnel"> 230 278 <primary sortas="b-iptunnel">iptunnel</primary> … … 236 284 <term><command>mii-tool</command></term> 237 285 <listitem> 238 <para>checks or sets the status of a network interface's Media Independent 239 Interface (MII) unit.</para> 286 <para> 287 checks or sets the status of a network interface's Media 288 Independent Interface (MII) unit. 289 </para> 240 290 <indexterm zone="net-tools mii-tool"> 241 291 <primary sortas="b-mii-tool">mii-tool</primary> … … 247 297 <term><command>nameif</command></term> 248 298 <listitem> 249 <para>names network interfaces based on MAC addresses.</para> 299 <para> 300 names network interfaces based on MAC addresses. 301 </para> 250 302 <indexterm zone="net-tools nameif"> 251 303 <primary sortas="b-nameif">nameif</primary> … … 257 309 <term><command>netstat</command></term> 258 310 <listitem> 259 <para>is used to report network connections, routing tables, and interface 260 statistics.</para> 311 <para> 312 is used to report network connections, routing tables, and 313 interface statistics. 314 </para> 261 315 <indexterm zone="net-tools netstat"> 262 316 <primary sortas="b-netstat">netstat</primary> … … 268 322 <term><command>nisdomainname</command></term> 269 323 <listitem> 270 <para>does the same as <command>domainname</command>.</para> 324 <para> 325 does the same as <command>domainname</command>. 326 </para> 271 327 <indexterm zone="net-tools nisdomainname"> 272 328 <primary sortas="b-nisdomainname">nisdomainname</primary> … … 278 334 <term><command>plipconfig</command></term> 279 335 <listitem> 280 <para>is used to fine tune the PLIP device parameters, to 281 improve its performance.</para> 336 <para> 337 is used to fine tune the PLIP device parameters, to 338 improve its performance. 339 </para> 282 340 <indexterm zone="net-tools plipconfig"> 283 341 <primary sortas="b-plipconfig">plipconfig</primary> … … 289 347 <term><command>rarp</command></term> 290 348 <listitem> 291 <para>is used to manipulate the kernel's RARP table.</para> 349 <para> 350 is used to manipulate the kernel's RARP table. 351 </para> 292 352 <indexterm zone="net-tools rarp"> 293 353 <primary sortas="b-rarp">rarp</primary> … … 299 359 <term><command>route</command></term> 300 360 <listitem> 301 <para>is used to manipulate the IP routing table.</para> 361 <para> 362 is used to manipulate the IP routing table. 363 </para> 302 364 <indexterm zone="net-tools route"> 303 365 <primary sortas="b-route">route</primary> … … 309 371 <term><command>slattach</command></term> 310 372 <listitem> 311 <para>attaches a network interface to a serial line. This allows you to use 312 normal terminal lines for point-to-point links to other computers.</para> 373 <para> 374 attaches a network interface to a serial line. This allows you to 375 use normal terminal lines for point-to-point links to others 376 computers. 377 </para> 313 378 <indexterm zone="net-tools slattach"> 314 379 <primary sortas="b-slattach">slattach</primary> … … 320 385 <term><command>ypdomainname</command></term> 321 386 <listitem> 322 <para>does the same as <command>domainname</command>.</para> 387 <para> 388 does the same as <command>domainname</command>. 389 </para> 323 390 <indexterm zone="net-tools ypdomainname"> 324 391 <primary sortas="b-ypdomainname">ypdomainname</primary> -
networking/netprogs/netfs.xml
rdcee7a56 rb51fe6e 21 21 </indexterm> 22 22 23 <para>While LFS is capable of mounting network file systems such as NFS, 24 these are not mounted by the <filename>mountfs</filename> init script. 25 Network file systems must be mounted after the networking is activated and 26 unmounted before the network goes down. The <filename>netfs</filename> 27 bootscript was written to handle both boot-time mounting of network 28 filesystems, if the entry in <filename>/etc/fstab</filename> contains the 29 <option>_netdev</option> option, and unmounting of all network filesystems 30 before the network is brought down.</para> 23 <para> 24 While LFS is capable of mounting network file systems such as NFS, 25 these are not mounted by the <filename>mountfs</filename> init script. 26 Network file systems must be mounted after the networking is activated and 27 unmounted before the network goes down. The <filename>netfs</filename> 28 bootscript was written to handle both boot-time mounting of network 29 filesystems, if the entry in <filename>/etc/fstab</filename> contains the 30 <option>_netdev</option> option, and unmounting of all network filesystems 31 before the network is brought down. 32 </para> 31 33 32 <para>As the <systemitem class="username">root</systemitem> user, install 33 the <filename>/etc/rc.d/init.d/netfs</filename> bootscript included with the 34 <xref linkend="bootscripts"/> package.</para> 34 <para> 35 As the <systemitem class="username">root</systemitem> user, install the 36 <filename>/etc/rc.d/init.d/netfs</filename> bootscript included with the 37 <xref linkend="bootscripts"/> package. 38 </para> 35 39 36 40 <screen role='root'><userinput>make install-netfs</userinput></screen> -
networking/netprogs/netprogs.xml
rdcee7a56 rb51fe6e 16 16 <title>Networking Programs</title> 17 17 18 <para>These applications are generally client applications used to 19 access the appropriate server across the building or across the world. 20 <application>Tcpwrappers</application> and <application>portmap</application> 21 are support programs for daemons that you may have running on your machine.</para> 18 <para> 19 These applications are generally client applications used to 20 access the appropriate server across the building or across the world. 21 <application>Tcpwrappers</application> and 22 <application>portmap</application> are support programs for daemons that 23 you may have running on your machine. 24 </para> 22 25 23 26 <xi:include xmlns:xi="http://www.w3.org/2001/XInclude" href="bridgeutils.xml"/> -
networking/netprogs/nfs-utils.xml
rdcee7a56 rb51fe6e 31 31 <title>Introduction to NFS Utilities</title> 32 32 33 <para>The <application>NFS Utilities</application> package contains the 34 userspace server and client tools necessary to use the kernel's NFS 35 abilities. NFS is a protocol that allows sharing file systems over the 36 network.</para> 33 <para> 34 The <application>NFS Utilities</application> package contains the 35 userspace server and client tools necessary to use the kernel's NFS 36 abilities. NFS is a protocol that allows sharing file systems over the 37 network. 38 </para> 37 39 38 40 &lfs91_checked; … … 41 43 <itemizedlist spacing='compact'> 42 44 <listitem> 43 <para>Download (HTTP): <ulink url="&nfs-utils-download-http;"/></para> 45 <para> 46 Download (HTTP): <ulink url="&nfs-utils-download-http;"/> 47 </para> 44 48 </listitem> 45 49 <listitem> 46 <para>Download (FTP): <ulink url="&nfs-utils-download-ftp;"/></para> 50 <para> 51 Download (FTP): <ulink url="&nfs-utils-download-ftp;"/> 52 </para> 47 53 </listitem> 48 54 <listitem> 49 <para>Download MD5 sum: &nfs-utils-md5sum;</para> 55 <para> 56 Download MD5 sum: &nfs-utils-md5sum; 57 </para> 50 58 </listitem> 51 59 <listitem> 52 <para>Download size: &nfs-utils-size;</para> 60 <para> 61 Download size: &nfs-utils-size; 62 </para> 53 63 </listitem> 54 64 <listitem> 55 <para>Estimated disk space required: &nfs-utils-buildsize;</para> 65 <para> 66 Estimated disk space required: &nfs-utils-buildsize; 67 </para> 56 68 </listitem> 57 69 <listitem> 58 <para>Estimated build time: &nfs-utils-time;</para> 70 <para> 71 Estimated build time: &nfs-utils-time; 72 </para> 59 73 </listitem> 60 74 </itemizedlist> … … 75 89 <xref linkend="sqlite"/>, 76 90 <xref linkend="mitkrb"/> or 77 <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/">libgssapi</ulink>, and 78 <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/">librpcsecgss</ulink> (for GSS and RPC security support) and 79 91 <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/"> 92 libgssapi 93 </ulink>, and 94 <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/"> 95 librpcsecgss 96 </ulink> (for GSS and RPC security support), and 80 97 <xref linkend="libcap-pam"/> 81 98 </para> … … 103 120 <title>Kernel Configuration</title> 104 121 105 <para>Enable the following options in the kernel configuration 106 (choose client and/or server support as appropriate) and recompile the 107 kernel if necessary:</para> 122 <para> 123 Enable the following options in the kernel configuration 124 (choose client and/or server support as appropriate) and recompile the 125 kernel if necessary: 126 </para> 108 127 109 128 <screen><literal>File systems ---> … … 112 131 <*/M> NFS server support [CONFIG_NFSD]</literal></screen> 113 132 114 <para>Select the appropriate sub-options that appear when the above options 115 are selected.</para> 133 <para> 134 Select the appropriate sub-options that appear when the above options 135 are selected. 136 </para> 116 137 117 138 <note> … … 142 163 <title>Installation of NFS Utilities</title> 143 164 144 <para>Before you compile the program, ensure that the <systemitem 145 class="username">nobody</systemitem> user and <systemitem 146 class="groupname">nogroup</systemitem> group have been created as done in 147 the current LFS book. You can add them by running the following commands 148 as the <systemitem class="username">root</systemitem> user:</para> 165 <para> 166 Before you compile the program, ensure that the <systemitem 167 class="username">nobody</systemitem> user and <systemitem 168 class="groupname">nogroup</systemitem> group have been created as done in 169 the current LFS book. You can add them by running the following commands 170 as the <systemitem class="username">root</systemitem> user: 171 </para> 149 172 150 173 <screen role="nodump"><userinput>groupadd -g 99 nogroup && … … 153 176 154 177 <note> 155 <para>The classic uid and gid values are 65534 which is also -2 when 156 interpreted as a signed 16-bit number. These values impact other files 157 on some filesystems that do not have support for sparse files. The 158 <systemitem class="username">nobody</systemitem> and <systemitem 159 class="groupname">nogroup</systemitem> values are relatively arbitrary. 160 The impact on a server is nil if the <filename>exports</filename> file 161 is configured correctly. If it is misconfigured, an 162 <command>ls -l</command> or <command>ps</command> listing will show a 163 uid or gid number of 65534 instead of a name. The client uses <systemitem 164 class="username">nobody</systemitem> only as the user running 165 <command>rpc.statd</command>.</para> 178 <para> 179 The classic uid and gid values are 65534 which is also -2 when 180 interpreted as a signed 16-bit number. These values impact other files 181 on some filesystems that do not have support for sparse files. The 182 <systemitem class="username">nobody</systemitem> and <systemitem 183 class="groupname">nogroup</systemitem> values are relatively arbitrary. 184 The impact on a server is nil if the <filename>exports</filename> file 185 is configured correctly. If it is misconfigured, an 186 <command>ls -l</command> or <command>ps</command> listing will show a 187 uid or gid number of 65534 instead of a name. The client uses 188 <systemitem class="username">nobody</systemitem> only as the user 189 running <command>rpc.statd</command>. 190 </para> 166 191 </note> 167 192 168 <para>Install <application>NFS Utilities</application> by running 169 the following commands:</para> 193 <para> 194 Install <application>NFS Utilities</application> by running 195 the following commands: 196 </para> 170 197 171 198 <screen><userinput>./configure --prefix=/usr \ … … 178 205 <!-- Test breakage: see 179 206 http://lists.linuxfromscratch.org/pipermail/blfs-book/2017-December/071861.html --> 180 <para>This package does not come with a working test suite.</para> 181 182 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 207 <para> 208 This package does not come with a working test suite. 209 </para> 210 211 <para> 212 Now, as the <systemitem class="username">root</systemitem> user: 213 </para> 183 214 184 215 <!-- dev note: make statduser=$(whoami) DESTDIR=<DESTDIR> install --> … … 190 221 191 222 <!-- commented, in case the tests get fixed 192 <para>The tests for this package require that the package be installed and 193 configured as specified below. In addition, the daemon from <xref 194 linkend="rpcbind"/> needs to be running and the tests need to be run as the 195 <systemitem class="username">root</systemitem> user.</para> 196 197 <para>To test the results, issue, as root: <command>make check</command>.</para>--> 223 <para> 224 The tests for this package require that the package be installed and 225 configured as specified below. In addition, the daemon from <xref 226 linkend="rpcbind"/> needs to be running and the tests need to be run as 227 the <systemitem class="username">root</systemitem> user. 228 </para> 229 230 <para> 231 To test the results, issue, as root: <command>make check</command>. 232 </para>--> 198 233 199 234 </sect2> … … 202 237 <title>Command Explanations</title> 203 238 <!-- 204 <para><command>sed ... support/nsm/rpc.c</command>: This sed it required 205 to fix a build issue with glibc-2.26 and later.</para> 239 <para> 240 <command>sed ... support/nsm/rpc.c</command>: This sed it required 241 to fix a build issue with glibc-2.26 and later. 242 </para> 206 243 --> 207 <para><parameter>--disable-nfsv4</parameter>: This allows the package to be 208 built when libnfsidmap has not been installed.</para> 209 210 <para><parameter>--disable-gss</parameter>: Disables support for 211 RPCSEC GSS (RPC Security).</para> 212 213 <para><command>chown nobody.nogroup /var/lib/nfs</command>: The 214 rpc.statd program uses the ownership of this directory to set 215 it's UID and GID. This command sets those to unprivileged entries. 244 <para> 245 <parameter>--disable-nfsv4</parameter>: This allows the package to be 246 built when libnfsidmap has not been installed. 247 </para> 248 249 <para> 250 <parameter>--disable-gss</parameter>: Disables support for 251 RPCSEC GSS (RPC Security). 252 </para> 253 254 <para> 255 <command>chown nobody.nogroup /var/lib/nfs</command>: The 256 rpc.statd program uses the ownership of this directory to set 257 it's UID and GID. This command sets those to unprivileged entries. 216 258 </para> 217 259 … … 224 266 <title>Server Configuration</title> 225 267 226 <para><filename>/etc/exports</filename> contains the exported directories 227 on NFS servers. Refer to the <filename>exports.5</filename> manual page 228 for the syntax of this file. Also refer to the "NFS HowTo" available at 229 <ulink url="http://nfs.sourceforge.net/nfs-howto/"/> for information on 230 how to configure the servers and clients in a secure manner. For example, 231 for sharing the <filename class="directory">/home</filename> directory 232 over the local network, the following line may be added:</para> 268 <para> 269 <filename>/etc/exports</filename> contains the exported directories 270 on NFS servers. Refer to the <filename>exports.5</filename> manual page 271 for the syntax of this file. Also refer to the "NFS HowTo" available at 272 <ulink url="http://nfs.sourceforge.net/nfs-howto/"/> for information on 273 how to configure the servers and clients in a secure manner. For 274 example, for sharing the <filename class="directory">/home</filename> 275 directory over the local network, the following line may be added: 276 </para> 233 277 234 278 <screen role="nodump"><userinput>cat >> /etc/exports << EOF … … 236 280 EOF</userinput></screen> 237 281 238 <note><para>Be sure to replace the directory, network address. and prefix above 239 to match your network. The only space in the line above should be between 240 the directory and the network address.</para></note> 282 <note> 283 <para> 284 Be sure to replace the directory, network address. and prefix above 285 to match your network. The only space in the line above should be 286 between the directory and the network address. 287 </para> 288 </note> 241 289 242 290 <indexterm zone="nfs-utils nfs-utils-server-config"> … … 248 296 <phrase revision="systemd">Systemd Units</phrase></title> 249 297 250 <para>Install the 251 <phrase revision="sysv"><filename>/etc/rc.d/init.d/nfs-server</filename> 252 init script</phrase> 253 <phrase revision="systemd">NFSv4 server units</phrase> 254 included in the <xref linkend="bootscripts" revision="sysv"/> 255 <xref linkend="systemd-units" revision="systemd"/> package 256 to start the server at boot.</para> 298 <para> 299 Install the 300 <phrase revision="sysv"> 301 <filename>/etc/rc.d/init.d/nfs-server</filename> 302 init script 303 </phrase> 304 <phrase revision="systemd">NFSv4 server units</phrase> 305 included in the <xref linkend="bootscripts" revision="sysv"/> 306 <xref linkend="systemd-units" revision="systemd"/> package 307 to start the server at boot. 308 </para> 257 309 258 310 <screen role="root" revision="systemd"><userinput>make install-nfsv4-server</userinput></screen> … … 271 323 </indexterm> 272 324 273 <para revision="sysv">Now create the 325 <para revision="sysv"> 326 Now create the 274 327 <filename>/etc/sysconfig/nfs-server</filename> configuration file: 275 328 </para> … … 282 335 283 336 <note revision="sysv"> 284 <para>The above parameters may be optionally placed in 337 <para> 338 The above parameters may be optionally placed in 285 339 <filename>/etc/sysconfig/rc.site</filename>. 286 340 </para> … … 302 356 </indexterm> 303 357 304 305 306 358 </sect4> 307 359 … … 311 363 <title>Client Configuration</title> 312 364 313 <para><filename>/etc/fstab</filename> contains the directories that 314 are to be mounted on the client. Alternately the partitions can be 315 mounted by using the <command>mount</command> command with the proper 316 options. To mount the <filename class="directory">/home</filename> 317 and <filename class="directory">/usr</filename> partitions, add the 318 following to the <filename>/etc/fstab</filename>:</para> 365 <para> 366 <filename>/etc/fstab</filename> contains the directories that 367 are to be mounted on the client. Alternately the partitions can be 368 mounted by using the <command>mount</command> command with the proper 369 options. To mount the <filename class="directory">/home</filename> 370 and <filename class="directory">/usr</filename> partitions, add the 371 following to the <filename>/etc/fstab</filename>: 372 </para> 319 373 320 374 <screen role="nodump"><userinput><replaceable><server-name></replaceable>:/home /home nfs rw,_netdev 0 0 321 375 <replaceable><server-name></replaceable>:/usr /usr nfs ro,_netdev 0 0</userinput></screen> 322 376 323 <para>The options which can be used are specified in <command>man 5 nfs</command>. 324 If both the client and server are running recent versions of linux, most of the 325 options will be negotiated (but see the Note above on nfsver=3). You can specify 326 either <literal>rw</literal> or 327 <literal>ro</literal>, <literal>_netdev</literal> if the filesystem is to be 328 automatically mounted at boot, or <literal>noauto</literal> (and perhaps 329 <literal>user</literal>) for other filesystems.</para> 330 331 <para>If the fileserver is not running a recent version of linux, you may need to 332 specifiy other options.</para> 333 334 <para>If you are using systemd, you may need to enable autofs v4 in your kernel, 335 and add the option <literal>comment=systemd.automount</literal>. Some machines 336 need this, because systemd tries to mount the external fs's before the network 337 is up, others do not need it. An alternative is for <systemitem 338 class="username">root</systemitem> to run <command>mount -a</command>.</para> 377 <para> 378 The options which can be used are specified in <command>man 5 nfs 379 </command>. If both the client and server are running recent versions 380 of linux, most of the options will be negotiated (but see the Note 381 above on nfsver=3). You can specify either <literal>rw</literal> or 382 <literal>ro</literal>, <literal>_netdev</literal> if the filesystem is 383 to be automatically mounted at boot, or <literal>noauto</literal> (and 384 perhaps <literal>user</literal>) for other filesystems. 385 </para> 386 387 <para> 388 If the fileserver is not running a recent version of linux, you may 389 need to specifiy other options. 390 </para> 391 392 <para revision="systemd"> 393 You may need to enable autofs v4 in your kernel, and add the option 394 <literal>comment=systemd.automount</literal>. Some machines need this, 395 because systemd tries to mount the external fs's before the 396 network is up, others do not need it. An alternative is for 397 <systemitem class="username">root</systemitem> to run 398 <command>mount -a</command>. 399 </para> 339 400 340 401 <indexterm zone="nfs-utils nfs-utils-client-config"> … … 355 416 </note> 356 417 357 <para>Install the 358 <phrase revision="sysv"> 359 <filename>/etc/rc.d/init.d/nfs-client</filename> init script</phrase> 360 <phrase revision="systemd">units</phrase> included in the 361 <xref linkend="bootscripts" revision="sysv"/> 362 <xref linkend="systemd-units" revision="systemd"/> package to start 363 the client services at boot.</para> 418 <para> 419 Install the 420 <phrase revision="sysv"> 421 <filename>/etc/rc.d/init.d/nfs-client</filename> init script 422 </phrase> 423 <phrase revision="systemd">units</phrase> included in the 424 <xref linkend="bootscripts" revision="sysv"/> 425 <xref linkend="systemd-units" revision="systemd"/> package to start 426 the client services at boot. 427 </para> 364 428 365 429 <screen role="root"><userinput>make install-nfs-client</userinput></screen> … … 369 433 </indexterm> 370 434 371 <para revision="sysv">To automatically mount <systemitem 372 class="filesystem">nfs</systemitem> filesystems, clients will also need 373 to install the <filename>netfs</filename> bootscript as described in 374 <xref linkend="postlfs-config-netfs"/>.</para> 435 <para revision="sysv"> 436 To automatically mount <systemitem class="filesystem">nfs 437 </systemitem> filesystems, clients will also need to install the 438 <filename>netfs</filename> bootscript as described in <xref 439 linkend="postlfs-config-netfs"/>. 440 </para> 375 441 376 442 <indexterm zone="nfs-utils nfs-utils-client-config" revision="sysv"> … … 409 475 <term><command>exportfs</command></term> 410 476 <listitem> 411 <para>maintains a list of NFS exported file systems.</para> 477 <para> 478 maintains a list of NFS exported file systems. 479 </para> 412 480 <indexterm zone="nfs-utils exportfs"> 413 481 <primary sortas="b-exportfs">exportfs</primary> … … 419 487 <term><command>mountstats</command></term> 420 488 <listitem> 421 <para>displays NFS client per-mount statistics.</para> 489 <para> 490 displays NFS client per-mount statistics. 491 </para> 422 492 <indexterm zone="nfs-utils mountstats"> 423 493 <primary sortas="b-mountstats">mountstats</primary> … … 429 499 <term><command>mount.nfs</command></term> 430 500 <listitem> 431 <para>is used to mount a network share using NFS</para> 501 <para> 502 is used to mount a network share using NFS. 503 </para> 432 504 <indexterm zone="nfs-utils mount.nfs"> 433 505 <primary sortas="b-mount.nfs">mount.nfs</primary> … … 439 511 <term><command>mount.nfs4</command></term> 440 512 <listitem> 441 <para>is used to mount a network share using NFSv4</para> 513 <para> 514 is used to mount a network share using NFSv4. 515 </para> 442 516 <indexterm zone="nfs-utils mount.nfs4"> 443 517 <primary sortas="b-mount.nfs4">mount.nfs4</primary> … … 449 523 <term><command>nfsconf</command></term> 450 524 <listitem> 451 <para>can be used to test for and retrieve configuration settings from 452 a range of nfs-utils configuration files.</para> 525 <para> 526 can be used to test for and retrieve configuration settings from 527 a range of nfs-utils configuration files. 528 </para> 453 529 <indexterm zone="nfs-utils nfsconf"> 454 530 <primary sortas="b-nfsconf">nfsconf</primary> … … 460 536 <term><command>nfsiostat</command></term> 461 537 <listitem> 462 <para>reports input/output statistics for network filesystems.</para> 538 <para> 539 reports input/output statistics for network filesystems. 540 </para> 463 541 <indexterm zone="nfs-utils nfsiostat-nfs-utils"> 464 542 <primary sortas="b-nfsiostat-nfs-utils">nfsiostat</primary> … … 470 548 <term><command>nfsstat</command></term> 471 549 <listitem> 472 <para>displays statistics kept about NFS client and server activity.</para> 550 <para> 551 displays statistics kept about NFS client and server activity. 552 </para> 473 553 <indexterm zone="nfs-utils nfsstat"> 474 554 <primary sortas="b-nfsstat">nfsstat</primary> … … 481 561 <term><command>osd_login</command></term> 482 562 <listitem> 483 <para>is a script that is a part of the autologin feature 484 mandated by the pnfs-objects standard.</para> 563 <para> 564 is a script that is a part of the autologin feature 565 mandated by the pnfs-objects standard. 566 </para> 485 567 <indexterm zone="nfs-utils osd_login"> 486 568 <primary sortas="b-osd_login">osd_login</primary> … … 493 575 <term><command>rpc.mountd</command></term> 494 576 <listitem> 495 <para>implements the NFS mount protocol on an NFS server.</para> 577 <para> 578 implements the NFS mount protocol on an NFS server. 579 </para> 496 580 <indexterm zone="nfs-utils rpc.mountd"> 497 581 <primary sortas="b-rpc.mountd">rpc.mountd</primary> … … 503 587 <term><command>rpc.nfsd</command></term> 504 588 <listitem> 505 <para>implements the user level part of the NFS 506 service on the server.</para> 589 <para> 590 implements the user level part of the NFS 591 service on the server. 592 </para> 507 593 <indexterm zone="nfs-utils rpc.nfsd"> 508 594 <primary sortas="b-rpc.nfsd">rpc.nfsd</primary> … … 514 600 <term><command>rpc.statd</command></term> 515 601 <listitem> 516 <para>is used by the NFS file locking service. Run on both sides, 517 client as well as server, when you want file locking enabled.</para> 602 <para> 603 is used by the NFS file locking service. Run on both sides, 604 client as well as server, when you want file locking enabled. 605 </para> 518 606 <indexterm zone="nfs-utils rpc.statd"> 519 607 <primary sortas="b-rpc.statd">rpc.statd</primary> … … 525 613 <term><command>rpcdebug</command></term> 526 614 <listitem> 527 <para>sets or clears the kernel's NFS client and server debug 528 flags.</para> 615 <para> 616 sets or clears the kernel's NFS client and server debug flags. 617 </para> 529 618 <indexterm zone="nfs-utils rpcdebug"> 530 619 <primary sortas="b-rpcdebug">rpcdebug</primary> … … 536 625 <term><command>showmount</command></term> 537 626 <listitem> 538 <para>displays mount information for an NFS server.</para> 627 <para> 628 displays mount information for an NFS server. 629 </para> 539 630 <indexterm zone="nfs-utils showmount"> 540 631 <primary sortas="b-showmount">showmount</primary> … … 546 637 <term><command>sm-notify</command></term> 547 638 <listitem> 548 <para>is used to send Network Status Monitor reboot messages.</para> 639 <para> 640 is used to send Network Status Monitor reboot messages. 641 </para> 549 642 <indexterm zone="nfs-utils sm-notify"> 550 643 <primary sortas="b-sm-notify">sm-notify</primary> … … 556 649 <term><command>start-statd</command></term> 557 650 <listitem> 558 <para>is a script called by nfsmount when mounting a filesystem with 559 locking enabled, if statd does not appear to be running. It can be 560 customised with whatever flags are appropriate for the site.</para> 651 <para> 652 is a script called by nfsmount when mounting a filesystem with 653 locking enabled, if statd does not appear to be running. It can be 654 customised with whatever flags are appropriate for the site. 655 </para> 561 656 <indexterm zone="nfs-utils start-statd"> 562 657 <primary sortas="b-start-statd">start-statd</primary> … … 568 663 <term><command>umount.nfs</command></term> 569 664 <listitem> 570 <para>is used to unmount a network share using NFS</para> 665 <para> 666 is used to unmount a network share using NFS. 667 </para> 571 668 <indexterm zone="nfs-utils umount.nfs"> 572 669 <primary sortas="b-umount.nfs">umount.nfs</primary> … … 578 675 <term><command>umount.nfs4</command></term> 579 676 <listitem> 580 <para>is used to unmount a network share using NFSv4</para> 677 <para> 678 is used to unmount a network share using NFSv4. 679 </para> 581 680 <indexterm zone="nfs-utils umount.nfs4"> 582 681 <primary sortas="b-umount.nfs4">umount.nfs4</primary> -
networking/netprogs/ntp.xml
rdcee7a56 rb51fe6e 30 30 <title>Introduction to ntp</title> 31 31 32 <para>The <application>ntp</application> package contains a 33 client and server to keep the time synchronized between various computers over 34 a network. This package is the official reference implementation of the 35 NTP protocol.</para> 32 <para> 33 The <application>ntp</application> package contains a client and server 34 to keep the time synchronized between various computers over 35 a network. This package is the official reference implementation of the 36 NTP protocol. 37 </para> 36 38 37 39 &lfs91_checked; … … 40 42 <itemizedlist spacing="compact"> 41 43 <listitem> 42 <para>Download (HTTP): <ulink url="&ntp-download-http;"/></para> 43 </listitem> 44 <listitem> 45 <para>Download (FTP): <ulink url="&ntp-download-ftp;"/></para> 46 </listitem> 47 <listitem> 48 <para>Download MD5 sum: &ntp-md5sum;</para> 49 </listitem> 50 <listitem> 51 <para>Download size: &ntp-size;</para> 52 </listitem> 53 <listitem> 54 <para>Estimated disk space required: &ntp-buildsize;</para> 55 </listitem> 56 <listitem> 57 <para>Estimated build time: &ntp-time;</para> 44 <para> 45 Download (HTTP): <ulink url="&ntp-download-http;"/> 46 </para> 47 </listitem> 48 <listitem> 49 <para> 50 Download (FTP): <ulink url="&ntp-download-ftp;"/> 51 </para> 52 </listitem> 53 <listitem> 54 <para> 55 Download MD5 sum: &ntp-md5sum; 56 </para> 57 </listitem> 58 <listitem> 59 <para> 60 Download size: &ntp-size; 61 </para> 62 </listitem> 63 <listitem> 64 <para> 65 Estimated disk space required: &ntp-buildsize; 66 </para> 67 </listitem> 68 <listitem> 69 <para> 70 Estimated build time: &ntp-time; 71 </para> 58 72 </listitem> 59 73 </itemizedlist> … … 72 86 <command>update-leap</command>) 73 87 <!- - The download code for update-leap uses the File::Fetch perl module, 74 which may use wget, or lynx, or some core perl modules, so maybe move75 to optional - ->88 which may use wget, or lynx, or some core perl modules, so maybe move 89 to optional - -> 76 90 </para> 77 91 --> … … 143 157 <title>Command Explanations</title> 144 158 145 <para><envar>CFLAGS="-O2 -g -fPIC"</envar>: This environment variable 146 is necessary to generate Position Independent Code needed for 147 use in the package libraries.</para> 148 149 <para><parameter>--bindir=/usr/sbin</parameter>: This parameter places 150 the administrative programs in <filename 151 class="directory">/usr/sbin</filename>.</para> 152 153 <para><parameter>--enable-linuxcaps</parameter>: ntpd is run as user 154 ntp, so use Linux capabilities for non-root clock control.</para> 155 156 <para><parameter>--with-lineeditlibs=readline</parameter>: This switch 157 enables <application>Readline</application> support for 158 <command>ntpdc</command> and <command>ntpq</command> programs. If omitted, 159 <application>libedit</application> will be used if installed, otherwise no 160 readline capabilites will be compiled.</para> 159 <para> 160 <envar>CFLAGS="-O2 -g -fPIC"</envar>: This environment variable 161 is necessary to generate Position Independent Code needed for 162 use in the package libraries. 163 </para> 164 165 <para> 166 <parameter>--bindir=/usr/sbin</parameter>: This parameter places 167 the administrative programs in <filename 168 class="directory">/usr/sbin</filename>. 169 </para> 170 171 <para> 172 <parameter>--enable-linuxcaps</parameter>: ntpd is run as user 173 ntp, so use Linux capabilities for non-root clock control. 174 </para> 175 176 <para> 177 <parameter>--with-lineeditlibs=readline</parameter>: This switch 178 enables <application>Readline</application> support for 179 <command>ntpdc</command> and <command>ntpq</command> programs. If omitted, 180 <application>libedit</application> will be used if installed, otherwise no 181 readline capabilites will be compiled. 182 </para> 161 183 162 184 </sect2> … … 168 190 <title>Config Files</title> 169 191 170 <para><filename>/etc/ntp.conf</filename></para> 192 <para> 193 <filename>/etc/ntp.conf</filename> 194 </para> 171 195 172 196 <indexterm zone="ntp ntp-config"> … … 179 203 <title>Configuration Information</title> 180 204 181 <para>The following configuration file first defines various ntp 182 servers with open access from different continents. Second, it 183 creates a drift file where <command>ntpd</command> stores the 184 frequency offset and a pid file to store the 185 <command>ntpd</command> process ID. Third, it defines the location 186 for the leap-second definition file 187 <filename>/etc/ntp.leapseconds</filename>, that the 188 <command>update-leap</command> script checks and updates, when 189 necessary. This script can be run as a cron job and the 190 <application>ntp</application> developers recommend a frequency of 191 about three weeks for the updates. Since the documentation included 192 with the package is sparse, visit the ntp website at 193 <ulink url="http://www.ntp.org/"/> and 194 <ulink url="http://www.pool.ntp.org/"/> for more information.</para> 205 <para> 206 The following configuration file first defines various ntp 207 servers with open access from different continents. Second, it 208 creates a drift file where <command>ntpd</command> stores the 209 frequency offset and a pid file to store the 210 <command>ntpd</command> process ID. Third, it defines the location 211 for the leap-second definition file 212 <filename>/etc/ntp.leapseconds</filename>, that the 213 <command>update-leap</command> script checks and updates, when 214 necessary. This script can be run as a cron job and the 215 <application>ntp</application> developers recommend a frequency of 216 about three weeks for the updates. Since the documentation included 217 with the package is sparse, visit the ntp website at 218 <ulink url="http://www.ntp.org/"/> and 219 <ulink url="http://www.pool.ntp.org/"/> for more information. 220 </para> 195 221 196 222 <screen role="root"><userinput>cat > /etc/ntp.conf << "EOF" … … 218 244 <para> 219 245 You may wish to add a <quote>Security session</quote>. For 220 explanations, see 221 <ulink url="https://www.eecis.udel.edu/~mills/ntp/html/accopt.html#restrict"/>.246 explanations, see <ulink url= 247 "https://www.eecis.udel.edu/~mills/ntp/html/accopt.html#restrict"/>. 222 248 </para> 223 249 … … 236 262 <title>Synchronizing the Time</title> 237 263 238 <para>There are two options. Option one is to run <command>ntpd</command> 239 continuously and allow it to synchronize the time in a gradual manner. The 240 other option is to run <command>ntpd</command> periodically (using cron) 241 and update the time each time <command>ntpd</command> is scheduled.</para> 242 243 <para>If you choose Option one, then install the 244 <phrase revision="sysv"><filename>/etc/rc.d/init.d/ntp</filename> 245 init script</phrase> 246 <phrase revision="systemd"><filename>ntpd.service</filename> unit</phrase> 247 included in the 248 <xref linkend="bootscripts" revision="sysv"/> 249 <xref linkend="systemd-units" revision="systemd"/> package.</para> 264 <para> 265 There are two options. Option one is to run <command>ntpd</command> 266 continuously and allow it to synchronize the time in a gradual manner. 267 The other option is to run <command>ntpd</command> periodically (using 268 cron) and update the time each time <command>ntpd</command> is 269 scheduled. 270 </para> 271 272 <para> 273 If you choose Option one, then install the 274 <phrase revision="sysv"><filename>/etc/rc.d/init.d/ntp</filename> 275 init script</phrase> 276 <phrase revision="systemd"><filename>ntpd.service</filename> 277 unit</phrase> 278 included in the 279 <xref linkend="bootscripts" revision="sysv"/> 280 <xref linkend="systemd-units" revision="systemd"/> package. 281 </para> 250 282 251 283 <indexterm zone="ntp ntp-init" revision="sysv"> … … 259 291 <screen role="root"><userinput>make install-ntpd</userinput></screen> 260 292 261 <para>If you prefer to run <command>ntpd</command> periodically, add the 262 following command to <systemitem class="username">root</systemitem>'s 263 <filename>crontab</filename>:</para> 293 <para> 294 If you prefer to run <command>ntpd</command> periodically, add the 295 following command to <systemitem class="username">root</systemitem>'s 296 <filename>crontab</filename>: 297 </para> 264 298 265 299 <screen><literal>ntpd -q</literal></screen> 266 300 267 <para revision="sysv">Execute the following command if you would like to 268 set the hardware clock to the current system time at shutdown and 269 reboot:</para> 301 <para revision="sysv"> 302 Execute the following command if you would like to set the hardware 303 clock to the current system time at shutdown and reboot: 304 </para> 270 305 271 306 <screen role="root" revision="sysv"><userinput>ln -v -sf ../init.d/setclock /etc/rc.d/rc0.d/K46setclock && 272 307 ln -v -sf ../init.d/setclock /etc/rc.d/rc6.d/K46setclock</userinput></screen> 273 308 274 <para revision="sysv">The other way around is already set up by 275 LFS.</para> 309 <para revision="sysv"> 310 The other way around is already set up by LFS. 311 </para> 276 312 277 313 </sect3> … … 305 341 <term><command>calc_tickadj</command></term> 306 342 <listitem> 307 <para>calculates optimal value for tick given ntp drift file.</para> 343 <para> 344 calculates optimal value for tick given ntp drift file. 345 </para> 308 346 <indexterm zone="ntp calc_tickadj"> 309 347 <primary sortas="b-calc_tickadj">calc_tickadj</primary> … … 315 353 <term><command>ntp-keygen</command></term> 316 354 <listitem> 317 <para>generates cryptographic data files used by the NTPv4 authentication 318 and identification schemes.</para> 355 <para> 356 generates cryptographic data files used by the NTPv4 authentication 357 and identification schemes. 358 </para> 319 359 <indexterm zone="ntp ntp-keygen"> 320 360 <primary sortas="b-ntp-keygen">ntp-keygen</primary> … … 326 366 <term><command>ntp-wait</command></term> 327 367 <listitem> 328 <para>is useful at boot time, to delay the boot sequence until 329 <command>ntpd</command> has set the time.</para> 368 <para> 369 is useful at boot time, to delay the boot sequence until 370 <command>ntpd</command> has set the time. 371 </para> 330 372 <indexterm zone="ntp ntp-wait"> 331 373 <primary sortas="b-ntp-wait">ntp-wait</primary> … … 337 379 <term><command>ntpd</command></term> 338 380 <listitem> 339 <para>is a ntp daemon that runs in the background and keeps 340 the date and time synchronized based on response from configured 341 ntp servers. It also functions as a ntp server.</para> 381 <para> 382 is a ntp daemon that runs in the background and keeps 383 the date and time synchronized based on response from configured 384 ntp servers. It also functions as a ntp server. 385 </para> 342 386 <indexterm zone="ntp ntpd"> 343 387 <primary sortas="b-ntpd">ntpd</primary> … … 349 393 <term><command>ntpdate</command></term> 350 394 <listitem> 351 <para>is a client program that sets the date and time based on 352 the response from an ntp server. This command is deprecated.</para> 395 <para> 396 is a client program that sets the date and time based on 397 the response from an ntp server. This command is deprecated. 398 </para> 353 399 <indexterm zone="ntp ntpdate"> 354 400 <primary sortas="b-ntpdate">ntpdate</primary> … … 360 406 <term><command>ntpdc</command></term> 361 407 <listitem> 362 <para>is used to query the ntp daemon about its current state 363 and to request changes in that state.</para> 408 <para> 409 is used to query the ntp daemon about its current state 410 and to request changes in that state. 411 </para> 364 412 <indexterm zone="ntp ntpdc"> 365 413 <primary sortas="b-ntpdc">ntpdc</primary> … … 371 419 <term><command>ntpq</command></term> 372 420 <listitem> 373 <para>is a utility program used to monitor <command>ntpd</command> 374 operations and determine performance.</para> 421 <para> 422 is a utility program used to monitor <command>ntpd</command> 423 operations and determine performance. 424 </para> 375 425 <indexterm zone="ntp ntpq"> 376 426 <primary sortas="b-ntpq">ntpq</primary> … … 382 432 <term><command>ntptime</command></term> 383 433 <listitem> 384 <para>reads and displays time-related kernel variables.</para> 434 <para> 435 reads and displays time-related kernel variables. 436 </para> 385 437 <indexterm zone="ntp ntptime"> 386 438 <primary sortas="b-ntptime">ntptime</primary> … … 392 444 <term><command>ntptrace</command></term> 393 445 <listitem> 394 <para>traces a chain of ntp servers back to the primary source.</para> 446 <para> 447 traces a chain of ntp servers back to the primary source. 448 </para> 395 449 <indexterm zone="ntp ntptrace"> 396 450 <primary sortas="b-ntptrace">ntptrace</primary> … … 402 456 <term><command>sntp</command></term> 403 457 <listitem> 404 <para>is a Simple Network Time Protocol (SNTP) client.</para> 458 <para> 459 is a Simple Network Time Protocol (SNTP) client. 460 </para> 405 461 <indexterm zone="ntp sntp"> 406 462 <primary sortas="b-sntp">sntp</primary> … … 412 468 <term><command>tickadj</command></term> 413 469 <listitem> 414 <para>reads, and optionally modifies, several timekeeping-related 415 variables in older kernels that do not have support for precision 416 timekeeping.</para> 470 <para> 471 reads, and optionally modifies, several timekeeping-related 472 variables in older kernels that do not have support for precision 473 timekeeping. 474 </para> 417 475 <indexterm zone="ntp tickadj"> 418 476 <primary sortas="b-tickadj">tickadj</primary> … … 424 482 <term><command>update-leap</command></term> 425 483 <listitem> 426 <para>is a script to verify and, if necessary, update the leap-second 427 definition file.</para> 484 <para> 485 is a script to verify and, if necessary, update the leap-second 486 definition file. 487 </para> 428 488 <indexterm zone="ntp update-leap"> 429 489 <primary sortas="b-update-leap">update-leap</primary> -
networking/netprogs/othernetprogs.xml
rdcee7a56 rb51fe6e 19 19 <ulink url="&blfs-wiki;/othernetprogs"/></para> 20 20 21 <para><application>NCPFS</application> contains client and administration 22 tools for use with Novell networks. See the User Notes for details.</para> 21 <para> 22 <application>NCPFS</application> contains client and administration 23 tools for use with Novell networks. See the User Notes for details. 24 </para> 23 25 24 26 </sect1> -
networking/netprogs/rpcbind.xml
rdcee7a56 rb51fe6e 30 30 <title>Introduction to rpcbind</title> 31 31 32 <para>The <application>rpcbind</application> program is a replacement for 33 <application>portmap</application>. It is required for import or export 34 of Network File System (NFS) shared directories. </para> 32 <para> 33 The <application>rpcbind</application> program is a replacement for 34 <application>portmap</application>. It is required for import or export 35 of Network File System (NFS) shared directories. 36 </para> 35 37 36 38 &lfs91_checked; … … 39 41 <itemizedlist spacing="compact"> 40 42 <listitem> 41 <para>Download (HTTP): <ulink url="&rpcbind-download-http;"/></para> 42 </listitem> 43 <listitem> 44 <para>Download (FTP): <ulink url="&rpcbind-download-ftp;"/></para> 45 </listitem> 46 <listitem> 47 <para>Download MD5 sum: &rpcbind-md5sum;</para> 48 </listitem> 49 <listitem> 50 <para>Download size: &rpcbind-size;</para> 51 </listitem> 52 <listitem> 53 <para>Estimated disk space required: &rpcbind-buildsize;</para> 54 </listitem> 55 <listitem> 56 <para>Estimated build time: &rpcbind-time;</para> 43 <para> 44 Download (HTTP): <ulink url="&rpcbind-download-http;"/> 45 </para> 46 </listitem> 47 <listitem> 48 <para> 49 Download (FTP): <ulink url="&rpcbind-download-ftp;"/> 50 </para> 51 </listitem> 52 <listitem> 53 <para> 54 Download MD5 sum: &rpcbind-md5sum; 55 </para> 56 </listitem> 57 <listitem> 58 <para> 59 Download size: &rpcbind-size; 60 </para> 61 </listitem> 62 <listitem> 63 <para> 64 Estimated disk space required: &rpcbind-buildsize; 65 </para> 66 </listitem> 67 <listitem> 68 <para> 69 Estimated build time: &rpcbind-time; 70 </para> 57 71 </listitem> 58 72 </itemizedlist> … … 95 109 96 110 <!-- Packages should adapt to standards, not the other way around --> 97 <para>In order to get <application>rpcbind</application> to work 98 properly, first fix the package to use correct service name:</para> 111 <para> 112 In order to get <application>rpcbind</application> to work 113 properly, first fix the package to use correct service name: 114 </para> 99 115 100 116 <screen><userinput>sed -i "/servname/s:rpcbind:sunrpc:" src/rpcbind.c</userinput></screen> 101 117 102 <para>Install <application>rpcbind</application> by running the following 103 commands:</para> 118 <para> 119 Install <application>rpcbind</application> by running the following 120 commands: 121 </para> 104 122 105 123 <screen revision="sysv"><userinput>patch -Np1 -i ../rpcbind-&rpcbind-version;-vulnerability_fixes-1.patch && … … 122 140 make</userinput></screen> 123 141 124 <para>This package does not come with a test suite.</para> 125 126 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 142 <para> 143 This package does not come with a test suite. 144 </para> 145 146 <para> 147 Now, as the <systemitem class="username">root</systemitem> user: 148 </para> 127 149 128 150 <screen role="root"><userinput>make install</userinput></screen> … … 133 155 <title>Command Explanations</title> 134 156 135 <para revision="sysv"><command>--with-rpcuser=root</command>: This works 136 around an error in the configure script.</para> 137 138 <para revision="sysv"><command>--without-systemdsystemunitdir</command>: 139 This version of BLFS does not support systemd.</para> 140 141 <para revision="systemd"><parameter>--with-rpcuser=rpc</parameter>: 142 This switch is used so the <command>rpcbind</command> daemon will 143 run as an unprivileged user instead of the 144 <systemitem class="username">root</systemitem> user.</para> 157 <para revision="sysv"> 158 <command>--with-rpcuser=root</command>: This works 159 around an error in the configure script. 160 </para> 161 162 <para revision="sysv"> 163 <command>--without-systemdsystemunitdir</command>: 164 This version of BLFS does not support systemd. 165 </para> 166 167 <para revision="systemd"> 168 <parameter>--with-rpcuser=rpc</parameter>: 169 This switch is used so the <command>rpcbind</command> daemon will 170 run as an unprivileged user instead of the 171 <systemitem class="username">root</systemitem> user. 172 </para> 145 173 146 174 </sect2> … … 153 181 <phrase revision="systemd">Systemd Unit</phrase></title> 154 182 155 <para>Install the 156 <phrase revision="sysv"><filename>/etc/rc.d/init.d/rpcbind</filename> 157 init script</phrase> 158 <phrase revision="systemd"><filename>rpcbind.service</filename> 159 unit</phrase> included in the 160 <xref linkend="bootscripts" revision="sysv"/> 161 <xref linkend="systemd-units" revision="systemd"/> package.</para> 183 <para> 184 Install the 185 <phrase revision="sysv"><filename>/etc/rc.d/init.d/rpcbind</filename> 186 init script</phrase> 187 <phrase revision="systemd"><filename>rpcbind.service</filename> 188 unit</phrase> included in the 189 <xref linkend="bootscripts" revision="sysv"/> 190 <xref linkend="systemd-units" revision="systemd"/> package. 191 </para> 162 192 163 193 <indexterm zone="rpcbind rpcbind-init" revision="sysv"> 164 194 <primary sortas="f-rpcbind">rpcbind</primary> 165 195 </indexterm> 166 196 167 197 <indexterm zone="rpcbind rpcbind-init" revision="systemd"> 168 198 <primary sortas="f-rpcbind">rpcbind.service</primary> 169 199 </indexterm> 170 200 … … 198 228 <term><command>rpcbind</command></term> 199 229 <listitem> 200 <para>is a server that converts RPC program numbers into universal 201 addresses. It must be running on the host to be able to make RPC 202 calls on a server on that machine. </para> 230 <para> 231 is a server that converts RPC program numbers into universal 232 addresses. It must be running on the host to be able to make RPC 233 calls on a server on that machine. 234 </para> 203 235 <indexterm zone="rpcbind rpcbind-prog"> 204 236 <primary sortas="b-rpcbind">rpcbind</primary> … … 210 242 <term><command>rpcinfo</command></term> 211 243 <listitem> 212 <para>makes an RPC call to an RPC server and reports data according 213 to the requested options. </para> 244 <para> 245 makes an RPC call to an RPC server and reports data according 246 to the requested options. 247 </para> 214 248 <indexterm zone="rpcbind rpcinfo"> 215 249 <primary sortas="b-rpcinfo">rpcinfo</primary> -
networking/netprogs/rsync.xml
rdcee7a56 rb51fe6e 30 30 <title>Introduction to rsync</title> 31 31 32 <para>The <application>rsync</application> package contains the 33 <command>rsync</command> utility. This is useful for synchronizing large 34 file archives over a network.</para> 32 <para> 33 The <application>rsync</application> package contains the 34 <command>rsync</command> utility. This is useful for synchronizing large 35 file archives over a network. 36 </para> 35 37 36 38 &lfs91_checked; … … 39 41 <itemizedlist spacing="compact"> 40 42 <listitem> 41 <para>Download (HTTP): <ulink url="&rsync-download-http;"/></para> 42 </listitem> 43 <listitem> 44 <para>Download (FTP): <ulink url="&rsync-download-ftp;"/></para> 45 </listitem> 46 <listitem> 47 <para>Download MD5 sum: &rsync-md5sum;</para> 48 </listitem> 49 <listitem> 50 <para>Download size: &rsync-size;</para> 51 </listitem> 52 <listitem> 53 <para>Estimated disk space required: &rsync-buildsize;</para> 54 </listitem> 55 <listitem> 56 <para>Estimated build time: &rsync-time;</para> 43 <para> 44 Download (HTTP): <ulink url="&rsync-download-http;"/> 45 </para> 46 </listitem> 47 <listitem> 48 <para> 49 Download (FTP): <ulink url="&rsync-download-ftp;"/> 50 </para> 51 </listitem> 52 <listitem> 53 <para> 54 Download MD5 sum: &rsync-md5sum; 55 </para> 56 </listitem> 57 <listitem> 58 <para> 59 Download size: &rsync-size; 60 </para> 61 </listitem> 62 <listitem> 63 <para> 64 Estimated disk space required: &rsync-buildsize; 65 </para> 66 </listitem> 67 <listitem> 68 <para> 69 Estimated build time: &rsync-time; 70 </para> 57 71 </listitem> 58 72 </itemizedlist> … … 73 87 <title>Installation of rsync</title> 74 88 75 <para>For security reasons, running the <application>rsync</application> 76 server as an unprivileged user and group is encouraged. If you intend to 77 run <command>rsync</command> as a daemon, create the 78 <systemitem class="username">rsyncd</systemitem> user and group 79 with the following commands issued by the 80 <systemitem class="username">root</systemitem> user:</para> 89 <para> 90 For security reasons, running the <application>rsync</application> 91 server as an unprivileged user and group is encouraged. If you intend to 92 run <command>rsync</command> as a daemon, create the 93 <systemitem class="username">rsyncd</systemitem> user and group 94 with the following commands issued by the 95 <systemitem class="username">root</systemitem> user: 96 </para> 81 97 82 98 <screen role="root"><userinput>groupadd -g 48 rsyncd && … … 84 100 -s /bin/false -u 48 rsyncd</userinput></screen> 85 101 86 <para>Install <application>rsync</application> by running the following 87 commands:</para> 102 <para> 103 Install <application>rsync</application> by running the following 104 commands: 105 </para> 88 106 89 107 <screen><userinput>./configure --prefix=/usr --without-included-zlib && 90 108 make</userinput></screen> 91 109 92 <para>If you have <xref linkend="doxygen"/> installed and wish to 93 build HTML API documentation, issue:</para> 110 <para> 111 If you have <xref linkend="doxygen"/> installed and wish to 112 build HTML API documentation, issue: 113 </para> 94 114 95 115 <screen remap="doc"><userinput>doxygen</userinput></screen> 96 116 97 <para>To test the results, issue: <command>make check</command>.</para> 98 99 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 117 <para> 118 To test the results, issue: <command>make check</command>. 119 </para> 120 121 <para> 122 Now, as the <systemitem class="username">root</systemitem> user: 123 </para> 100 124 101 125 <screen role='root'><userinput>make install</userinput></screen> 102 126 103 <para>If you built the documentation, install it using the following 104 commands as the <systemitem class="username">root</systemitem> user:</para> 127 <para> 128 If you built the documentation, install it using the following 129 commands as the <systemitem class="username">root</systemitem> user: 130 </para> 105 131 106 132 <screen role='root' … … 126 152 <title>Config Files</title> 127 153 128 <para><filename>/etc/rsyncd.conf</filename></para> 154 <para> 155 <filename>/etc/rsyncd.conf</filename> 156 </para> 129 157 130 158 <indexterm zone="rsync rsync-config"> … … 137 165 <title>Configuration Information</title> 138 166 139 <para>For client access to remote files, you may need to install the 140 <xref linkend="openssh"/> package to connect to the remote server.</para> 141 142 <para>This is a simple download-only configuration to set up running 143 <command>rsync</command> as a server. See the rsyncd.conf(5) 144 man-page for additional options (i.e., user authentication).</para> 167 <para> 168 For client access to remote files, you may need to install the 169 <xref linkend="openssh"/> package to connect to the remote server. 170 </para> 171 172 <para> 173 This is a simple download-only configuration to set up running 174 <command>rsync</command> as a server. See the rsyncd.conf(5) 175 man-page for additional options (i.e., user authentication). 176 </para> 145 177 146 178 <screen role="root"><userinput>cat > /etc/rsyncd.conf << "EOF" … … 161 193 EOF</userinput></screen> 162 194 163 <para>You can find additional configuration information and general 164 documentation about <command>rsync</command> at 165 <ulink url="http://rsync.samba.org/documentation.html"/>.</para> 195 <para> 196 You can find additional configuration information and general 197 documentation about <command>rsync</command> at 198 <ulink url="http://rsync.samba.org/documentation.html"/>. 199 </para> 166 200 167 201 </sect3> … … 171 205 <phrase revision="systemd">Systemd Unit</phrase></title> 172 206 173 <para>Note that you only want to start the 174 <application>rsync</application> server if you want to provide an 175 <application>rsync</application> archive on your local machine. 176 You don't need this <phrase revision="sysv">script</phrase> 177 <phrase revision="systemd">unit</phrase> to run the 178 <application>rsync</application> client.</para> 179 180 <para>Install the 181 <phrase revision="sysv"><filename>/etc/rc.d/init.d/rsyncd</filename> init 182 script</phrase> 183 <phrase revision="systemd"><filename>rsyncd.service</filename> 184 unit</phrase> included in the 185 <xref linkend="bootscripts" revision="sysv"/> 186 <xref linkend="systemd-units" revision="systemd"/> package.</para> 207 <para> 208 Note that you only want to start the 209 <application>rsync</application> server if you want to provide an 210 <application>rsync</application> archive on your local machine. 211 You don't need this <phrase revision="sysv">script</phrase> 212 <phrase revision="systemd">unit</phrase> to run the 213 <application>rsync</application> client. 214 </para> 215 216 <para> 217 Install the 218 <phrase revision="sysv"><filename>/etc/rc.d/init.d/rsyncd</filename> 219 init script</phrase> 220 <phrase revision="systemd"><filename>rsyncd.service</filename> 221 unit</phrase> included in the 222 <xref linkend="bootscripts" revision="sysv"/> 223 <xref linkend="systemd-units" revision="systemd"/> package. 224 </para> 187 225 188 226 <screen role="root"><userinput>make install-rsyncd</userinput></screen> 189 227 190 228 <note revision="systemd"> 191 <para>This package comes with two types of units: A service file and a 192 socket file. The service file will start rsync daemon once at boot 193 and it will keep running until the system shuts down. The socket file 194 will make systemd listen on rsync port (Default 873, needs to be 195 edited for anything else) and will start rsync daemon when something 196 tries to connect to that port and stop the daemon when the connection 197 is terminated. This is called socket activation and is analogous to 198 using <application>{,x}inetd</application> on a SysVinit based 199 system.</para> 200 201 202 <para>By default, the first method is used - rsync daemon is started 203 at boot and stopped at shutdown. If the socket method is desired, you 204 need to run as the 205 <systemitem class="username">root</systemitem> user:</para> 229 <para> 230 This package comes with two types of units: A service file and a 231 socket file. The service file will start rsync daemon once at boot 232 and it will keep running until the system shuts down. The socket file 233 will make systemd listen on rsync port (Default 873, needs to be 234 edited for anything else) and will start rsync daemon when something 235 tries to connect to that port and stop the daemon when the connection 236 is terminated. This is called socket activation and is analogous to 237 using <application>{,x}inetd</application> on a SysVinit based 238 system. 239 </para> 240 241 <para> 242 By default, the first method is used - rsync daemon is started 243 at boot and stopped at shutdown. If the socket method is desired, you 244 need to run as the 245 <systemitem class="username">root</systemitem> user: 246 </para> 206 247 207 248 <screen role="nodump"><userinput>systemctl stop rsyncd && … … 210 251 systemctl start rsyncd.socket</userinput></screen> 211 252 212 <para>Note that socket method is only useful for remote backups. For 213 local backups you'll need the service method.</para> 253 <para> 254 Note that socket method is only useful for remote backups. For 255 local backups you'll need the service method. 256 </para> 214 257 </note> 215 258 … … 241 284 <term><command>rsync</command></term> 242 285 <listitem> 243 <para>is a replacement for <command>rcp</command> (and 244 <command>scp</command>) that has many more features. It uses the 245 <quote>rsync algorithm</quote> which provides a very fast method of 246 syncing remote files. It does this by sending just the differences 247 in the files across the link, without requiring that both sets of 248 files are present at one end of the link beforehand.</para> 286 <para> 287 is a replacement for <command>rcp</command> (and 288 <command>scp</command>) that has many more features. It uses the 289 <quote>rsync algorithm</quote> which provides a very fast method of 290 syncing remote files. It does this by sending just the differences 291 in the files across the link, without requiring that both sets of 292 files are present at one end of the link beforehand. 293 </para> 249 294 <indexterm zone="rsync rsync-prog"> 250 295 <primary sortas="b-rsync">rsync</primary> -
networking/netprogs/samba.xml
rdcee7a56 rb51fe6e 30 30 <title>Introduction to Samba</title> 31 31 32 <para>The <application>Samba</application> package provides file and print 33 services to SMB/CIFS clients and Windows networking to Linux clients. 34 <application>Samba</application> can also be configured as a Windows Domain 35 Controller replacement, a file/print server acting as a member of a Windows 36 Active Directory domain and a NetBIOS (rfc1001/1002) nameserver (which 37 among other things provides LAN browsing support).</para> 32 <para> 33 The <application>Samba</application> package provides file and print 34 services to SMB/CIFS clients and Windows networking to Linux clients. 35 <application>Samba</application> can also be configured as a Windows 36 Domain Controller replacement, a file/print server acting as a member 37 of a Windows Active Directory domain and a NetBIOS (rfc1001/1002) 38 nameserver (which among other things provides LAN browsing support). 39 </para> 38 40 39 41 &lfs91_checked; … … 42 44 <itemizedlist spacing="compact"> 43 45 <listitem> 44 <para>Download (HTTP): <ulink url="&samba-download-http;"/></para> 46 <para> 47 Download (HTTP): <ulink url="&samba-download-http;"/> 48 </para> 45 49 </listitem> 46 50 <listitem> 47 <para>Download (FTP): <ulink url="&samba-download-ftp;"/></para> 51 <para> 52 Download (FTP): <ulink url="&samba-download-ftp;"/> 53 </para> 48 54 </listitem> 49 55 <listitem> 50 <para>Download MD5 sum: &samba-md5sum;</para> 56 <para> 57 Download MD5 sum: &samba-md5sum; 58 </para> 51 59 </listitem> 52 60 <listitem> 53 <para>Download size: &samba-size;</para> 61 <para> 62 Download size: &samba-size; 63 </para> 54 64 </listitem> 55 65 <listitem> 56 <para>Estimated disk space required: &samba-buildsize;</para> 66 <para> 67 Estimated disk space required: &samba-buildsize; 68 </para> 57 69 </listitem> 58 70 <listitem> 59 <para>Estimated build time: &samba-time;</para> 71 <para> 72 Estimated build time: &samba-time; 73 </para> 60 74 </listitem> 61 75 </itemizedlist> … … 124 138 125 139 <bridgehead renderas="sect4">Optional (for the Developer Test Suite)</bridgehead> 126 <para role="optional">Install in listed order: 127 <xref linkend="six"/>, 128 <ulink url="&pypi;/argparse/">argparse</ulink>, 129 <ulink url="&pypi;/extras/">extras</ulink>, 130 <ulink url="&pypi;/py/">py</ulink>, 131 <ulink url="&pypi;/enum34/">enum34</ulink>, 132 <ulink url="&pypi;/hypothesis/">hypothesis</ulink>, 133 <ulink url="&pypi;/pytest/">pytest</ulink>, 134 <ulink url="&pypi;/coverage/">coverage</ulink>, 135 <ulink url="&pypi;/pytest-cov/">pytest-cov</ulink>, 136 <ulink url="&pypi;/doctools/">doctools</ulink>, 137 <ulink url="&pypi;/unittest2/">unittest2</ulink>, 138 <ulink url="&pypi;/testtools/">testtools</ulink>, 139 <ulink url="&pypi;/fixtures/">fixtures</ulink>, 140 <ulink url="&pypi;/python-mimeparse/">python-mimeparse</ulink>, 141 <ulink url="&pypi;/contextlib2/">contextlib2</ulink>, 142 <ulink url="&pypi;/traceback2/">traceback2</ulink>, 143 <ulink url="&pypi;/linecache2/">linecache2</ulink>, 144 <ulink url="&pypi;/testscenarios/">testscenarios</ulink>, 145 <ulink url="&pypi;/testresources/">testresources</ulink>, 146 <ulink url="&pypi;/virtualenv/">virtualenv</ulink>, 147 <ulink url="&pypi;/pbr/">pbr</ulink>, and 148 <ulink url="&pypi;/python-subunit/">python-subunit</ulink></para> 140 <para role="optional"> 141 Install in listed order: 142 <xref linkend="six"/>, 143 <ulink url="&pypi;/argparse/">argparse</ulink>, 144 <ulink url="&pypi;/extras/">extras</ulink>, 145 <ulink url="&pypi;/py/">py</ulink>, 146 <ulink url="&pypi;/enum34/">enum34</ulink>, 147 <ulink url="&pypi;/hypothesis/">hypothesis</ulink>, 148 <ulink url="&pypi;/pytest/">pytest</ulink>, 149 <ulink url="&pypi;/coverage/">coverage</ulink>, 150 <ulink url="&pypi;/pytest-cov/">pytest-cov</ulink>, 151 <ulink url="&pypi;/doctools/">doctools</ulink>, 152 <ulink url="&pypi;/unittest2/">unittest2</ulink>, 153 <ulink url="&pypi;/testtools/">testtools</ulink>, 154 <ulink url="&pypi;/fixtures/">fixtures</ulink>, 155 <ulink url="&pypi;/python-mimeparse/">python-mimeparse</ulink>, 156 <ulink url="&pypi;/contextlib2/">contextlib2</ulink>, 157 <ulink url="&pypi;/traceback2/">traceback2</ulink>, 158 <ulink url="&pypi;/linecache2/">linecache2</ulink>, 159 <ulink url="&pypi;/testscenarios/">testscenarios</ulink>, 160 <ulink url="&pypi;/testresources/">testresources</ulink>, 161 <ulink url="&pypi;/virtualenv/">virtualenv</ulink>, 162 <ulink url="&pypi;/pbr/">pbr</ulink>, and 163 <ulink url="&pypi;/python-subunit/">python-subunit</ulink> 164 </para> 149 165 150 166 <para condition="html" role="usernotes">User Notes: … … 156 172 <title>Installation of Samba</title> 157 173 158 <para>Fix a test that always fails:</para> 174 <para> 175 Fix a test that always fails: 176 </para> 159 177 160 178 <screen><userinput>echo "^samba4.rpc.echo.*on.*ncacn_np.*with.*object.*nt4_dc" >> selftest/knownfail</userinput></screen> 161 179 162 <para>Install <application>Samba</application> by running the following 163 commands:</para> 180 <para> 181 Install <application>Samba</application> by running the following 182 commands: 183 </para> 164 184 165 185 <screen revision="sysv"><userinput>CFLAGS="-I/usr/include/tirpc" \ … … 190 210 make</userinput></screen> 191 211 192 <para>To test the results, as the 193 <systemitem class="username">root</systemitem> user, issue: 194 <command>make quicktest</command>. The test suite will produce lines that 195 look like failures, but these are innocuous. The last few lines of output 196 should report <emphasis>"ALL OK"</emphasis> for a good test run. A summary 197 of any failures can be found in 198 <filename class="directory">./st/summary</filename>.</para> 199 200 <!-- If doing a security update or a new minor version (point releases do not apply 201 here), run 'make testenv' before running 'make test' and 'make subunit-test'. This 202 will setup the test environment and make the tests run faster, as well as point 203 out any glaring issues that might affect the new Samba installation. With 4.10.4, 204 I got 236 failures, 73 errors, and 2 unexpected successes. These were all known 205 upstream, and you can find them in the knownfail list in their git repo. 206 This is per Upstream's recommendation over IRC.--> 212 <para> 213 To test the results, as the 214 <systemitem class="username">root</systemitem> user, issue: 215 <command>make quicktest</command>. The test suite will produce lines that 216 look like failures, but these are innocuous. The last few lines of output 217 should report <emphasis>"ALL OK"</emphasis> for a good test run. A summary 218 of any failures can be found in 219 <filename class="directory">./st/summary</filename>. 220 </para> 221 222 <!-- 223 If doing a security update or a new minor version (point releases do not 224 apply here), run 'make testenv' before running 'make test' and 'make 225 subunit-test'. This will setup the test environment and make the tests 226 run faster, as well as point out any glaring issues that might affect 227 the new Samba installation. With 4.10.4, I got 236 failures, 73 errors, 228 and 2 unexpected successes. These were all known upstream, and you can 229 find them in the knownfail list in their git repo. This is per 230 Upstream's recommendation over IRC. 231 --> 207 232 208 233 <note> 209 <para>Additionally, developer test suites are available. If you've 210 installed the optional python modules above, you can run these tests with 211 <command>make test</command>. It is not recommended for the average 212 builder at around 290 SBU and over a gigabyte of disk space, and you 213 should expect ~73 errors and ~30 failures from the 3000+ tests.</para> 234 <para> 235 Additionally, developer test suites are available. If you've installed 236 the optional python modules above, you can run these tests with 237 <command>make test</command>. It is not recommended for the average 238 builder at around 290 SBU and over a gigabyte of disk space, and you 239 should expect ~73 errors and ~30 failures from the 3000+ tests. 240 </para> 214 241 </note> 215 242 216 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 243 <para> 244 Now, as the <systemitem class="username">root</systemitem> user: 245 </para> 217 246 218 247 <screen role="root"><userinput>make install && … … 240 269 <title>Command Explanations</title> 241 270 242 <para><parameter>--enable-fhs</parameter>: Assigns all other file paths in 243 a manner compliant with the Filesystem Hierarchy Standard (FHS).</para> 244 245 <para revision="sysv"><parameter>--without-systemd</parameter>: Disable 246 <application>systemd</application> integration, since it is not built 247 in the System V version of LFS/BLFS.</para> 248 249 <para><parameter>--without-ad-dc</parameter>: Disable 250 Active Directory Domain Controller functionality. See <ulink 251 url="https://wiki.samba.org/index.php/Setup_a_Samba_Active_Directory_Domain_Controller"> 252 Setup a Samba Active Directory Domain Controller</ulink> for detailed 253 information. Remove this switch if you've installed the Python modules 254 needed for ADS support. Note that BLFS does not provide a samba bootscript 255 for an Active Directory domain controller.</para> 256 257 <para><option>--with-selftest-prefix=SELFTEST_PREFIX</option>: This option 258 specifies the test suite work directory (default=./st).</para> 259 260 <para><command>mv -v /usr/lib/libnss_win{s,bind}.so* /lib</command>: 261 The nss libraries are installed in /usr/lib by default. Move them to 262 /lib.</para> 263 264 <para><command>ln -v -sf ../../lib/libnss_winbind.so.2 /usr/lib/libnss_winbind.so</command> 265 and <command>ln -v -sf ../../lib/libnss_wins.so.2 /usr/lib/libnss_wins.so</command>: 266 These symlinks are required when applications build against these 267 libraries.</para> 268 269 <para><command>install -v -m644 examples/LDAP/* /etc/openldap/schema</command>: 270 These commands are used to copy sample Samba schemas to the OpenLDAP 271 <filename class='directory'>schema</filename> directory.</para> 272 273 <para><command>install -v -m644 ../examples/smb.conf.default 274 /etc/samba</command>: This copies a default <filename>smb.conf</filename> 275 file into <filename>/etc/samba</filename>. This sample configuration will 276 not work until you copy it to <filename>/etc/samba/smb.conf</filename> and 277 make the appropriate changes for your installation. See the configuration 278 section for minimum values which must be set.</para> 271 <para> 272 <parameter>--enable-fhs</parameter>: Assigns all other file paths in 273 a manner compliant with the Filesystem Hierarchy Standard (FHS). 274 </para> 275 276 <para revision="sysv"> 277 <parameter>--without-systemd</parameter>: Disable 278 <application>systemd</application> integration, since it is not built 279 in the System V version of LFS/BLFS. 280 </para> 281 282 <para> 283 <parameter>--without-ad-dc</parameter>: Disable 284 Active Directory Domain Controller functionality. See <ulink url= 285 "https://wiki.samba.org/index.php/Setup_a_Samba_Active_Directory_Domain_Controller"> 286 Setup a Samba Active Directory Domain Controller</ulink> for detailed 287 information. Remove this switch if you've installed the Python modules 288 needed for ADS support. Note that BLFS does not provide a samba bootscript 289 for an Active Directory domain controller. 290 </para> 291 292 <para> 293 <option>--with-selftest-prefix=SELFTEST_PREFIX</option>: This option 294 specifies the test suite work directory (default=./st). 295 </para> 296 297 <para> 298 <command>mv -v /usr/lib/libnss_win{s,bind}.so* /lib</command>: 299 The nss libraries are installed in 300 <filename class="directory">/usr/lib</filename> by default. Move them to 301 <filename class="directory">/lib</filename>. 302 </para> 303 304 <para> 305 <command>ln -v -sf ../../lib/libnss_winbind.so.2 /usr/lib/libnss_winbind.so</command> 306 and <command>ln -v -sf ../../lib/libnss_wins.so.2 /usr/lib/libnss_wins.so</command>: 307 These symlinks are required when applications build against these 308 libraries. 309 </para> 310 311 <para> 312 <command>install -v -m644 examples/LDAP/* /etc/openldap/schema</command>: 313 These commands are used to copy sample Samba schemas to the OpenLDAP 314 <filename class='directory'>schema</filename> directory. 315 </para> 316 317 <para> 318 <command>install -v -m644 ../examples/smb.conf.default 319 /etc/samba</command>: This copies a default <filename>smb.conf</filename> 320 file into <filename>/etc/samba</filename>. This sample configuration will 321 not work until you copy it to <filename>/etc/samba/smb.conf</filename> and 322 make the appropriate changes for your installation. See the configuration 323 section for minimum values which must be set. 324 </para> 279 325 280 326 </sect2> … … 286 332 <title>Config Files</title> 287 333 288 <para>/etc/samba/smb.conf</para> 334 <para> 335 /etc/samba/smb.conf 336 </para> 289 337 290 338 <indexterm zone="samba samba-config"> … … 297 345 <title>Printing to SMB Clients</title> 298 346 299 <para>If you use <application>CUPS</application> for print services, 300 and you wish to print to a printer attached to an SMB client, you 301 need to create an SMB backend device. To create the device, issue the 302 following command as the <systemitem class="username">root</systemitem> 303 user:</para> 304 305 <screen role="root"><userinput>ln -v -sf /usr/bin/smbspool /usr/lib/cups/backend/smb</userinput></screen> 347 <para> 348 If you use <application>CUPS</application> for print services, and you 349 wish to print to a printer attached to an SMB client, you need to 350 create an SMB backend device. To create the device, issue the following 351 command as the <systemitem class="username">root</systemitem> user: 352 </para> 353 354 <screen role="root"><userinput>install -dvm 755 /usr/lib/cups/backend && 355 ln -v -sf /usr/bin/smbspool /usr/lib/cups/backend/smb</userinput></screen> 306 356 307 357 </sect3> … … 310 360 <title>Configuration Information</title> 311 361 312 <para>Due to the complexity and the many various uses for 313 <application>Samba</application>, complete configuration for all the 314 package's capabilities is well beyond the scope of the BLFS book. This 315 section provides instructions to configure the 316 <filename>/etc/samba/smb.conf</filename> file for two common scenarios. 317 The complete contents of <filename>/etc/samba/smb.conf</filename> will 318 depend on the purpose of <application>Samba</application> 319 installation.</para> 362 <para> 363 Due to the complexity and the many various uses for 364 <application>Samba</application>, complete configuration for all the 365 package's capabilities is well beyond the scope of the BLFS book. This 366 section provides instructions to configure the 367 <filename>/etc/samba/smb.conf</filename> file for two common scenarios. 368 The complete contents of <filename>/etc/samba/smb.conf</filename> will 369 depend on the purpose of <application>Samba</application> 370 installation. 371 </para> 320 372 321 373 <note> 322 <para>You may find it easier to copy the configuration parameters shown 323 below into an empty <filename>/etc/samba/smb.conf</filename> file 324 instead of copying and editing the default file as mentioned in the 325 <quote>Command Explanations</quote> section. How you create/edit the 326 <filename>/etc/samba/smb.conf</filename> file will be left up to 327 you. Do ensure the file is only writeable by the 328 <systemitem class="username">root</systemitem> user (mode 644).</para> 374 <para> 375 You may find it easier to copy the configuration parameters shown 376 below into an empty <filename>/etc/samba/smb.conf</filename> file 377 instead of copying and editing the default file as mentioned in the 378 <quote>Command Explanations</quote> section. How you create/edit the 379 <filename>/etc/samba/smb.conf</filename> file will be left up to 380 you. Do ensure the file is only writeable by the 381 <systemitem class="username">root</systemitem> user (mode 644). 382 </para> 329 383 </note> 330 384 … … 332 386 <title>Scenario 1: Minimal Standalone Client-Only Installation</title> 333 387 334 <para>Choose this variant if you only want to transfer files using 335 <command>smbclient</command>, mount Windows shares and print to Windows 336 printers, and don't want to share your files and printers to Windows 337 machines.</para> 338 339 <para>A <filename>/etc/samba/smb.conf</filename> file with the following 340 three parameters is sufficient:</para> 388 <para> 389 Choose this variant if you only want to transfer files using 390 <command>smbclient</command>, mount Windows shares and print to 391 Windows printers, and don't want to share your files and printers to 392 Windows machines. 393 </para> 394 395 <para> 396 A <filename>/etc/samba/smb.conf</filename> file with the following 397 three parameters is sufficient: 398 </para> 341 399 342 400 <screen role='root'><literal>[global] … … 345 403 unix charset = <replaceable>ISO-8859-1</replaceable></literal></screen> 346 404 347 <para>The values in this example specify that the computer belongs to a 348 Windows workgroup named 349 <quote><replaceable>MYGROUP</replaceable></quote>, uses the 350 <quote><replaceable>cp850</replaceable></quote> character set on the 351 wire when talking to MS-DOS and MS Windows 9x, and that the filenames 352 are stored in the <quote><replaceable>ISO-8859-1</replaceable></quote> 353 encoding on the disk. Adjust these values appropriately for your 354 installation. The <quote>unix charset</quote> value must be the same as 355 the output of <command>locale charmap</command> when executed with the 356 <envar>LANG</envar> variable set to your preferred locale, otherwise the 357 <command>ls</command> command may not display correct filenames of 358 downloaded files.</para> 359 360 <para>There is no need to run any <application>Samba</application> 361 servers in this scenario, thus you don't need to install the provided 362 bootscripts.</para> 405 <para> 406 The values in this example specify that the computer belongs to a 407 Windows workgroup named 408 <quote><replaceable>MYGROUP</replaceable></quote>, uses the 409 <quote><replaceable>cp850</replaceable></quote> character set on the 410 wire when talking to MS-DOS and MS Windows 9x, and that the filenames 411 are stored in the <quote><replaceable>ISO-8859-1</replaceable></quote> 412 encoding on the disk. Adjust these values appropriately for your 413 installation. The <quote>unix charset</quote> value must be the same 414 as the output of <command>locale charmap</command> when executed with 415 the <envar>LANG</envar> variable set to your preferred locale, 416 otherwise the <command>ls</command> command may not display correct 417 filenames of downloaded files. 418 </para> 419 420 <para> 421 There is no need to run any <application>Samba</application> 422 servers in this scenario, thus you don't need to install the provided 423 bootscripts. 424 </para> 363 425 364 426 </sect4> … … 367 429 <title>Scenario 2: Standalone File/Print Server</title> 368 430 369 <para>Choose this variant if you want to share your files and printers 370 to Windows machines in your workgroup in addition to the capabilities 371 described in Scenario 1.</para> 372 373 <para>In this case, the <filename>/etc/samba/smb.conf.default</filename> 374 file may be a good template to start from. Also add 375 <quote>dos charset</quote> and <quote>unix charset</quote> parameters 376 to the <quote>[global]</quote> section as described in Scenario 1 in 377 order to prevent filename corruption. For security reasons, you may 378 wish to define 379 <replaceable>path = /home/alice/shared-files</replaceable>, 380 assuming your user name is <replaceable>alice</replaceable> and you 381 only want to share the files in that directory, instead of your entire 382 home. Then, replace <replaceable>homes</replaceable> by 383 <replaceable>shared-files</replaceable> and change also the 384 <quote><literal>comment</literal></quote> if used the configuration 385 file below or the <filename>/etc/samba/smb.conf.default</filename> 386 to create yours.</para> 387 388 <para>The following configuration file creates a separate share for each 389 user's home directory and also makes all printers available to Windows 390 machines:</para> 431 <para> 432 Choose this variant if you want to share your files and printers 433 to Windows machines in your workgroup in addition to the capabilities 434 described in Scenario 1. 435 </para> 436 437 <para> 438 In this case, the <filename>/etc/samba/smb.conf.default</filename> 439 file may be a good template to start from. Also add 440 <quote>dos charset</quote> and <quote>unix charset</quote> parameters 441 to the <quote>[global]</quote> section as described in Scenario 1 in 442 order to prevent filename corruption. For security reasons, you may 443 wish to define 444 <replaceable>path = /home/alice/shared-files</replaceable>, 445 assuming your user name is <replaceable>alice</replaceable> and you 446 only want to share the files in that directory, instead of your entire 447 home. Then, replace <replaceable>homes</replaceable> by 448 <replaceable>shared-files</replaceable> and change also the 449 <quote><literal>comment</literal></quote> if used the configuration 450 file below or the <filename>/etc/samba/smb.conf.default</filename> 451 to create yours. 452 </para> 453 454 <para> 455 The following configuration file creates a separate share for each 456 user's home directory and also makes all printers available to Windows 457 machines: 458 </para> 391 459 392 460 <screen role='root'><literal>[global] … … 407 475 printable = yes</literal></screen> 408 476 409 <para>Other parameters you may wish to customize in the 410 <quote>[global]</quote> section include:</para> 477 <para> 478 Other parameters you may wish to customize in the 479 <quote>[global]</quote> section include: 480 </para> 411 481 412 482 <screen role='root'><literal> server string = … … 419 489 local master =</literal></screen> 420 490 421 <para>Reference the comments in the 422 <filename>/etc/samba/smb.conf.default</filename> file for information 423 regarding these parameters.</para> 424 425 <para>Since the <command>smbd</command> and <command>nmbd</command> 426 daemons are needed in this case, install the <filename>samba</filename> 427 bootscript. Be sure to run <command>smbpasswd</command> (with the 428 <option>-a</option> option to add users) to enable and 429 set passwords for all accounts that need 430 <application>Samba</application> access. Using the default 431 <application>Samba</application> passdb backend, any user you attempt 432 to add will also be required to exist in the 433 <filename>/etc/passwd</filename> file.</para> 491 <para> 492 Reference the comments in the 493 <filename>/etc/samba/smb.conf.default</filename> file for information 494 regarding these parameters. 495 </para> 496 497 <para> 498 Since the <command>smbd</command> and <command>nmbd</command> daemons 499 are needed in this case, install the <filename>samba</filename> 500 bootscript. Be sure to run <command>smbpasswd</command> (with the 501 <option>-a</option> option to add users) to enable and set passwords 502 for all accounts that need <application>Samba</application> access. 503 Using the default <application>Samba</application> passdb backend, 504 any user you attempt to add will also be required to exist in the 505 <filename>/etc/passwd</filename> file. 506 </para> 434 507 435 508 </sect4> … … 438 511 <title>Advanced Requirements</title> 439 512 440 <para>More complex scenarios involving domain control or membership are 441 possible. Such setups are advanced topics and cannot be adequately 442 covered in BLFS. Many complete books have been written on these topics 443 alone. Note that in some domain membership scenarios, the 444 <command>winbindd</command> daemon and the corresponding bootscript are 445 needed.</para> 446 447 <para>There is quite a bit of documentation available which covers many 448 of these advanced configurations. Point your web browser to the links 449 below to view some of the documentation included with the 450 <application>Samba</application> package:</para> 513 <para> 514 More complex scenarios involving domain control or membership are 515 possible. Such setups are advanced topics and cannot be adequately 516 covered in BLFS. Many complete books have been written on these topics 517 alone. Note that in some domain membership scenarios, the 518 <command>winbindd</command> daemon and the corresponding bootscript 519 are needed. 520 </para> 521 522 <para> 523 There is quite a bit of documentation available which covers many 524 of these advanced configurations. Point your web browser to the links 525 below to view some of the documentation included with the 526 <application>Samba</application> package: 527 </para> 451 528 452 529 <itemizedlist spacing='compact'> 453 530 <listitem> 454 <para>Using Samba, 2nd Edition; a popular book published by O'Reilly 455 <ulink url="http://www.samba.org/samba/docs/using_samba/toc.html"/></para> 456 </listitem> 457 <listitem> 458 <para>The Official Samba HOWTO and Reference Guide <ulink 459 url="http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/"/> 531 <para> 532 Using Samba, 2nd Edition; a popular book published by O'Reilly 533 <ulink url= 534 "http://www.samba.org/samba/docs/using_samba/toc.html"/> 460 535 </para> 461 536 </listitem> 462 537 <listitem> 463 <para>Samba-3 by Example 464 <ulink url="http://www.samba.org/samba/docs/man/Samba-Guide/"/> 538 <para> 539 The Official Samba HOWTO and Reference Guide <ulink url= 540 "http://www.samba.org/samba/docs/man/Samba-HOWTO-Collection/"/> 541 </para> 542 </listitem> 543 <listitem> 544 <para> 545 Samba-3 by Example 546 <ulink url="http://www.samba.org/samba/docs/man/Samba-Guide/"/> 465 547 </para> 466 548 </listitem> … … 472 554 <title>Guest account</title> 473 555 474 <para>The default <application>Samba</application> installation uses the 475 <systemitem class='username'>nobody</systemitem> user for guest access 476 to the server. This can be overridden by setting the 477 <option>guest account =</option> parameter in the 478 <filename>/etc/samba/smb.conf</filename> file. If you utilize the 479 <option>guest account =</option> parameter, ensure this user exists in 480 the <filename>/etc/passwd</filename> file.</para> 556 <para> 557 The default <application>Samba</application> installation uses the 558 <systemitem class='username'>nobody</systemitem> user for guest 559 access to the server. This can be overridden by setting the 560 <option>guest account =</option> parameter in the 561 <filename>/etc/samba/smb.conf</filename> file. If you utilize the 562 <option>guest account =</option> parameter, ensure this user exists 563 in the <filename>/etc/passwd</filename> file. 564 </para> 481 565 482 566 </sect4> … … 485 569 <title>Boot Script</title> 486 570 487 <para>For your convenience, boot scripts have been provided for 488 <application>Samba</application>. There are two included in the 489 <xref linkend="bootscripts"/> package. The first, 490 <filename>samba</filename>, will start the <command>smbd</command> 491 and <command>nmbd</command> daemons needed to provide SMB/CIFS 492 services. The second script, <filename>winbind</filename>, starts 493 the <command>winbindd</command> daemon, used for providing Windows 494 domain services to Linux clients.</para> 571 <para> 572 For your convenience, boot scripts have been provided for 573 <application>Samba</application>. There are two included in the 574 <xref linkend="bootscripts"/> package. The first, 575 <filename>samba</filename>, will start the <command>smbd</command> 576 and <command>nmbd</command> daemons needed to provide SMB/CIFS 577 services. The second script, <filename>winbind</filename>, starts 578 the <command>winbindd</command> daemon, used for providing Windows 579 domain services to Linux clients. 580 </para> 495 581 496 582 <indexterm zone="samba samba-init"> … … 538 624 539 625 <note> 540 <para>This package comes with two types of units: A service file and a 541 socket file. The service file will start the smbd daemon once at boot 542 and it will keep running until the system shuts down. The socket file 543 will make systemd listen on the smbd port (Default 445, needs to be 544 edited for anything else) and will start the smbd daemon when something 545 tries to connect to that port and stop the daemon when the connection 546 is terminated. This is called socket activation and is analogous to 547 using <application>{,x}inetd</application> on a SysVinit based 548 system.</para> 549 550 <para>By default, the first method is used - the smbd daemon is started 551 at boot and stopped at shutdown. If the socket method is desired, you 552 need to run the following commands as the 553 <systemitem class="username">root</systemitem> user:</para> 626 <para> 627 This package comes with two types of units: A service file and a 628 socket file. The service file will start the smbd daemon once at 629 boot and it will keep running until the system shuts down. The 630 socket file will make systemd listen on the smbd port (Default 445, 631 needs to be edited for anything else) and will start the smbd 632 daemon when something tries to connect to that port and stop the 633 daemon when the connection is terminated. This is called socket 634 activation and is analogous to using 635 <application>{,x}inetd</application> on a SysVinit based system. 636 </para> 637 638 <para> 639 By default, the first method is used - the smbd daemon is started 640 at boot and stopped at shutdown. If the socket method is desired, 641 you need to run the following commands as the <systemitem 642 class="username">root</systemitem> user: 643 </para> 554 644 555 645 <screen role="root"><userinput>systemctl stop smbd && … … 558 648 systemctl start smbd.socket</userinput></screen> 559 649 560 <para>Note that only the smbd daemon can be socket activated.</para> 650 <para> 651 Note that only the smbd daemon can be socket activated. 652 </para> 561 653 </note> 562 654 </sect4> … … 626 718 <term><command>cifsdd</command></term> 627 719 <listitem> 628 <para>is the dd command for SMB.</para> 720 <para> 721 is the dd command for SMB. 722 </para> 629 723 <indexterm zone="samba cifsdd"> 630 724 <primary sortas="b-cifsdd">cifsdd</primary> … … 636 730 <term><command>dbwrap_tool</command></term> 637 731 <listitem> 638 <para>is used to read and manipulate TDB/CTDB databases using 639 the dbwrap interface.</para> 732 <para> 733 is used to read and manipulate TDB/CTDB databases using 734 the dbwrap interface. 735 </para> 640 736 <indexterm zone="samba dbwrap_tool"> 641 737 <primary sortas="b-dbwrap_tool">dbwrap_tool</primary> … … 647 743 <term><command>eventlogadm</command></term> 648 744 <listitem> 649 <para>is used to write records to eventlogs from STDIN, add the 650 specified source and DLL eventlog registry entries and display the 651 active eventlog names (from <filename>smb.conf</filename>).</para> 745 <para> 746 is used to write records to eventlogs from STDIN, add the 747 specified source and DLL eventlog registry entries and display the 748 active eventlog names (from <filename>smb.conf</filename>). 749 </para> 652 750 <indexterm zone="samba eventlogadm"> 653 751 <primary sortas="b-eventlogadm">eventlogadm</primary> … … 659 757 <term><command>findsmb</command></term> 660 758 <listitem> 661 <para>is used to list info about machines that respond to SMB name 662 queries on a subnet.</para> 759 <para> 760 is used to list info about machines that respond to SMB name 761 queries on a subnet. 762 </para> 663 763 <indexterm zone="samba findsmb"> 664 764 <primary sortas="b-findsmb">findsmb</primary> … … 670 770 <term><command>gentest</command></term> 671 771 <listitem> 672 <para>is used to run random generic SMB operations against two 673 SMB servers and show the differences in behavior.</para> 772 <para> 773 is used to run random generic SMB operations against two 774 SMB servers and show the differences in behavior. 775 </para> 674 776 <indexterm zone="samba gentest"> 675 777 <primary sortas="b-gentest">gentest</primary> … … 681 783 <term><command>ldbadd</command></term> 682 784 <listitem> 683 <para>is a command-line utility for adding records to an LDB 684 database.</para> 785 <para> 786 is a command-line utility for adding records to an LDB 787 database. 788 </para> 685 789 <indexterm zone="samba ldbadd"> 686 790 <primary sortas="b-ldbadd">ldbadd</primary> … … 692 796 <term><command>ldbdel</command></term> 693 797 <listitem> 694 <para>is a command-line program for deleting LDB database 695 records.</para> 798 <para> 799 is a command-line program for deleting LDB database records. 800 </para> 696 801 <indexterm zone="samba ldbdel"> 697 802 <primary sortas="b-ldbdel">ldbdel</primary> … … 703 808 <term><command>ldbedit</command></term> 704 809 <listitem> 705 <para>allows you to edit LDB databases using your preferred 706 editor.</para> 810 <para> 811 allows you to edit LDB databases using your preferred editor. 812 </para> 707 813 <indexterm zone="samba ldbedit"> 708 814 <primary sortas="b-ldbedit">ldbedit</primary> … … 714 820 <term><command>ldbmodify</command></term> 715 821 <listitem> 716 <para>allows you to modify records in an LDB database.</para> 822 <para> 823 allows you to modify records in an LDB database. 824 </para> 717 825 <indexterm zone="samba ldbmodify"> 718 826 <primary sortas="b-ldbmodify">ldbmodify</primary> … … 724 832 <term><command>ldbrename</command></term> 725 833 <listitem> 726 <para>allows you to rename LDB databases.</para> 834 <para> 835 allows you to rename LDB databases. 836 </para> 727 837 <indexterm zone="samba ldbrename"> 728 838 <primary sortas="b-ldbrename">ldbrename</primary> … … 734 844 <term><command>ldbsearch</command></term> 735 845 <listitem> 736 <para>searches an LDB database for records matching a specified 737 expression.</para> 846 <para> 847 searches an LDB database for records matching a specified 848 expression. 849 </para> 738 850 <indexterm zone="samba ldbsearch"> 739 851 <primary sortas="b-ldbsearch">ldbsearch</primary> … … 745 857 <term><command>locktest</command></term> 746 858 <listitem> 747 <para>is used to find differences in locking between two SMB 748 servers.</para> 859 <para> 860 is used to find differences in locking between two SMB servers. 861 </para> 749 862 <indexterm zone="samba locktest"> 750 863 <primary sortas="b-locktest">locktest</primary> … … 756 869 <term><command>masktest</command></term> 757 870 <listitem> 758 <para>is used to find differences in wildcard matching between 759 Samba's implementation and that of a remote server.</para> 871 <para> 872 is used to find differences in wildcard matching between 873 Samba's implementation and that of a remote server. 874 </para> 760 875 <indexterm zone="samba masktest"> 761 876 <primary sortas="b-masktest">masktest</primary> … … 767 882 <term><command>mvxattr</command></term> 768 883 <listitem> 769 <para>is used to recursively rename extended attributes.</para> 884 <para> 885 is used to recursively rename extended attributes. 886 </para> 770 887 <indexterm zone="samba mvxattr"> 771 888 <primary sortas="b-mvxattr">mvxattr</primary> … … 777 894 <term><command>ndrdump</command></term> 778 895 <listitem> 779 <para>is a DCE/RPC Packet Parser and Dumper.</para> 896 <para> 897 is a DCE/RPC Packet Parser and Dumper. 898 </para> 780 899 <indexterm zone="samba ndrdump"> 781 900 <primary sortas="b-ndrdump">ndrdump</primary> … … 787 906 <term><command>net</command></term> 788 907 <listitem> 789 <para>is a tool for administration of 790 <application>Samba</application> and remote CIFS servers, similar 791 to the <command>net</command> utility for DOS/Windows.</para> 908 <para> 909 is a tool for administration of <application>Samba</application> 910 and remote CIFS servers, similar to the <command>net</command> 911 utility for DOS/Windows. 912 </para> 792 913 <indexterm zone="samba net"> 793 914 <primary sortas="b-net">net</primary> … … 799 920 <term><command>nmbd</command></term> 800 921 <listitem> 801 <para>is the <application>Samba</application> 802 NetBIOS name server.</para> 922 <para> 923 is the <application>Samba</application> NetBIOS name server. 924 </para> 803 925 <indexterm zone="samba nmbd"> 804 926 <primary sortas="b-nmbd">nmbd</primary> … … 810 932 <term><command>nmblookup</command></term> 811 933 <listitem> 812 <para>is used to query NetBIOS names and map 813 them to IP addresses.</para> 934 <para> 935 is used to query NetBIOS names and map them to IP addresses. 936 </para> 814 937 <indexterm zone="samba nmblookup"> 815 938 <primary sortas="b-nmblookup">nmblookup</primary> … … 821 944 <term><command>ntlm_auth</command></term> 822 945 <listitem> 823 <para>is a tool to allow external access to Winbind's 824 NTLM authentication function.</para> 946 <para> 947 is a tool to allow external access to Winbind's 948 NTLM authentication function. 949 </para> 825 950 <indexterm zone="samba ntlm_auth"> 826 951 <primary sortas="b-ntlm_auth">ntlm_auth</primary> … … 832 957 <term><command>oLschema2ldif</command></term> 833 958 <listitem> 834 <para>converts LDAP schema's to LDB-compatible LDIF.</para> 959 <para> 960 converts LDAP schema's to LDB-compatible LDIF. 961 </para> 835 962 <indexterm zone="samba oLschema2ldif"> 836 963 <primary sortas="b-oLschema2ldif">oLschema2ldif</primary> … … 842 969 <term><command>pdbedit</command></term> 843 970 <listitem> 844 <para>is a tool used to manage the SAM database.</para> 971 <para> 972 is a tool used to manage the SAM database. 973 </para> 845 974 <indexterm zone="samba pdbedit"> 846 975 <primary sortas="b-pdbedit">pdbedit</primary> … … 852 981 <term><command>pidl</command></term> 853 982 <listitem> 854 <para>is an IDL (Interface Definition Language) compiler 855 written in Perl.</para> 983 <para> 984 is an IDL (Interface Definition Language) compiler 985 written in Perl. 986 </para> 856 987 <indexterm zone="samba pidl"> 857 988 <primary sortas="b-pidl">pidl</primary> … … 863 994 <term><command>profiles</command></term> 864 995 <listitem> 865 <para>is a utility that reports and changes SIDs in Windows 866 registry files. It currently only supports Windows NT.</para> 996 <para> 997 is a utility that reports and changes SIDs in Windows 998 registry files. It currently only supports Windows NT. 999 </para> 867 1000 <indexterm zone="samba profiles"> 868 1001 <primary sortas="b-profiles">profiles</primary> … … 874 1007 <term><command>regdiff</command></term> 875 1008 <listitem> 876 <para>is a Diff program for Windows registry files.</para> 1009 <para> 1010 is a Diff program for Windows registry files. 1011 </para> 877 1012 <indexterm zone="samba regdiff"> 878 1013 <primary sortas="b-regdiff">regdiff</primary> … … 884 1019 <term><command>regpatch</command></term> 885 1020 <listitem> 886 <para>applies registry patches to registry files.</para> 1021 <para> 1022 applies registry patches to registry files. 1023 </para> 887 1024 <indexterm zone="samba regpatch"> 888 1025 <primary sortas="b-regpatch">regpatch</primary> … … 894 1031 <term><command>regshell</command></term> 895 1032 <listitem> 896 <para>is a Windows registry file browser using readline.</para> 1033 <para> 1034 is a Windows registry file browser using readline. 1035 </para> 897 1036 <indexterm zone="samba regshell"> 898 1037 <primary sortas="b-regshell">regshell</primary> … … 904 1043 <term><command>regtree</command></term> 905 1044 <listitem> 906 <para>is a text-mode registry viewer.</para> 1045 <para> 1046 is a text-mode registry viewer. 1047 </para> 907 1048 <indexterm zone="samba regtree"> 908 1049 <primary sortas="b-regtree">regtree</primary> … … 914 1055 <term><command>rpcclient</command></term> 915 1056 <listitem> 916 <para>is used to execute MS-RPC client side functions.</para> 1057 <para> 1058 is used to execute MS-RPC client side functions. 1059 </para> 917 1060 <indexterm zone="samba rpcclient"> 918 1061 <primary sortas="b-rpcclient">rpcclient</primary> … … 924 1067 <term><command>samba</command></term> 925 1068 <listitem> 926 <para>is a server to provide AD and SMB/CIFS services 927 to clients.</para> 1069 <para> 1070 is a server to provide AD and SMB/CIFS services 1071 to clients. 1072 </para> 928 1073 <indexterm zone="samba samba-prog"> 929 1074 <primary sortas="b-samba-prog">samba</primary> … … 935 1080 <term><command>samba_dnsupdate</command></term> 936 1081 <listitem> 937 <para>is used to update our DNS names using TSIG-GSS.</para> 1082 <para> 1083 is used to update our DNS names using TSIG-GSS. 1084 </para> 938 1085 <indexterm zone="samba samba_dnsupdate"> 939 1086 <primary sortas="b-samba_dnsupdate">samba_dnsupdate</primary> … … 945 1092 <term><command>samba_kcc</command></term> 946 1093 <listitem> 947 <para>is a script used to compute your KCC (Knowledge 948 Consistency Checker) topology.</para> 1094 <para> 1095 is a script used to compute your KCC (Knowledge 1096 Consistency Checker) topology. 1097 </para> 949 1098 <indexterm zone="samba samba_kcc"> 950 1099 <primary sortas="b-samba_kcc">samba_kcc</primary> … … 956 1105 <term><command>samba-gpupdate</command></term> 957 1106 <listitem> 958 <para>allows you to edit Microsoft Group Policy Objects (GPOs).</para> 1107 <para> 1108 allows you to edit Microsoft Group Policy Objects (GPOs). 1109 </para> 959 1110 <indexterm zone="samba samba-gpupdate"> 960 1111 <primary sortas="b-samba-gpupdate">samba-gpupdate</primary> … … 966 1117 <term><command>samba-regedit</command></term> 967 1118 <listitem> 968 <para>is a ncurses based tool to manage the Samba registry.</para> 1119 <para> 1120 is a ncurses based tool to manage the Samba registry. 1121 </para> 969 1122 <indexterm zone="samba samba-regedit"> 970 1123 <primary sortas="b-samba-regedit">samba-regedit</primary> … … 976 1129 <term><command>samba_spnupdate</command></term> 977 1130 <listitem> 978 <para>is a script to update the servicePrincipalName 979 names from spn_update_list.</para> 1131 <para> 1132 is a script to update the servicePrincipalName 1133 names from spn_update_list. 1134 </para> 980 1135 <indexterm zone="samba samba_spnupdate"> 981 1136 <primary sortas="b-samba_spnupdate">samba_spnupdate</primary> … … 987 1142 <term><command>samba-tool</command></term> 988 1143 <listitem> 989 <para>is the main Samba administration tool.</para> 1144 <para> 1145 is the main Samba administration tool. 1146 </para> 990 1147 <indexterm zone="samba samba-tool"> 991 1148 <primary sortas="b-samba-tool">samba-tool</primary> … … 997 1154 <term><command>samba_upgradedns</command></term> 998 1155 <listitem> 999 <para>is a Unix SMB/CIFS implementation.</para> 1156 <para> 1157 is a Unix SMB/CIFS implementation. 1158 </para> 1000 1159 <indexterm zone="samba samba_upgradedns"> 1001 1160 <primary sortas="b-samba_upgradedns">samba_upgradedns</primary> … … 1007 1166 <term><command>sharesec</command></term> 1008 1167 <listitem> 1009 <para>manipulates share ACL permissions on SMB file shares.</para> 1168 <para> 1169 manipulates share ACL permissions on SMB file shares. 1170 </para> 1010 1171 <indexterm zone="samba sharesec"> 1011 1172 <primary sortas="b-sharesec">sharesec</primary> … … 1017 1178 <term><command>smbcacls</command></term> 1018 1179 <listitem> 1019 <para>is used to manipulate Windows NT access control lists.</para> 1180 <para> 1181 is used to manipulate Windows NT access control lists. 1182 </para> 1020 1183 <indexterm zone="samba smbcacls"> 1021 1184 <primary sortas="b-smbcacls">smbcacls</primary> … … 1027 1190 <term><command>smbclient</command></term> 1028 1191 <listitem> 1029 <para>is a SMB/CIFS access utility, similar to FTP.</para> 1192 <para> 1193 is a SMB/CIFS access utility, similar to FTP. 1194 </para> 1030 1195 <indexterm zone="samba smbclient"> 1031 1196 <primary sortas="b-smbclient">smbclient</primary> … … 1037 1202 <term><command>smbcontrol</command></term> 1038 1203 <listitem> 1039 <para>is used to control running <command>smbd</command>, 1040 <command>nmbd</command> and <command>winbindd</command> 1041 daemons.</para> 1204 <para> 1205 is used to control running <command>smbd</command>, 1206 <command>nmbd</command> and <command>winbindd</command> daemons. 1207 </para> 1042 1208 <indexterm zone="samba smbcontrol"> 1043 1209 <primary sortas="b-smbcontrol">smbcontrol</primary> … … 1049 1215 <term><command>smbcquotas</command></term> 1050 1216 <listitem> 1051 <para>is used to manipulate Windows NT quotas on 1052 SMB file shares.</para> 1217 <para> 1218 is used to manipulate Windows NT quotas on SMB file shares. 1219 </para> 1053 1220 <indexterm zone="samba smbcquotas"> 1054 1221 <primary sortas="b-smbcquotas">smbcquotas</primary> … … 1060 1227 <term><command>smbd</command></term> 1061 1228 <listitem> 1062 <para>is the main <application>Samba</application> daemon which 1063 provides SMB/CIFS services to clients.</para> 1229 <para> 1230 is the main <application>Samba</application> daemon which 1231 provides SMB/CIFS services to clients. 1232 </para> 1064 1233 <indexterm zone="samba smbd"> 1065 1234 <primary sortas="b-smbd">smbd</primary> … … 1071 1240 <term><command>smbget</command></term> 1072 1241 <listitem> 1073 <para>is a simple utility with <command>wget</command>-like 1074 semantics, that can download files from SMB servers. You can specify 1075 the files you would like to download on the command-line.</para> 1242 <para> 1243 is a simple utility with <command>wget</command>-like semantics, 1244 that can download files from SMB servers. You can specify the 1245 files you would like to download on the command-line. 1246 </para> 1076 1247 <indexterm zone="samba smbget"> 1077 1248 <primary sortas="b-smbget">smbget</primary> … … 1083 1254 <term><command>smbpasswd</command></term> 1084 1255 <listitem> 1085 <para>changes a user's <application>Samba</application> 1086 password.</para> 1256 <para> 1257 changes a user's <application>Samba</application> password. 1258 </para> 1087 1259 <indexterm zone="samba smbpasswd"> 1088 1260 <primary sortas="b-smbpasswd">smbpasswd</primary> … … 1094 1266 <term><command>smbspool</command></term> 1095 1267 <listitem> 1096 <para>sends a print job to an SMB printer.</para> 1268 <para> 1269 sends a print job to an SMB printer. 1270 </para> 1097 1271 <indexterm zone="samba smbspool"> 1098 1272 <primary sortas="b-smbspool">smbspool</primary> … … 1104 1278 <term><command>smbstatus</command></term> 1105 1279 <listitem> 1106 <para>reports current <application>Samba</application> 1107 connections.</para> 1280 <para> 1281 reports current <application>Samba</application> connections. 1282 </para> 1108 1283 <indexterm zone="samba smbstatus"> 1109 1284 <primary sortas="b-smbstatus">smbstatus</primary> … … 1115 1290 <term><command>smbtar</command></term> 1116 1291 <listitem> 1117 <para>is a shell script used for backing up SMB/CIFS shares 1118 directly to Linux tape drives or a file.</para> 1292 <para> 1293 is a shell script used for backing up SMB/CIFS shares 1294 directly to Linux tape drives or a file. 1295 </para> 1119 1296 <indexterm zone="samba smbtar"> 1120 1297 <primary sortas="b-smbtar">smbtar</primary> … … 1127 1304 <term><command>smbta-util</command></term> 1128 1305 <listitem> 1129 <para>is a tool to ease the configuration of the 1130 vfs_smb_traffic_analyzer module regarding data encryption.</para> 1306 <para> 1307 is a tool to ease the configuration of the 1308 vfs_smb_traffic_analyzer module regarding data encryption. 1309 </para> 1131 1310 <indexterm zone="samba smbta-util"> 1132 1311 <primary sortas="b-smbta-util">smbta-util</primary> … … 1139 1318 <term><command>smbtorture</command></term> 1140 1319 <listitem> 1141 <para>is a testsuite that runs several tests against a SMB 1142 server.</para> 1320 <para> 1321 is a testsuite that runs several tests against a SMB server. 1322 </para> 1143 1323 <indexterm zone="samba smbtorture"> 1144 1324 <primary sortas="b-smbtorture">smbtorture</primary> … … 1150 1330 <term><command>smbtree</command></term> 1151 1331 <listitem> 1152 <para>is a text-based SMB network browser.</para> 1332 <para> 1333 is a text-based SMB network browser. 1334 </para> 1153 1335 <indexterm zone="samba smbtree"> 1154 1336 <primary sortas="b-smbtree">smbtree</primary> … … 1160 1342 <term><command>tdbbackup</command></term> 1161 1343 <listitem> 1162 <para>is a tool for backing up or validating the integrity of 1163 <application>Samba</application> <filename>.tdb</filename> 1164 files.</para> 1344 <para> 1345 is a tool for backing up or validating the integrity of 1346 <application>Samba</application> <filename>.tdb</filename> files. 1347 </para> 1165 1348 <indexterm zone="samba tdbbackup"> 1166 1349 <primary sortas="b-tdbbackup">tdbbackup</primary> … … 1172 1355 <term><command>tdbdump</command></term> 1173 1356 <listitem> 1174 <para> is a tool used to print the contents of a 1175 <application>Samba</application> <filename>.tdb</filename> 1176 file.</para> 1357 <para> 1358 is a tool used to print the contents of a 1359 <application>Samba</application> <filename>.tdb</filename> file. 1360 </para> 1177 1361 <indexterm zone="samba tdbdump"> 1178 1362 <primary sortas="b-tdbdump">tdbdump</primary> … … 1184 1368 <term><command>tdbrestore</command></term> 1185 1369 <listitem> 1186 <para> is a tool for creating a <application>Samba</application> 1187 <filename>.tdb</filename> file out of a ntdbdump.</para> 1370 <para> 1371 is a tool for creating a <application>Samba</application> 1372 <filename>.tdb</filename> file out of a ntdbdump. 1373 </para> 1188 1374 <indexterm zone="samba tdbrestore"> 1189 1375 <primary sortas="b-tdbrestore">tdbrestore</primary> … … 1195 1381 <term><command>tdbtool</command></term> 1196 1382 <listitem> 1197 <para>is a tool which allows simple database manipulation from the 1198 command line.</para> 1383 <para> 1384 is a tool which allows simple database manipulation from the 1385 command line. 1386 </para> 1199 1387 <indexterm zone="samba tdbtool"> 1200 1388 <primary sortas="b-tdbtool">tdbtool</primary> … … 1206 1394 <term><command>testparm</command></term> 1207 1395 <listitem> 1208 <para>checks an <filename>smb.conf</filename> file for proper 1209 syntax.</para> 1396 <para> 1397 checks an <filename>smb.conf</filename> file for proper syntax. 1398 </para> 1210 1399 <indexterm zone="samba testparm"> 1211 1400 <primary sortas="b-testparm">testparm</primary> … … 1217 1406 <term><command>wbinfo</command></term> 1218 1407 <listitem> 1219 <para>queries a running <command>winbindd</command> daemon.</para> 1408 <para> 1409 queries a running <command>winbindd</command> daemon. 1410 </para> 1220 1411 <indexterm zone="samba wbinfo"> 1221 1412 <primary sortas="b-wbinfo">wbinfo</primary> … … 1227 1418 <term><command>winbindd</command></term> 1228 1419 <listitem> 1229 <para>resolves names from Windows NT servers.</para> 1420 <para> 1421 resolves names from Windows NT servers. 1422 </para> 1230 1423 <indexterm zone="samba winbindd"> 1231 1424 <primary sortas="b-winbindd">winbindd</primary> … … 1237 1430 <term><filename class='libraryfile'>libnss_winbind.so</filename></term> 1238 1431 <listitem> 1239 <para>provides Name Service Switch API functions for resolving names 1240 from NT servers.</para> 1432 <para> 1433 provides Name Service Switch API functions for resolving names 1434 from NT servers. 1435 </para> 1241 1436 <indexterm zone="samba libnss_winbind"> 1242 1437 <primary sortas="c-libnss_winbind">libnss_winbind.so</primary> … … 1248 1443 <term><filename class='libraryfile'>libnss_wins.so</filename></term> 1249 1444 <listitem> 1250 <para>provides API functions for Samba's implementation of the 1251 Windows Internet Naming Service.</para> 1445 <para> 1446 provides API functions for Samba's implementation of the 1447 Windows Internet Naming Service. 1448 </para> 1252 1449 <indexterm zone="samba libnss_wins"> 1253 1450 <primary sortas="c-libnss_wins">libnss_wins.so</primary> … … 1259 1456 <term><filename class='libraryfile'>libnetapi.so</filename></term> 1260 1457 <listitem> 1261 <para>provides the API functions for the administration tools used 1262 for Samba and remote CIFS servers.</para> 1458 <para> 1459 provides the API functions for the administration tools used 1460 for Samba and remote CIFS servers. 1461 </para> 1263 1462 <indexterm zone="samba libnetapi"> 1264 1463 <primary sortas="c-libnetapi">libnetapi.so</primary> … … 1270 1469 <term><filename class='libraryfile'>libsmbclient.so</filename></term> 1271 1470 <listitem> 1272 <para>provides the API functions for the Samba SMB client tools.</para> 1471 <para> 1472 provides the API functions for the Samba SMB client tools. 1473 </para> 1273 1474 <indexterm zone="samba libsmbclient"> 1274 1475 <primary sortas="c-libsmbclient">libsmbclient.so</primary> … … 1280 1481 <term><filename class='libraryfile'>libsmbsharemodes.so</filename></term> 1281 1482 <listitem> 1282 <para>provides API functions for accessing SMB share modes 1283 (locks etc.)</para> 1483 <para> 1484 provides API functions for accessing SMB share modes (locks etc.) 1485 </para> 1284 1486 <indexterm zone="samba libsmbsharemodes"> 1285 1487 <primary sortas="c-libsmbsharemodes">libsmbsharemodes.so</primary> … … 1291 1493 <term><filename class='libraryfile'>libwbclient.so</filename></term> 1292 1494 <listitem> 1293 <para>provides API functions for Windows domain client services.</para> 1495 <para> 1496 provides API functions for Windows domain client services. 1497 </para> 1294 1498 <indexterm zone="samba libwbclient"> 1295 1499 <primary sortas="c-libwbclient">libwbclient.so</primary> -
networking/netprogs/wget.xml
rdcee7a56 rb51fe6e 113 113 114 114 <!-- libwww-perl/HTTP-Daemon/#21 --> 115 <para>HTTPS tests are known to fail if Perl module IO::Socket::INET6 116 is installed.</para> 115 <para> 116 HTTPS tests are known to fail if Perl module IO::Socket::INET6 117 is installed. 118 </para> 117 119 118 120 <para> -
networking/netprogs/wireless-tools.xml
rdcee7a56 rb51fe6e 30 30 <title>Introduction to Wireless Tools</title> 31 31 32 <para>The Wireless Extension (WE) is a generic API in the Linux kernel 33 allowing a driver to expose configuration and statistics specific to common 34 Wireless LANs to user space. A single set of tools can support all the 35 variations of Wireless LANs, regardless of their type as long as the 36 driver supports Wireless Extensions. WE parameters may also be changed on 37 the fly without restarting the driver (or Linux).</para> 38 39 <para>The <application>Wireless Tools</application> (WT) package is a set 40 of tools allowing manipulation of the Wireless Extensions. They use a 41 textual interface to support the full Wireless Extension.</para> 32 <para> 33 The Wireless Extension (WE) is a generic API in the Linux kernel allowing 34 a driver to expose configuration and statistics specific to common 35 Wireless LANs to user space. A single set of tools can support all the 36 variations of Wireless LANs, regardless of their type as long as the 37 driver supports Wireless Extensions. WE parameters may also be changed on 38 the fly without restarting the driver (or Linux). 39 </para> 40 41 <para> 42 The <application>Wireless Tools</application> (WT) package is a set 43 of tools allowing manipulation of the Wireless Extensions. They use a 44 textual interface to support the full Wireless Extension. 45 </para> 42 46 43 47 &lfs91_checked; … … 46 50 <itemizedlist spacing='compact'> 47 51 <listitem> 48 <para>Download (HTTP): <ulink url="&wireless-download-http;"/></para> 49 </listitem> 50 <listitem> 51 <para>Download (FTP): <ulink url="&wireless-download-ftp;"/></para> 52 </listitem> 53 <listitem> 54 <para>Download MD5 sum: &wireless-md5sum;</para> 55 </listitem> 56 <listitem> 57 <para>Download size: &wireless-size;</para> 58 </listitem> 59 <listitem> 60 <para>Estimated disk space required: &wireless-buildsize;</para> 61 </listitem> 62 <listitem> 63 <para>Estimated build time: &wireless-time;</para> 52 <para> 53 Download (HTTP): <ulink url="&wireless-download-http;"/> 54 </para> 55 </listitem> 56 <listitem> 57 <para> 58 Download (FTP): <ulink url="&wireless-download-ftp;"/> 59 </para> 60 </listitem> 61 <listitem> 62 <para> 63 Download MD5 sum: &wireless-md5sum; 64 </para> 65 </listitem> 66 <listitem> 67 <para> 68 Download size: &wireless-size; 69 </para> 70 </listitem> 71 <listitem> 72 <para> 73 Estimated disk space required: &wireless-buildsize; 74 </para> 75 </listitem> 76 <listitem> 77 <para> 78 Estimated build time: &wireless-time; 79 </para> 64 80 </listitem> 65 81 </itemizedlist> … … 88 104 </indexterm> 89 105 90 <para>To use <application>Wireless Tools</application>, the kernel must 91 have the appropriate drivers and other support available. The appropriate 92 bus must also be available. For many laptops, the PCMCIA bus 93 (CONFIG_PCCARD) needs to be built. In some cases, this bus support will 94 also need to be built for embedded wireless cards. The appropriate bridge 95 support also needs to be built. For many modern laptops, the CardBus host 96 bridge (CONFIG_YENTA) will be needed.</para> 97 98 <para>In addition to the bus, the actual driver for the specific wireless 99 card must also be available. There are many wireless cards and they don't 100 all work with Linux. The first place to look for card support is the kernel. 101 The drivers are located in Device Drivers → Network Device Support 102 → Wireless LAN (non-hamradio). There are also external drivers 103 available for some very common cards. For more information, look 104 at the user notes.</para> 105 106 <para>After the correct drivers are loaded, the interface will 107 appear in <filename>/proc/net/wireless</filename>.</para> 106 <para> 107 To use <application>Wireless Tools</application>, the kernel must have 108 the appropriate drivers and other support available. The appropriate bus 109 must also be available. For many laptops, the PCMCIA bus (CONFIG_PCCARD) 110 needs to be built. In some cases, this bus support will also need to be 111 built for embedded wireless cards. The appropriate bridge support also 112 needs to be built. For many modern laptops, the CardBus host bridge 113 (CONFIG_YENTA) will be needed. 114 </para> 115 116 <para> 117 In addition to the bus, the actual driver for the specific wireless card 118 must also be available. There are many wireless cards and they don't 119 all work with Linux. The first place to look for card support is the 120 kernel. The drivers are located in Device Drivers → Network Device 121 Support → Wireless LAN (non-hamradio). There are also external 122 drivers available for some very common cards. For more information, 123 look at the user notes. 124 </para> 125 126 <para> 127 After the correct drivers are loaded, the interface will 128 appear in <filename>/proc/net/wireless</filename>. 129 </para> 108 130 109 131 </sect2> … … 112 134 <title>Installation of Wireless Tools</title> 113 135 114 <para>First, apply a patch that fixes a problem when numerous 115 networks are available:</para> 136 <para> 137 First, apply a patch that fixes a problem when numerous 138 networks are available: 139 </para> 116 140 117 141 <screen><userinput>patch -Np1 -i ../wireless_tools-&wireless-tools-version;-fix_iwlist_scanning-1.patch</userinput></screen> 118 142 119 <para>To install <application>Wireless Tools</application>, 120 use the following commands:</para> 143 <para> 144 To install <application>Wireless Tools</application>, 145 use the following commands: 146 </para> 121 147 122 148 <screen><userinput>make</userinput></screen> 123 149 124 <para>This package does not come with a test suite.</para> 125 126 <para>Now, as the <systemitem class="username">root</systemitem> user:</para> 150 <para> 151 This package does not come with a test suite. 152 </para> 153 154 <para> 155 Now, as the <systemitem class="username">root</systemitem> user: 156 </para> 127 157 128 158 <screen role="root"><userinput>make PREFIX=/usr INSTALL_MAN=/usr/share/man install</userinput></screen> … … 133 163 <title>Command Explanations</title> 134 164 135 <para><command>INSTALL_MAN=/usr/share/man</command>: Install manual pages 136 in /usr/share/man instead of /usr/man</para> 165 <para> 166 <command>INSTALL_MAN=/usr/share/man</command>: Install manual pages 167 in <filename class="directory">/usr/share/man</filename> instead of 168 <filename class="directory">/usr/man</filename>. 169 </para> 137 170 138 171 </sect2> … … 162 195 <term><command>ifrename</command></term> 163 196 <listitem> 164 <para>renames network interfaces based on various static criteria.</para> 197 <para> 198 renames network interfaces based on various static criteria. 199 </para> 165 200 <indexterm zone="wireless_tools ifrename"> 166 201 <primary sortas="b-ifrename">ifrename</primary> … … 172 207 <term><command>iwconfig</command></term> 173 208 <listitem> 174 <para>configures a wireless network interface.</para> 209 <para> 210 configures a wireless network interface. 211 </para> 175 212 <indexterm zone="wireless_tools iwconfig"> 176 213 <primary sortas="b-iwconfig">iwconfig</primary> … … 182 219 <term><command>iwevent</command></term> 183 220 <listitem> 184 <para>displays wireless events generated by drivers and setting 185 changes.</para> 221 <para> 222 displays wireless events generated by drivers and setting changes. 223 </para> 186 224 <indexterm zone="wireless_tools iwevent"> 187 225 <primary sortas="b-iwevent">iwevent</primary> … … 193 231 <term><command>iwgetid</command></term> 194 232 <listitem> 195 <para>reports ESSID, NWID or AP/Cell Address of wireless networks.</para> 233 <para> 234 reports ESSID, NWID or AP/Cell Address of wireless networks. 235 </para> 196 236 <indexterm zone="wireless_tools iwgetid"> 197 237 <primary sortas="b-iwgetid">iwgetid</primary> … … 203 243 <term><command>iwlist</command></term> 204 244 <listitem> 205 <para>gets detailed wireless information from a wireless interface.</para> 245 <para> 246 gets detailed wireless information from a wireless interface. 247 </para> 206 248 <indexterm zone="wireless_tools iwlist"> 207 249 <primary sortas="b-iwlist">iwlist</primary> … … 213 255 <term><command>iwpriv</command></term> 214 256 <listitem> 215 <para>configures optional (private) parameters of a wireless network 216 interface.</para> 257 <para> 258 configures optional (private) parameters of a wireless network 259 interface. 260 </para> 217 261 <indexterm zone="wireless_tools iwpriv"> 218 262 <primary sortas="b-iwpriv">iwpriv</primary> … … 224 268 <term><command>iwspy</command></term> 225 269 <listitem> 226 <para>gets wireless statistics from specific node.</para> 270 <para> 271 gets wireless statistics from specific node. 272 </para> 227 273 <indexterm zone="wireless_tools iwspy"> 228 274 <primary sortas="b-iwspy">iwspy</primary> … … 234 280 <term><filename class='libraryfile'>libiw.so</filename></term> 235 281 <listitem> 236 <para>contains functions required by the wireless programs and 237 provides an API for other programs.</para> 282 <para> 283 contains functions required by the wireless programs and 284 provides an API for other programs. 285 </para> 238 286 <indexterm zone="wireless_tools libiw"> 239 287 <primary sortas="c-libiw">libiw.so</primary> -
networking/netprogs/wpa_supplicant.xml
rdcee7a56 rb51fe6e 206 206 </para> 207 207 208 <note><para>The following directory name is labelled qt4, but 209 is compatible with <xref linkend="qt5"/>.</para></note> 208 <note> 209 <para> 210 The following directory name is labelled qt4, but 211 is compatible with <xref linkend="qt5"/>. 212 </para> 213 </note> 210 214 211 215 <screen><userinput>pushd wpa_gui-qt4 && … … 315 319 To connect to an access point that uses a password, you need to put 316 320 the pre-shared key in 317 <phrase revision="sysv"><filename> 318 /etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</filename>.</phrase> 319 <phrase revision="systemd"><filename> 320 /etc/wpa_supplicant/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</filename>.</phrase> 321 <phrase revision="sysv"> 322 <filename> 323 /etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf 324 </filename>. 325 </phrase> 326 <phrase revision="systemd"> 327 <filename> 328 /etc/wpa_supplicant/wpa_supplicant-<replaceable>wifi0</replaceable>.conf 329 </filename>. 330 </phrase> 321 331 SSID is the string that the access point/router transmits to 322 332 identify itself. Run the following command as the … … 324 334 </para> 325 335 326 <screen role=" root" revision="sysv"><userinput>wpa_passphrase <replaceable>SSID</replaceable> <replaceable>SECRET_PASSWORD</replaceable> > /etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</userinput></screen>327 328 <screen role=" root" revision="systemd"><userinput>install -v -dm755 /etc/wpa_supplicant &&336 <screen role="nodump" revision="sysv"><userinput>wpa_passphrase <replaceable>SSID</replaceable> <replaceable>SECRET_PASSWORD</replaceable> > /etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</userinput></screen> 337 338 <screen role="nodump" revision="systemd"><userinput>install -v -dm755 /etc/wpa_supplicant && 329 339 wpa_passphrase <replaceable>SSID</replaceable> <replaceable>SECRET_PASSWORD</replaceable> > /etc/wpa_supplicant/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</userinput></screen> 330 340 331 341 <para> 332 <phrase revision="sysv"><filename>/etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf </filename></phrase> 333 <phrase revision="systemd"><filename>/etc/wpa_supplicant/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</filename></phrase> 342 <phrase revision="sysv"> 343 <filename> 344 /etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf 345 </filename> 346 </phrase> 347 <phrase revision="systemd"> 348 <filename> 349 /etc/wpa_supplicant/wpa_supplicant-<replaceable>wifi0</replaceable>.conf 350 </filename> 351 </phrase> 334 352 can hold the details of several access points. When 335 353 <command>wpa_supplicant</command> is started, it will scan for the … … 340 358 If you want to connect to an access point that isn't password 341 359 protected, put an entry like this in 342 <phrase revision="sysv" ><filename>/etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</filename></phrase> 343 <phrase revision="systemd"><filename>/etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</filename></phrase>. 360 <phrase revision="sysv"> 361 <filename> 362 /etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf 363 </filename> 364 </phrase> 365 <phrase revision="systemd"> 366 <filename> 367 /etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf 368 </filename> 369 </phrase>. 344 370 Replace "Some-SSID" with the SSID of the access point/router. 345 371 </para> … … 350 376 }</screen> 351 377 352 <para>Connecting to a new access point that is not in the configuration 353 file can be accomplished manually via the command line or GUI, but it 354 must be done via a privileged user. To do that, add the following to the 355 configuration file:</para> 378 <para> 379 Connecting to a new access point that is not in the configuration 380 file can be accomplished manually via the command line or GUI, but it 381 must be done via a privileged user. To do that, add the following to 382 the configuration file: 383 </para> 356 384 357 385 <screen>ctrl_interface=DIR=/run/wpa_supplicant GROUP=<privileged group>
Note:
See TracChangeset
for help on using the changeset viewer.