<?xml version="1.0" encoding="utf-8" ?>

<rss version="2.0" 
   xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"
   xmlns:admin="http://webns.net/mvcb/"
   xmlns:dc="http://purl.org/dc/elements/1.1/"
   xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
   xmlns:wfw="http://wellformedweb.org/CommentAPI/"
   xmlns:content="http://purl.org/rss/1.0/modules/content/"
   >
<channel>
    <title>Daniel E. Markle's Blog - System Administration</title>
    <link>http://ashtech.net/~syntax/blog/</link>
    <description>Blatherings on Technology and Life</description>
    <dc:language>en</dc:language>
    <admin:errorReportsTo rdf:resource="mailto:" />
    <generator>Serendipity 1.2.1 - http://www.s9y.org/</generator>
    <managingEditor>syntax@ashtech.net (Daniel E. Markle)</managingEditor>
<webMaster>syntax@ashtech.net (Daniel E. Markle)</webMaster>

    <image>
        <url>http://ashtech.net/~syntax/blog/uploads/128blackcat.png</url>
        <title>RSS: Daniel E. Markle's Blog - System Administration - Blatherings on Technology and Life</title>
        <link>http://ashtech.net/~syntax/blog/</link>
        <width>128</width>
        <height>128</height>
    </image>

<item>
    <title>Agile Documentation Thoughts for Small Groups</title>
    <link>http://ashtech.net/~syntax/blog/archives/169-Agile-Documentation-Thoughts-for-Small-Groups.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/169-Agile-Documentation-Thoughts-for-Small-Groups.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=169</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=169</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    Working for a small company, our projects tend to be small. Processes and programs are best documented as tasks are first done and over time as improvements are made. Trying to document everything up front is a waste of time, as the requirements change throughout. Waiting until the end, the documentation is never completed as some other urgent project comes along. Humans are frighteningly perishable and can get hit by a bus/meteor/disease at any time.&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://ashtech.net/~syntax/blog/archives/169-Agile-Documentation-Thoughts-for-Small-Groups.html#extended&quot;&gt;Continue reading &quot;Agile Documentation Thoughts for Small Groups&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Thu, 30 Jul 2009 23:03:25 -0400</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/169-guid.html</guid>
    
</item>
<item>
    <title>Debian 5 Mailutils and Maildir</title>
    <link>http://ashtech.net/~syntax/blog/archives/162-Debian-5-Mailutils-and-Maildir.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/162-Debian-5-Mailutils-and-Maildir.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=162</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=162</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    When setting up &lt;a href=&quot;http://en.wikipedia.org/wiki/Maildir&quot;&gt;Maildir&lt;/a&gt; in Debian 5.0, getting the generic &lt;code&gt;mail&lt;/code&gt; applications working correctly can be tricky.&lt;ul&gt;&lt;li&gt;Install the &#039;mailutils&#039; package, not the bsd mailx package.&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;Do &lt;strong&gt;not&lt;/strong&gt; touch the mailutils /etc/mail.rc file; there are some promising looking variables here like &lt;code&gt;mailbox-type&lt;/code&gt; but these do not do what is desired. When the MAIL environment variable is set correctly mailutils will automatically detect the maildir box type.&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;Do &lt;strong&gt;not&lt;/strong&gt; touch /etc/login.defs; the promising looking lines in here are deprecated.&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;Edit files in &lt;code&gt;/etc/pam.d&lt;/code&gt;, changing the pam_mail.so lines as shown (assuming ~/Maildir as the selected location):&lt;br /&gt;
  &lt;ul&gt;&lt;br /&gt;
  &lt;li&gt;login: default login shells&lt;br /&gt;
  &lt;code&gt;session    optional   pam_mail.so dir=~/Maildir standard&lt;/code&gt;&lt;br /&gt;
  &lt;/li&gt;&lt;br /&gt;
  &lt;li&gt;su: set up for proper MAIL when using su; nopen does not show &#039;new mail&#039; message&lt;br /&gt;
  &lt;code&gt;session    optional   pam_mail.so dir=~/Maildir nopen&lt;/code&gt;&lt;br /&gt;
  &lt;/li&gt;&lt;br /&gt;
  &lt;li&gt;sshd: set up MAIL properly when logging in with ssh; this line probably has a noenv by default which needs removed to set this properly&lt;br /&gt;
  &lt;code&gt;session    optional     pam_mail.so dir=~/Maildir standard&lt;/code&gt;&lt;br /&gt;
  &lt;/li&gt;&lt;/ul&gt;&lt;/li&gt;&lt;/ul&gt; 
    </content:encoded>

    <pubDate>Wed, 08 Apr 2009 16:32:48 -0400</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/162-guid.html</guid>
    
