Shaun Q
2006-Aug-21 19:53 UTC
[syslinux] Passing parameters for the server's hostname/ip to the client?
Hey everyone -- Is there a way to refer to the server with the tftpboot images so that when a client is booting diskless, it can mount an nfs directory to that tftp server? That is to say that I have a tftp server on 192.168.0.244. The usr directory is set to be shared amoung the diskless clients via nfs. In the root image, I have /etc/fstab set to something like: blah blah 192.168.0.244:/usrnfs /usr ... But instead of that entry being 192.168.0.244 in there, I want it to be more dynamic, something like: blah blah tftpboot_passed_from_pxe:/usrnfs /usr This is so that if the 192.168.0.244 machine goes down, the engineers here can just boot up a secondary server with a copy of the first one and not have to edit anything, just boot the secondary server and reboot the diskless clients. Does that make sense? :) Thanks! Shaun
H. Peter Anvin
2006-Aug-21 23:33 UTC
[syslinux] Passing parameters for the server's hostname/ip to the client?
Shaun Q wrote:> Hey everyone -- > > Is there a way to refer to the server with the tftpboot images so that > when a client is booting diskless, it can mount an nfs directory to that > tftp server? > > That is to say that I have a tftp server on 192.168.0.244. The usr > directory is set to be shared amoung the diskless clients via nfs. In the > root image, I have /etc/fstab set to something like: > blah > blah > 192.168.0.244:/usrnfs /usr ... > > But instead of that entry being 192.168.0.244 in there, I want it to be > more dynamic, something like: > blah > blah > tftpboot_passed_from_pxe:/usrnfs /usr > > This is so that if the 192.168.0.244 machine goes down, the engineers > here can just boot up a secondary server with a copy of the first one and > not have to edit anything, just boot the secondary server and reboot the > diskless clients. > > Does that make sense? :) >The easiest way to do that is to just use a DNS entry. -hpa