From owner-freebsd-current Sat Oct 14 19:33:44 2000 Delivered-To: freebsd-current@freebsd.org Received: from mass.osd.bsdi.com (termroom.bsdcon.org [206.55.247.2]) by hub.freebsd.org (Postfix) with ESMTP id 4ADEB37B66E for ; Sat, 14 Oct 2000 19:33:39 -0700 (PDT) Received: from mass.osd.bsdi.com (localhost [127.0.0.1]) by mass.osd.bsdi.com (8.11.0/8.9.3) with ESMTP id e9F0hwf01063; Sat, 14 Oct 2000 17:43:58 -0700 (PDT) (envelope-from msmith@mass.osd.bsdi.com) Message-Id: <200010150043.e9F0hwf01063@mass.osd.bsdi.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: mjacob@feral.com Cc: current@freebsd.org Subject: Re: Our kernel just got too big again. :) In-reply-to: Your message of "Sat, 14 Oct 2000 17:32:30 PDT." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 14 Oct 2000 17:43:58 -0700 From: Mike Smith Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > > > The problem with such an approach is that it's not very user-friendly > > > to first-time installers who have no idea how to drive the loader. > > > > Most of the relevant modules can actually be tried by sysinstall. In the > > CD case we can just put them on the CDROM. I'd be inclined to look for > > somewhere that you can fit ~110k and put nfs.ko.gz there. 8) > > I was thinking about making sure that drivers that would get you to your > install media would be what you'd load- nothing else. This would include > network drivers... That'd work; we could offload a lot of storage drivers (CAM, RAID, etc are all loadable...) -- ... every activity meets with opposition, everyone who acts has his rivals and unfortunately opponents also. But not because people want to be opponents, rather because the tasks and relationships force people to take different points of view. [Dr. Fritz Todt] V I C T O R Y N O T V E N G E A N C E To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message