</item>
<item>
    <title>PostgreSQL Upgrade to 8.3 on Debian Encoding Issues</title>
    <link>http://ashtech.net/~syntax/blog/archives/160-PostgreSQL-Upgrade-to-8.3-on-Debian-Encoding-Issues.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/160-PostgreSQL-Upgrade-to-8.3-on-Debian-Encoding-Issues.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=160</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=160</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    PostgreSQL has improved its checking for proper locale handling in version 8.3. Due to inconsistencies caused by changing defaults in past versions of Debian, some database clusters contain UTF8 and LATIN1 databases in the same cluster. This can cause problems when trying to restore from a pgdump file with errors similar to:&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;ERROR:  encoding LATIN1 does not match server&#039;s locale en_US.UTF-8&lt;br /&gt;
DETAIL:  The server&#039;s LC_CTYPE setting requires encoding UTF8.&lt;/code&gt; &lt;br /&gt;&lt;a href=&quot;http://ashtech.net/~syntax/blog/archives/160-PostgreSQL-Upgrade-to-8.3-on-Debian-Encoding-Issues.html#extended&quot;&gt;Continue reading &quot;PostgreSQL Upgrade to 8.3 on Debian Encoding Issues&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Wed, 18 Mar 2009 19:28:36 -0400</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/160-guid.html</guid>
    
</item>
<item>
    <title>Cron Uses /usr/sbin/sendmail</title>
    <link>http://ashtech.net/~syntax/blog/archives/124-Cron-Uses-usrsbinsendmail.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/124-Cron-Uses-usrsbinsendmail.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=124</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=124</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    On a server running Zimbra on Ubuntu, to get cron job output sent to an e-mail address, make the following link:&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;ln -s /opt/zimbra/postfix/sbin/sendmail /usr/sbin/sendmail&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
Until this is done, crontab output will silently vaporize. &lt;br /&gt;&lt;a href=&quot;http://ashtech.net/~syntax/blog/archives/124-Cron-Uses-usrsbinsendmail.html#extended&quot;&gt;Continue reading &quot;Cron Uses /usr/sbin/sendmail&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Thu, 22 Jan 2009 20:09:33 -0500</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/124-guid.html</guid>
    
</item>
<item>
    <title>Be Careful with / in ProxyPass</title>
    <link>http://ashtech.net/~syntax/blog/archives/110-Be-Careful-with-in-ProxyPass.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/110-Be-Careful-with-in-ProxyPass.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=110</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=110</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    I use the built-in Apache 2.2 ajp ProxyPass support when deploying Tomcat and JBoss applications via Apache.  When doing so, be careful your slashes match up or you can have subtle problems with applications which use redirects.  For example, I was deploying a &lt;a href=&quot;http://jspwiki.org&quot;&gt;JSPWiki&lt;/a&gt; but having an odd problem with authentication where logins would seem to fail but then work fine if I manually reloaded the page.  I was using this Apache configuration:&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;ProxyPass           /webdevwiki  ajp://127.0.0.1:8009/webdevwiki/&lt;br /&gt;
ProxyPassReverse    /webdevwiki  ajp://127.0.0.1:8009/webdevwiki/&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
This appeared to work fine, but when logging in an extra slash would get added to the Login.jsp redirection page.  This kept the redirect to the main page from working, causing it to reload the Login.jsp infinitely even though login had been successful.  A manual click of the reload button fixed the site, with authentication and all other functions working until trying to log in again.&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;ProxyPass           /webdevwiki  ajp://127.0.0.1:8009/webdevwiki&lt;br /&gt;
ProxyPassReverse    /webdevwiki  ajp://127.0.0.1:8009/webdevwiki&lt;/code&gt;&lt;br /&gt;
&lt;br /&gt;
Removing the extra slashes as shown fixed this issue. 
    </content:encoded>

    <pubDate>Tue, 05 Feb 2008 18:06:26 -0500</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/110-guid.html</guid>
    
