Way back on Fri, 29 Aug 1997 08:58:33 -0700, "Jeffrey G. Micono 6533
(Ktech)" <jgmicon_at_sandia.gov> said:
> I finally figured it out after I posted last night, however,
> Tim Winders<twinders_at_spc.cc.tx.us> did offer a suggestion that I
> should test tftp.
> The problem was I had insufficient stuff in my bootptab entry.
> I originally had this:
> lanserv:ha=0080A317EE59:ip=134.253.237.163:td=/tftpboot:hd=/lantronix
> What I eventually got working is this:
> .info:\
> :ds=134.253.181.25 132.175.42.2:\
> :sm=255.255.0.0:gw=134.253.237.254:\
> :vm=rfc1048:
> .lantronix:\
> :hd=/tftpboot/lantronix:\
> :tc=.info:
> lanserv:ht=ether:ha=0080A317EE59:ip=134.253.237.163:tc=.lantronix:
I had the same problem Jeffrey did, saved the message, and only recently
followed up on it. I played around with it a bit, and it seems the
magic here is the 'ht=ether' key. So long as BIND can resolve the name
you give the device in the bootptab file (i.e., in this instance,
'lanserv' is mapped to an IP address in the /etc/hosts table, by NIS, or
by DNS), you can dispense with the ip, ds, sm, gw, and vm fields (unless
your device needs some of this info to boot). We were looking at this
to boot a DEC terminal server and some stray X terms we had lying
around.
--
Robert L. McMillin | Not the voice of Syseca, Inc. | rlm_at_syseca-us.com
Personal: rlm_at_helen.surfcty.com | rlm_at_netcom.com
Put 'rabbit' in your Subject: or my spam-schnauzer will eat your message.
Received on Wed Jan 14 1998 - 21:33:12 NZDT