Hi all, Attached is the 2nd rev of the Lighttpd Arc Case, I'll post this to the Wiki tomorrow. There are a couple of holes in it, one is something I'm investigating in the background and the other is a question on one of the points raised by Jyri.
The first hole is that I'm still looking at the loadable modules, some actually exist even when libraries that they would appear to depend on were not available at build time. This is explained in the Arc Case, I just need to add the explanation and I'm investigating this. The second hole is RBAC. How do I add entries to prof_attr and exec_attr in /etc/security via a package install without a script? I assume that this is straightforward and that I just simply don't know the answer. The last question concerns exported interfaces, Jyri made the following point: "Also, be more specific. "/usr/sbin/lighttpd" is Uncommitted, what does that mean? Is it the physical pathname that's Uncommitted? Or the command line options of that CLI? Or its exit code? Or the module APIs contained in it? Something else? All of it?" I think I get this and have followed the example of the MySQL Arc Case. The worry I have is that I'm not sure how best to document these things in the available columns and how to determine what their stability is. Can someone advise. Thanks Amanda -------------- next part -------------- An embedded and charset-unspecified text was scrubbed... Name: lighttpd-arc-draft.txt URL: <http://mail.opensolaris.org/pipermail/webstack-discuss/attachments/20080229/4f26d3e2/attachment.txt>
