Xref: utzoo comp.protocols.tcp-ip.ibmpc:4041 bit.listserv.novell:7201 Path: utzoo!attcan!uunet!shelby!lll-winken!bu.edu!wuarchive!zaphod.mps.ohio-state.edu!samsung!umich!vela!srodawa From: srodawa@vela.acs.oakland.edu (Dr. Srodawa) Newsgroups: comp.protocols.tcp-ip.ibmpc,bit.listserv.novell Subject: Re: PC remote boot protocol Message-ID: <3514@vela.acs.oakland.edu> Date: 25 Oct 90 02:08:31 GMT References: <90296.121048MAH@awiwuw11.wu-wien.ac.at> Reply-To: srodawa@vela.acs.oakland.edu (Dr. Srodawa) Organization: Oakland University, Rochester MI Lines: 29 In article <90296.121048MAH@awiwuw11.wu-wien.ac.at> MAH@awiwuw11.wu-wien.ac.at (Michael Haberler) writes: >I wonder if there's a `standard' way to have a PC boot via LAN? There is a protocol, bootp. There is a unix daemon (server) called bootpd. The protocol is covered by a couple of RFCs. I just got this a few weeks ago and have been running it for two weeks. It compiled with no changes on 4.3BSD on a VAX 11/750. It took one change to the make file (documented) to make it on a Sun. I believe I got the stuff from lancaster.andrew.cmu.edu. I know for sure it was from Carnegie-Mellon, my memory could be faulty on the full system name. It came via anonymous ftp. --- I am using this only to get the machine name and internet address as a function of the ethernet address. That is, I'm not using it to boot. It does allow a pathname for a boot file to be given which it returns in the record. The file is read using the tftp protocol. --- The program is SUPPOSED to work either standalong or invoked by inetd. I am running it standalone, starting it in the rc.local file. For some reason, the inetd method didn't work for me. We have enough systems hitting this a standalone process probably makes good sense anyway. Ron. -- | Ronald J. Srodawa | Internet: srodawa@unix.secs.oakland.edu | | School of Engineering and CS | UUCP: srodawa@egrunix.UUCP | | Oakland University | Voice: (313) 370-2247 | | Rochester, Michigan 48309-4401 | |