Bill Studenmund wrote:
> My only concern is the use of _LKM_ENV_VERSION. I'd rather we just use a
> string-based matching. i.e. if you had DEBUG and MULTIPROCESSOR, the
> string'd be something like, "DEBUG,MULTIPROCESSOR". While I notice that
> you are labeling bit positions (I think that's what the other string's
> doing), we still run into issues if we ever define more than 32 options we
> track.

Well, I mainly used bit positions for simlicity of compares and
generation of the number. It's actually quite simple
to generate&compre string environment IDs too, so I'd change
that to use strings. Not that the max of 32 options would be too
limiting :) but it's better to use nonlimiting scheme from start.
 
> Also, is there a way to force an LKM load? i.e. tell the kernel, "Yes, I
> realize you might not like this, please load it anyway." ?? That way we
> can eventually move more complicated policy to userland.

I thought about flag like this, just not implemented it yet.
I'll add an ioctl & modload flag for that.
 
Jaromir
-- 
Jaromir Dolecek <jdolecek@NetBSD.org>            http://www.NetBSD.cz/
-=- We should be mindful of the potential goal, but as the tantric    -=-
-=- Buddhist masters say, ``You may notice during meditation that you -=-
-=- sometimes levitate or glow.   Do not let this distract you.''     -=-