Re: [Unattended] Fully unattended, changing pxelinux boot files

2004-02-06 Thread Rönnblom Janåke /Teknous
Max Lovius <[EMAIL PROTECTED]> skriver: >Thanks for all the ideas and advice. > >Patrick J. LoPresti Wrote: >> 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. > >Brad Erdman Wrote: >>This is what I do. It work

RE: [Unattended] Fully unattended, changing pxelinux boot files

2004-02-06 Thread Max Lovius
Thanks, I should have rtfm... Linux to the rescue then.:-) Max -Original Message- From: Patrick J. LoPresti [mailto:[EMAIL PROTECTED] Sent: Friday, 06 February, 2004 3:56 PM To: Max Lovius Cc: 'Brad Erdman'; '[EMAIL PROTECTED]' Subject: Re: [Unattended] Fully

Re: [Unattended] Fully unattended, changing pxelinux boot files

2004-02-06 Thread Patrick J. LoPresti
Max Lovius <[EMAIL PROTECTED]> writes: > When I try on the client to use IO::Socket, IO::Handle, I die with "can't > locate SelectSaver.pm in @INC (@INC contains: Z:\lib > /dev/env/DJDIR/lib/perl5 /dev/env/DJDIR/lib/perl5/site > /dev/env/DJDIR/lib/perl5/site..."then the other modules same thing.

RE: [Unattended] Fully unattended, changing pxelinux boot files

2004-02-06 Thread Max Lovius
Thanks for all the ideas and advice. Patrick J. LoPresti Wrote: > 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. Brad Erdman Wrote: >This is what I do. It works very well, but as stated, there are security i

RE: [Unattended] Fully unattended, changing pxelinux boot files

2004-02-04 Thread Brad Erdman
> 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

Re: [Unattended] Fully unattended, changing pxelinux boot files

2004-02-04 Thread Patrick J. LoPresti
Max Lovius <[EMAIL PROTECTED]> writes: > What I want to do is : > > (1) remotely reboot a computer. > (2) have the first boot, partion hard drive. > (3) have the second reboot, continue the unattended installation. Easy enough. > (4) have a system that will then change automatically "unattended

RE: [Unattended] Fully unattended, changing pxelinux boot files

2004-02-04 Thread Brad Erdman
Lovius [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 04, 2004 2:27 AM > To: 'Jordan Share' > Cc: '[EMAIL PROTECTED]' > Subject: RE: [Unattended] Fully unattended, changing pxelinux boot files > > Jordan Share wrote: > > >Rather than change the c

RE: [Unattended] Fully unattended, changing pxelinux boot files

2004-02-04 Thread Max Lovius
Jordan Share wrote: >Rather than change the config files (if that is indeed what you need to >do), you might consider changing the IP addresses handed out to the >various MAC addresses. pxelinux.0 will get its config file based on >what IP address it was given. So you could dynamically reconf

Re: [Unattended] Fully unattended, changing pxelinux boot files

2004-02-03 Thread Jordan Share
Max Lovius wrote: I am working on fully unattended installations ideas. Anyone done any work on changing pxelinux boot files? The last step! Or some other way to complete the task of automation? Might I have missed something? The only thing I can think of is a perl or dos tftp client! But thought

[Unattended] Fully unattended, changing pxelinux boot files

2004-02-03 Thread Max Lovius
I am working on fully unattended installations ideas. Anyone done any work on changing pxelinux boot files? The last step! Or some other way to complete the task of automation? Might I have missed something? The only thing I can think of is a perl or dos tftp client! But thought I should ask, befor