From owner-freebsd-questions Sun Apr 7 16:21:14 1996 Return-Path: owner-questions Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id QAA11096 for questions-outgoing; Sun, 7 Apr 1996 16:21:14 -0700 (PDT) Received: from perki.connect.com.au (perki.connect.com.au [192.189.54.5]) by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA11091 for ; Sun, 7 Apr 1996 16:21:09 -0700 (PDT) Received: (from uucp@localhost) by perki.connect.com.au id JAA23406 (8.7.4/IDA-1.6); Mon, 8 Apr 1996 09:21:02 +1000 (EST) >Received: from localhost (giles@localhost [127.0.0.1]) by nemeton.com.au (8.6.12/8.6.9) with SMTP id HAA08267; Mon, 8 Apr 1996 07:52:31 +1000 Message-Id: <199604072152.HAA08267@nemeton.com.au> To: Robert N Watson cc: questions@freebsd.org Subject: Re: netboot without BOOTP/DHCP Date: Mon, 08 Apr 1996 07:52:30 +1000 From: Giles Lean Content-Type: text Sender: owner-questions@freebsd.org X-Loop: FreeBSD.org Precedence: bulk On Sat, 6 Apr 1996 10:52:18 -0500 (EST) Robert N Watson wrote: > I'd like to use netboot and a reduced kernel to load up FreeBSD > occasionally on my old 386 (which used to be my primary BSD system > back in 2.0 :) -- does anyone have a modified netboot that has a > hardcoded set of IP's to use, instead of bootp? Someone was working on this; I haven't heard recently. One gross hack is to boot from a floppy disk with a modified init that chroots the whole system. This sounded a wierd suggestion when it was made to me, but I did try it and it did work. The output of mount(8) was a little confusing though! [Code available if I haven't already tossed it on the grounds of ugliness.] > Would it be relatively easy (or hard) to modify netboot to use > a config file with settings specific to that PC instead of relying on > bootp? Easy -- hard code the IP addresses in the netboot code Middling -- use a configuration file (probably requires a DOS C compiler) Hard -- much anything else Giles