"Diskless Nodes with Gentoo", September 16, 2005 version: There are a couple of initscripts that should typically not be run by a diskless client. They are net.eth0 dhcp in.tftpd nfs If one for some reason re-runs the copy command in Code Listing 2.12 all these initscripts will be symlinked from /diskless/192.168.1.21/etc/runlevels/default/. Therefore I suggest to add a few words about this under the "Initialisation scripts" header towards the end of the document. Something like ----------------------------------------- You typically don't want your slave to act as a server for dhcp, tftp or nfs (you already have the master for this). Furthermore you don't want the slave to run the initscript that sets up the network interface, since that is done earlier on in the boot sequence. Therefore make sure to remove the following symlinks: Code Listing X.X: # rm -f /diskless/192.168.1.21/etc/runlevels/default/net.eth0 # rm -f /diskless/192.168.1.21/etc/runlevels/default/dhcp # rm -f /diskless/192.168.1.21/etc/runlevels/default/in.tftpd # rm -f /diskless/192.168.1.21/etc/runlevels/default/nfs
rather than naming them explicitly, it should be mentioned that you clean all the scripts that are used on the host system but not the slave
(In reply to comment #1) > rather than naming them explicitly, it should be mentioned that you clean all > the scripts that are used on the host system but not the slave I agree that this is precisely what to do. However I still think it may be useful to mention these links explicitly, just to minimize the mental effort that a first-time diskless administrator must spend to get a slave to boot successfully. No big deal though.
This is already present in the doc. See this paragraph just below code listing 6.3: "You need as many init scripts under /diskless/192.168.1.21/etc/runlevels as you need services on your diskless nodes. It all depends on what you want your slaves to do." Obviously, the user will add and delete runscripts as necessary. Thanks for reporting, though.
