Is there anyway to get around the packet-size
problem with bootp and remote installs?
The trickyness I am having is this. If I only have one bootp
server, I don't have to use :sa=...:, but if I do, I have to use
:sa=...:, in case the bootpd that answers the request isn't the one
with the OS distribution on it. BUT, using :sa=...: makes the bootp
packet too big (i.e. daemon.log messages from bootpd are the familiar
"no room for ..."). I have never seen this problem with bootpd's on
other Unix's, even with failry loaded entries. Am I missing something?
I _assume_ that there is no way around this problem because the new ris
stuff goes through pains to keep the total byte count in the bootp
entries it creates to a minimum (like using the /ris/ris1.a link to
/usr/var/adm/ris1.alpha), but maybe someone has a suggestion. I would
prefer to be able to replicate the same /etc/bootptab entry to
all of the systems. Is there some twist on dhcp with joind that would
help this problem? Maybe new firmware on the systems (dec3000/M700's)?
Thanks for any clues.
_____________________________________________________________________
/ Brian C. Hill bchill_at_bch.net
http://brian.bch.net \
| Systems Programmer University of California, Davis |
| Unix Specialist BCH Technical Services |
Received on Tue May 19 1998 - 20:33:55 NZST