<?xml version="1.0" encoding="utf-8"?>
<!DOCTYPE rss [<!ENTITY % HTMLlat1 PUBLIC "-//W3C//ENTITIES Latin 1 for XHTML//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml-lat1.ent">]>
<rss version="2.0" xml:base="http://lopsa.org">
<channel>
 <title>doug&#039;s blog</title>
 <link>http://lopsa.org/blog/1</link>
 <description></description>
 <language>en</language>
<item>
 <title>musings on a maint</title>
 <link>http://lopsa.org/node/1597</link>
 <description>&lt;p&gt;We have a large maintenance this weekend as the electricians cutover power to a several hundred AMP 480V switch panel in preparation for bringing a large 675KW UPS online. Also, at the same time, they lumped in some plumbing work to cutover to the 14&quot; chilled water mains. So, in order to avoid any sort of inrush issues, we&#039;re shutting down the 588 machines in the cluster.&lt;/p&gt;
&lt;p&gt;The current measurement units on the Starline 400A buses still read between 20A and 28A after shutdown, which means that this power is divided among 50 24 port Voltaire switches, 2 288 port Voltaire switches, 20 HP 10/100 ProCurve 2600 series switches, 22 Force 10 S50N switches, and 2 Force 10 S2410 switches, as well as whatever inefficiency exists in powering 30 Servertech 60A CDUs, 4 30A 0U PDUS, 10 30A 2U PDUs (all of which have monitoring hardware on board), and a Cyclades ACS 48 port console server. That&#039;s a fair bit more current than I would have intuited, and a fair percentage of a medium loaded cluster consuming about 160 A per phase at 208V (3 phase).&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1597&quot; dc:identifier=&quot;http://lopsa.org/node/1597&quot; dc:title=&quot;musings on a maint&quot; trackback:ping=&quot;http://lopsa.org/trackback/1597&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Fri, 14 Mar 2008 22:28:16 -0700</pubDate>
 <author>doug</author>
</item>
<item>
 <title>So, you&#039;ve got to do a BIOS upgrade on a modern computer and it only comes in DOS</title>
 <link>http://lopsa.org/node/1534</link>
 <description>&lt;p&gt;The premise is believable enough. There are still quite a few vendors out there that still distribute BIOS updates as a floppy image. Heck, they even make it &#039;easy&#039; for you.. The program comes in a self-contained executable that has the image inside it. All you have to do is run the thing and put in the floppy disk.. and...&lt;br /&gt;
Oh.. wait a second..&lt;br /&gt;
Where&#039;s that floppy disk?&lt;br /&gt;
Hmmm.&lt;br /&gt;
Ok, so we&#039;ll use the CDROM image and...&lt;br /&gt;
ARGH.. this machine is a server bought in large quantities.. It doesn&#039;t have a CDROM.&lt;br /&gt;
Fine Fine.. We&#039;ll use one of these &lt;a href=&quot;http://www.oreillynet.com/digitalmedia/blog/2004/10/utility_to_make_usb_flash_driv.html&quot;&gt;new tools&lt;/a&gt; that can turn a USB flash key into a bootable device. It&#039;s a modern machine. It supports that (Finally! Something modernish!).&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1534&quot; dc:identifier=&quot;http://lopsa.org/node/1534&quot; dc:title=&quot;So, you&#039;ve got to do a BIOS upgrade on a modern computer and it only comes in DOS&quot; trackback:ping=&quot;http://lopsa.org/trackback/1534&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Wed, 31 Oct 2007 19:02:29 -0700</pubDate>
 <author>doug</author>
</item>
<item>
 <title>a handy strace hack</title>
 <link>http://lopsa.org/node/1501</link>
 <description>&lt;p&gt;Say you want to strace a script.. Well, you can&#039;t, right? Because strace expects ELF (or other object format) executables as a target, or a running process. So one trick is to put a sleep at the top of the process, start it, do a quick ps, then strace -p.. Ugly, but effective in many cases.&lt;/p&gt;
