On Nov 9, 2007 10:53 AM, new_guy wrote:
Sadly, justifying the obvious through these means is often a requirement.
Here's an approach you might consider. Take a best practice /
standards guide such as from NIST:
http://www.itl.nist.gov/lab/bulletns/bltndec02.htm
http://csrc.nist.gov/publications/drafts/800-44-Version2/Draft-SP800-44v...
And for the points your organization feels are important (like what
you've listed above), map how OpenBSD's implementation and OS approach
addresses those points. You'll find this is a pretty good indicator
and should be well accepted by the folks that matter.
DS
| Theodore Tso | Re: -mm merge plans for 2.6.23 -- sys_fallocate |
| Amit K. Arora | [RFC] Heads up on sys_fallocate() |
| Tarkan Erimer | Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3 |
| Greg Kroah-Hartman | [PATCH 011/196] sysfs: Fix a copy-n-paste typo in comment |
git: | |
| Jarek Poplawski | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| David Miller | Re: [GIT]: Networking |
| Gerrit Renker | [PATCH 27/37] dccp: Integration of dynamic feature activation - part 2 (server side) |
| Frans Pop | svc: failed to register lockdv1 RPC service (errno 97). |
