--9l24NVCWtSuIVIod
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On 2005.08.29 15:24:09 +0000, Bill Studenmund wrote:
| On Mon, Aug 29, 2005 at 11:03:59PM +0100, Rui Paulo wrote:
| > I prefer:
| > 	security.bsd.*
| > And no variables_like_this_one. It's ugly, IMHO.
|=20
| Part of the reason I suggested using the FreeBSD names is that no names=
=20
| jump out at me as the best name to use. So in cases of indecision, go wit=
h=20
| prior art. :-)
|=20
| If the consensus is that variables_like_this_one are ugly, then that is a=
=20
| reason for a different name. Is it a sufficent reason to be different fro=
m=20
| prior art? Not sure. I will however not argue the point.
|=20
| > | Also, I am partially enamored of what FreeBSD has done with the naming
| > | here. They are indicating. with the "bsd" node under "security", that
| > | these controls/status are part of the "bsd" security model. Yes, "uni=
x" =20
| > | could have been used, as well as "uid/gid" (but that seems unwieldy).=
 But
| > | we leave space for future models, which our discussions indicate may =
soon=20
| > | be coming (well, I hope so :-). [...]
| >=20
| > I agree. FreeBSD folks have security.bsd.* and security.jail.* and that
| > seems to be well organized:
| > 	security.<framework>.<option>
| >=20
| > Also, Elad's code works perfectly after my netstat(1) changes, so we ha=
ve
| > 1) working code; 2) a discussion on which sysctl variable to use;
| >=20
| > 2) should end ASAP!
|=20
| So then what name do you propose? security.bsd.?

Yes.

		-- Rui Paulo

--9l24NVCWtSuIVIod
Content-Type: application/pgp-signature
Content-Disposition: inline

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

iD8DBQFDE6FfZPqyxs9FH4QRAo4pAJ4jsYp2+ATFFrffw3UYonskQ6M7mACfXT0a
D1fArATqZTskwGO0JxqCNas=
=Tlrj
-----END PGP SIGNATURE-----

--9l24NVCWtSuIVIod--