&lt;p&gt;Another thing you can do is grab the &lt;i &gt;shebang&lt;/i&gt; line from the top of the script and parse it out and run strace on that and lookup the proper argument for the command interpreter that you are executing and pass all of that to strace.&lt;/p&gt;
&lt;p&gt;Since I have to do this so frequent, and I don&#039;t want to care about which arguments work best with which interpreters, I wrote a little C generalized wrapper that reexecs the program I&#039;m interested.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1501&quot; dc:identifier=&quot;http://lopsa.org/node/1501&quot; dc:title=&quot;a handy strace hack&quot; trackback:ping=&quot;http://lopsa.org/trackback/1501&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Wed, 08 Aug 2007 11:49:25 -0700</pubDate>
 <author>doug</author>
</item>
<item>
 <title>Towards a resilient NTP configuration in NTP4</title>
 <link>http://lopsa.org/node/1480</link>
 <description>&lt;p&gt;NTP 4 introduces some interesting new things that few people seem to know about, are sparsely documented, and are difficult to setup correctly, however they can help with synchronization in the event of total external network failure (even if you don&#039;t have a reference time source).&lt;/p&gt;
&lt;p&gt;Now, some reference time sources aren&#039;t expensive (others are), but sometimes you care more about node-to-node synchronization than you do about absolute time accuracy. One example might be a large computational cluster where, if the network is disconnected from the Internet for a while, or if the primary time source is down, you don&#039;t want the individual nodes to drift apart.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1480&quot; dc:identifier=&quot;http://lopsa.org/node/1480&quot; dc:title=&quot;Towards a resilient NTP configuration in NTP4&quot; trackback:ping=&quot;http://lopsa.org/trackback/1480&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/46">Network</category>
 <category domain="http://lopsa.org/taxonomy/term/119">Protocols</category>
 <pubDate>Thu, 12 Jul 2007 06:15:51 -0700</pubDate>
 <author>doug</author>
</item>
<item>
 <title>Luke on Config Mgmt</title>
 <link>http://lopsa.org/node/1139</link>
 <description>&lt;p&gt;
Luke Kanies blogs a &lt;a href=&quot;http://www.oreillynet.com/sysadmin/blog/2007/02/why_isnt_system_administration.html&quot;&gt;rant&lt;/a&gt; on configuration management that claims that the entire state of system administration is broken. Maybe he&#039;s right, maybe he&#039;s wrong. The problem is, he describes a microcosm of system administration in configuration management and then goes on to conclude that all tools of all aspects of system administration suck and that the field is stuck in the stone ages. It&#039;s quite a logical leap. It would be like me complaining that all tools in all of medicine stuck because dentists still use pliers and knives to pull teeth. How large a percentage of your day to day sysadmin work is spent doing configuration management that would benefit from tools like lscfg, bcfg2, puppet, cfengine, or radmind? For me, it&#039;s less than 1% of my daily work. 
&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1139&quot; dc:identifier=&quot;http://lopsa.org/node/1139&quot; dc:title=&quot;Luke on Config Mgmt&quot; trackback:ping=&quot;http://lopsa.org/trackback/1139&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Fri, 09 Feb 2007 11:51:35 -0800</pubDate>
 <author>doug</author>
</item>
<item>
 <title>Anthony Spina blogs on tagging</title>
 <link>http://lopsa.org/node/1138</link>
 <description>&lt;p&gt;
Anthony Spina writes an interesting article on the Splunk blog (&lt;a href=&quot;http://splunkideas.blogspot.com/2007/02/youve-tagged-your-it-now-tag-your-ip.html&quot;&gt;here&lt;/a&gt;). Using network databases like this can make distributed operations much easier. How do you tag your machines?
&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/1138&quot; dc:identifier=&quot;http://lopsa.org/node/1138&quot; dc:title=&quot;Anthony Spina blogs on tagging&quot; trackback:ping=&quot;http://lopsa.org/trackback/1138&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/118">Naming</category>
 <category domain="http://lopsa.org/taxonomy/term/21">Networking</category>
 <pubDate>Fri, 09 Feb 2007 11:39:57 -0800</pubDate>
 <author>doug</author>
</item>
<item>
 <title>LOPSA blogging tips and shortcuts</title>
 <link>http://lopsa.org/ContentTips</link>
 <description>&lt;h2&gt; Some tips on publishing content &lt;/h2&gt;

Most people don&#039;t know some of the shortcuts you can use to make content publishing easier and more useful. One of the first lessons is using interwiki to provide quick links to reference material.
&lt;p/&gt;
For some tips on using this, see &lt;a href=&quot;http://lopsa.org/interwiki/6&quot;&gt;http://lopsa.org/interwiki/6&lt;/a&gt;.
&lt;p/&gt;
Also, below the list of input filters when you are composing your blog entry you will find a link that says &lt;a href=&quot;http://lopsa.org/filter/tips&quot;&gt;More information about formatting options&lt;/a&gt;. This link can also be accessed directly at &lt;a href=&quot;http://lopsa.org/filter/tips&quot;&gt;http://lopsa.org/filter/tips&lt;/a&gt;.

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/ContentTips&quot; dc:identifier=&quot;http://lopsa.org/ContentTips&quot; dc:title=&quot;LOPSA blogging tips and shortcuts&quot; trackback:ping=&quot;http://lopsa.org/trackback/861&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Sun, 29 Oct 2006 17:43:37 -0800</pubDate>
 <author>doug</author>
</item>
<item>
 <title>NAS appliances comparisons and pitfalls</title>
 <link>http://lopsa.org/node/860</link>
 <description>&lt;p&gt;
Daniel Feenburg at &lt;a href=&quot;http://nber.org&quot;&gt;NBER&lt;/a&gt; writes a &lt;a href=&quot;http://www.nber.org/sys-admin/linux-nas-raid.html&quot;&gt;good review&lt;/a&gt; comparing performance, reliability, price, and other aspects of common RAID NAS solutions. Among those covered are &lt;a href=&quot;http://netapp.com&quot;&gt;Netapp&lt;/a&gt;, &lt;a href=&quot;http://dnfstorage.com&quot;&gt;DNF&lt;/a&gt;, &lt;a href=&quot;http://www.emdstorage.com/&quot;&gt;Excel-Meridian&lt;/a&gt;, and Linux white-box with RedHat Linux and &lt;a href=&quot;http://www.promise.com&quot;&gt;promise&lt;/a&gt; IDE controller. 
&lt;/p&gt;
&lt;p&gt;
What makes this version somewhat unique is it deals with the problem of secondary unrecoverable bit-errors that were previously undetected but manifest themselves when you go to rebuild a failed drive. This problem is more common than one would hope, and it is explained well.
&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/860&quot; dc:identifier=&quot;http://lopsa.org/node/860&quot; dc:title=&quot;NAS appliances comparisons and pitfalls&quot; trackback:ping=&quot;http://lopsa.org/trackback/860&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <category domain="http://lopsa.org/taxonomy/term/157">NAS</category>
 <pubDate>Sun, 29 Oct 2006 17:23:03 -0800</pubDate>
 <author>doug</author>
</item>
<item>
 <title>Ohio Linux Conf</title>
 <link>http://lopsa.org/node/808</link>
 <description>&lt;p&gt;&lt;img src=&quot;http://ohiolinux.org/image/slideshow5.jpg&quot; width=&quot;120px&quot; height=&quot;120px&quot; align=&quot;right&quot;&gt;Stephen Potter and I are meeting lots of new potential members &lt;a href=&quot;http://ohiolinux.org&quot;&gt;here&lt;/a&gt; . At least one new member has already signed up. Since they don&#039;t have official networking, I&#039;m logged in via GPRS. Many people haven&#039;t heard of LOPSA, so raising awareness is part of our target. The event looks to be a big success. Hundreds of people filter by the booth at every break. The projected attendance is 1700 people. Our own &lt;a href=&quot;/user/324&quot;&gt;Beth Lynn Eicher&lt;/a&gt; is one of the conference organizers and doing a great job, here.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/808&quot; dc:identifier=&quot;http://lopsa.org/node/808&quot; dc:title=&quot;Ohio Linux Conf&quot; trackback:ping=&quot;http://lopsa.org/trackback/808&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Sat, 30 Sep 2006 08:07:08 -0700</pubDate>
 <author>doug</author>
</item>
<item>
 <title>Sysadmin Bookshelf</title>
 <link>http://lopsa.org/node/730</link>
 <description>&lt;p&gt;There&#039;s some interest in creating a sysadmin bookshelf, which I think is a great idea. We&#039;ve basically got all the &#039;categories&#039; we need, I think, in the Standards category taxonomy. It&#039;s nice to reuse things for multiple purposes. It gives a sense of coherency to site organization and allows you to browse through things in multiple ways regardless of content type. The next step would be to do something like is done for Tools.&lt;br /&gt;
  I&#039;m thinking of a Bookshelf content type that would make use of some of the amazon features we have (affiliates program for discounts), or other vendors like Pearson where we have even better discounts. Then, add the voting API to the nodes to allow scoring. Associating them into the taxonomy allows browsing (you could find all books and tools related to Network Visualization. That&#039;d be pretty cool). If anybody would like to work on this (some knowledge of drupal is helpful, but not required), let me know. Seems like about 10 hours of work to get something at least beta quality.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/730&quot; dc:identifier=&quot;http://lopsa.org/node/730&quot; dc:title=&quot;Sysadmin Bookshelf&quot; trackback:ping=&quot;http://lopsa.org/trackback/730&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Fri, 04 Aug 2006 09:47:50 -0700</pubDate>
 <author>doug</author>
</item>
<item>
 <title>Netflow tools I need to investigate</title>
 <link>http://lopsa.org/node/259</link>
 <description>&lt;p&gt;
&lt;a href=&quot;http://www.splintered.net/sw/flow-tools/&quot;&gt;Flowtools&lt;/a&gt;
&lt;a href=&quot;http://silktools.sourceforge.net/&quot;&gt;SiLK&lt;/a&gt;
&lt;a href=&quot;http://nfsen.sourceforge.net/&quot;&gt;nfsen&lt;/a&gt;
&lt;a href=&quot;http://nfdump.sourceforge.net/&quot;&gt;nfdump&lt;/a&gt;
&lt;a href=&quot;http://www.ntop.org/&quot;&gt;ntop&lt;/a&gt;
&lt;a href=&quot;http://ipacco.sourceforge.net/index.php&quot;&gt;ipacco (not really netflow)&lt;/a&gt;
&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/259&quot; dc:identifier=&quot;http://lopsa.org/node/259&quot; dc:title=&quot;Netflow tools I need to investigate&quot; trackback:ping=&quot;http://lopsa.org/trackback/259&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Sat, 04 Mar 2006 14:20:18 -0800</pubDate>
 <author>doug</author>
</item>
<item>
 <title>Notes from SPAM guru session</title>
 <link>http://lopsa.org/antispam</link>
 <description>&lt;p&gt;
As promised, here are my notes on the [anti] SPAM guru session held Thursday Decmber 7 from 9AM to 10:30AM. This document is member editable in wiki format. Add stuff as needed. Put offsite hyper links in square brackets. Put onsite hyperlinks in square brackets. Any link starting with http: is automatically hyperlinked; in square brackets it&#039;s an offsite link.
&lt;h4&gt; examples: &lt;/h4&gt;
[onsite link]
[offsite link|&lt;a href=&quot;http://offsite.link&quot;&gt;http://offsite.link&lt;/a&gt;]
&lt;/p&gt;
&lt;p&gt;
see also &lt;a href=&quot;http://lopsa.org/filter/tips&quot;&gt;filter tips&lt;/a&gt;
&lt;/p&gt;
&lt;p&gt;
&lt;h2&gt; technology breakdown &lt;/h2&gt;
&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt; whitelists
&lt;li&gt; blacklists
&lt;li&gt; reputation
&lt;li&gt; bayesian
&lt;li&gt; spf and other sender verification
&lt;/ul&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/antispam&quot; dc:identifier=&quot;http://lopsa.org/antispam&quot; dc:title=&quot;Notes from SPAM guru session&quot; trackback:ping=&quot;http://lopsa.org/trackback/169&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <enclosure url="http://lopsa.org/files/lisa04spam.sxi" length="103367" type="application/vnd.sun.xml.impress" />
 <pubDate>Tue, 13 Dec 2005 11:03:18 -0800</pubDate>
 <author>doug</author>
</item>
<item>
 <title>Principles of volunteerism</title>
 <link>http://lopsa.org/node/139</link>
 <description>&lt;p&gt;I&#039;ve been thinking a bit about how to foster volunteerism and developing some principles to make it vibrant and healthy. Things like:&lt;/p&gt;


&lt;ul&gt;
&lt;li&gt;Make realistic time committments. Saying that you can commit only 2 hours a week and delivering is better than saying you can commit 8 and delivering 4. In order to effectively divide work the volunteer coordinators need to know accurate time committments to assign resources. Overcommittment can also lead to burnout; we value our volunteers. &lt;/li&gt;
&lt;/ul&gt;




&lt;ul&gt;
&lt;li&gt;2 sets of eyes are better than one. In our jobs, just running something by somebody else can result in quick resolution to problems. It helps to identify the important parts and clear our heads of the irrelevent stuff. We can apply the same principles towards volunteering and project development.&lt;/li&gt;
&lt;/ul&gt;


&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/139&quot; dc:identifier=&quot;http://lopsa.org/node/139&quot; dc:title=&quot;Principles of volunteerism&quot; trackback:ping=&quot;http://lopsa.org/trackback/139&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Fri, 02 Dec 2005 19:48:26 -0800</pubDate>
 <author>doug</author>
</item>
<item>
 <title>You can do that with a Netra?</title>
 <link>http://lopsa.org/node/137</link>
 <description>&lt;p&gt;
Most people don&#039;t realize the level of management information that you can get from a Netra (104 or 200 or v120). Sure, they are old and slow by modern standards, but they are extremely rugged and come in AC and DC varieties which is very handy when you are a telco shop or have telco components. The Lights out Management (LOM) functionality is still the best in breed of any vendor, and had capabilities 4 years ago that others are still trying to catch up to today. Rackable is next best and things go down hill from there. 
&lt;p&gt;
(possibly incomplete) list of components:
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;http://www.sun.com/products-n-solutions/hw/networking/solutions/sunsnetra.html#sun_netra&quot;&gt;Sun Netra SNMP Management Agent&lt;/a&gt;. Lots of documentation here. a few mib files too. If you take a look at the entity mib it will look suspiciously like IPMI. I think the IPMI WG used the sun entity mib as a reference model.

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/137&quot; dc:identifier=&quot;http://lopsa.org/node/137&quot; dc:title=&quot;You can do that with a Netra?&quot; trackback:ping=&quot;http://lopsa.org/trackback/137&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Fri, 02 Dec 2005 14:10:25 -0800</pubDate>
 <author>doug</author>
</item>
<item>
 <title>Keeping Drafts</title>
 <link>http://lopsa.org/node/114</link>
 <description>&lt;p&gt;Are you borderline (or fully!?) ADD like me? Do you have trouble doing just one thing at a time? Do you write and then keep drafts for later? Well, I don&#039;t know about the first two, but I can help with the last one. I added a block on the left of the main blog screen &#039;My Drafts&#039; that shows up if you have any unpublished documents.&lt;/p&gt;
&lt;p&gt;So, let&#039;s say you want to come back to an entry later, you can uncheck the &#039;published&#039; box at the top. It won&#039;t show up. Nobody will know it&#039;s there! (possibly including you). My Drafts will show you all the unpublished documents that you own so that you can click on them and finish editing and publish, or delete them.&lt;/p&gt;

&lt;!--
&lt;rdf:RDF xmlns:rdf=&quot;http://www.w3.org/1999/02/22-rdf-syntax-ns#&quot; xmlns:dc=&quot;http://purl.org/dc/elements/1.1/&quot; xmlns:trackback=&quot;http://madskills.com/public/xml/rss/module/trackback/&quot;&gt;
&lt;rdf:Description rdf:about=&quot;http://lopsa.org/node/114&quot; dc:identifier=&quot;http://lopsa.org/node/114&quot; dc:title=&quot;Keeping Drafts&quot; trackback:ping=&quot;http://lopsa.org/trackback/114&quot; /&gt;
&lt;/rdf:RDF&gt;
--&gt;

</description>
 <pubDate>Fri, 18 Nov 2005 00:08:42 -0800</pubDate>
 <author>doug</author>
</item>
</channel>
</rss>
