Subject: Re: Upcoming security model abstraction
To: None <elad@NetBSD.org>
From: YAMAMOTO Takashi <firstname.lastname@example.org>
Date: 09/04/2006 00:10:11
> > secmodel/sm_bsd44_foo.c ?
> > Or put the security models into src/sys/kern/secmodel_bsd44_* ?
> Personally, I think '<model>_<function>.c' is elaborate enough.
bsd44.c can easily conflict with something from other unrelated subsystems,
if one choose the same naming scheme as you. eg. bsd44 scheduler.
> Consider 'bsd44_suser.c' or 'bsd44_securelevel.c' - should make it
> clear what these are; if this is still too 'vague' (and seriously,
> take a moment to think where this is really effective), I'll go for
i vote for secmodel_<model>.c (and secmodel_<model>_foo.c where
<model> needs two or more files).