Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!usc!sdd.hp.com!spool.mu.edu!news.cs.indiana.edu!widener!iggy.GW.Vitalink.COM!lll-winken!lll-crg.llnl.gov
From: rwolski@lll-crg.llnl.gov (Richard Wolski)
Newsgroups: comp.protocols.tcp-ip
Subject: Bootp questions (a possible reposting)
Keywords: bootp
Message-ID: <94488@lll-winken.LLNL.GOV>
Date: 2 Apr 91 22:12:25 GMT
Sender: usenet@lll-winken.LLNL.GOV
Organization: Lawrence Livermore National Laboratory
Lines: 40
Nntp-Posting-Host: lll-crg.llnl.gov

Profuse apologies to those of you who have seen this before.  I am 
posting this request for a friend with a somewhat unreliable news feed.

Thanks for your patience,

Rich

===============================================

Sorry if you have seen this before, but my news feed
has been flakey lately and I haven't seen it
posted.


Hi.

I have some questions about bootp that someone out
there might be able to answer.

Is the bootp 2.1 (cmu) the must current version?
What other versions are there out there
(and where can I get them)?

Is bootp the most widely used protocol
to boot up network devices? Are there others?

Has anyone run up against the 64 byte limitation
of vendor specific data? If so, what did you
do you about it?

What is the method for specifying a vendor
magic cookie (do you have to modify
the boop server source?).

Thanks any information will be appreciated!
If I get responses, I will post the replies.

Emily Hipp
ehipp@wrs.com