From owner-freebsd-current Tue Apr 4 13:55:18 1995 Return-Path: current-owner Received: (from majordom@localhost) by freefall.cdrom.com (8.6.10/8.6.6) id NAA23215 for current-outgoing; Tue, 4 Apr 1995 13:55:18 -0700 Received: from cs.weber.edu (cs.weber.edu [137.190.16.16]) by freefall.cdrom.com (8.6.10/8.6.6) with SMTP id NAA23209 for ; Tue, 4 Apr 1995 13:55:14 -0700 Received: by cs.weber.edu (4.1/SMI-4.1.1) id AA18525; Tue, 4 Apr 95 14:45:56 MDT From: terry@cs.weber.edu (Terry Lambert) Message-Id: <9504042045.AA18525@cs.weber.edu> Subject: Re: cvs commit: src/sys/i386/conf Makefile.i386 To: nate@trout.sri.MT.net (Nate Williams) Date: Tue, 4 Apr 95 14:45:55 MDT Cc: rkw@dataplex.net, current@FreeBSD.org In-Reply-To: <199504041758.LAA06600@trout.sri.MT.net> from "Nate Williams" at Apr 4, 95 11:58:51 am X-Mailer: ELM [version 2.4dev PL52] Sender: current-owner@FreeBSD.org Precedence: bulk > *BLECH* BSD systems have *never* (and should *never*) require that you > have the complete source tree installed just to build a kernel. Making > them go through alot of trouble to build a kernel is a waste of their > time. Many, many more people build kernels w/out src trees than people > who build kernels w/src trees. We are trying to make the system > *easier* to use for the avg. user w/out penalizing the developer. I'm glad you said this. When will the binary link kit be available? I've often thought that it should be possible to configure devices in and out of the kernel without regenerating more than a single object file containing the device switches. The really nice thing about this, of course, is that multiport board drivers and Adaptec drivers using Adaptec code, and (potentially) the Intel supplied-for-MACH binary math coprocesser emulator could all be supplied without sources in full conformance to the non disclosure agreements required to obtain them. To make the nay-sayers happy, putting the source in escrow with the condition that a non-disclosure be signed to obtain it should be sufficient to not vest too much in a driver writer as a single point of failure. That's just a legal niceity, however, and the main point, that it be *possible*, is the important thing. Actually, sufficient reliance on a devfs, loadable modules, and soft autoconfiguration with a "save" for "/kernel -c" boot should make it totally unnecessary to have a link kit to get a new kernel configuration anyway. Terry Lambert terry@cs.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.