Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 28 Jan 1999 05:37:18 -0500 (EST)
From:      Peter Dufault <dufault@hda.com>
To:        wollman@khavrinen.lcs.mit.edu (Garrett Wollman)
Cc:        robert@cyrus.watson.org, freebsd-current@FreeBSD.ORG
Subject:   Re: Naming files in sys/kern
Message-ID:  <199901281037.FAA10916@hda.hda.com>
In-Reply-To: <199901280228.VAA14247@khavrinen.lcs.mit.edu> from Garrett Wollman at "Jan 27, 99 09:28:47 pm"

next in thread | previous in thread | raw e-mail | index | archive | help
> <<On Wed, 27 Jan 1999 18:30:15 -0500 (EST), Robert Watson <robert@cyrus.watson.org> said:
> 
> > It's not clear to me, when thinking of introducing a new file (say, for
> > auditing support :), what I should name it.  Would it be kern_audit.c or
> > sys_audit.c?
> 
> Depends on what it is auditing.  If it only auditing the basic I/O
> operations, then it would go in sys_*.c.  If it's a more general
> kernel facility, then it goes in kern_*.c.
> 
> > Or, if it is POSIX.1e, would it go into a /usr/src/sys/posix1e
> > directory as the posix4 realtime stuff did (assuming that support
> > for additional features from that posix draft were going to be
> > forthcoming)?
> 
> Giving the unhelpful tendency of Project 1003 to renumber its
> standards after-the-fact (or fold them into the main 1003.1 document),
> I would suggest against using committee identifiers like this.

This is posix4 due to my stupidity - I bought the O'Reilly "posix.4"
book and changed the name to that even though I used to know
better.

I started with this in its own directory since it is supposed to
be able to be enabled/disabled en masse via feature test macros,
and because I wanted to keep all the posixy stuff in one place with
calls out into the regular BSD kernel.  Since the name is wrong,
I think right thing to do now is make this directory something that
means "posix_subsystem" and put similar chunks that follow similar
rules there.  That keeps the code associated with twisty standardized
feature test macros in one place.

Peter

-- 
Peter Dufault (dufault@hda.com)   Realtime development, Machine control,
HD Associates, Inc.               Safety critical systems, Agency approval

To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-current" in the body of the message



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199901281037.FAA10916>