home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!haven.umd.edu!darwin.sura.net!spool.mu.edu!uwm.edu!rpi!usc!elroy.jpl.nasa.gov!swrinde!cs.utexas.edu!sun-barr!news2me.EBay.Sun.COM!seven-up.East.Sun.COM!tyger.Eng.Sun.COM!geoff
- From: geoff@tyger.Eng.Sun.COM (Geoff Arnold @ Sun BOS - R.H. coast near the top)
- Newsgroups: comp.protocols.nfs
- Subject: Re: PC-NFS and Bootp
- Date: 5 Nov 1992 13:56:26 GMT
- Organization: SunSelect
- Lines: 22
- Distribution: na
- Message-ID: <1db96aINN4b4@seven-up.East.Sun.COM>
- References: <Bx7pzE.6DL@willamette.edu>
- NNTP-Posting-Host: tyger.east.sun.com
-
- Quoth dan@willamette.edu (Dan Revel) (in <Bx7pzE.6DL@willamette.edu>):
- #I would like to be able to use BOOTP to provide boot info (ip address,
- #etc.) to our PC-NFS clients. Right now they are RARPing, but I would
- #like to be able to set up clients on a subnet that does not have a RARP
- #server. Is this possible? Is it the 'right' approach?
-
- Our current thinking (*not* committed product plans, please note!) is
- that we'll skip BOOTP and adopt DHCP, which is a much more complete
- solution. There are a couple of gotchas in the current PC-NFS code
- which make it impractical for someone to plug in their own BOOTP/DHCP
- module; we plan to eliminate these bugs in the next PC-NFS release and
- roll out DHCP support as soon after that as practicable. Bear in mind
- that DHCP is still not an RFC, though the client-server protocol seems
- essentially stable. (Server-server is a different kettle of
- fish.....:-)
-
- Geoff
- --
- Geoff Arnold, PC-NFS architect, Sun Select. (geoff.arnold@East.Sun.COM)
- -----------
- News software that enforces a four-line .signature limit is responsible for
- the fact that these postings just go on and on and on and seem to end in mid-
-