From owner-freebsd-arch@FreeBSD.ORG Wed Jul 30 16:52:24 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 5EC4F37B401; Wed, 30 Jul 2003 16:52:24 -0700 (PDT) Received: from mail.cyberonic.com (mail.cyberonic.com [4.17.179.4]) by mx1.FreeBSD.org (Postfix) with ESMTP id 573BD43F85; Wed, 30 Jul 2003 16:52:23 -0700 (PDT) (envelope-from jmg@hydrogen.funkthat.com) Received: from hydrogen.funkthat.com (node-40244c0a.sfo.onnet.us.uu.net [64.36.76.10]) by mail.cyberonic.com (8.12.8/8.12.5) with ESMTP id h6V0Op0n009119; Wed, 30 Jul 2003 20:24:51 -0400 Received: (from jmg@localhost) by hydrogen.funkthat.com (8.12.9/8.11.6) id h6UNqKT7059224; Wed, 30 Jul 2003 16:52:20 -0700 (PDT) (envelope-from jmg) Date: Wed, 30 Jul 2003 16:52:20 -0700 From: John-Mark Gurney To: Robert Watson Message-ID: <20030730235220.GH10708@funkthat.com> Mail-Followup-To: Robert Watson , arch@freebsd.org References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4.1i X-Operating-System: FreeBSD 4.2-RELEASE i386 X-PGP-Fingerprint: B7 EC EF F8 AE ED A7 31 96 7A 22 B3 D8 56 36 F4 X-Files: The truth is out there X-URL: http://resnet.uoregon.edu/~gurney_j/ X-Resume: http://resnet.uoregon.edu/~gurney_j/resume.html 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 Reply-To: John-Mark Gurney 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 23:52:24 -0000 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."