>    > this is fine, but i don't see any pressing need to change config(8).
>    > if you use <sun68k/foo.h>, this will get picked up by the -I$S/sys/arch
>    > that is default in kernel builds.  add this to your bootblock includes
>    > as well, and you should be fine?
>    
>    Then I'd have to do #include <sun68k/include/foo.h>, which won't work
>    once these headers get installed.  I.e., in kernel sources I'm doing
>    #include <machine/foo.h>, where arch/sun2/include/foo.h does #include
>    <sun68k/foo.h>, and everything's going to end up under /usr/include.
>    Typical example is disklabel.h.
> 
> 
> they don't go in sys/arch/sun68k, but sys/dev/sun68k, and you refer to them
> as <dev/sun68k/foo.h>, which works both ways.

This would put bootblock code and several non-device-related code and
header files under sys/dev?

Matt

--
Matt Fredette
http://mit.edu/fredette/www