From owner-svn-doc-all@FreeBSD.ORG Wed Mar 5 20:11:16 2014 Return-Path: Delivered-To: svn-doc-all@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) (using TLSv1 with cipher ADH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BB94F614; Wed, 5 Mar 2014 20:11:16 +0000 (UTC) Received: from svn.freebsd.org (svn.freebsd.org [IPv6:2001:1900:2254:2068::e6a:0]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by mx1.freebsd.org (Postfix) with ESMTPS id A68EC913; Wed, 5 Mar 2014 20:11:16 +0000 (UTC) Received: from svn.freebsd.org ([127.0.1.70]) by svn.freebsd.org (8.14.8/8.14.8) with ESMTP id s25KBGTU081019; Wed, 5 Mar 2014 20:11:16 GMT (envelope-from dru@svn.freebsd.org) Received: (from dru@localhost) by svn.freebsd.org (8.14.8/8.14.8/Submit) id s25KBGSW081018; Wed, 5 Mar 2014 20:11:16 GMT (envelope-from dru@svn.freebsd.org) Message-Id: <201403052011.s25KBGSW081018@svn.freebsd.org> From: Dru Lavigne Date: Wed, 5 Mar 2014 20:11:16 +0000 (UTC) To: doc-committers@freebsd.org, svn-doc-all@freebsd.org, svn-doc-head@freebsd.org Subject: svn commit: r44138 - head/en_US.ISO8859-1/books/handbook/advanced-networking X-SVN-Group: doc-head MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-BeenThere: svn-doc-all@freebsd.org X-Mailman-Version: 2.1.17 Precedence: list List-Id: "SVN commit messages for the entire doc trees \(except for " user" , " projects" , and " translations" \)" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 05 Mar 2014 20:11:16 -0000 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 @@ - How to set up network PXE booting. + How to set up network PXE + booting. @@ -3856,60 +3857,61 @@ ifconfig_lagg0="laggp The &intel; Preboot eXecution Environment - (PXE) 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 - NFS server. PXE support is usually - available in the BIOS. To use - PXE when the machine starts, - select the Boot from network option in - the BIOS setup or type a function key - during system initialization. + (PXE) 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 NFS server. + PXE support is usually available in the + BIOS. To use PXE when the + machine starts, select the Boot from network + option in the BIOS setup or type a function + key during system initialization. In order to provide the files needed for an operating system - to boot over the network, a - PXE setup also requires properly configured - DHCP, TFTP, and NFS - servers, where: + to boot over the network, a PXE setup also + requires properly configured DHCP, + TFTP, and NFS servers, + where: - - - Initial parameters, such as an - IP address, executable boot filename and location, - server name, and root path are obtained from the - DHCP server. - + + + Initial parameters, such as an IP + address, executable boot filename and location, server name, + and root path are obtained from the + DHCP server. + - - The operating system loader file is booted using - TFTP. - + + The operating system loader file is booted using + TFTP. + - - The file systems are loaded using - NFS. - - + + The file systems are loaded using + NFS. + + - When a computer PXE boots, it receives information over - DHCP about where to obtain the initial boot - loader file. After the host computer - receives this information, it downloads the boot loader via - TFTP and then executes the boot loader. - In &os;, the boot loader file is + When a computer PXE boots, it receives + information over DHCP about where to obtain + the initial boot loader file. After the host computer receives + this information, it downloads the boot loader via + TFTP and then executes the boot loader. In + &os;, the boot loader file is /boot/pxeboot. After /boot/pxeboot executes, the &os; kernel is - loaded and the rest of the &os; bootup sequence proceeds, as described in - . + loaded and the rest of the &os; bootup sequence proceeds, as + described in . - This section describes how to configure these services - on a &os; system so that other systems can - PXE boot into &os;. Refer to &man.diskless.8; for more information. - - - 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. + This section describes how to configure these services on a + &os; system so that other systems can PXE + boot into &os;. Refer to &man.diskless.8; for more + information. + + + 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. @@ -3930,35 +3932,37 @@ ifconfig_lagg0="laggp - The steps shown in this section configure the built-in - NFS and TFTP servers. The - next section demonstrates how to install and configure the - DHCP server. In this example, the - directory which will contain the files used by PXE users is - /b/tftpboot/FreeBSD/install. It is - important that this directory exists and that the same directory - name is set in both /etc/inetd.conf and - /usr/local/etc/dhcpd.conf. + The steps shown in this section configure the built-in + NFS and TFTP servers. + The next section demonstrates how to install and configure the + DHCP server. In this example, the + directory which will contain the files used by + PXE users is + /b/tftpboot/FreeBSD/install. It is + important that this directory exists and that the same + directory name is set in both + /etc/inetd.conf and + /usr/local/etc/dhcpd.conf. - Create the root directory which will contain a &os; installation - to be NFS mounted: + Create the root directory which will contain a &os; + installation to be NFS mounted: &prompt.root; export NFSROOTDIR=/b/tftpboot/FreeBSD/install &prompt.root; mkdir -p ${NFSROOTDIR} - Enable the NFS server by adding this line to - /etc/rc.conf: - + Enable the NFS server by adding + this line to /etc/rc.conf: + nfs_server_enable="YES" - Export the diskless root directory via NFS by - adding the following to + Export the diskless root directory via + NFS by adding the following to /etc/exports: /b -ro -alldirs @@ -3984,14 +3988,13 @@ ifconfig_lagg0="laggp tftp dgram udp wait root /usr/libexec/tftpd tftpd -l -s /b/tftpboot - - Some - PXE versions require the - TCP version of - TFTP. In this case, uncomment the second - tftp line which contains - stream tcp. - + + Some PXE versions require the + TCP version of + TFTP. In this case, uncomment the + second tftp line which contains + stream tcp. + @@ -4002,7 +4005,8 @@ ifconfig_lagg0="laggp Rebuild the &os; kernel and userland (refer to for more detailed instructions): + linkend="makeworld"/> for more detailed + instructions): &prompt.root; cd /usr/src &prompt.root; make buildworld @@ -4019,9 +4023,9 @@ ifconfig_lagg0="laggp - Test that the TFTP server works - and can download the boot loader which will be obtained - via PXE: + Test that the TFTP server works and + can download the boot loader which will be obtained via + PXE: &prompt.root; tftp localhost tftp> get FreeBSD/install/boot/pxeboot @@ -4046,26 +4050,28 @@ Received 264951 bytes in 0.1 seconds Set the root password in the PXE - environment for client machines which - are PXE booting : + environment for client machines which are + PXE booting : &prompt.root; chroot ${NFSROOTDIR} &prompt.root; passwd - If needed, enable &man.ssh.1; root logins for client machines - which are PXE booting by editing - ${NFSROOTDIR}/etc/ssh/sshd_config - and enabling PermitRootLogin. This - option is documented in &man.sshd.config.5;. + If needed, enable &man.ssh.1; root logins for client + machines which are PXE booting by + editing + ${NFSROOTDIR}/etc/ssh/sshd_config and + enabling PermitRootLogin. This option + is documented in &man.sshd.config.5;. - Perform any other needed customizations of the PXE - environment in ${NFSROOTDIR}. These customizations could - include things like installing packages or - editing the password file with &man.vipw.8;. + Perform any other needed customizations of the + PXE environment in + ${NFSROOTDIR}. These customizations + could include things like installing packages or editing + the password file with &man.vipw.8;. @@ -4091,32 +4097,31 @@ Received 264951 bytes in 0.1 seconds - Configuring the <acronym>DHCP</acronym> Server + Configuring the <acronym>DHCP</acronym> Server - - DHCP - diskless operation - + + DHCP + diskless operation + - The - DHCP server does not need to be the same - machine as the TFTP and NFS server, but it needs - to be accessible in the network. - - DHCP is not part of the &os; - base system but can be installed using the - net/isc-dhcp42-server port or - package. - - Once installed, - edit the configuration file, - /usr/local/etc/dhcpd.conf. Configure - the next-server, - filename, and - root-path settings as seen in this - example: + The DHCP server does not need to be the + same machine as the TFTP and + NFS server, but it needs to be accessible + in the network. + + DHCP is not part of the &os; base + system but can be installed using the + net/isc-dhcp42-server port or + package. + + Once installed, edit the configuration file, + /usr/local/etc/dhcpd.conf. Configure + the next-server, + filename, and + root-path settings as seen in this + example: - subnet 192.168.0.0 netmask 255.255.255.0 { + 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 secondshost declarations. --> - The next-server directive is used - to specify the IP address of the - TFTP - server. - - The filename directive defines - the path to /boot/pxeboot. A - relative filename is used, meaning that - /b/tftpboot is not included in the - path. - - The root-path option defines - the path to the NFS root file system. - - Once the edits are saved, enable - NFS at boot time by adding the - following line to /etc/rc.conf: - - dhcpd_enable="YES" - - Then, start the DHCP service: - - &prompt.root; service isc-dhcpd start - + The next-server directive is used to + specify the IP address of the + TFTP server. + + The filename directive defines the path + to /boot/pxeboot. A relative filename is + used, meaning that /b/tftpboot is not + included in the path. + + The root-path option defines the path + to the NFS root file system. + + Once the edits are saved, enable NFS at + boot time by adding the following line to + /etc/rc.conf: + + dhcpd_enable="YES" + + Then, start the DHCP service: + + &prompt.root; service isc-dhcpd start +