From owner-freebsd-current Thu Jun 4 14:40:55 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id OAA15242 for freebsd-current-outgoing; Thu, 4 Jun 1998 14:40:55 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from smtp01.primenet.com (daemon@smtp01.primenet.com [206.165.6.131]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA15183 for ; Thu, 4 Jun 1998 14:40:42 -0700 (PDT) (envelope-from tlambert@usr08.primenet.com) Received: (from daemon@localhost) by smtp01.primenet.com (8.8.8/8.8.8) id OAA26381; Thu, 4 Jun 1998 14:40:40 -0700 (MST) Received: from usr08.primenet.com(206.165.6.208) via SMTP by smtp01.primenet.com, id smtpd026330; Thu Jun 4 14:40:34 1998 Received: (from tlambert@localhost) by usr08.primenet.com (8.8.5/8.8.5) id OAA13434; Thu, 4 Jun 1998 14:40:29 -0700 (MST) From: Terry Lambert Message-Id: <199806042140.OAA13434@usr08.primenet.com> Subject: Re: I see one major problem with DEVFS... To: eivind@yes.no (Eivind Eklund) Date: Thu, 4 Jun 1998 21:40:29 +0000 (GMT) Cc: tlambert@primenet.com, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG In-Reply-To: <19980604214541.64381@follo.net> from "Eivind Eklund" at Jun 4, 98 09:45:41 pm X-Mailer: ELM [version 2.4 PL25] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > > What task can you perform with config that you don't think you would > > be able to perform without config? > > Configure and compile the FreeBSD kernel OK... > without doing large changes compared to the present source. This is one of those sacred cows I was talking about... ELF is going to get us part way there, and it's a "large change relative to the current way things are". The big issue here is *only* the boot blocks, since aggregation is a matter of "what is default in the kernel" and "what objects are linked into the 'installed' subdirectory from the 'available' subdirectory". A secondardy issue comes into play *only* if you want to dictate the ability to change the agregation of a post-linked kernel. I personally feel that this is a worthwhile goal, even though it means that you must place discrete drivers into discrete ELF sections so that an image archiver can insert or extract them at will. If there's a "config" after this point, it's a UI to toggle hard links and an ELF image archiver interface to be called when the user selects "create a custom kernel". Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message