</item>
<item>
    <title>Making Apache 2.2 valid-user work with mod_authnz_ldap</title>
    <link>http://ashtech.net/~syntax/blog/archives/108-Making-Apache-2.2-valid-user-work-with-mod_authnz_ldap.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/108-Making-Apache-2.2-valid-user-work-with-mod_authnz_ldap.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=108</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=108</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    Apache 2.2&#039;s &lt;a href=&quot;http://httpd.apache.org/docs/2.2/mod/mod_authnz_ldap.html&quot; &gt;mod_authnz_ldap&lt;/a&gt; has significant differences from Apache 2.0&#039;s &lt;a href=&quot;http://httpd.apache.org/docs/2.0/mod/mod_auth_ldap.html&quot; &gt;mod_auth_ldap&lt;/a&gt;.  Moving to 2.2, some significant changes are needed which can be confusing and cause seemingly nonsensical authorization loops if directives are missed.&lt;br /&gt;
&lt;br /&gt;
&lt;h4&gt;Necessary modules&lt;/h4&gt;&lt;ul&gt;&lt;li&gt;auth_basic&lt;/li&gt;&lt;li&gt;authz_user&lt;/li&gt;&lt;li&gt;ldap&lt;/li&gt;&lt;li&gt;authnz_ldap&lt;/li&gt;&lt;/ul&gt;&lt;h4&gt;Directives&lt;/h4&gt;&lt;code&gt;&lt;br /&gt;
        AuthType basic&lt;br /&gt;
        AuthBasicProvider ldap&lt;br /&gt;
        AuthName &quot;My Site&quot;&lt;br /&gt;
        AuthLDAPURL ldap://ldap1.example.com/ou=People,o=Example&lt;br /&gt;
        AuthzLDAPAuthoritative Off&lt;br /&gt;
        Require valid-user&lt;br /&gt;
&lt;/code&gt;&lt;br /&gt;
&lt;code&gt;AuthBasicProvider ldap&lt;/code&gt; is needed instead of &lt;code&gt;AuthLDAPEnabled on&lt;/code&gt;, which no longer exists as a valid directive.&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;AuthzLDAPAuthoritative Off&lt;/code&gt; is needed to allow the authorization to fall though to &lt;code&gt;Require valid-user&lt;/code&gt;, otherwise you will get &lt;code&gt; auth _ldap authorise: authorisation denied&lt;/code&gt; in your debug messages after it successfully authenticates the user but fails to find an authorization directive to allow access.  These messages will not show up in your logs by default, so it can be confusing if you watch the ldap server, see authentication succeed, and wonder why it keeps requesting a username and password. 
    </content:encoded>

    <pubDate>Thu, 03 Jan 2008 12:46:05 -0500</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/108-guid.html</guid>
    
</item>
<item>
    <title>Zimbra Calendar Reminders Not Individually Configurable</title>
    <link>http://ashtech.net/~syntax/blog/archives/95-Zimbra-Calendar-Reminders-Not-Individually-Configurable.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/95-Zimbra-Calendar-Reminders-Not-Individually-Configurable.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=95</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=95</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    &lt;a href=&quot;http://zimbra.com/&quot;&gt;Zimbra&lt;/a&gt; lacks a calendar feature commonly used by serious Outlook and Entourage users, the ability to configure reminders for individual calendar entries.  The workaround is to create a &#039;reminder&#039; calendar entry, which does not work well as it requires manually changing the reminder if the original appointment changes.  If you are a current or prospective Zimbra user and would like to have this feature added, please &lt;a href=&quot;http://bugzilla.zimbra.com/show_bug.cgi?id=8854&quot; &gt;vote for this bug&lt;/a&gt;.  On a related note, the Zimbra Toaster (which provides popup notification of new mail) does not support calendar reminders, which is documented in &lt;a href=&quot;http://bugzilla.zimbra.com/show_bug.cgi?id=12740&quot; &gt;this bug&lt;/a&gt;. 
    </content:encoded>

    <pubDate>Fri, 06 Jul 2007 10:57:39 -0400</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/95-guid.html</guid>
    
