<?xml version="1.0"?>
<rss version="2.0">
  <channel>
    <title>Advogato blog for partain</title>
    <link>http://www.advogato.org/person/partain/</link>
    <description>Advogato blog for partain</description>
    <language>en-us</language>
    <generator>mod_virgule</generator>
    <pubDate>Fri, 5 Sep 2008 04:49:29 GMT</pubDate>
    <item>
      <pubDate>Mon, 21 Aug 2000 09:17:28 GMT</pubDate>
      <title>21 Aug 2000</title>
      <link>http://www.advogato.org/person/partain/diary.html?start=0</link>
      <guid>http://www.advogato.org/person/partain/diary.html?start=0</guid>
      <description>Checked in another tranche of &lt;a
href="http://ark.sourceforge.net"&gt;Arusha&lt;/a&gt; code (blurb
above),
which brings a major goal much closer.
&lt;p&gt;
The goal is that &lt;em&gt;all&lt;/em&gt; sysadmin ``added value'' about
software installations (and, well, everything else, too :-)
can be expressed in `packages' -- and that ``added value''
can be shared with other `teams' of sysadmins around the
universe.
&lt;p&gt;
In particular, not only can a software install (e.g. tcp
wrappers) be expressed as a package -- hardly a new idea --
but the &lt;em&gt;configuration&lt;/em&gt; for said software can also be
a package.  Not only can fellow sysadmins elsewhere use the
same software, but they can pick up on my install procedure
and/or my local configuration by ``inheriting'' my relevant
packages. (The Arusha Project brings &lt;a
href="http://ark.sourceforge.net/xml-objects.html"&gt;a kind of
object orientation&lt;/a&gt; to Unix sysadmin.)
&lt;p&gt;
Anyway, it's starting to work!
See note above about project `uncles' (and `aunts') :-)
</description>
    </item>
  </channel>
</rss>
