Subject: Re: LKM's and NetBSD kernels.
To: Greg A. Woods <firstname.lastname@example.org>
From: Jason Thorpe <email@example.com>
Date: 06/10/1996 17:27:52
On Mon, 10 Jun 96 20:06:48 -0400 (EDT)
firstname.lastname@example.org (Greg A. Woods) wrote:
> I had been testing against the value of NetBSD (from <sys/param.h>) in
> my #ifdefs, not NetBSD?_?.
Ah, that is supposed to change along with NetBSD?_?...
> > I'll let JT comment further on when the NetBSD1_2 symbol will change to 1.
> Which reminds me. How is a LKM supposed to check this?
> I had assumed the current version symbol would be stored in a static
> variable somewhere, but I find instead LKM_VERSION, which isn't related
> at all (and in kern_lkm.c seems to be the only value passed to the
> module for comparison on startup).
> This kernel release management is still a bit primitive and very hairy! ;-)
I'm not really sure ... I must admit that I don't spend a lot of time
thinking about such things.
If you come up with a solution, let us know, and we'll certainly consider
integrating it into the kernel!
----save the ancient forests - http://www.bayarea.net/~thorpej/forest/----
Jason R. Thorpe email@example.com
NASA Ames Research Center Home: 408.866.1912
NAS: M/S 258-6 Work: 415.604.0935
Moffett Field, CA 94035 Pager: 415.428.6939