From owner-freebsd-hackers  Tue May 14 16:49:46 1996
Return-Path: owner-hackers
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id QAA24700
          for hackers-outgoing; Tue, 14 May 1996 16:49:46 -0700 (PDT)
Received: from ref.tfs.com (ref.tfs.com [140.145.254.251])
          by freefall.freebsd.org (8.7.3/8.7.3) with ESMTP id QAA24694
          for <hackers@freebsd.org>; Tue, 14 May 1996 16:49:44 -0700 (PDT)
Received: (from julian@localhost) by ref.tfs.com (8.7.3/8.6.9) id SAA04377; Mon, 13 May 1996 18:19:07 -0700 (PDT)
Message-Id: <199605140119.SAA04377@ref.tfs.com>
Subject: Re: errros on making floppies
To: jin@george.lbl.gov (Jin Guojun[ITG])
Date: Mon, 13 May 1996 18:19:07 -0700 (PDT)
From: "JULIAN Elischer" <julian@ref.tfs.com>
Cc: jkh@time.cdrom.com, hackers@freebsd.org
In-Reply-To: <199605132356.QAA00758@george.lbl.gov> from "Jin Guojun[ITG]" at May 13, 96 04:56:22 pm
X-Mailer: ELM [version 2.4 PL25 ME8b]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I'm working on changing the Makefiles in release/ so that each floppy
is a subdir and can be made individually, (well at least the important
ones (fixit,root))
having such basic functionality tied up so inherently with that spaghetti
that is the release code is a probelm here, because we need to be able
to know out small boot-disks without doing all the rest of that stuff.
doing a make in bin, sbin, usr.sbin and usr.bin is acceptable
as the .o's are needed for the crunched binaries, but
we don't want to have to cut a whole release..
we'd also like to see a selection of floppies produced during
a normal 'make world'  and that is my aim....
we'll see how successful I can be in this....
the aim is to produce at least:
1.4MB kernel floppy
1.4MB root floppy with massively crunched stuff.

Then, hopefully if that works:
a 1.4MB floppy with 'kernel of your choice' pluss a crunched binary
with just enough functionality to do what we need.

The final stage (if I ever understand all this) is:
a floppy with an MFS filesystem with our custom stuff on it

> 
> >> I am trying to figure out why NFS installation fails on our network.
> >> When I tried to make floppies I get following errors. Please advice
> >> how I can make these floppies.
> >> 
> >> # make boot.flp
> >
> >You can't _just_ do this step - you need to do an entire make release
> >first.
> >
> >                                                Jordan
>