From owner-freebsd-current Thu Apr 20 13: 8:16 2000 Delivered-To: freebsd-current@freebsd.org Received: from khavrinen.lcs.mit.edu (khavrinen.lcs.mit.edu [18.24.4.193]) by hub.freebsd.org (Postfix) with ESMTP id 03B1637BE97 for ; Thu, 20 Apr 2000 13:08:11 -0700 (PDT) (envelope-from wollman@khavrinen.lcs.mit.edu) Received: (from wollman@localhost) by khavrinen.lcs.mit.edu (8.9.3/8.9.3) id QAA05867; Thu, 20 Apr 2000 16:06:51 -0400 (EDT) (envelope-from wollman) Date: Thu, 20 Apr 2000 16:06:51 -0400 (EDT) From: Garrett Wollman Message-Id: <200004202006.QAA05867@khavrinen.lcs.mit.edu> To: Maxim Sobolev Cc: Donn Miller , Stijn Hoop , current@FreeBSD.ORG Subject: Re: Stale modules (Re: panic in the morning) In-Reply-To: <38FF5369.7BE907CA@altavista.net> References: <20000419162806.A8502@gil.physik.rwth-aachen.de> <20000420112449.C51522@pcwin002.win.tue.nl> <38FF44A6.F7C3C20B@cvzoom.net> <38FF5369.7BE907CA@altavista.net> Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG < said: > Looks like *really* nice idea. This would allow to solve "stale > modules" problem at minimal cost. Long ago, in a galaxy far, far away... (well, OK, seven years ago, in FreeBSD 1.0) I was working on developing a loadable-module system for FreeBSD (which I eventually threw out when Terry Lambert donated his LKM implementation). In my version, the config file included statements like `module foo', which config(8) interpreted as `link the files listed in the files file as ``optional foo'' into a separate module foo.o'. We can't do this for everything marked `optional' because not all of those combinations actually make sense. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same wollman@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message