From owner-freebsd-current Sun Apr 18 9:16:19 1999 Delivered-To: freebsd-current@freebsd.org Received: from zippy.dyn.ml.org (pm3-36.ppp.wenet.net [206.15.85.36]) by hub.freebsd.org (Postfix) with ESMTP id 2BEC214CF7 for ; Sun, 18 Apr 1999 09:16:16 -0700 (PDT) (envelope-from garbanzo@hooked.net) Received: from localhost (garbanzo@localhost [127.0.0.1]) by zippy.dyn.ml.org (8.9.3/8.9.1) with ESMTP id JAA89643; Sun, 18 Apr 1999 09:13:46 -0700 (PDT) (envelope-from garbanzo@hooked.net) Date: Sun, 18 Apr 1999 09:13:46 -0700 (PDT) From: Alex Zepeda To: "Jordan K. Hubbard" Cc: current Subject: Re: newbus and modem(s) In-Reply-To: <1011.924426030@zippy.cdrom.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Sun, 18 Apr 1999, Jordan K. Hubbard wrote: > > I'm as excited as anyone to see progress, especially if it means the > > ability to modularize the kernel and load various drivers on demand. But, > > alas, it seems this whole thing was rushed horribly. > > Not at all, it's simply something which will require some time to work > out the details of in -current. Which means that it perhaps should be worked out before being merged. Take for instance CAM. It didn't work perfectly, but it sure got a lot more exposure than newbus, and when it was integrated it caused very few problems. > People forget all too often that -current is the bleeding edge and you > shouldn't even bother (truly) to track it unless you're willing and > able to bleed occasionally. I'm actually always happy to see this > lesson driven home again when it looks like people are getting waaaaay > too complacent about -current. :-) Well, why not make ext2fs the default fs just to shake things up? It's one thing to expect panics and soon, but it's another thing to import code that wasn't ready. - alex To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message