Sure, sorry.  PXE is Intel's Pre Execution Environment.  In the past it really
only applied to network boots.  As such we had to use something called BPBatch.
Just recently though they've allowed booting to the hard drive.  Basically, when
the machine boots it, before it loads the OS, it goes up to the server and reads a
configuration file.  Based on the contents of that configuration file the boot
continues.  It allows centralized management of the boot process.  So, if used for
distribution, most of the time you just boot to the local hard drive.  If you want
to update something, like the whole machine :-), you can have it boot off of the
server.  In our case, using Red Hat, we get to the RH CD via TFTP and we install
using Kickstart.  No, we had no particular problems getting that environment
running and we've not patched the stock Red Hat Kickstart in any way.

I hope that answers your question.  A search brings up many hits but the short
Intel writeup is at:
http://developer.intel.com/ial/wfm/wfmover.htm#new

Paul Lussier wrote:

> In a message dated: Fri, 16 Mar 2001 11:48:35 EST
> Greg Kettmann said:
>
> >We use RH's Kickstart and PXE Linux to avoid the diskette problem and to make
> >decisions at boot time as to whether we'd like to boot across a network or
> >from the local hard drive.
> [...snip...]
> >PXE Linux (or even just PXE) does require support from the Ethernet adapter
> >but it's not difficult to find suitable adapters.   I don't know how this
> >translates into the non-Intel space and would be interested to hear.
>
> Can you expound upon what PXE Linux is?  I've never heard of it.
>
> Thanks,
> --
>
> Seeya,
> Paul
> ----
>         It may look like I'm just sitting here doing nothing,
>    but I'm really actively waiting for all my problems to go away.
>
>          If you're not having fun, you're not doing it right!


**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************

Reply via email to