home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!spool.mu.edu!enterpoop.mit.edu!eru.mt.luth.se!lunic!sunic!mcsun!sun4nl!sci.kun.nl!cs.kun.nl!lwj
- From: lwj@cs.kun.nl (Luc Rooijakkers)
- Newsgroups: comp.protocols.nfs
- Subject: Obtain PC-NFS serial over BOOTP?
- Message-ID: <C17nnG.8rp@sci.kun.nl>
- Date: 21 Jan 93 15:42:51 GMT
- Sender: news@sci.kun.nl (News owner)
- Organization: University of Nijmegen, The Netherlands
- Lines: 29
- Nntp-Posting-Host: zeus.cs.kun.nl
-
- I am looking for a program that uses BOOTP to obtain a PC-NFS
- serial number and then patches it into the already loaded PCNFS.SYS
- (which is easily found by walking the DOS device chain). This would
- allow me to distribute identical boot floppies. I am using a packet driver.
-
- Such a program could also construct a NETWORK.BAT and DRIVES.BAT from
- the BOOTP info, so that PC-NFS does not need to RARP and access NIS for
- this info.
-
- So, I have several questions:
-
- 1) Does such a program exist?
-
- 2) If not, does a reasonably small BOOTP client program exist? Several
- packages are capable of using BOOTP, but they are all rather large.
- I could then easily add the functionality myself.
-
- 3) Is there a standard way of adding PC-NFS serial numbers, NIS domain,
- NIS server, etc to bootptab (i.e. what RFC1048 numbers are used?)
-
- 4) Is there a way to get NET INIT to read NETWORK.BAT and/or DRIVES.BAT
- from somewhere else then NFSPATH (e.g. stdin)? Or do I have to invoke
- all the NET commands myself (does NET INIT do anything more then reading
- NETWORK.BAT and DRIVES.BAT?)
-
- --
- Luc Rooijakkers Internet: lwj@cs.kun.nl
- Faculty of Mathematics and Computer Science UUCP: uunet!cs.kun.nl!lwj
- University of Nijmegen, the Netherlands tel. +3180652271
-