From owner-freebsd-arch@FreeBSD.ORG Wed Jul 30 14:04:42 2003 Return-Path: Delivered-To: freebsd-arch@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 6958337B405 for ; Wed, 30 Jul 2003 14:04:42 -0700 (PDT) Received: from mail.speakeasy.net (mail9.speakeasy.net [216.254.0.209]) by mx1.FreeBSD.org (Postfix) with ESMTP id EB67643F3F for ; Wed, 30 Jul 2003 14:04:40 -0700 (PDT) (envelope-from jhb@FreeBSD.org) Received: (qmail 25144 invoked from network); 30 Jul 2003 21:04:40 -0000 Received: from unknown (HELO server.baldwin.cx) ([216.27.160.63]) (envelope-sender )encrypted SMTP for ; 30 Jul 2003 21:04:40 -0000 Received: from laptop.baldwin.cx (gw1.twc.weather.com [216.133.140.1]) by server.baldwin.cx (8.12.9/8.12.9) with ESMTP id h6UL4cGI068928; Wed, 30 Jul 2003 17:04:38 -0400 (EDT) (envelope-from jhb@FreeBSD.org) Message-ID: X-Mailer: XFMail 1.5.4 on FreeBSD X-Priority: 3 (Normal) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 8bit MIME-Version: 1.0 In-Reply-To: Date: Wed, 30 Jul 2003 17:04:59 -0400 (EDT) From: John Baldwin To: Robert Watson cc: arch@FreeBSD.org Subject: RE: Breaking out kern_mac.c into multiple files X-BeenThere: freebsd-arch@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussion related to FreeBSD architecture List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 30 Jul 2003 21:04:42 -0000 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 <>< http://www.FreeBSD.org/~jhb/ "Power Users Use the Power to Serve!" - http://www.FreeBSD.org/