From owner-freebsd-hackers Sat Dec 17 18:57:43 1994 Return-Path: hackers-owner Received: (from root@localhost) by freefall.cdrom.com (8.6.8/8.6.6) id SAA25020 for hackers-outgoing; Sat, 17 Dec 1994 18:57:43 -0800 Received: from Root.COM (implode.Root.COM [198.145.90.1]) by freefall.cdrom.com (8.6.8/8.6.6) with ESMTP id SAA25012 for ; Sat, 17 Dec 1994 18:57:00 -0800 Received: from corbin.Root.COM (corbin.Root.COM [198.145.90.18]) by Root.COM (8.6.8/8.6.5) with ESMTP id SAA08795; Sat, 17 Dec 1994 18:55:49 -0800 Received: from localhost (localhost [127.0.0.1]) by corbin.Root.COM (8.6.9/8.6.5) with SMTP id SAA01031; Sat, 17 Dec 1994 18:55:48 -0800 Message-Id: <199412180255.SAA01031@corbin.Root.COM> X-Authentication-Warning: corbin.Root.COM: Host localhost didn't use HELO protocol To: kurto@tiny.mcs.usu.edu (Kurt Olsen) cc: hackers@freebsd.org Subject: Re: boottime device configuration In-reply-to: Your message of "Sat, 17 Dec 94 21:12:26 MST." <199412180412.VAA07410@tiny.mcs.usu.edu> From: David Greenman Reply-To: davidg@Root.COM Date: Sat, 17 Dec 1994 18:55:14 -0800 Sender: hackers-owner@freebsd.org Precedence: bulk > >I just had an interesting idea and thought I would get other people >'s opinions. Now that there is the facility to reconfigure devices at >boottime, why not have a /dev_config or something that would hold a list >of device configurations. This was when a person changes how their hardware >is setup, it won't require a full recompile. Plus for people not interested >in recompiling a kernel, it would allow them to change the setup of the >generic kernels. > >I'm not sure how difficult it would be to read a file, but this seems like >it would be quite helpful. I was also thinking of moving many devices out >to LKMs, but from reading Terry's reply, maybe that's not such a good idea. >However if the devices were written correctly (ie. load at boot time and >stay that way,) we could make a kernel that had minimal support and then >provide a bunch of LKMs that could be loaded depending on a person's hardware. >This would look really nice to people who didn't feel quite adept at building >up a kernel. Plus make it really easy to do binary upgrades of different >device drivers. All of the above has been heavily discussed over the past 4 months or so, and the idea is generally the direction that we're headed. It's still unclear if we will be storing the device configuration information in the kernel binary somehow or if it will be stored in a seperate file. Do the latter either complicates the boot code or creates a chicken-and-egg problem for the configuration of the boot device. -DG