From owner-cvs-all Sat Dec 11 5:49: 0 1999 Delivered-To: cvs-all@freebsd.org Received: from mimer.webgiro.com (mimer.webgiro.com [212.209.29.5]) by hub.freebsd.org (Postfix) with ESMTP id 2E26314C39; Sat, 11 Dec 1999 05:48:56 -0800 (PST) (envelope-from abial@webgiro.com) Received: by mimer.webgiro.com (Postfix, from userid 66) id 356892DC07; Sat, 11 Dec 1999 14:49:43 +0100 (CET) Received: by mx.webgiro.com (Postfix, from userid 1001) id 410537811; Sat, 11 Dec 1999 14:46:13 +0100 (CET) Received: from localhost (localhost [127.0.0.1]) by mx.webgiro.com (Postfix) with ESMTP id 32B7B10E10; Sat, 11 Dec 1999 14:46:13 +0100 (CET) Date: Sat, 11 Dec 1999 14:46:13 +0100 (CET) From: Andrzej Bialecki To: Greg Lehey Cc: cvs-committers@FreeBSD.org, cvs-all@FreeBSD.org Subject: Re: cvs commit: src/release/picobsd Makefile src/release/picobsd/build Makefile Makefile.mfs In-Reply-To: <199912102143.NAA50148@freefall.freebsd.org> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-cvs-all@FreeBSD.ORG Precedence: bulk On Fri, 10 Dec 1999, Greg Lehey wrote: > grog 1999/12/10 13:43:10 PST > > Added files: > release/picobsd Makefile > release/picobsd/build Makefile Makefile.mfs I appreciate your work, and I consider it to be a step in right direction, but you should've discussed this with either me or Doug White before committing ( *cough* the word MAINTAINER comes to my mind). The end result for now is that we have two conflicting methods of building the floppies, and neither works (you broke the "custom" target when building with 'build' script, and your "custom" floppy doesn't compile because some Makefiles have 0 length). > Log: > Add 'custom' directory with significantly restructured build (now > using make instead of custom scripts) and two floppies instead of > one. The resultant floppy can do everything that the individual > floppies (dial, net, install, isp, router) could do, modulo some bit Well, not really. The individual floppies were there for a reason: smaller memory footprint. While it's becoming of less concern nowadays, there is still a lot of people with old junky 486 with 8MB SIMM RAM. A general purpose, one-size-fits-all floppy doesn't work for them. OTOH, having your "custom" floppy is certainly desirable if you can afford it. > Structure is in place for using the same build for the other > directories, but I'm no longer sure we need this. The current first See above. > floppy will run fine by itself, but the size of a compressed kernel > has increased by nearly 50% since 3.2, and there's not much space for > anything useful on the remainder of the floppy. The current method It depends on what you want to put on mfs. If you consider e.g. the original "router" floppy, you could do even with 4MB RAM, which is important for embedded systems. > creates a larger mfs and can read as many floppies as the user can It's a good feature, as I said. We just need to discuss the whole picture. (BTW, I don't want you to back it out. I want you to fix it :-) Andrzej Bialecki // WebGiro AB, Sweden (http://www.webgiro.com) // ------------------------------------------------------------------- // ------ FreeBSD: The Power to Serve. http://www.freebsd.org -------- // --- Small & Embedded FreeBSD: http://www.freebsd.org/~picobsd/ ---- To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe cvs-all" in the body of the message