</item>
<item>
    <title>APC Back-UPS XS 1500</title>
    <link>http://ashtech.net/~syntax/blog/archives/94-APC-Back-UPS-XS-1500.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/94-APC-Back-UPS-XS-1500.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=94</wfw:comment>

    <slash:comments>20</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=94</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    &lt;img src=&quot;http://ashtech.net/~syntax/images/apc_ups_xs1500.jpg&quot; alt=&quot;&quot; style=&quot;float: left; padding-right: 4px;&quot; /&gt;In the area where I reside power fluctuations and outages are numerous, so having a UPS is crucial when doing serious computer work.  When my old Belkin F6C800 unit recently died a malodorous death, I decided to return to APC.  Browsing the local Best Buy, I saw a &lt;a href=&quot;http://www.apcc.com/resource/include/techspec_index.cfm?base_sku=BX1500LCD&quot; &gt;Back-UPS XS 1500 LCD&lt;/a&gt; on the shelf with, as the name implies, an LCD display.  Such a geeky feature was beyond resistance for me.&lt;br /&gt;
&lt;br /&gt;
I use a &lt;a href=&quot;http://www.apcc.com/resource/include/techspec_index.cfm?base_sku=BX1500&quot; &gt;Back-UPS XS 1500&lt;/a&gt; (without the LCD) for various machines downstairs, and it works well.  The only issue with it is the noise; it beeps every time the power fluctuates with no way to turn it off.  On some days when my power is particularly bad, this results in perpetual beeping every few minutes.  Obviously they received many customer complaints about this, as the XS 1500 LCD has two buttons on the front; &#039;Power&#039; and &#039;Mute&#039;.&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;Update:&lt;/strong&gt; The display readings for this device are &lt;a href=&quot;http://ashtech.net/~syntax/blog/archives/94-APC-Back-UPS-XS-1500.html#comments&quot;&gt;proving to be inaccurate when tested&lt;/a&gt;.  Do not rely on the readings from this device. &lt;br /&gt;&lt;a href=&quot;http://ashtech.net/~syntax/blog/archives/94-APC-Back-UPS-XS-1500.html#extended&quot;&gt;Continue reading &quot;APC Back-UPS XS 1500&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Fri, 08 Jun 2007 07:16:47 -0400</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/94-guid.html</guid>
    
</item>
<item>
    <title>Google Checkout</title>
    <link>http://ashtech.net/~syntax/blog/archives/88-Google-Checkout.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/88-Google-Checkout.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=88</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=88</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    I made a purchase with &lt;a href=&quot;http://checkout.google.com&quot;&gt;Google Checkout&lt;/a&gt; earlier this week and was really impressed with the user experience.  While doing some research into using it, I found they are offering &lt;a href=&quot;http://checkout.google.com/support/sell/bin/answer.py?answer=52976&amp;topic=10090&quot; &gt;free checkout services&lt;/a&gt; until 2008.  This seems to be a killer deal for budding businesses; setting up a merchant account and transaction fees are a considerable obstacle for new businesses.&lt;br /&gt;
&lt;br /&gt;
It does however lack &lt;a href=&quot;http://icdevgroup.org/&quot;&gt;Interchange&lt;/a&gt; support.  It is possible to use the basic embedded-in-page checkout with Interchange now, but this HTML option doesn&#039;t provide as nice of an experience for the user.   It also requires more administration work as the retailer has to manually process orders using Google&#039;s checkout site.  Building and contributing Google Checkout XML interface support for Interchange may be in my future. 
    </content:encoded>

    <pubDate>Thu, 03 May 2007 00:25:28 -0400</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/88-guid.html</guid>
    
</item>
<item>
    <title>Recursive Commands Dangerous in Scratchbox User Directories</title>
    <link>http://ashtech.net/~syntax/blog/archives/83-Recursive-Commands-Dangerous-in-Scratchbox-User-Directories.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/83-Recursive-Commands-Dangerous-in-Scratchbox-User-Directories.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=83</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=83</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    &lt;img src=&quot;http://ashtech.net/~syntax/images/errors/lilo-borked.png&quot; alt=&quot;&quot; style=&quot;float: left; padding-right: 6px;&quot; /&gt;When using &lt;a href=&quot;http://www.scratchbox.org/&quot; &gt;scratchbox&lt;/a&gt; (a &lt;a href=&quot;http://en.wikipedia.org/wiki/Cross_compiler&quot; &gt;cross-compilation&lt;/a&gt; toolkit), be very careful when moving or deleting user data from the &lt;code&gt;/scratchbox/users&lt;/code&gt; directory.  There are hard links to &lt;code&gt;/dev&lt;/code&gt;, &lt;code&gt;/sys&lt;/code&gt;, and other important directories there after adding users.  Recursive commands are extremely dangerous in these user directories.  The LILO boot results at the left were caused after moving scratchbox into its own partition using recursive commands.&lt;br /&gt;
