On Wed, 27 Jan 1999, Garrett Wollman wrote:
> < 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/
> < 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.
< 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 g
I was wondering what the naming scheme for files in /usr/src/sys/kern was
:). There seem to be several sorts of files there--
bus_if.mdevice_.m imgact_*.c
inflate.c init_*.ckern_*.c
link_*.cmake*.{pl,sh} md5c.c
