From owner-freebsd-hackers@FreeBSD.ORG Thu Jan 8 14:02:55 2004 Return-Path: Delivered-To: freebsd-hackers@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 30C6A16A4CE; Thu, 8 Jan 2004 14:02:55 -0800 (PST) Received: from praetor.linc-it.com (adsl-068-157-070-217.sip.jan.bellsouth.net [68.157.70.217]) by mx1.FreeBSD.org (Postfix) with ESMTP id 38B9643D4C; Thu, 8 Jan 2004 14:02:53 -0800 (PST) (envelope-from fullermd@over-yonder.net) Received: from mortis.over-yonder.net (adsl-19-157-169.jan.bellsouth.net [68.19.157.169]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by praetor.linc-it.com (Postfix) with ESMTP id E825B1522C; Thu, 8 Jan 2004 16:02:51 -0600 (CST) Received: by mortis.over-yonder.net (Postfix, from userid 100) id F1FAC20F3D; Thu, 8 Jan 2004 16:02:49 -0600 (CST) Date: Thu, 8 Jan 2004 16:02:49 -0600 From: "Matthew D. Fuller" To: Scott Long Message-ID: <20040108220249.GM48603@over-yonder.net> References: <20040107235737.I32227@pooker.samsco.home> <20040108075059.GK53429@silverwraith.com> <20040108075811.GJ48603@over-yonder.net> <20040108015954.V32598@pooker.samsco.home> <20040108101451.GK48603@over-yonder.net> <20040108033905.A32598@pooker.samsco.home> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20040108033905.A32598@pooker.samsco.home> User-Agent: Mutt/1.4.1i-fullermd.1 X-Editor: vi X-OS: FreeBSD cc: hackers@freebsd.org Subject: Re: Discussion on the future of floppies in 5.x and 6.x X-BeenThere: freebsd-hackers@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 08 Jan 2004 22:02:55 -0000 On Thu, Jan 08, 2004 at 03:43:55AM -0700 I heard the voice of Scott Long, and lo! it spake thus: > > Well, regardless of how you label it, these floppies still require lots > of care and feeding in order to work. We currently have no way to > support multiple floppies in a convenient way. My hope is that, with this piece taken care of, the amount of care and feeding necessary to maintain it will be minimized. When adding new drivers, you'd have to stick their names in a list somewhere to be split out, but that's pretty minimal. It should help avoid all the juggling we keep having to do to manage the size. > This can be fixed in a variety of ways that range from fragile hacks to > wonderful designs, but it still requires someone to put forth the > effort. My offer for a 'floppy maintainer' is quite sincere; I hope > that someone takes an interest and steps up to the challenge. I have some interest in this, to be sure. However, every time I've ventured into src/release/ in the past, I've come away with an intense desire for absinthe. I've never successfully built a release, and it's been my impression that you can't just build the floppies, you have to build the full release to have everything in place to build them. That takes a huge chunk of disk space (to say nothing of _TIME_! Just building the kernel and modules takes the better part of a half hour), which are two things in chronically short supply. -- Matthew Fuller (MF4839) | fullermd@over-yonder.net Systems/Network Administrator | http://www.over-yonder.net/~fullermd/ "The only reason I'm burning my candle at both ends, is because I haven't figured out how to light the middle yet"