&lt;br /&gt;
&lt;code&gt;/scratchbox/sbin/sbox_umount_all&lt;/code&gt; is your friend. 
    </content:encoded>

    <pubDate>Wed, 14 Feb 2007 22:15:35 -0500</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/83-guid.html</guid>
    
</item>
<item>
    <title>S.M.A.R.T. is Dumb</title>
    <link>http://ashtech.net/~syntax/blog/archives/82-S.M.A.R.T.-is-Dumb.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/82-S.M.A.R.T.-is-Dumb.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=82</wfw:comment>

    <slash:comments>1</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=82</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    I have never had a good experience with &lt;a href=&quot;http://en.wikipedia.org/wiki/Self-Monitoring%2C_Analysis%2C_and_Reporting_Technology&quot; &gt;S.M.A.R.T.&lt;/a&gt; (Self-Monitoring, Analysis, and Reporting Technology).  It usually only reports the drive is about to fail after the drive has already failed and is completely unreadable.  My latest drive failure is yet another case of this, but interesting in that this failure seems to have been quite easily predictable.  The drive was obviously failing from the output of the S.M.A.R.T. monitoring system, with 197 new defects, and over 50 uncorrected errors.  Yet the software in the drive still reports &lt;code&gt;SMART Health Status: OK&lt;/code&gt;. &lt;br /&gt;&lt;a href=&quot;http://ashtech.net/~syntax/blog/archives/82-S.M.A.R.T.-is-Dumb.html#extended&quot;&gt;Continue reading &quot;S.M.A.R.T. is Dumb&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Thu, 08 Feb 2007 10:44:11 -0500</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/82-guid.html</guid>
    
</item>
<item>
    <title>OS X: Fixing a Missing Ethernet Port</title>
    <link>http://ashtech.net/~syntax/blog/archives/73-OS-X-Fixing-a-Missing-Ethernet-Port.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/73-OS-X-Fixing-a-Missing-Ethernet-Port.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=73</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=73</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    If your ethernet port is not working on OS X (it seems to be most common and/or only on the Intel Macbooks):&lt;ul&gt;&lt;br /&gt;
&lt;li&gt;Rename /Library/Preferences/SystemConfiguration&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;Toggle a setting in the Network System Preferences panel&lt;/li&gt;&lt;br /&gt;
&lt;li&gt;Setup your Network as desired and test it, the configuration should rebuild and your network should now work&lt;/li&gt;&lt;br /&gt;
&lt;/ul&gt;A friend had this happen on his brand new Macbook Pro Core 2.  However, it has never happened on mine.  This may mean the software preload was bad, especially if this happens on a new machine, so doing an Archive and Install is probably a good idea.&lt;br /&gt;
&lt;br /&gt;
&lt;strong&gt;Update:&lt;/strong&gt; Further testing indicates this problem was caused by bad firmware on a &lt;a href=&quot;http://www.smc.com/index.cfm?event=viewProduct&amp;localeCode=EN_USA&amp;cid=7&amp;scid=&amp;pid=1485&quot; &gt;SMC SMCGS16-SMART switch&lt;/a&gt;.  The problem only occurred upon connection to this brand and model of switch, and was resolved permanently by upgrading the firmware in the switch from v.1.00.04 to v.1.00.06_16. 
    </content:encoded>

    <pubDate>Mon, 27 Nov 2006 15:53:32 -0500</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/73-guid.html</guid>
    
</item>
<item>
    <title>Verizon.net and Third Party DSL Routers</title>
    <link>http://ashtech.net/~syntax/blog/archives/72-Verizon.net-and-Third-Party-DSL-Routers.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/72-Verizon.net-and-Third-Party-DSL-Routers.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=72</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=72</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    When configuring a third party router with Verizon.net DSL, the DSL modem may need reconfigured to bridged mode and the third party router configured to handle PPPoE instead of the provided DSL modem.  I found this issue in particular with the Westell 6100 DSL modems Verizon is now issuing. An excellent resource in this case is &lt;a href=&quot;http://members.verizon.net/~res08lyg/6100.htm&quot; &gt;this information on configuring the Westell 6100 in bridged mode&lt;/a&gt;, then follow the third party router&#039;s instructions for PPPoE.  Note the &amp;lt;username&amp;gt;@verizon.net and password configured for e-mail is the same one needed for PPPoE. 
    </content:encoded>

    <pubDate>Tue, 21 Nov 2006 17:44:41 -0500</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/72-guid.html</guid>
    
