cam 06/10/30 16:58:27 Modified: diskless-howto.xml Log: Some cleaning, NO content change for translators.
Revision Changes Path 1.29 xml/htdocs/doc/en/diskless-howto.xml file : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/diskless-howto.xml?rev=1.29&view=markup plain: http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/diskless-howto.xml?rev=1.29&content-type=text/plain diff : http://sources.gentoo.org/viewcvs.py/gentoo/xml/htdocs/doc/en/diskless-howto.xml?r1=1.28&r2=1.29 Index: diskless-howto.xml =================================================================== RCS file: /var/cvsroot/gentoo/xml/htdocs/doc/en/diskless-howto.xml,v retrieving revision 1.28 retrieving revision 1.29 diff -u -r1.28 -r1.29 --- diskless-howto.xml 30 Oct 2006 16:39:22 -0000 1.28 +++ diskless-howto.xml 30 Oct 2006 16:58:27 -0000 1.29 @@ -1,26 +1,25 @@ <?xml version="1.0" encoding="UTF-8"?> -<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/diskless-howto.xml,v 1.28 2006/10/30 16:39:22 cam Exp $ --> +<!-- $Header: /var/cvsroot/gentoo/xml/htdocs/doc/en/diskless-howto.xml,v 1.29 2006/10/30 16:58:27 cam Exp $ --> <!DOCTYPE guide SYSTEM "/dtd/guide.dtd"> <guide link="/doc/en/diskless-howto.xml"> - <title>Diskless Nodes with Gentoo</title> <author title="Researcher"> - <mail link="[EMAIL PROTECTED]">Michael Andrews</mail> + <mail link="[EMAIL PROTECTED]">Michael Andrews</mail> </author> <author title="Editor"> - <mail link="[EMAIL PROTECTED]">Kristian Jerpetjoen</mail> + <mail link="[EMAIL PROTECTED]">Kristian Jerpetjoen</mail> </author> <author title="Reviewer"> - <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail> + <mail link="[EMAIL PROTECTED]">Sven Vermeulen</mail> </author> <author title="Reviewer"> - <mail link="[EMAIL PROTECTED]">Xavier Neys</mail> + <mail link="[EMAIL PROTECTED]">Xavier Neys</mail> </author> <abstract> -This HOWTO will help you create setup diskless nodes with Gentoo Linux +This HOWTO will help you create setup diskless nodes with Gentoo Linux. </abstract> <!-- The content of this document is licensed under the CC-BY-SA license --> @@ -32,18 +31,17 @@ <chapter> <title>Introduction</title> - <section> <title>About this HOWTO</title> <body> <p> -This HOWTO will help you setup <e>diskless</e> workstations based on -the Gentoo Linux distribution. We intend to make this as user friendly -as possible and cater to the Linux newbie, because every one of us was one at a -certain point :) While an experienced user could easily tie the multiple HOWTOs -available on diskless nodes and networking together we hope that this guide can -ease the installation for all interested users, geeks or not. +This HOWTO will help you setup <e>diskless</e> workstations based on the Gentoo +Linux distribution. We intend to make this as user friendly as possible and +cater to the Linux newbie, because every one of us was one at a certain point :) +While an experienced user could easily tie the multiple HOWTOs available on +diskless nodes and networking together we hope that this guide can ease the +installation for all interested users, geeks or not. </p> </body> @@ -54,13 +52,13 @@ <p> A diskless machine is a PC without any of the usual boot devices such as hard -disks, floppy drives or CD-ROMs. The diskless node boots off the network and -needs a server that will provide it with storage space as a local hard disk -would. From now on we call the server the <e>master</e>, while the diskless -machine gets called the <e>slave</e> (what's in a name :). The slave node -needs a network adapter that supports PXE booting or Etherboot; check <uri -link="http://www.etherboot.org";>Etherboot.org</uri> for support listings. Most -modern cards support PXE and many built-in adapters on motherboards will also +disks, floppy drives or CD-ROMs. The diskless node boots off the network and +needs a server that will provide it with storage space as a local hard disk +would. From now on we call the server the <e>master</e>, while the diskless +machine gets called the <e>slave</e> (what's in a name :). The slave node needs +a network adapter that supports PXE booting or Etherboot; check <uri +link="http://www.etherboot.org";>Etherboot.org</uri> for support listings. Most +modern cards support PXE and many built-in adapters on motherboards will also work. </p> @@ -71,10 +69,10 @@ <body> <p> -You should have Gentoo installed on your master node and enough space on the -master to store the file systems of the slave nodes you want to host. Also make -sure you have one interface to the internet separated from the local area -connection. +You should have Gentoo installed on your master node and enough space on the +master to store the file systems of the slave nodes you want to host. Also make +sure you have one interface to the internet separated from the local area +connection. </p> </body> @@ -96,17 +94,17 @@ </note> <p> -The kernel is the software that sits between your hardware and all other -software you have loaded on your machine, essentially the heart of a kernel -based operating system. When your computer is started, the BIOS executes the -instructions found at the reserved boot space of your hard drive. These -instructions are typically a boot loader that loads your kernel. After your -kernel has been loaded all processes are handled by the kernel. +The kernel is the software that sits between your hardware and all other +software you have loaded on your machine, essentially the heart of a kernel +based operating system. When your computer is started, the BIOS executes the +instructions found at the reserved boot space of your hard drive. These +instructions are typically a boot loader that loads your kernel. After your +kernel has been loaded all processes are handled by the kernel. </p> <p> -For more information on kernels and kernel configuration you might want to -check out the <uri link="http://www.tldp.org/HOWTO/Kernel-HOWTO.html";>kernel +For more information on kernels and kernel configuration you might want to check +out the <uri link="http://www.tldp.org/HOWTO/Kernel-HOWTO.html";>kernel HOWTO</uri>. </p> @@ -117,9 +115,9 @@ <body> <p> -The master kernel can be as large and as customized as you would like but -there are a few required kernel options you need to select. Go into your -kernel configuration menu by typing: +The master kernel can be as large and as customized as you would like but there +are a few required kernel options you need to select. Go into your kernel +configuration menu by typing: </p> <pre caption="Editing the master's kernel configuration"> @@ -128,10 +126,10 @@ </pre> <p> -You should get a grey and blue GUI that offers a safe alternative to manually -editing the <path>/usr/src/linux/.config</path> file. If your kernel is -currently functioning well you might want to save the current configuration -file by exiting the GUI and type: +You should get a grey and blue GUI that offers a safe alternative to manually +editing the <path>/usr/src/linux/.config</path> file. If your kernel is +currently functioning well you might want to save the current configuration file +by exiting the GUI and type: </p> <pre caption="Backing up the master's kernel configuration"> @@ -139,9 +137,9 @@ </pre> <p> -Go into the following sub-menus and make sure the listed items are checked -as built-in (and <e>NOT</e> as modular). The options show below are taken from -the 2.6.10 kernel version. If you use a different version, the text or sequence +Go into the following sub-menus and make sure the listed items are checked as +built-in (and <e>NOT</e> as modular). The options show below are taken from the +2.6.10 kernel version. If you use a different version, the text or sequence might differ. Just make sure you select at least those shown below. </p> @@ -156,14 +154,14 @@ [*] TCP/IP networking [*] IP: multicasting [ ] Network packet filtering (replaces ipchains) - + File systems ---> Network File Systems ---> <*> NFS server support [*] Provide NFSv3 server support <comment> -If you want to access the internet through your master node and/or have a +If you want to access the internet through your master node and/or have a secure firewall make sure to add support for iptables </comment> [*] Network packet filtering (replaces ipchains) @@ -175,19 +173,18 @@ <p> If you want to use packet filtering, you can add the rest as modules later. Make sure to read the <uri -link="/doc/en/security/security-handbook.xml?part=1&chap=12">Gentoo -Security Handbook Chapter about Firewalls</uri> on how to set this up -properly. +link="/doc/en/security/security-handbook.xml?part=1&chap=12">Gentoo Security +Handbook Chapter about Firewalls</uri> on how to set this up properly. </p> <note> -These kernel configuration options should only be added to your system -specific configuration options and are not meant to completely replace your -kernel configuration. +These kernel configuration options should only be added to your system specific +configuration options and are not meant to completely replace your kernel +configuration. </note> <p> -After you have re-configured the master's kernel you will want to rebuild it: +After you have re-configured the master's kernel you will want to rebuild it: </p> <pre caption="Recompiling the master's kernel and modules"> @@ -211,15 +208,15 @@ <body> <p> -It is recommended that you compile the slave kernel without any modules, since -loading and setting them up via remote boot is a difficult and unnecessary -process. Additionally, the slave kernel should be as small and compact as -possible in order to efficiently boot from the network. We are going to compile +It is recommended that you compile the slave kernel without any modules, since +loading and setting them up via remote boot is a difficult and unnecessary +process. Additionally, the slave kernel should be as small and compact as +possible in order to efficiently boot from the network. We are going to compile the slave's kernel in the same place where the master was configured. </p> <p> -To avoid confusion and wasting time it is probably a good idea to backup the +To avoid confusion and wasting time it is probably a good idea to backup the master's configuration file by typing: </p> @@ -228,10 +225,10 @@ </pre> <p> -Now we will want to configure the slave's kernel in the same fashion we -configured the master's kernel. If you want to start with a fresh -configuration file you can always recover the default -<path>/usr/src/linux/.config</path> file by typing: +Now we will want to configure the slave's kernel in the same fashion we +configured the master's kernel. If you want to start with a fresh configuration +file you can always recover the default <path>/usr/src/linux/.config</path> file +by typing: </p> <pre caption="Getting a clean kernel configuration"> @@ -249,8 +246,8 @@ </pre> <p> -You will want to make sure you select the following options as built-in -and <e>NOT</e> as kernel modules: +You will want to make sure you select the following options as built-in and +<e>NOT</e> as kernel modules: </p> <pre caption="slave's kernel options"> @@ -269,7 +266,7 @@ File systems ---> Network File Systems ---> - <*> file system support + <*> file system support [*] Provide NFSv3 client support [*] Root file system on NFS </pre> @@ -279,14 +276,14 @@ </note> <impo> -It is important that you add your network adapter into the kernel (and not as -a module) on the nodes. Using modules however is generally not a problem for +It is important that you add your network adapter into the kernel (and not as a +module) on the nodes. Using modules however is generally not a problem for diskless nodes. </impo> <p> -Now the slave's kernel needs to be compiled. You have to be careful here -because you don't want to mess up the modules (if any) you have built for the +Now the slave's kernel needs to be compiled. You have to be careful here +because you don't want to mess up the modules (if any) you have built for the master: </p> @@ -297,14 +294,14 @@ <p> Now create the directory on the master that will be used to hold slaves' files -and required system files. We use <path>/diskless</path> but you may choose -any location you like. Now copy the slave's bzImage into the -<path>/diskless</path> directory: +and required system files. We use <path>/diskless</path> but you may choose any +location you like. Now copy the slave's bzImage into the <path>/diskless</path> +directory: </p> <note> If you are using different architectures you might want to save each config into -<path>.config_arch</path>. Do the same with the images: save them into the +<path>.config_arch</path>. Do the same with the images: save them into the <path>/diskless</path> as <path>bzImage_arch</path>. </note> @@ -320,15 +317,14 @@ <body> <p> -The master and slave filesystems can be tweaked and changed a lot. Right now -we are only interested in getting a preliminary filesystem of appropriate -configuration files and mount points. First we need to create a directory -within <path>/diskless</path> for the first slave. Each slave needs it's own -root file system because sharing certain system files will cause permission -problems and hard crashes. You can call these directories anything you want -but I suggest using the slaves IP addresses as they are unique and not -confusing. The static IP of our first slave will be, for instance, -<c>192.168.1.21</c>: +The master and slave filesystems can be tweaked and changed a lot. Right now we +are only interested in getting a preliminary filesystem of appropriate +configuration files and mount points. First we need to create a directory within +<path>/diskless</path> for the first slave. Each slave needs it's own root file +system because sharing certain system files will cause permission problems and +hard crashes. You can call these directories anything you want but I suggest +using the slaves IP addresses as they are unique and not confusing. The static +IP of our first slave will be, for instance, <c>192.168.1.21</c>: </p> <pre caption="Creating a remote root directory"> @@ -336,9 +332,9 @@ </pre> <p> -Various configuration files in <path>/etc</path> need to be altered to work on -the slave. Copy the master's <path>/etc</path> directory onto your -new slave root by typing: +Various configuration files in <path>/etc</path> need to be altered to work on +the slave. Copy the master's <path>/etc</path> directory onto your new slave +root by typing: </p> <pre caption="Creating /etc for the slave's filesystem"> @@ -395,7 +391,6 @@ </section> </chapter> - <chapter> <title>Configuring the DHCP server</title> <section> @@ -403,12 +398,12 @@ <body> <p> -DHCP stands for Dynamic Host Configuration Protocol. The DHCP server is the -first computer the slaves will communicate with when they PXE boot. The -primary purpose of the DHCP server is to assign IP addresses. The DHCP server -can assign IP addresses based on hosts ethernet MAC addresses. Once the slave -has an IP address, the DHCP server will tell the slave where to get its -initial file system and kernel. +DHCP stands for Dynamic Host Configuration Protocol. The DHCP server is the +first computer the slaves will communicate with when they PXE boot. The primary +purpose of the DHCP server is to assign IP addresses. The DHCP server can +assign IP addresses based on hosts ethernet MAC addresses. Once the slave has +an IP address, the DHCP server will tell the slave where to get its initial file +system and kernel. </p> </body> @@ -418,7 +413,7 @@ <body> <p> -There are several things you will want to make sure are working before you +There are several things you will want to make sure are working before you begin. First check your network connectivity: </p> @@ -428,7 +423,7 @@ </pre> <p> -You will want to make sure you have have an <e>eth0</e> device running. It +You will want to make sure you have have an <e>eth0</e> device running. It should look something like this: </p> @@ -455,8 +450,8 @@ <body> <p> -If your network does not already have a DHCP server installed you will need -to install one: +If your network does not already have a DHCP server installed you will need to +install one: </p> <pre caption="Installing the dhcp server"> @@ -464,7 +459,7 @@ </pre> <p> -If your network already has a DHCP server installed you will have to edit the +If your network already has a DHCP server installed you will have to edit the configuration file to get the PXE boot to function correctly. </p> @@ -486,8 +481,8 @@ </pre> <p> -The general layout of the file is set up in an indented fashion and looks -like this: +The general layout of the file is set up in an indented fashion and looks like +this: </p> <pre caption="Sample dhcpd.conf layout"> @@ -508,7 +503,7 @@ </pre> <p> -The <c>shared-network</c> block is optional and should be used for IPs you want +The <c>shared-network</c> block is optional and should be used for IPs you want to assign that belong to the same network topology. At least one <c>subnet</c> must be declared and the optional <c>group</c> block allows you to group options between items. A good example of <path>dhcpd.conf</path> looks like this: @@ -585,21 +580,20 @@ <note> There is nothing prohibiting the use of both PXE boot and Etherboot together. -The above Code Listing is merely an example; if you have issues, please -consult the DHCPd documentation. +The above Code Listing is merely an example; if you have issues, please consult +the DHCPd documentation. </note> <p> -The IP address after <c>next-server</c> will be asked for the specified -<c>filename</c>. This IP address should be the IP of the tftp server, usually +The IP address after <c>next-server</c> will be asked for the specified +<c>filename</c>. This IP address should be the IP of the tftp server, usually the same as the master's IP address. The <c>filename</c> is relative to the -<path>/diskless</path> directory (this is due to the tftp server specific -options which will be covered later). Inside the <c>host</c> block, the -<c>hardware ethernet</c> option specifies a MAC address, and +<path>/diskless</path> directory (this is due to the tftp server specific +options which will be covered later). Inside the <c>host</c> block, the +<c>hardware ethernet</c> option specifies a MAC address, and <c>fixed-address</c> assigns a fixed IP address to that particular MAC address. -There is a pretty good man page on -<path>dhcpd.conf</path> with options that are beyond the scope of this HOWTO. -You can read it by typing: +There is a pretty good man page on <path>dhcpd.conf</path> with options that are +beyond the scope of this HOWTO. You can read it by typing: </p> <pre caption="Viewing the man pages for dhcpd.conf"> @@ -613,9 +607,8 @@ <body> <p> -Before you start the dhcp initialisation script edit the -<path>/etc/conf.d/dhcp</path> file so that it looks something like -this: +Before you start the dhcp initialisation script edit the +<path>/etc/conf.d/dhcp</path> file so that it looks something like this: </p> <pre caption="Sample /etc/conf.d/dhcp"> @@ -624,10 +617,10 @@ </pre> <p> -The <c>IFACE</c> variable is the device -you wish to run your DHCP server on, in our case <c>eth0</c>. Adding more -arguments to the <c>IFACE</c> variable can be useful for a complex network -topology with multiple Ethernet cards. To start the dhcp server type: +The <c>IFACE</c> variable is the device you wish to run your DHCP server on, in +our case <c>eth0</c>. Adding more arguments to the <c>IFACE</c> variable can be +useful for a complex network topology with multiple Ethernet cards. To start the +dhcp server type: </p> <pre caption="Starting the dhcp server on the master"> @@ -666,8 +659,8 @@ </note> <p> -If you get the following message it probably means there is something wrong -in the configuration file but that the DHCP server is broadcasting correctly. +If you get the following message it probably means there is something wrong in +the configuration file but that the DHCP server is broadcasting correctly. </p> <pre caption="Sample dhpc server error"> @@ -688,20 +681,18 @@ </chapter> <chapter> -<title>Configuring the TFTP server and PXE Linux Bootloader and/or Etherboot </title> +<title>Configuring the TFTP server and PXE Linux Bootloader and/or Etherboot</title> <section> <title>About the TFTP server</title> <body> <p> -TFTP stands for Trivial File Transfer Protocol. The TFTP server is going to -supply the slaves with a kernel and an initial filesystem. All of the -slave kernels and filesystems will be stored on the TFTP server, so it's -probably a good idea to make the master the TFTP server. +TFTP stands for Trivial File Transfer Protocol. The TFTP server is going to +supply the slaves with a kernel and an initial filesystem. All of the slave +kernels and filesystems will be stored on the TFTP server, so it's probably a +good idea to make the master the TFTP server. </p> - - </body> </section> <section> @@ -709,9 +700,9 @@ <body> <p> -A highly recommended tftp server is available as the tftp-hpa package. -This tftp server happens to be written by the author of SYSLINUX and it works -very well with pxelinux. To install simply type: +A highly recommended tftp server is available as the tftp-hpa package. This +tftp server happens to be written by the author of SYSLINUX and it works very +well with pxelinux. To install simply type: </p> <pre caption="Installing the tfp server"> @@ -736,9 +727,9 @@ </pre> <p> -The <c>-l</c> option indicates that this server listens in stand alone mode so -you don't have to run inetd. The <c>-v</c> indicates that log/error messages -should be verbose. The <c>-s /diskless</c> specifies the root of your tftp +The <c>-l</c> option indicates that this server listens in stand alone mode so +you don't have to run inetd. The <c>-v</c> indicates that log/error messages +should be verbose. The <c>-s /diskless</c> specifies the root of your tftp server. </p> @@ -773,11 +764,10 @@ <body> <p> -This section is not required if you are only using Etherboot. -PXELINUX is the network bootloader equivalent to LILO or GRUB and will be -served via TFTP. It is essentially a tiny set of instructions that tells the -client where to locate its kernel and initial filesystem and allows for -various kernel options. +This section is not required if you are only using Etherboot. PXELINUX is the +network bootloader equivalent to LILO or GRUB and will be served via TFTP. It +is essentially a tiny set of instructions that tells the client where to locate +its kernel and initial filesystem and allows for various kernel options. </p> </body> @@ -787,8 +777,8 @@ <body> <p> -You will need to get the pxelinux.0 file which comes in the SYSLINUX package -by H. Peter Anvin. You can install this package by typing: +You will need to get the pxelinux.0 file which comes in the SYSLINUX package by +H. Peter Anvin. You can install this package by typing: </p> <pre caption="Installing syslinux"> @@ -806,8 +796,8 @@ </note> <p> -Before you start your tftp server you need to setup pxelinux. First copy -the pxelinux binary into your <path>/diskless</path> directory: +Before you start your tftp server you need to setup pxelinux. First copy the +pxelinux binary into your <path>/diskless</path> directory: </p> <pre caption="Setting up the remote bootloader"> @@ -817,13 +807,13 @@ </pre> <p> -This will create a default bootloader configuration file. The binary -<path>pxelinux.0</path> will look in the <path>pxelinux.cfg</path> directory -for a file whose name is the client's IP address in hexadecimal. If it does not -find that file it will remove the rightmost digit from the file name and try -again until it runs out of digits. Versions 2.05 and later of syslinux first -perform a search for a file named after the MAC address. If no file is found, -it starts the previously mentioned discovery routine. If none is found, the +This will create a default bootloader configuration file. The binary +<path>pxelinux.0</path> will look in the <path>pxelinux.cfg</path> directory for +a file whose name is the client's IP address in hexadecimal. If it does not find +that file it will remove the rightmost digit from the file name and try again +until it runs out of digits. Versions 2.05 and later of syslinux first perform a +search for a file named after the MAC address. If no file is found, it starts +the previously mentioned discovery routine. If none is found, the <path>default</path> file is used. </p> @@ -863,7 +853,7 @@ compiled the slave kernel with <c>NFS_ROOT_SUPPORT</c>, we will specify the nfsroot here. The first IP is the master's IP and the second IP is the directory that was created in <path>/diskless</path> to store the slave's -initial filesystem. +initial filesystem. </p> </body> @@ -878,8 +868,8 @@ </note> <p> -Etherboot boots network boot images from a TFTP server. As the PXE this is -equivalent to LILO or GRUB. The <c>mknbi</c> utility enables you to create +Etherboot boots network boot images from a TFTP server. As the PXE this is +equivalent to LILO or GRUB. The <c>mknbi</c> utility enables you to create different images using different options. </p> @@ -890,10 +880,10 @@ <body> <p> -You will need to get the <c>mknbi</c> (utility for making tagged kernel images -useful for netbooting) package to create your Etherboot images. This tool will -create a preconfigured kernel image from your original kernel. This contains -the boot options as shown further down. +You will need to get the <c>mknbi</c> (utility for making tagged kernel images +useful for netbooting) package to create your Etherboot images. This tool will +create a preconfigured kernel image from your original kernel. This contains the +boot options as shown further down. </p> <pre caption="Installing mknbi"> @@ -907,9 +897,9 @@ <body> <p> -In this section we will create a simple etherboot image. As the dhcp server -gives out the clients root-path in the "option root-path" dhcp.conf, we do -not have to include this here. More details can be found in the mknbi manual. +In this section we will create a simple etherboot image. As the dhcp server +gives out the clients root-path in the "option root-path" dhcp.conf, we do not +have to include this here. More details can be found in the mknbi manual. </p> <pre caption="mknbi manual"> @@ -917,9 +907,9 @@ </pre> <p> -Making the boot images. This will create a ELF bootable image capable of -passing dhcp and the rootpath to the kernel. Also forcing the kernel to browse -the network for a dhcp server. +Making the boot images. This will create a ELF bootable image capable of passing +dhcp and the rootpath to the kernel. Also forcing the kernel to browse the +network for a dhcp server. </p> <pre caption="making netboot images"> @@ -927,7 +917,7 @@ </pre> <note> -For the arch specific images you have to type <c>bzImage_arch</c> and +For the arch specific images you have to type <c>bzImage_arch</c> and <c>vmlinuz_arch</c>. </note> @@ -947,12 +937,12 @@ </pre> <p> -Now you can listen to various network traffic and make sure your client/server -interactions are functioning. If something isn't working there are a few -things you might want to check. First make sure that the client/server is -physically connected properly and that the networking cables are not damaged. -If your client/server is not receiving requests on a particular port make sure -that there is no firewall interference. To listen to interaction between two +Now you can listen to various network traffic and make sure your client/server +interactions are functioning. If something isn't working there are a few things +you might want to check. First make sure that the client/server is physically +connected properly and that the networking cables are not damaged. If your +client/server is not receiving requests on a particular port make sure that +there is no firewall interference. To listen to interaction between two computers type: </p> @@ -961,7 +951,7 @@ </pre> <p> -You can also use <c>tcpdump</c> to listen on particular port such as the tftp +You can also use <c>tcpdump</c> to listen on particular port such as the tftp port by typing: </p> @@ -970,11 +960,11 @@ </pre> <p> -A common error you might receive is: "PXE-E32: TFTP open time-out". -This is probably due to firewall issues. If you are using <c>TCPwrappers</c>, -you might want to check <path>/etc/hosts.allow</path> and -<path>etc/hosts.deny</path> and make sure that they are configured properly. -The client should be allowed to connect to the server. +A common error you might receive is: "PXE-E32: TFTP open time-out". This is +probably due to firewall issues. If you are using <c>TCPwrappers</c>, you might +want to check <path>/etc/hosts.allow</path> and <path>etc/hosts.deny</path> and +make sure that they are configured properly. The client should be allowed to +connect to the server. </p> </body> @@ -988,8 +978,8 @@ <body> <p> -NFS stands for Network File System. The NFS server will be used to serve -directories to the slave. This part can be somewhat personalized later, but +NFS stands for Network File System. The NFS server will be used to serve +directories to the slave. This part can be somewhat personalized later, but right now all we want is a preliminary slave node to boot diskless. </p> @@ -1000,11 +990,11 @@ <body> <p> -Various client/server services do not listen on a particular port, but instead -rely on RPCs (Remote Procedure Calls). When the service is initialised it -listens on a random port and then registers this port with the Portmapper -utility. NFS relies on RPCs and thus requires Portmapper to be running -before it is started. +Various client/server services do not listen on a particular port, but instead +rely on RPCs (Remote Procedure Calls). When the service is initialised it +listens on a random port and then registers this port with the Portmapper +utility. NFS relies on RPCs and thus requires Portmapper to be running before +it is started. </p> </body> @@ -1014,8 +1004,8 @@ <body> <p> -The NFS Server needs kernel level support so if you don't have this you should -recompile your master's kernel. To double check your master's kernel +The NFS Server needs kernel level support so if you don't have this you should +recompile your master's kernel. To double check your master's kernel configuration type: </p> @@ -1024,7 +1014,7 @@ </pre> <p> -You should see output that looks something like this if your kernel has been +You should see output that looks something like this if your kernel has been properly configured: </p> @@ -1057,7 +1047,7 @@ </pre> <p> -This package will emerge a portmapping utility, nfs server, and nfs client +This package will emerge a portmapping utility, nfs server, and nfs client utilities and will automatically handle initialisation dependencies. </p> @@ -1078,13 +1068,13 @@ </pre> <p> -The <path>/etc/exports</path> file specifies how, to who and what to export -through NFS. The slave's fstab will be altered so that it can mount the NFS +The <path>/etc/exports</path> file specifies how, to who and what to export +through NFS. The slave's fstab will be altered so that it can mount the NFS filesystems that the master is exporting. </p> <p> -A typical <path>/etc/exports</path> for the master should look something like +A typical <path>/etc/exports</path> for the master should look something like this: </p> @@ -1100,15 +1090,14 @@ </pre> <p> -The first field indicates the directory to be exported and the next field +The first field indicates the directory to be exported and the next field indicates to who and how. This field can be divided in two parts: who should be -allowed to mount that particular directory, and what the mounting -client can do to the filesystem: <c>ro</c> for read only, <c>rw</c> for -read/write; <c>no_root_squash</c> and <c>no_all_squash</c> are -important for diskless clients that are writing to the disk, so that they -don't get "squashed" when making I/O requests. The slave's fstab file, -<path>/diskless/192.168.1.21/etc/fstab</path>, should look like -this: +allowed to mount that particular directory, and what the mounting client can do +to the filesystem: <c>ro</c> for read only, <c>rw</c> for read/write; +<c>no_root_squash</c> and <c>no_all_squash</c> are important for diskless +clients that are writing to the disk, so that they don't get "squashed" when +making I/O requests. The slave's fstab file, +<path>/diskless/192.168.1.21/etc/fstab</path>, should look like this: </p> <pre caption="Sample slave fstab"> @@ -1131,14 +1120,14 @@ mounted and the second field indicates where. The third field describes the filesystem and should be NFS for any NFS mounted directory. The fourth field indicates various options that will be used in the mounting process (see -mount(1) for info on mount options). Some people have had difficulties with +mount(1) for info on mount options). Some people have had difficulties with soft mount points so we made them all hard, but you should look into various -<path>/etc/fstab</path> options to make your cluster more efficient. +<path>/etc/fstab</path> options to make your cluster more efficient. </p> <p> -The last file you should edit is <path>/etc/conf.d/nfs</path> which -describes a few options for nfs when it is initialised and looks like this: +The last file you should edit is <path>/etc/conf.d/nfs</path> which describes a +few options for nfs when it is initialised and looks like this: </p> <pre caption="Sample master /etc/conf.d/nfs"> @@ -1163,7 +1152,7 @@ <body> <p> -You should start the nfs server with its init script located in +You should start the nfs server with its init script located in <path>/etc/init.d</path> by typing: </p> @@ -1190,7 +1179,7 @@ <body> <p> -We will now make the slave's file system in sync with the master's and provide +We will now make the slave's file system in sync with the master's and provide the necessary binaries while still preserving slave specific files. </p> @@ -1201,8 +1190,7 @@ </pre> <note> -The reason for rsync -avz instead of cp is to maintain symlinks and -permissions +The reason for rsync -avz instead of cp is to maintain symlinks and permissions. </note> </body> @@ -1215,8 +1203,8 @@ The default scripts will try to run <e>checkroot</e> which does not make sense on your slave nodes. The hard way out is to manually edit the <path>/diskless/192.168.1.21/sbin/rc</path> script but this is cumbersome, -dangerous and could break if you decided to sync your node file system again -and forgot to leave this script alone. The trick is to have a +dangerous and could break if you decided to sync your node file system again and +forgot to leave this script alone. The trick is to have a <path>/fastboot</path> file when your system boots. This file tells <e>checkroot</e> not to run any file system check. But it will also erase the file when it has finished the initialisation process. That is why we need to @@ -1258,10 +1246,10 @@ </p> <warn> -Do not use the <c>rc-update</c> program to add or remove scripts from the -slave runlevels when logged on your master. This would change your master -runlevels. You need to create the links manually or log into your slave nodes -using ssh or connect a screen and keyboard to your slave. +Do not use the <c>rc-update</c> program to add or remove scripts from the slave +runlevels when logged on your master. This would change your master runlevels. +You need to create the links manually or log into your slave nodes using ssh or +connect a screen and keyboard to your slave. </warn> <pre caption="Typical slave runlevels"> @@ -1271,7 +1259,7 @@ drwxr-xr-x 2 root root 4096 2003-10-01 21:10 default drwxr-xr-x 2 root root 4096 2003-03-13 19:05 nonetwork drwxr-xr-x 2 root root 4096 2003-02-23 12:26 single - + /diskless/192.168.1.21/etc/runlevels/boot: total 0 lrwxrwxrwx 1 root root 20 2003-10-18 17:28 bootmisc -> /etc/init.d/bootmisc @@ -1285,7 +1273,7 @@ lrwxrwxrwx 1 root root 20 2003-10-18 17:28 netmount -> /etc/init.d/netmount lrwxrwxrwx 1 root root 21 2003-10-18 17:28 rmnologin -> /etc/init.d/rmnologin lrwxrwxrwx 1 root root 19 2003-10-18 17:28 urandom -> /etc/init.d/urandom - + /diskless/192.168.1.21/etc/runlevels/default: total 0 lrwxrwxrwx 1 root root 23 2003-10-18 17:28 consolefont -> /etc/init.d/consolefont @@ -1295,11 +1283,11 @@ lrwxrwxrwx 1 root root 16 2003-10-18 17:28 sshd -> /etc/init.d/sshd lrwxrwxrwx 1 root root 21 2003-10-18 17:28 syslog-ng -> /etc/init.d/syslog-ng lrwxrwxrwx 1 root root 17 2003-10-18 17:28 vixie-cron -> /etc/init.d/vixie-cron - + /diskless/192.168.1.21/etc/runlevels/nonetwork: total 0 lrwxrwxrwx 1 root root 17 2003-10-18 17:28 local -> /etc/init.d/local - + /diskless/192.168.1.21/etc/runlevels/single: total 0 </pre> @@ -1312,7 +1300,7 @@ </body> </section> -<!-- +<!-- <section> <title>An alternative : ClusterNFS</title> @@ -1327,7 +1315,7 @@ <p> If you don't fancy having a distinct root for each slave because it needs some -maintenance when upgrading files from the master directories, you could share +maintenance when upgrading files from the master directories, you could share the same root across all nodes, master and slaves included. This means all your machines need to be compatible because you will have only one set of binaries. You also need to be aware that this might have security issues because all of @@ -1350,7 +1338,7 @@ </p> <p> -Very shortly, this is what differs from the installation procedure described +Very shortly, this is what differs from the installation procedure described above: </p> @@ -1407,6 +1395,6 @@ </body> </section> --> -</chapter> +</chapter> </guide> -- [email protected] mailing list
