Changeset 7b478500
- Timestamp:
- 06/11/2016 05:26:20 AM (7 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 7.10, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, basic, bdubbs/svn, elogind, kea, ken/inkscape-core-mods, lazarus, lxqt, nosym, perl-modules, plabs/python-mods, qt5new, trunk, upgradedb, xry111/intltool, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- cec6657e
- Parents:
- a9e71e2
- Location:
- networking/netprogs
- Files:
-
- 8 edited
Legend:
- Unmodified
- Added
- Removed
-
networking/netprogs/cifsutils.xml
ra9e71e2 r7b478500 99 99 commands:</para> 100 100 101 <screen ><userinput>./configure --prefix=/usr \101 <screen revision="sysv"><userinput>./configure --prefix=/usr \ 102 102 --disable-pam \ 103 103 --disable-systemd && 104 make</userinput></screen> 105 106 <screen revision="systemd"><userinput>./configure --prefix=/usr \ 107 --disable-pam && 104 108 make</userinput></screen> 105 109 … … 120 124 PAM support.</para> 121 125 122 <para><parameter>--disable-systemd</parameter>: Disable systemd 123 specific behavior for <command>mount.cifs</command>. Remove it for 124 systems running with systemd.</para> 126 <para revision="sysv"><parameter>--disable-systemd</parameter>: 127 Disable systemd specific behavior for 128 <command>mount.cifs</command>. Remove it for systems running with 129 systemd.</para> 125 130 126 131 <para><option>--with-pamdir=/lib/security</option>: Install the PAM -
networking/netprogs/netfs.xml
ra9e71e2 r7b478500 36 36 <screen role='root'><userinput>make install-netfs</userinput></screen> 37 37 38 <para revision="systemd">TBA</para>39 38 </sect1> -
networking/netprogs/nfs-utils.xml
ra9e71e2 r7b478500 70 70 <xref linkend="libevent"/>, 71 71 <xref linkend="sqlite"/> and 72 <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/">libnfsidmap</ulink> (for NFSv4 support), 72 <phrase revision="sysv"><ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/">libnfsidmap</ulink></phrase> 73 <phrase revision="systemd"><xref linkend="libnfsidmap"/></phrase> 74 (for NFSv4 support), 73 75 <xref linkend="mitkrb"/> or 74 76 <ulink url="http://www.citi.umich.edu/projects/nfsv4/linux/">libgssapi</ulink>, and … … 218 220 219 221 <sect4 id="nfs-utils-server-init"> 220 <title>Boot Script</title> 221 222 <para>Install the <filename>/etc/rc.d/init.d/nfs-server</filename> 223 init script included in the <xref linkend="bootscripts" revision="sysv"/> 222 <title><phrase revision="sysv">Boot Script</phrase> 223 <phrase revision="systemd">Systemd Units</phrase></title> 224 225 <para>Install the 226 <phrase revision="sysv"><filename>/etc/rc.d/init.d/nfs-server</filename> 227 init script</phrase> 228 <phrase revision="systemd">NFSv4 server units</phrase> 229 included in the <xref linkend="bootscripts" revision="sysv"/> 224 230 <xref linkend="systemd-units" revision="systemd"/> package 225 231 to start the server at boot.</para> 226 232 233 <screen role="root" revision="systemd"><userinput>make install-nfsv4-server</userinput></screen> 234 235 <para revision="systemd"> 236 If you have disabled NFSv4 support, run the following command as the 237 <systemitem class="username">root</systemitem> user to omit the NFSv4 238 specific systemd units: 239 </para> 240 241 <!-- both --> 227 242 <screen role="root"><userinput>make install-nfs-server</userinput></screen> 228 243 229 <indexterm zone="nfs-utils nfs-utils-server-init" >244 <indexterm zone="nfs-utils nfs-utils-server-init" revision="sysv"> 230 245 <primary sortas="f-nfs-server">nfs-server</primary> 231 246 </indexterm> 232 247 233 <para>Now create the <filename>/etc/sysconfig/nfs-server</filename> 234 configuration file:</para> 235 236 <screen role="root"><userinput>cat > /etc/sysconfig/nfs-server << "EOF" 248 <para revision="sysv">Now create the 249 <filename>/etc/sysconfig/nfs-server</filename> configuration file: 250 </para> 251 252 <screen role="root" revision="sysv"><userinput>cat > /etc/sysconfig/nfs-server << "EOF" 237 253 <literal>PORT="2049" 238 254 PROCESSES="8" … … 241 257 EOF</userinput></screen> 242 258 243 <note><para>The above parameters may be optionally placed in 244 <filename>/etc/sysconfig/rc.site</filename>.</para></note> 245 246 <indexterm zone="nfs-utils nfs-utils-server-init"> 259 <note revision="sysv"> 260 <para>The above parameters may be optionally placed in 261 <filename>/etc/sysconfig/rc.site</filename>. 262 </para> 263 </note> 264 265 <indexterm zone="nfs-utils nfs-utils-server-init" revision="sysv"> 247 266 <primary 248 267 sortas="e-etc-sysconfig-nfs-server">/etc/sysconfig/nfs-server</primary> 249 268 </indexterm> 269 270 <para revision="systemd"> 271 You can edit the <filename>/etc/default/nfs-utils</filename> 272 file to change the startup options for NFS daemons. Defaults 273 should be fine for most use cases. 274 </para> 275 276 <indexterm zone="nfs-utils nfs-utils-server-init" revision="systemd"> 277 <primary sortas="e-etc-default-nfs-utils">/etc/default/nfs-utils</primary> 278 </indexterm> 279 280 250 281 251 282 </sect4> … … 287 318 288 319 <sect4 id="nfs-utils-client-init"> 289 <title>Boot Script</title> 290 291 <note><para>The following boot script is not required if the 292 nfs-server script is installed.</para></note> 293 294 <para>Install the <filename>/etc/rc.d/init.d/nfs-client</filename> init 295 script included in the <xref linkend="bootscripts" revision="sysv"/> 320 <title><phrase revision="sysv">Boot Script</phrase> 321 <phrase revision="systemd">Systemd Units</phrase></title> 322 323 <note> 324 <para> 325 The following <phrase revision="sysv">boot script is</phrase> 326 <phrase revision="systemd">systemd units are</phrase> not required 327 if the nfs-server <phrase revision="sysv">script is</phrase> 328 <phrase revision="systemd">units are</phrase> installed. 329 </para> 330 </note> 331 332 <para>Install the 333 <phrase revision="sysv"> 334 <filename>/etc/rc.d/init.d/nfs-client</filename> init script</phrase> 335 <phrase revision="systemd">units</phrase> included in the 336 <xref linkend="bootscripts" revision="sysv"/> 296 337 <xref linkend="systemd-units" revision="systemd"/> package to start 297 338 the client services at boot.</para> … … 308 349 <xref linkend="postlfs-config-netfs"/>.</para> 309 350 310 <indexterm zone="nfs-utils nfs-utils-client-config" >351 <indexterm zone="nfs-utils nfs-utils-client-config" revision="sysv"> 311 352 <primary sortas="f-netfs">netfs</primary> 312 353 </indexterm> -
networking/netprogs/ntp.xml
ra9e71e2 r7b478500 215 215 216 216 <para>If you choose Option one, then install the 217 <filename>/etc/rc.d/init.d/ntp</filename> 218 init script included in the 217 <phrase revision="sysv"><filename>/etc/rc.d/init.d/ntp</filename> 218 init script</phrase> 219 <phrase revision="systemd"><filename>ntpd.service</filename> unit</phrase> 220 included in the 219 221 <xref linkend="bootscripts" revision="sysv"/> 220 222 <xref linkend="systemd-units" revision="systemd"/> package.</para> 221 223 222 <indexterm zone="ntp ntp-init" >224 <indexterm zone="ntp ntp-init" revision="sysv"> 223 225 <primary sortas="f-ntp">ntp</primary> 226 </indexterm> 227 228 <indexterm zone="ntp ntp-init" revision="systemd"> 229 <primary sortas="f-ntpd">ntpd.service</primary> 224 230 </indexterm> 225 231 … … 232 238 <screen><literal>ntpd -q</literal></screen> 233 239 234 <para>Execute the following command if you would like to set the 235 hardware clock to the current system time at shutdown and reboot:</para> 236 237 <screen role="root"><userinput>ln -v -sf ../init.d/setclock /etc/rc.d/rc0.d/K46setclock && 240 <para revision="sysv">Execute the following command if you would like to 241 set the hardware clock to the current system time at shutdown and 242 reboot:</para> 243 244 <screen role="root" revision="sysv"><userinput>ln -v -sf ../init.d/setclock /etc/rc.d/rc0.d/K46setclock && 238 245 ln -v -sf ../init.d/setclock /etc/rc.d/rc6.d/K46setclock</userinput></screen> 239 246 240 <para>The other way around is already set up by LFS.</para> 247 <para revision="sysv">The other way around is already set up by 248 LFS.</para> 241 249 242 250 </sect3> -
networking/netprogs/rpcbind.xml
ra9e71e2 r7b478500 83 83 <title>Installation of rpcbind</title> 84 84 85 <para revision="systemd"> 86 There should be a dedicated user and group to take control 87 of the <command>rpcbind</command> daemon after it is started. 88 Issue the following commands as the 89 <systemitem class="username">root</systemitem> user: 90 </para> 91 92 <screen role="root" revision="systemd"><userinput>groupadd -g 28 rpc && 93 useradd -c "RPC Bind Daemon Owner" -d /dev/null -g rpc \ 94 -s /bin/false -u 28 rpc</userinput></screen> 95 85 96 <!-- Packages should adapt to standards, not the other way around --> 86 97 <para>In order to get <application>rpcbind</application> to work … … 102 113 <screen revision="systemd"><userinput>patch -Np1 -i ../rpcbind-&rpcbind-version;-tirpc_fix-1.patch && 103 114 104 ./configure --prefix=/usr 105 --bindir=/sbin 106 --with-rpcuser=r oot&&115 ./configure --prefix=/usr \ 116 --bindir=/sbin \ 117 --with-rpcuser=rpc && 107 118 make</userinput></screen> 108 119 … … 118 129 <title>Command Explanations</title> 119 130 120 <para ><command>--with-rpcuser=root</command>: This works around an error in121 the configure script.</para>131 <para revision="sysv"><command>--with-rpcuser=root</command>: This works 132 around an error in the configure script.</para> 122 133 123 134 <para revision="sysv"><command>--without-systemdsystemunitdir</command>: 124 135 BLFS does not support systemd.</para> 125 136 137 <para revision="systemd"><parameter>--with-rpcuser=rpc</parameter>: 138 This switch is used so the <command>rpcbind</command> daemon will 139 run as an unprivileged user instead of the 140 <systemitem class="username">root</systemitem> user.</para> 141 126 142 </sect2> 127 143 … … 130 146 131 147 <sect3 id="rpcbind-init"> 132 <title>Boot Script</title> 133 134 <para>Install the <filename>/etc/rc.d/init.d/rpcbind</filename> init 135 script included in the <xref linkend="bootscripts" revision="sysv"/> 148 <title><phrase revision="sysv">Boot Script</phrase> 149 <phrase revision="systemd">Systemd Unit</phrase></title> 150 151 <para>Install the 152 <phrase revision="sysv"><filename>/etc/rc.d/init.d/rpcbind</filename> 153 init script</phrase> 154 <phrase revision="systemd"><filename>rpcbind.service</filename> 155 unit</phrase> included in the 156 <xref linkend="bootscripts" revision="sysv"/> 136 157 <xref linkend="systemd-units" revision="systemd"/> package.</para> 137 158 138 <indexterm zone="rpcbind rpcbind-init" >159 <indexterm zone="rpcbind rpcbind-init" revision="sysv"> 139 160 <primary sortas="f-rpcbind">rpcbind</primary> 161 </indexterm> 162 163 <indexterm zone="rpcbind rpcbind-init" revision="systemd"> 164 <primary sortas="f-rpcbind">rpcbind.service</primary> 140 165 </indexterm> 141 166 -
networking/netprogs/rsync.xml
ra9e71e2 r7b478500 165 165 166 166 <sect3 id="rsync-init"> 167 <title>Boot Script</title> 167 <title><phrase revision="sysv">Boot Script</phrase> 168 <phrase revision="systemd">Systemd Unit</phrase></title> 168 169 169 170 <para>Note that you only want to start the 170 171 <application>rsync</application> server if you want to provide an 171 172 <application>rsync</application> archive on your local machine. 172 You don't need this script to run the 173 You don't need this <phrase revision="sysv">script</phrase> 174 <phrase revision="systemd">unit</phrase> to run the 173 175 <application>rsync</application> client.</para> 174 176 175 <para>Install the <filename>/etc/rc.d/init.d/rsyncd</filename> init 176 script included in the 177 <para>Install the 178 <phrase revision="sysv"><filename>/etc/rc.d/init.d/rsyncd</filename> init 179 script</phrase> 180 <phrase revision="systemd"><filename>rsyncd.service</filename> 181 unit</phrase> included in the 177 182 <xref linkend="bootscripts" revision="sysv"/> 178 183 <xref linkend="systemd-units" revision="systemd"/> package.</para> 179 184 180 185 <screen role="root"><userinput>make install-rsyncd</userinput></screen> 186 187 <note revision="systemd"> 188 <para>This package comes with two types of units: A service file and a 189 socket file. The service file will start rsync daemon once at boot 190 and it will keep running until the system shuts down. The socket file 191 will make systemd listen on rsync port (Default 873, needs to be 192 edited for anything else) and will start rsync daemon when something 193 tries to connect to that port and stop the daemon when the connection 194 is terminated. This is called socket activation and is analogous to 195 using <application>{,x}inetd</application> on a SysVinit based 196 system.</para> 197 198 199 <para>By default, the first method is used - rsync daemon is started 200 at boot and stopped at shutdown. If the socket method is desired, you 201 need to run as the 202 <systemitem class="username">root</systemitem> user:</para> 203 204 <screen role="root"><userinput>systemctl stop rsyncd && 205 systemctl disable rsyncd && 206 systemctl enable rsyncd.socket && 207 systemctl start rsyncd.socket</userinput></screen> 208 209 <para>Note that socket method is only useful for remote backups. For 210 local backups you'll need the service method.</para> 211 </note> 181 212 182 213 </sect3> -
networking/netprogs/samba.xml
ra9e71e2 r7b478500 121 121 commands:</para> 122 122 123 <screen ><userinput>./configure \123 <screen revision="sysv"><userinput>./configure \ 124 124 --prefix=/usr \ 125 125 --sysconfdir=/etc \ … … 130 130 --without-ad-dc \ 131 131 --without-systemd && 132 make</userinput></screen> 133 134 <screen revision="systemd"><userinput>./configure \ 135 --prefix=/usr \ 136 --sysconfdir=/etc \ 137 --localstatedir=/var \ 138 --with-piddir=/run/samba \ 139 --with-pammodulesdir=/lib/security \ 140 --enable-fhs && 132 141 make</userinput></screen> 133 142 … … 183 192 a manner compliant with the Filesystem Hierarchy Standard (FHS).</para> 184 193 185 <para ><parameter>--without-systemd</parameter>: Disable194 <para revision="sysv"><parameter>--without-systemd</parameter>: Disable 186 195 <application>systemd</application> integration, which is not part of 187 196 LFS/BLFS. If you use <application>systemd</application>, replace by 188 197 <parameter>--with-systemd</parameter>.</para> 189 198 190 <para ><option>--without-ad-dc</option>: Disable Active Directory Domain191 Controller functionality. See <ulink199 <para revision="sysv"><option>--without-ad-dc</option>: Disable Active 200 Directory Domain Controller functionality. See <ulink 192 201 url="https://wiki.samba.org/index.php/Setup_a_Samba_Active_Directory_Domain_Controller"> 193 202 Setup a Samba Active Directory Domain Controller</ulink> for detailed 194 information. 203 information.</para> 195 204 196 205 <para><option>--with-selftest-prefix=SELFTEST_PREFIX</option>: This option … … 203 212 <para><command>ln -v -sf ../../lib/libnss_winbind.so.2 /usr/lib/libnss_winbind.so</command> 204 213 and <command>ln -v -sf ../../lib/libnss_wins.so.2 /usr/lib/libnss_wins.so</command>: 205 These symlinks are required when applicates build against these libraries.</para> 214 These symlinks are required when applicationss build against these 215 libraries.</para> 206 216 207 217 <para><command>install -v -m644 examples/LDAP/* /etc/openldap/schema</command>: … … 407 417 </sect4> 408 418 409 <sect4 id="samba-init" >419 <sect4 id="samba-init" revision="sysv"> 410 420 <title>Boot Script</title> 411 421 412 422 <para>For your convenience, boot scripts have been provided for 413 423 <application>Samba</application>. There are two included in the 414 <xref linkend="bootscripts" revision="sysv"/> 415 <xref linkend="systemd-units" revision="systemd"/> package. The first, 424 <xref linkend="bootscripts"/> package. The first, 416 425 <filename>samba</filename>, will start the <command>smbd</command> 417 426 and <command>nmbd</command> daemons needed to provide SMB/CIFS … … 453 462 <screen role="root"><userinput>make install-winbindd</userinput></screen> 454 463 455 </sect4> 464 </sect4> 465 466 <sect4 id="samba-init-sysd" revision="systemd"> 467 <title>Systemd Units</title> 468 469 <para>The default <application>Samba</application> installation uses the 470 <systemitem class='username'>nobody</systemitem> user for guest access 471 to the server. This can be overridden by setting the 472 <option>guest account =</option> parameter in the 473 <filename>/etc/samba/smb.conf</filename> file. If you utilize the 474 <option>guest account =</option> parameter, ensure this user exists in 475 the <filename>/etc/passwd</filename> file.</para> 476 477 <para> 478 To start the <application>Samba</application> daemons at boot, 479 install the systemd units from the <xref linkend="systemd-units"/> 480 package by running the following command as the 481 <systemitem class="username">root</systemitem> user: 482 </para> 483 484 <indexterm zone="samba samba-init-sysd"> 485 <primary sortas="f-samba">samba</primary> 486 </indexterm> 487 488 <screen role="root"><userinput>make install-samba</userinput></screen> 489 490 <para> 491 To start the <command>winbindd</command> daemon at boot, 492 install the systemd unit from the <xref linkend="systemd-units"/> 493 package by running the following command as the 494 <systemitem class="username">root</systemitem> user: 495 </para> 496 497 <indexterm zone="samba samba-init-sysd"> 498 <primary sortas="f-winbindd">winbindd</primary> 499 </indexterm> 500 501 <screen role="root"><userinput>make install-winbindd</userinput></screen> 502 503 <note> 504 <para>This package comes with two types of units: A service file and a 505 socket file. The service file will start the smbd daemon once at boot 506 and it will keep running until the system shuts down. The socket file 507 will make systemd listen on the smbd port (Default 445, needs to be 508 edited for anything else) and will start the smbd daemon when something 509 tries to connect to that port and stop the daemon when the connection 510 is terminated. This is called socket activation and is analogous to 511 using <application>{,x}inetd</application> on a SysVinit based 512 system.</para> 513 514 <para>By default, the first method is used - the smbd daemon is started 515 at boot and stopped at shutdown. If the socket method is desired, you 516 need to run the following commands as the 517 <systemitem class="username">root</systemitem> user:</para> 518 519 <screen role="root"><userinput>systemctl stop smbd && 520 systemctl disable smbd && 521 systemctl enable smbd.socket && 522 systemctl start smbd.socket</userinput></screen> 523 524 <para>Note that only the smbd daemon can be socket activated.</para> 525 </note> 526 </sect4> 456 527 457 528 </sect3> -
networking/netprogs/wpa_supplicant.xml
ra9e71e2 r7b478500 215 215 install -v -m644 doc/docbook/wpa_{cli,passphrase,supplicant}.8 /usr/share/man/man8/</userinput></screen> 216 216 217 <para revision="systemd"> 218 Install the <application>systemd</application> support files by 219 running the following command as the <systemitem 220 class="username">root</systemitem> user: 221 </para> 222 223 <screen role="root" revision="systemd"><userinput>install -v -m644 systemd/*.service /lib/systemd/system/</userinput></screen> 224 217 225 <para> 218 226 If you have built <application>WPA Supplicant</application> with … … 228 236 /etc/dbus-1/system.d/wpa_supplicant.conf</userinput></screen> 229 237 238 <para revision="systemd"> 239 Additionally, enable the <filename>wpa_supplicant.service</filename> 240 so that <application>systemd</application> can properly activate the 241 <application>D-Bus</application> service. Note that the 242 per-connection service and the D-Bus service cannot be enabled 243 at the same time. Run the following command as the 244 <systemitem class="username">root</systemitem> user: 245 </para> 246 247 <screen role="root" revision="systemd"><userinput>systemctl enable wpa_supplicant</userinput></screen> 248 230 249 <para> 231 250 If you have built the <application>WPA Supplicant</application> GUI … … 258 277 <title>Config File</title> 259 278 260 <para >279 <para revision="sysv"> 261 280 <filename>/etc/sysconfig/wpa_supplicant-*.conf</filename> 262 281 </para> 263 282 264 <indexterm zone="wpa_supplicant wpa_supplicant-config"> 283 <para revision="systemd"> 284 <filename>/etc/wpa_supplicant/wpa_supplicant-*.conf</filename> 285 </para> 286 287 <indexterm zone="wpa_supplicant wpa_supplicant-config" revision="sysv"> 265 288 <primary 266 289 sortas="e-etc-sysconfig-wpa_supplicant-star.conf">/etc/sysconfig/wpa_supplicant-*.conf</primary> 267 290 </indexterm> 268 291 292 <indexterm zone="wpa_supplicant wpa_supplicant-config" revision="systemd"> 293 <primary 294 sortas="e-etc-wpa_supplicant-wpa_supplicant-star.conf">/etc/wpa_supplicant/wpa_supplicant-*.conf</primary> 295 </indexterm> 296 269 297 </sect3> 270 298 … … 274 302 <para> 275 303 To connect to an access point that uses a password, you need to put 276 the pre-shared key in <filename> 277 /etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</filename>. 304 the pre-shared key in 305 <phrase revision="sysv"><filename> 306 /etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</filename>.</phrase> 307 <phrase revision="systemd"><filename> 308 /etc/wpa_supplicant/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</filename>.</phrase> 278 309 SSID is the string that the access point/router transmits to 279 310 identify itself. Run the following command as the … … 281 312 </para> 282 313 283 <screen role="root"><userinput>wpa_passphrase <replaceable>SSID</replaceable> <replaceable>SECRET_PASSWORD</replaceable> > /etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</userinput></screen> 314 <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> 315 316 <screen role="root" revision="systemd"><userinput>install -v -dm755 /etc/wpa_supplicant && 317 wpa_passphrase <replaceable>SSID</replaceable> <replaceable>SECRET_PASSWORD</replaceable> > /etc/wpa_supplicant/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</userinput></screen> 284 318 285 319 <para> 286 <filename>/etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf 287 </filename> can hold the details of several access points. When 320 <phrase revision="sysv"><filename>/etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf </filename></phrase> 321 <phrase revision="systemd"><filename>/etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</filename></phrase> 322 can hold the details of several access points. When 288 323 <command>wpa_supplicant</command> is started, it will scan for the 289 324 SSIDs it can see and choose the appropriate password to connect. … … 292 327 <para> 293 328 If you want to connect to an access point that isn't password 294 protected, put an entry like this in <filename> 295 /etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</filename>. 329 protected, put an entry like this in 330 <phrase revision="sysv"><filename>/etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</filename></phrase> 331 <phrase revision="systemd"><filename>/etc/sysconfig/wpa_supplicant-<replaceable>wifi0</replaceable>.conf</filename></phrase>. 296 332 Replace "Some-SSID" with the SSID of the access point/router. 297 333 </para> … … 314 350 <title>Connecting to an Access Point</title> 315 351 316 <para id="wpa-service" >352 <para id="wpa-service" revision="sysv"> 317 353 If you want to configure network interfaces at boot using 318 354 <command>wpa_supplicant</command>, you need to install the 319 355 <filename>/lib/services/wpa</filename> script 320 included in <xref linkend="bootscripts" revision="sysv"/> 321 <xref linkend="systemd-units" revision="systemd"/> package: 322 </para> 323 324 <screen role="root"><userinput>make install-service-wpa</userinput></screen> 325 326 <indexterm zone="wpa_supplicant wpa-service"> 356 included in <xref linkend="bootscripts"/> package: 357 </para> 358 359 <screen role="root" revision="sysv"><userinput>make install-service-wpa</userinput></screen> 360 361 <indexterm zone="wpa_supplicant wpa-service" revision="sysv"> 327 362 <primary sortas="f-wpa">wpa</primary> 328 363 </indexterm> 329 364 330 <para >365 <para revision="sysv"> 331 366 If your router/access point uses DHCP to allocate IP addresses, you 332 367 can install <xref linkend="dhcp"/> client and use it to … … 337 372 </para> 338 373 339 <screen role="root" ><userinput>cat > /etc/sysconfig/ifconfig.<replaceable>wifi0</replaceable> << "EOF"374 <screen role="root" revision="sysv"><userinput>cat > /etc/sysconfig/ifconfig.<replaceable>wifi0</replaceable> << "EOF" 340 375 <literal>ONBOOT="yes" 341 376 IFACE="<replaceable>wlan0</replaceable>" … … 358 393 EOF</userinput></screen> 359 394 360 <para >395 <para revision="sysv"> 361 396 If you prefer <xref linkend="dhcpcd"/> instead of 362 397 <xref linkend="dhcp"/> client, then create the … … 366 401 </para> 367 402 368 <screen role="root" ><userinput>cat > /etc/sysconfig/ifconfig.<replaceable>wifi0</replaceable> << "EOF"403 <screen role="root" revision="sysv"><userinput>cat > /etc/sysconfig/ifconfig.<replaceable>wifi0</replaceable> << "EOF" 369 404 <literal>ONBOOT="yes" 370 405 IFACE="<replaceable>wlan0</replaceable>" … … 379 414 EOF</userinput></screen> 380 415 381 <para >416 <para revision="sysv"> 382 417 Alternatively, if you use static addresses on your local network, 383 418 then create the … … 387 422 </para> 388 423 389 <screen role="root" ><userinput>cat > /etc/sysconfig/ifconfig.<replaceable>wifi0</replaceable> << "EOF"424 <screen role="root" revision="sysv"><userinput>cat > /etc/sysconfig/ifconfig.<replaceable>wifi0</replaceable> << "EOF" 390 425 <literal>ONBOOT="yes" 391 426 IFACE="<replaceable>wlan0</replaceable>" … … 402 437 EOF</userinput></screen> 403 438 439 <para revision="systemd"> 440 There are 3 types of <application>systemd</application> units 441 that were installed: 442 </para> 443 444 <itemizedlist spacing="compact" revision="systemd"> 445 <listitem> 446 <para> 447 wpa_supplicant@.service 448 </para> 449 </listitem> 450 <listitem> 451 <para> 452 wpa_supplicant-nl80211@.service 453 </para> 454 </listitem> 455 <listitem> 456 <para> 457 wpa_supplicant-wired@.service 458 </para> 459 </listitem> 460 </itemizedlist> 461 462 <para revision="systemd"> 463 The only difference between 3 of them is what driver 464 is used for connecting (-D option). The first one uses 465 the default driver, the second one uses the nl80211 466 driver and the third one uses the wired driver. 467 </para> 468 404 469 <para> 405 470 You can connect to the wireless access point by … … 408 473 </para> 409 474 410 <screen role="root" ><userinput>ifup <replaceable>wifi0</replaceable></userinput></screen>411 412 <para >475 <screen role="root" revision="sysv"><userinput>ifup <replaceable>wifi0</replaceable></userinput></screen> 476 477 <para revision="sysv"> 413 478 Replace <replaceable>wlan0</replaceable> with the correct 414 479 wireless interface and <replaceable>wifi0</replaceable> … … 418 483 to have identical names, ie both contain 419 484 <replaceable>wifi0</replaceable> in their name. 485 </para> 486 487 <screen role="root" revision="systemd"><userinput>systemctl start wpa_supplicant@<replaceable>wlan0</replaceable></userinput></screen> 488 489 <para revision="systemd"> 490 To connect to the wireless access point at 491 boot, simply enable the appropriate 492 <command>wpa_supplicant</command> service 493 by running the following command as the 494 <systemitem class="username">root</systemitem> user: 495 </para> 496 497 <screen role="root" revision="systemd"><userinput>systemctl enable wpa_supplicant@<replaceable>wlan0</replaceable></userinput></screen> 498 499 <para revision="systemd"> 500 Depending on your setup, you can replace the 501 <filename>wpa_supplicant@.service</filename> 502 with any other listed above. 503 </para> 504 505 <para revision="systemd"> 506 To assign a network address to your wireless interface, consult the 507 <ulink url="&lfs-root;/chapter07/network.html">General Network Configuration</ulink> 508 page in LFS. 420 509 </para> 421 510
Note:
See TracChangeset
for help on using the changeset viewer.