</item>
<item>
    <title>Ubuntu X Server Breakage</title>
    <link>http://ashtech.net/~syntax/blog/archives/57-Ubuntu-X-Server-Breakage.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/57-Ubuntu-X-Server-Breakage.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=57</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=57</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    I have been using &lt;a href=&quot;http://ubuntulinux.org/&quot;&gt;Ubuntu&lt;/a&gt; on various desktops lately; it is one of the most polished Linux distributions I have ever used from a desktop refinement standpoint.  However, Ubuntu&#039;s desktop refinement appears to only be skin deep.&lt;br /&gt;
&lt;br /&gt;
The Ubuntu developers tend to make major changes right before release time without adequate testing; &lt;a href=&quot;http://www.nzlinux.org.nz/blogs/2005/04/12/ubuntu-disaster/&quot;&gt;Hoary&#039;s last minute Gnome update&lt;/a&gt;, the many issues I&#039;ve had getting Dapper to work with most video cards (only one machine I&#039;ve tested on so far works with the LiveCD without using safe mode, two have required the alternative install), and the PowerPC LiveCD installer crashing on yaboot thus making the LiveCD installer quite useless on that platform.&lt;br /&gt;
&lt;br /&gt;
All of these issues were quite obvious, happen either every time or extremely often, and would have been caught with even the most rudimentary of testing.  Apparently &lt;a href=&quot;http://www.ubuntuforums.org/showthread.php?t=241254&quot;&gt;this lack of testing extends to their updates as well&lt;/a&gt;.  If I had not noticed their past pattern of not testing before release, I would find it rather amazing that such an update, which kills X11 on their two most major platforms so consistently, slipped through. 
    </content:encoded>

    <pubDate>Tue, 22 Aug 2006 10:49:16 -0400</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/57-guid.html</guid>
    
</item>
<item>
    <title>Data Scrub with Linux RAID or Die</title>
    <link>http://ashtech.net/~syntax/blog/archives/53-Data-Scrub-with-Linux-RAID-or-Die.html</link>
            <category>System Administration</category>
    
    <comments>http://ashtech.net/~syntax/blog/archives/53-Data-Scrub-with-Linux-RAID-or-Die.html#comments</comments>
    <wfw:comment>http://ashtech.net/~syntax/blog/wfwcomment.php?cid=53</wfw:comment>

    <slash:comments>3</slash:comments>
    <wfw:commentRss>http://ashtech.net/~syntax/blog/rss.php?version=2.0&amp;type=comments&amp;cid=53</wfw:commentRss>
    

    <author>syntax@ashtech.net (Daniel E. Markle)</author>
    <content:encoded>
    &lt;img src=&quot;/~syntax/images/satadrives.jpg&quot; alt=&quot;&quot; style=&quot;float: right;&quot; /&gt;It is absolutely critical to use data scrubbing with Linux software RAID.  If you fail to do so, when one of the drives fail and the new one is put in place to resync with, the chance of losing all data is very high.  When Linux resyncs a RAID array, it steps through each and every block on the disk(s) it is syncing from.  If there are any bad blocks on the &#039;good&#039; drives data scrubbing hasn&#039;t found (or data scrubbing isn&#039;t being used), that drive will also be marked as unusable.  This renders your array useless unless an array is in use that can recover from multiple drive failures at the same time, or you have quite a few days to spend on manual recovery.&lt;br /&gt;
&lt;br /&gt;
See this &lt;a href=&quot;http://gentoo-wiki.com/HOWTO_Gentoo_Install_on_Software_RAID#Data_Scrubbing&quot;&gt;information on how to do data scrubbing with Linux RAID&lt;/a&gt; for another description and instructions on how to do this. &lt;br /&gt;&lt;a href=&quot;http://ashtech.net/~syntax/blog/archives/53-Data-Scrub-with-Linux-RAID-or-Die.html#extended&quot;&gt;Continue reading &quot;Data Scrub with Linux RAID or Die&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Wed, 09 Aug 2006 10:29:25 -0400</pubDate>
    <guid isPermaLink="false">http://ashtech.net/~syntax/blog/archives/53-guid.html</guid>
    
</item>

</channel>
</rss>