On October 23, 2013, Nicholas Leippe wrote: > Why do you need to customize the bootloader binary?
The original idea was, as stated, to put each interface's default boot options in a different file (i.e. the "default" for eth1 is /tftpboot/pxelinux.conf/default.eth1 and for eth2 it's /tftpboot/pxelinux.conf/default.eth2), but I am reminded by other posts that I can do the same by making filenames that represent the IP address. That's a handy way to accomplish the thing I was after. So that's what I'll do. Thanks Michael Torrie! :) --- Dan On Wed, Oct 23, 2013 at 8:21 PM, Nicholas Leippe <[email protected]> wrote: > Why do you need to customize the bootloader binary? > > > On Wed, Oct 23, 2013 at 2:15 AM, Dan Egli <[email protected]> wrote: > > > Anyone know of a good page that details building the pxe boot file > > (pxelinux.0)? In one of my side projects I'm considering setting the boot > > server so that if boxes are connected to eth1 the "default" file they > pull > > would be something like /tftpboot/primary/default, and if it's connected > to > > eth2, it would be /tftpboot/secondary/default. The problem is I've only > > ever used the provided pxelinux.0 file, so I wouldn't know how to build a > > new one. If someone knows of a good web page that describes how to > > customize the pxelinux.0 file so that I could have like > > /tftpboot/pxelinux.primary and /tftpboot/pxelinux.secondary, I'd love to > > know of it. This is likely to be on Fedora if that makes any difference. > > Step by Step directions preferred. :) > > > > > > > > Thanks! > > > > > > --- Dan > > > > /* > > PLUG: http://plug.org, #utah on irc.freenode.net > > Unsubscribe: http://plug.org/mailman/options/plug > > Don't fear the penguin. > > */ > > > > /* > PLUG: http://plug.org, #utah on irc.freenode.net > Unsubscribe: http://plug.org/mailman/options/plug > Don't fear the penguin. > */ > /* PLUG: http://plug.org, #utah on irc.freenode.net Unsubscribe: http://plug.org/mailman/options/plug Don't fear the penguin. */
