From owner-freebsd-hackers Thu Sep 25 21:09:36 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id VAA05310 for hackers-outgoing; Thu, 25 Sep 1997 21:09:36 -0700 (PDT) Received: from usr05.primenet.com (tlambert@usr05.primenet.com [206.165.6.205]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id VAA05287; Thu, 25 Sep 1997 21:09:23 -0700 (PDT) Received: (from tlambert@localhost) by usr05.primenet.com (8.8.5/8.8.5) id VAA00555; Thu, 25 Sep 1997 21:09:09 -0700 (MST) From: Terry Lambert Message-Id: <199709260409.VAA00555@usr05.primenet.com> Subject: Re: IMPORTANT ANNOUNCEMENT TO ALL 'CURRENT' USERS... To: scrappy@hub.org (The Hermit Hacker) Date: Fri, 26 Sep 1997 04:09:08 +0000 (GMT) Cc: tlambert@primenet.com, karl@Mcs.Net, hackers@FreeBSD.ORG, current@FreeBSD.ORG In-Reply-To: from "The Hermit Hacker" at Sep 25, 97 08:41:59 pm X-Mailer: ELM [version 2.4 PL23] Content-Type: text Sender: owner-freebsd-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk > > then you need to get the sources in /usr/src/usr.sbin/config, and > > rebuild "config". > > Hrmmm...I always considered this to be "standard operating procedure" > when upgrading my kernel: check to make sure config sources haven't > changed *Shrug* I always considered config to be wasteful, now that it's possible to include or not include modules and have them dynamically register themselves via SYSINIT() simply by deciding that you will/won't link that particular object into the kernel. Once ELF is there, modules can go into different sections, and an ELF object archiver can configure/deconfigure modules without even needing to relink the darned things. *Shrug* 8-) Terry Lambert terry@lambert.org --- Any opinions in this posting are my own and not those of my present or previous employers.