Date: Wed, 30 Jul 2003 17:04:59 -0400 (EDT) From: John Baldwin <jhb@FreeBSD.org> To: Robert Watson <rwatson@FreeBSD.org> Cc: arch@FreeBSD.org Subject: RE: Breaking out kern_mac.c into multiple files Message-ID: <XFMail.20030730170459.jhb@FreeBSD.org> In-Reply-To: <Pine.NEB.3.96L.1030730164805.89045P-100000@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 30-Jul-2003 Robert Watson wrote: > > 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). sys/security/mac please. We already have a sys/security directory, let's use it. -- John Baldwin <jhb@FreeBSD.org> <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?XFMail.20030730170459.jhb>