Re: [SLUG] Problems With Network Boot via bootp for Wyse Winterm 5355

From: Russell Hires (rhires@earthlink.net)
Date: Thu Apr 03 2003 - 21:14:19 EST


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Having played with netbooting a bit, I know that you may need to know the
ethernet card's unique ID. I forget the right name for it, and since you
aren't booting the terminal you wouldn't have a way to find out. :-| Hmm...

But it's an idea... :-) I wish I could be more helpful...

Russell

On Thursday 03 April 2003 09:20 am, John Clay wrote:
> I have a Winterm 5355se (obsolete - unsupported) that supports bootp. I'm
> trying to get it to boot off of my operational LTSP system but have been
> unsuccessful so far. It makes some headway as I see the following in
> /var/log/messages pertaining to it on the LTSP server:
>
> DHCPDISCOVER blah blah blah .....
> DHCPOFFER .....
> DHCPREQUEST .....
> DHCPACK .....
>
> The terminal gets it's IP address and can be pinged. So it's getting, and
> is able to use, some of the information sent by dhcpd in the reply packet
> which should include the: * IP address
> * netmask
> * pathname of the kernel
> * pathname of the root file system
> * optional parameters
>
> My understanding is that the bootp code is then supposed to use tftp, and
> the information listed above, to download the kernel but I see no evidence
> of an attempt to do that in /var/log/messages.
>
> The water is deep and I'm out of ideas.
>
> If anyone has a hunch how to proceed please let me know.
>
> Thanks Much
> John Clay
> Tallahassee, FL

- --
Linux -- the OS for the Renaissance Man
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org

iD8DBQE+jOp8AqKGrvVshJQRAizfAKDQpCypmdAee7Q1g0/X5cpHHTUb5QCfXh5u
i/Ut2plfnew5A4o6Zf3ArgE=
=RfZY
-----END PGP SIGNATURE-----



This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 17:58:03 EDT