os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Whitespace-only fixes: indentation and wrap long lines. Translators,

Browse source 
please ignore.
This commit is contained in:
Warren Block 2012-06-14 12:04:00 +00:00
parent 08e28d303b
commit cab218977c
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/head/; revision=39044
1 changed files with 53 additions and 51 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

104
en_US.ISO8859-1/books/handbook/advanced-networking/chapter.sgml
View file

@ -4635,62 +4635,64 @@ myhost.example.com:/b/tftpboot/FreeBSD/install / nfs ro
</step> </step>
<step> <step>
<para>Use the <filename role="package">net/wireshark</filename>
port to debug the network traffic involved during the <para>Use the
<filename role="package">net/wireshark</filename> port to
debug the network traffic involved during the
<acronym>PXE</acronym> booting process, which is <acronym>PXE</acronym> booting process, which is
illustrated in the diagram below. illustrated in the diagram below. In
In <xref linkend="network-pxe-setting-up-dhcp">, an <xref linkend="network-pxe-setting-up-dhcp">, an example
example configuration is shown where the configuration is shown where the <acronym>DHCP</acronym>,
<acronym>DHCP</acronym>, <acronym>TFTP</acronym>, and <acronym>TFTP</acronym>, and <acronym>NFS</acronym>
<acronym>NFS</acronym> servers are actually on the same servers are actually on the same machine. However, these
machine. However, these severs can be on separate severs can be on separate machines.</para>
machines.</para>
<figure> <figure>
<title>PXE Booting process with NFS root mount</title> <title>PXE Booting process with NFS root mount</title>
<mediaobjectco> <mediaobjectco>
<imageobjectco> <imageobjectco>
<areaspec units="calspair"> <areaspec units="calspair">
<area id="co-pxenfs1" coords="2873,8133 3313,7266"> <area id="co-pxenfs1" coords="2873,8133 3313,7266">
<area id="co-pxenfs2" coords="3519,6333 3885,5500"> <area id="co-pxenfs2" coords="3519,6333 3885,5500">
<area id="co-pxenfs3" coords="4780,5866 5102,5200"> <area id="co-pxenfs3" coords="4780,5866 5102,5200">
<area id="co-pxenfs4" coords="4794,4333 5102,3600"> <area id="co-pxenfs4" coords="4794,4333 5102,3600">
<area id="co-pxenfs5" coords="3108,2666 3519,1800"> <area id="co-pxenfs5" coords="3108,2666 3519,1800">
</areaspec> </areaspec>
<imageobject> <imageobject>
<imagedata fileref="advanced-networking/pxe-nfs"> <imagedata fileref="advanced-networking/pxe-nfs">
</imageobject> </imageobject>
<calloutlist> <calloutlist>
<callout arearefs="co-pxenfs1"> <callout arearefs="co-pxenfs1">
<para>Client broadcasts DHCPDISCOVER.</para> <para>Client broadcasts DHCPDISCOVER.</para>
</callout> </callout>
<callout arearefs="co-pxenfs2"> <callout arearefs="co-pxenfs2">
<para>DHCP server responds with IP address, <para>DHCP server responds with IP address,
<literal>next-server</literal>, <literal>next-server</literal>,
<literal>filename</literal>, and <literal>filename</literal>, and
<literal>root-path</literal>.</para> <literal>root-path</literal>.</para>
</callout> </callout>
<callout arearefs="co-pxenfs3"> <callout arearefs="co-pxenfs3">
<para>Client sends <acronym>TFTP</acronym> <para>Client sends <acronym>TFTP</acronym>
request to <literal>next-server</literal> request to <literal>next-server</literal>
asking to retrieve asking to retrieve
<literal>filename</literal>.</para> <literal>filename</literal>.</para>
</callout> </callout>
<callout arearefs="co-pxenfs4"> <callout arearefs="co-pxenfs4">
<para>TFTP server responds and sends <para>TFTP server responds and sends
<literal>filename</literal> to client.</para> <literal>filename</literal> to client.</para>
</callout> </callout>
<callout arearefs="co-pxenfs5"> <callout arearefs="co-pxenfs5">
<para>Client executes <para>Client executes
<literal>filename</literal> which is <literal>filename</literal> which is
&man.pxeboot.8;. &man.pxeboot.8; loads the &man.pxeboot.8;. &man.pxeboot.8; loads the
kernel. When the kernel executes, the root kernel. When the kernel executes, the root
filesystem specified by filesystem specified by
<literal>root-path</literal> is mounted over <literal>root-path</literal> is mounted over
<acronym>NFS</acronym>.</para> <acronym>NFS</acronym>.</para>
</callout> </callout>
</calloutlist> </calloutlist>
</imageobjectco> </imageobjectco>
</mediaobjectco> </mediaobjectco>
</figure> </figure>
</step> </step>