svn commit: r44138 - head/en_US.ISO8859-1/books/handbook/advanced-networking
Dru Lavigne
dru at FreeBSD.org
Wed Mar 5 20:11:16 UTC 2014
Author: dru
Date: Wed Mar 5 20:11:16 2014
New Revision: 44138
URL: http://svnweb.freebsd.org/changeset/doc/44138
Log:
White space fix only. Translators can ignore.
Sponsored by: iXsystems
Modified:
head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml
Modified: head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Wed Mar 5 19:33:39 2014 (r44137)
+++ head/en_US.ISO8859-1/books/handbook/advanced-networking/chapter.xml Wed Mar 5 20:11:16 2014 (r44138)
@@ -37,7 +37,8 @@
</listitem>
<listitem>
- <para>How to set up network <acronym>PXE</acronym> booting.</para>
+ <para>How to set up network <acronym>PXE</acronym>
+ booting.</para>
</listitem>
<listitem>
@@ -3856,60 +3857,61 @@ ifconfig_<literal>lagg0</literal>="laggp
</indexterm>
<para>The &intel; Preboot eXecution Environment
- (<acronym>PXE</acronym>) allows an operating system to boot
- over the network. For example, a &os; system can boot over the network and operate
- without a local disk, using file systems mounted from an
- <acronym>NFS</acronym> server. <acronym>PXE</acronym> support is usually
- available in the <acronym>BIOS</acronym>. To use
- <acronym>PXE</acronym> when the machine starts,
- select the <literal>Boot from network</literal> option in
- the <acronym>BIOS</acronym> setup or type a function key
- during system initialization.</para>
+ (<acronym>PXE</acronym>) allows an operating system to boot over
+ the network. For example, a &os; system can boot over the
+ network and operate without a local disk, using file systems
+ mounted from an <acronym>NFS</acronym> server.
+ <acronym>PXE</acronym> support is usually available in the
+ <acronym>BIOS</acronym>. To use <acronym>PXE</acronym> when the
+ machine starts, select the <literal>Boot from network</literal>
+ option in the <acronym>BIOS</acronym> setup or type a function
+ key during system initialization.</para>
<para>In order to provide the files needed for an operating system
- to boot over the network, a
- <acronym>PXE</acronym> setup also requires properly configured
- <acronym>DHCP</acronym>, <acronym>TFTP</acronym>, and <acronym>NFS</acronym>
- servers, where:</para>
+ to boot over the network, a <acronym>PXE</acronym> setup also
+ requires properly configured <acronym>DHCP</acronym>,
+ <acronym>TFTP</acronym>, and <acronym>NFS</acronym> servers,
+ where:</para>
- <itemizedlist>
- <listitem>
- <para>Initial parameters, such as an
- <acronym>IP</acronym> address, executable boot filename and location,
- server name, and root path are obtained from the
- <acronym>DHCP</acronym> server.</para>
- </listitem>
+ <itemizedlist>
+ <listitem>
+ <para>Initial parameters, such as an <acronym>IP</acronym>
+ address, executable boot filename and location, server name,
+ and root path are obtained from the
+ <acronym>DHCP</acronym> server.</para>
+ </listitem>
- <listitem>
- <para>The operating system loader file is booted using
- <acronym>TFTP</acronym>.</para>
- </listitem>
+ <listitem>
+ <para>The operating system loader file is booted using
+ <acronym>TFTP</acronym>.</para>
+ </listitem>
- <listitem>
- <para>The file systems are loaded using
- <acronym>NFS</acronym>.</para>
- </listitem>
- </itemizedlist>
+ <listitem>
+ <para>The file systems are loaded using
+ <acronym>NFS</acronym>.</para>
+ </listitem>
+ </itemizedlist>
- <para>When a computer <acronym>PXE</acronym> boots, it receives information over
- <acronym>DHCP</acronym> about where to obtain the initial boot
- loader file. After the host computer
- receives this information, it downloads the boot loader via
- <acronym>TFTP</acronym> and then executes the boot loader.
- In &os;, the boot loader file is
+ <para>When a computer <acronym>PXE</acronym> boots, it receives
+ information over <acronym>DHCP</acronym> about where to obtain
+ the initial boot loader file. After the host computer receives
+ this information, it downloads the boot loader via
+ <acronym>TFTP</acronym> and then executes the boot loader. In
+ &os;, the boot loader file is
<filename>/boot/pxeboot</filename>. After
<filename>/boot/pxeboot</filename> executes, the &os; kernel is
- loaded and the rest of the &os; bootup sequence proceeds, as described in
- <xref linkend="boot"/>.</para>
+ loaded and the rest of the &os; bootup sequence proceeds, as
+ described in <xref linkend="boot"/>.</para>
- <para>This section describes how to configure these services
- on a &os; system so that other systems can
- <acronym>PXE</acronym> boot into &os;. Refer to &man.diskless.8; for more information.</para>
-
- <caution>
- <para>As described, the system providing these services is insecure. It should live in
- a protected area of a network and be untrusted by other
- hosts.</para>
+ <para>This section describes how to configure these services on a
+ &os; system so that other systems can <acronym>PXE</acronym>
+ boot into &os;. Refer to &man.diskless.8; for more
+ information.</para>
+
+ <caution>
+ <para>As described, the system providing these services is
+ insecure. It should live in a protected area of a network and
+ be untrusted by other hosts.</para>
</caution>
<sect2 xml:id="network-pxe-nfs">
@@ -3930,35 +3932,37 @@ ifconfig_<literal>lagg0</literal>="laggp
</authorgroup>
</info>
- <para>The steps shown in this section configure the built-in
- <acronym>NFS</acronym> and <acronym>TFTP</acronym> servers. The
- next section demonstrates how to install and configure the
- <acronym>DHCP</acronym> server. In this example, the
- directory which will contain the files used by <acronym>PXE</acronym> users is
- <filename>/b/tftpboot/FreeBSD/install</filename>. It is
- important that this directory exists and that the same directory
- name is set in both <filename>/etc/inetd.conf</filename> and
- <filename>/usr/local/etc/dhcpd.conf</filename>.</para>
+ <para>The steps shown in this section configure the built-in
+ <acronym>NFS</acronym> and <acronym>TFTP</acronym> servers.
+ The next section demonstrates how to install and configure the
+ <acronym>DHCP</acronym> server. In this example, the
+ directory which will contain the files used by
+ <acronym>PXE</acronym> users is
+ <filename>/b/tftpboot/FreeBSD/install</filename>. It is
+ important that this directory exists and that the same
+ directory name is set in both
+ <filename>/etc/inetd.conf</filename> and
+ <filename>/usr/local/etc/dhcpd.conf</filename>.</para>
<procedure>
<step>
- <para>Create the root directory which will contain a &os; installation
- to be <acronym>NFS</acronym> mounted:</para>
+ <para>Create the root directory which will contain a &os;
+ installation to be <acronym>NFS</acronym> mounted:</para>
<screen>&prompt.root; <userinput>export NFSROOTDIR=/b/tftpboot/FreeBSD/install</userinput>
&prompt.root; <userinput>mkdir -p ${NFSROOTDIR}</userinput></screen>
</step>
<step>
- <para>Enable the <acronym>NFS</acronym> server by adding this line to
- <filename>/etc/rc.conf</filename>:</para>
-
+ <para>Enable the <acronym>NFS</acronym> server by adding
+ this line to <filename>/etc/rc.conf</filename>:</para>
+
<programlisting>nfs_server_enable="YES"</programlisting>
</step>
<step>
- <para>Export the diskless root directory via <acronym>NFS</acronym> by
- adding the following to
+ <para>Export the diskless root directory via
+ <acronym>NFS</acronym> by adding the following to
<filename>/etc/exports</filename>:</para>
<programlisting>/b -ro -alldirs</programlisting>
@@ -3984,14 +3988,13 @@ ifconfig_<literal>lagg0</literal>="laggp
<programlisting>tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /b/tftpboot</programlisting>
- <note>
- <para>Some
- <acronym>PXE</acronym> versions require the
- <acronym>TCP</acronym> version of
- <acronym>TFTP</acronym>. In this case, uncomment the second
- <literal>tftp</literal> line which contains
- <literal>stream tcp</literal>.</para>
- </note>
+ <note>
+ <para>Some <acronym>PXE</acronym> versions require the
+ <acronym>TCP</acronym> version of
+ <acronym>TFTP</acronym>. In this case, uncomment the
+ second <literal>tftp</literal> line which contains
+ <literal>stream tcp</literal>.</para>
+ </note>
</step>
<step>
@@ -4002,7 +4005,8 @@ ifconfig_<literal>lagg0</literal>="laggp
<step>
<para>Rebuild the &os; kernel and userland (refer to <xref
- linkend="makeworld"/> for more detailed instructions):</para>
+ linkend="makeworld"/> for more detailed
+ instructions):</para>
<screen>&prompt.root; <userinput>cd /usr/src</userinput>
&prompt.root; <userinput>make buildworld</userinput>
@@ -4019,9 +4023,9 @@ ifconfig_<literal>lagg0</literal>="laggp
</step>
<step>
- <para>Test that the <acronym>TFTP</acronym> server works
- and can download the boot loader which will be obtained
- via <acronym>PXE</acronym>:</para>
+ <para>Test that the <acronym>TFTP</acronym> server works and
+ can download the boot loader which will be obtained via
+ <acronym>PXE</acronym>:</para>
<screen>&prompt.root; <userinput>tftp localhost</userinput>
tftp> <userinput>get FreeBSD/install/boot/pxeboot</userinput>
@@ -4046,26 +4050,28 @@ Received 264951 bytes in 0.1 seconds</sc
<step>
<para>Set the root password in the <acronym>PXE</acronym>
- environment for client machines which
- are <acronym>PXE</acronym> booting :</para>
+ environment for client machines which are
+ <acronym>PXE</acronym> booting :</para>
<screen>&prompt.root; <userinput>chroot ${NFSROOTDIR}</userinput>
&prompt.root; <userinput>passwd</userinput></screen>
</step>
<step>
- <para>If needed, enable &man.ssh.1; root logins for client machines
- which are <acronym>PXE</acronym> booting by editing
- <filename>${NFSROOTDIR}/etc/ssh/sshd_config</filename>
- and enabling <literal>PermitRootLogin</literal>. This
- option is documented in &man.sshd.config.5;.</para>
+ <para>If needed, enable &man.ssh.1; root logins for client
+ machines which are <acronym>PXE</acronym> booting by
+ editing
+ <filename>${NFSROOTDIR}/etc/ssh/sshd_config</filename> and
+ enabling <literal>PermitRootLogin</literal>. This option
+ is documented in &man.sshd.config.5;.</para>
</step>
<step>
- <para>Perform any other needed customizations of the <acronym>PXE</acronym>
- environment in <filename>${NFSROOTDIR}</filename>. These customizations could
- include things like installing packages or
- editing the password file with &man.vipw.8;.</para>
+ <para>Perform any other needed customizations of the
+ <acronym>PXE</acronym> environment in
+ <filename>${NFSROOTDIR}</filename>. These customizations
+ could include things like installing packages or editing
+ the password file with &man.vipw.8;.</para>
</step>
</procedure>
@@ -4091,32 +4097,31 @@ Received 264951 bytes in 0.1 seconds</sc
</sect2>
<sect2 xml:id="network-pxe-setting-up-dhcp">
- <title>Configuring the <acronym>DHCP</acronym> Server</title>
+ <title>Configuring the <acronym>DHCP</acronym> Server</title>
- <indexterm>
- <primary>DHCP</primary>
- <secondary>diskless operation</secondary>
- </indexterm>
+ <indexterm>
+ <primary>DHCP</primary>
+ <secondary>diskless operation</secondary>
+ </indexterm>
- <para>The
- <acronym>DHCP</acronym> server does not need to be the same
- machine as the <acronym>TFTP</acronym> and <acronym>NFS</acronym> server, but it needs
- to be accessible in the network.</para>
-
- <para><acronym>DHCP</acronym> is not part of the &os;
- base system but can be installed using the
- <package>net/isc-dhcp42-server</package> port or
- package.</para>
-
- <para>Once installed,
- edit the configuration file,
- <filename>/usr/local/etc/dhcpd.conf</filename>. Configure
- the <literal>next-server</literal>,
- <literal>filename</literal>, and
- <literal>root-path</literal> settings as seen in this
- example:</para>
+ <para>The <acronym>DHCP</acronym> server does not need to be the
+ same machine as the <acronym>TFTP</acronym> and
+ <acronym>NFS</acronym> server, but it needs to be accessible
+ in the network.</para>
+
+ <para><acronym>DHCP</acronym> is not part of the &os; base
+ system but can be installed using the
+ <package>net/isc-dhcp42-server</package> port or
+ package.</para>
+
+ <para>Once installed, edit the configuration file,
+ <filename>/usr/local/etc/dhcpd.conf</filename>. Configure
+ the <literal>next-server</literal>,
+ <literal>filename</literal>, and
+ <literal>root-path</literal> settings as seen in this
+ example:</para>
- <programlisting>subnet 192.168.0.0 netmask 255.255.255.0 {
+ <programlisting>subnet 192.168.0.0 netmask 255.255.255.0 {
range 192.168.0.2 192.168.0.3 ;
option subnet-mask 255.255.255.0 ;
option routers 192.168.0.1 ;
@@ -4146,30 +4151,28 @@ Received 264951 bytes in 0.1 seconds</sc
inside the <literal>host</literal> declarations.</para>
-->
- <para>The <literal>next-server</literal> directive is used
- to specify the <acronym>IP</acronym> address of the
- <acronym>TFTP</acronym>
- server.</para>
-
- <para>The <literal>filename</literal> directive defines
- the path to <filename>/boot/pxeboot</filename>. A
- relative filename is used, meaning that
- <filename>/b/tftpboot</filename> is not included in the
- path.</para>
-
- <para>The <literal>root-path</literal> option defines
- the path to the <acronym>NFS</acronym> root file system.</para>
-
- <para>Once the edits are saved, enable
- <acronym>NFS</acronym> at boot time by adding the
- following line to <filename>/etc/rc.conf</filename>:</para>
-
- <programlisting>dhcpd_enable="YES"</programlisting>
-
- <para>Then, start the <acronym>DHCP</acronym> service:</para>
-
- <screen>&prompt.root; <userinput>service isc-dhcpd start</userinput></screen>
- </sect2>
+ <para>The <literal>next-server</literal> directive is used to
+ specify the <acronym>IP</acronym> address of the
+ <acronym>TFTP</acronym> server.</para>
+
+ <para>The <literal>filename</literal> directive defines the path
+ to <filename>/boot/pxeboot</filename>. A relative filename is
+ used, meaning that <filename>/b/tftpboot</filename> is not
+ included in the path.</para>
+
+ <para>The <literal>root-path</literal> option defines the path
+ to the <acronym>NFS</acronym> root file system.</para>
+
+ <para>Once the edits are saved, enable <acronym>NFS</acronym> at
+ boot time by adding the following line to
+ <filename>/etc/rc.conf</filename>:</para>
+
+ <programlisting>dhcpd_enable="YES"</programlisting>
+
+ <para>Then, start the <acronym>DHCP</acronym> service:</para>
+
+ <screen>&prompt.root; <userinput>service isc-dhcpd start</userinput></screen>
+ </sect2>
<!--
Are these sections still needed?
<sect2>
@@ -4220,24 +4223,23 @@ options BOOTP_NFSROOT # NFS mount r
<literal>root-path</literal> in
<filename>/usr/local/etc/dhcpd.conf</filename>.</para>
- <para>Using <command>make world</command> to populate
- root is quick and will install a complete
- virgin system, not just the root file system, into
- <envar>DESTDIR</envar>. Execute the following
- script:</para>
+ <para>Using <command>make world</command> to populate root is
+ quick and will install a complete virgin system, not just
+ the root file system, into <envar>DESTDIR</envar>. Execute
+ the following script:</para>
- <programlisting>#!/bin/sh
+ <programlisting>#!/bin/sh
export DESTDIR=/data/misc/diskless
mkdir -p ${DESTDIR}
cd /usr/src; make buildworld && make buildkernel
make installworld && make installkernel
cd /usr/src/etc; make distribution</programlisting>
- <para>Once done, customize
- <filename>/etc/rc.conf</filename> and
- <filename>/etc/fstab</filename> placed into
- <envar>DESTDIR</envar> according to the system's
- requirements.</para>
+ <para>Once done, customize
+ <filename>/etc/rc.conf</filename> and
+ <filename>/etc/fstab</filename> placed into
+ <envar>DESTDIR</envar> according to the system's
+ requirements.</para>
</sect2>
<sect2>
@@ -4292,25 +4294,23 @@ cd /usr/src/etc; make distribution</prog
<sect2>
<title>Debugging <acronym>PXE</acronym> Problems</title>
- <para>Once all of the services are configured and started,
- <acronym>PXE</acronym> clients should be able to
- automatically load &os; over the network. If a particular
- client is unable to connect,
- when that client machine boots up, enter the
- <acronym>BIOS</acronym> configuration menu and confirm
- that it is set to boot from the network.</para>
-
- <para>This section describes some troubleshooting tips
- for isolating the source of the configuration problem should no
- clients be able to <acronym>PXE</acronym> boot.</para>
-
+ <para>Once all of the services are configured and started,
+ <acronym>PXE</acronym> clients should be able to
+ automatically load &os; over the network. If a particular
+ client is unable to connect, when that client machine boots
+ up, enter the <acronym>BIOS</acronym> configuration menu and
+ confirm that it is set to boot from the network.</para>
+
+ <para>This section describes some troubleshooting tips for
+ isolating the source of the configuration problem should no
+ clients be able to <acronym>PXE</acronym> boot.</para>
+
<procedure>
<step>
-
<para>Use the <package>net/wireshark</package> package or
port to debug the network traffic involved during the
- <acronym>PXE</acronym> booting process, which is illustrated
- in the diagram below.</para>
+ <acronym>PXE</acronym> booting process, which is
+ illustrated in the diagram below.</para>
<figure>
<title><acronym>PXE</acronym> Booting Process with
More information about the svn-doc-all
mailing list