<<On Wed, 27 Jan 1999 18:30:15 -0500 (EST), Robert Watson <rob...@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. If it's controlled by a compile-time option, it should probably be called POSIX_AUDITING rather than POSIX_1e or something of that nature, since your statement implies that there is a useful granularity of features. -GAWollman -- Garrett A. Wollman | O Siem / We are all family / O Siem / We're all the same woll...@lcs.mit.edu | O Siem / The fires of freedom Opinions not those of| Dance in the burning flame MIT, LCS, CRS, or NSA| - Susan Aglukark and Chad Irschick To Unsubscribe: send mail to majord...@freebsd.org with "unsubscribe freebsd-current" in the body of the message
