>> (Out of idle curiosity, if you have the time and inclination to
>> satisfy it - and this may well be something that I don't know only
>> because I'm at home and all this stuff is at work - how do all the
>> kernel config bits get into sys/conf/files and sys/conf/majors and
>> such when you use the package?  I specifically went looking [...].)

> They don't.

> All the config(8) stuff hardwire the autoconf(9) structures in the
> kernel binary.  When tap(4) is built as a LKM, there are routines to
> attach to and detach from the autoconf(9) framework dynamically that
> are used at appropriate times.

Sure.  But what about when it's compiled into the kernel, rather than
modload(8)ed?  Is that something the package can't do?  Have I already
stumbled across the correct tack to take - dropping
if_tap{,_stub}.{c,h} into the kernel source tree and adding entries
manually to sys/conf/files and sys/conf/majors - and just botched it
slightly in respects you explained last message?

/~\ The ASCII				der Mouse
\ / Ribbon Campaign
 X  Against HTML	       mouse@rodents.montreal.qc.ca
/ \ Email!	     7D C8 61 52 5D E7 2D 39  4E F1 31 3E E8 B3 27 4B