> Harder. You need a way for the install.pl on the client machine to > indicate a state change back to the TFTP (or maybe DHCP) server. > > The easiest approach, I think, is to export the pxelinux.cfg directory > inside the TFTP root as a Windows share, modify the boot disk to mount > it as P: or whatever, and edit install.pl to generate a pxelinux > config file named after the system's IP address.
This is what I do. It works very well, but as stated, there are security implications. An additional step I take is to enforce quota's on the hard drive and give the install account a 1MB limit. This makes it effectively useless for the unscrupulous person looking for a dump site. > You will need to > configure your DHCP server to hand out a fixed IP address to the > client, I am afraid, unless you have programmatic control over the > DHCP options (which is unlikely unless your DHCP server is a Unix > box). > This will work, although it will not be secure because anybody on your > network might map the pxelinux.cfg directory and scribble all over it. > > This can probably be corrected... You could export a different > directory (call it "incoming.cfg" or somesuch) and have install.pl > write its config file there. Then you would manually or automatically > move that file over to pxelinux.cfg, but only if you were expecting it > to appear. So anybody on your network could still drop files into > "incoming.cfg", but those files would have no effect unless you moved > them over to pxelinux.cfg. > > How much work are you willing to do to make this happen? You should > probably start by downloading a copy of SYSLINUX (see > http://syslinux.zytor.com/) and reading the pxelinux.doc file... > > - Pat > > > ------------------------------------------------------- > The SF.Net email is sponsored by EclipseCon 2004 > Premiere Conference on Open Tools Development and Integration > See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. > http://www.eclipsecon.org/osdn > _______________________________________________ > unattended-info mailing list > [EMAIL PROTECTED] > https://lists.sourceforge.net/lists/listinfo/unattended-info ------------------------------------------------------- The SF.Net email is sponsored by EclipseCon 2004 Premiere Conference on Open Tools Development and Integration See the breadth of Eclipse activity. February 3-5 in Anaheim, CA. http://www.eclipsecon.org/osdn _______________________________________________ unattended-info mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/unattended-info
