This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
--------------enigECB54ABBD8311697846DA233
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

YAMAMOTO Takashi wrote:
>>>secmodel/sm_bsd44_foo.c ?

sm_bdsm? I bet people like that kind of security enforcement ;).

>>>Or put the security models into src/sys/kern/secmodel_bsd44_* ?
>>Personally, I think '<model>_<function>.c' is elaborate enough.
>>I'll go for
>>'secmodel_<model>_<function>.c'.
> i vote for secmodel_<model>.c (and secmodel_<model>_foo.c where
> <model> needs two or more files).

Or perhaps secmodel/securelevel_<model>.c and secmodel/secmodel_<model>.c:

secmodel/secmodel_bsd44.c
secmodel/secmodel_russianroulette.c
secmodel/securelevel_bsd44.c
secmodel/securelevel_russianroulette.c

Cheers,
-- 
         Thomas E. Spanjaard
         tgen@netphreax.net

--------------enigECB54ABBD8311697846DA233
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: OpenPGP digital signature
Content-Disposition: attachment; filename="signature.asc"

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (NetBSD)

iD8DBQFE+x+V6xCMwBJ+1+sRAwidAJ9tLqfd6XAuNIHLdGy+EQnoQVWL6gCfWoyn
r3pwi39zg9P/rCpbBUfMDuI=
=9o1b
-----END PGP SIGNATURE-----

--------------enigECB54ABBD8311697846DA233--