smf(5): Manifest destiny, Round One
I received polite mail this morning reminding me that I have mugs to ship. I got distracted during break, but we’ll be boxing up the mugs and getting them to the authors. So, for Round One, here is the set of submitted service manifests submitted to date:
application/informix |
application/mysql |
application/oracle/[database] |
application/oracle/[listener] |
[application]/popfile |
[application/print]/cups |
[application/print]/xprint |
[network/ident:pident] |
[network/nntp:inn] |
network/ntp:openntp |
network/[smtp:postfix] |
network/[smtp:qmail] |
network/txpi:tcp] |
[network/xcom:default] |
* Ben’s Postfix conversion is very simple, and works if postfix is in root
‘s default path; in contrast, Peter Tribble built a full stack of mail processing atop Postfix in smf
(5) a few months back. Plus they both have mugs already.
We’re now in the process of assembling all of the manifests we know about at the OpenSolaris smf
(5) community. If you sent in a manifest without a URL, it would be preferable to give us a link to it, and to give it a copyright and (OSI-approved) licence. (Send me mail if this appears confusing or is difficult.)
Suggestions for Round Two (beyond PostgreSQL and the other database management systems) are welcomed!
[ T: OpenSolaris Solaris smf ]