Breaking out kern_mac.c into multiple files

[John-Mark Gurney]

Robert Watson wrote this message on Wed, Jul 30, 2003 at 16:50 -0400:
> As the scope of the MAC Framework has grown, so has kern_mac.c.  It's
> reached the point where breaking it into separate files would make it a
> lot easier to read, by virtue of logically grouping its exposed functions,
> APIs, etc.  Similarly scoped extension frameworks, such as NetGraph and
> GEOM, have opted to go into sys/$framework, with files named similarly. 
> My leaning was to do something similar -- add sys/mac, and then have
> mac_framework.c, mac_net.c, mac_sysvipc.c, etc.  I probably won't get to
> this for a bit because I want to avoid introducing large numbers of
> conflicts for our outstanding changes, but I was going to poll for general
> interest in placement, naming, etc.  Some of the other choices would be to
> keep it in kern/, but rename (similar to the System V IPC bits, VFS bits,
> et al). 

Can the MAC framework be loaded as a module?  If so, then
sys/(security/)?/mac is my vote.  If it's going to be an intregal part
of the system that will be standard, then kern/ is open.

-- 
  John-Mark Gurney				Voice: +1 415 225 5579

     "All that I will do, has been done, All that I have, has not."