Date: Thu, 4 Jun 1998 21:40:29 +0000 (GMT) From: Terry Lambert <tlambert@primenet.com> To: eivind@yes.no (Eivind Eklund) Cc: tlambert@primenet.com, wollman@khavrinen.lcs.mit.edu, current@FreeBSD.ORG Subject: Re: I see one major problem with DEVFS... Message-ID: <199806042140.OAA13434@usr08.primenet.com> In-Reply-To: <19980604214541.64381@follo.net> from "Eivind Eklund" at Jun 4, 98 09:45:41 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> > 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199806042140.OAA13434>