When using an Etherboot (or BOOTP) boot ROM network booting is quite straightforward:
The client PC contacts the DHCP (or BOOTP) server to get its IP address and the name of
the boot image file (ltsp kernel) to transfer down and execute.  The client PC uses TFTP to
download the ltsp kernel from the boot server; hence the reason for the TFTP daemon. 
                                 
In PXE booting, things are little different.  The PXE client must first download a
network bootstrap program (nbp) also known as the PXE loader.  The PXE loader will in turn
transfer down the ltsp kernel.  Why is this so?  This is just the nature of PXE.
The PXE loader or nbp must not be greater than 32K in size; otherwise, you'll get the
unintuitive "PXE-E3A TFTP too many packages"  error.  Furthermore,  PXE boot ROMs are
unable to execute tagged kernels.
                                 
Have a look at the PXE-LTSP How-To or the PXELINUX doc for details. These files have links on the LTSP
website.
                                 
 
----- Original Message -----
From: "Bala murugan" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Saturday, December 21, 2002 10:50 PM
Subject: [Ltsp-discuss] error in Client TFTP connection

> Dear guys
>
> I have installed as per documentation in my RH7.3. In my client PC
> sucessfully connectet via TFTP. But Client gives the following error
> "Too many pakages"
>
> Fresh installation
> My client ethernet card is Intel Pro 10/100+
>
> Please suggest me
>
>
> Balamurugan.T
> Network Engineer
> Chennai -India
>

Reply via email to