<?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>Pet Pixels - Techie</title>
    <link>http://marcus.bointon.com/</link>
    <description>Marcus Bointon gets opinionated</description>
    <dc:language>en</dc:language>
    <admin:errorReportsTo rdf:resource="mailto:marcusblog@bointon.com" />
    <generator>Serendipity 1.2.1 - http://www.s9y.org/</generator>
    <pubDate>Wed, 19 Mar 2008 11:26:03 GMT</pubDate>

    <image>
        <url>http://marcus.bointon.com/templates/default/img/s9y_banner_small.png</url>
        <title>RSS: Pet Pixels - Techie - Marcus Bointon gets opinionated</title>
        <link>http://marcus.bointon.com/</link>
        <width>100</width>
        <height>21</height>
    </image>

<item>
    <title>SunSpider benchmarks updated</title>
    <link>http://marcus.bointon.com/archives/57-SunSpider-benchmarks-updated.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/57-SunSpider-benchmarks-updated.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=57</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=57</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    I updated &lt;a href=&quot;http://marcus.bointon.com/archives/50-SunSpider-Benchmarks-WebKit-Rocks.html&quot;&gt;my previous post on Sunspider benchmarks&lt;/a&gt; to include Safari 3.1, FireFox 3b4 and IE 8b1. 
    </content:encoded>

    <pubDate>Wed, 19 Mar 2008 11:26:03 +0000</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/57-guid.html</guid>
    
</item>
<item>
    <title>Microsoft finally gets it</title>
    <link>http://marcus.bointon.com/archives/56-Microsoft-finally-gets-it.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/56-Microsoft-finally-gets-it.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=56</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=56</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    I somehow missed Microsoft&#039;s announcement that (in a complete U-turn from &lt;a href=&quot;http://blogs.msdn.com/ie/archive/2008/01/21/compatibility-and-ie8.aspx&quot;&gt;previous announcements&lt;/a&gt;) &lt;a href=&quot;http://blogs.msdn.com/ie/archive/2008/03/03/microsoft-s-interoperability-principles-and-ie8.aspx&quot;&gt;IE8 will support web standards mode by default&lt;/a&gt;, and thus any broken sites will have to enable IE7 mode by a meta tag. So finally, IE will cease to be the albatross around the neck of the internet, and developers the world over will at last be able to write standards-compliant sites that work in all major browsers.&lt;br /&gt;
&lt;br /&gt;
I had real trouble believing that MS had convinced so many prominent web standards advocates (&lt;a href=&quot;http://alistapart.com/articles/minorthreat&quot;&gt;here&lt;/a&gt; and &lt;a href=&quot;http://alistapart.com/articles/beyonddoctype&quot; &gt;here&lt;/a&gt;) that the previous option was in some way a good thing, when it essentially meant that MS expected 99% of the web to change in order to support the 1% (almost entirely intranets and thus of no public interest) that are so badly written that they couldn&#039;t survive a browser update.&lt;br /&gt;
&lt;br /&gt;
I&#039;m very happy to see this change of heart, which was a really unexpected thing to see from MS. They don&#039;t normally give a stuff about such things, so they fully deserve the adulation that their announcement is getting in the comments. It also vindicates the slagging I gave the authors of those articles promoting the evil meta tag!&lt;br /&gt;
&lt;br /&gt;
So, &lt;strong&gt;Thank you Microsoft&lt;/strong&gt;! I look forward to not having to do anything special for IE - you probably just doubled the world&#039;s web development productivity rate! Who knows - one day IE might be as good as Firefox or Safari... 
    </content:encoded>

    <pubDate>Fri, 14 Mar 2008 16:19:49 +0000</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/56-guid.html</guid>
    <category>firefox</category>
<category>ie</category>
<category>meta</category>
<category>safari</category>
<category>standards</category>

</item>
<item>
    <title>Email Luddism</title>
    <link>http://marcus.bointon.com/archives/55-Email-Luddism.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/55-Email-Luddism.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=55</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=55</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    Here&#039;s a little rant I&#039;ve been meaning to get out for a while.&lt;br /&gt;
&lt;br /&gt;
Whenever the subject of email client support of some particular email feature comes up, someone always posts a comment to the tune of &quot;HTML doesn&#039;t belong in email anyway, all email should be plain text&quot;. What they&#039;re saying is that they outright reject two important features: MIME and progressive enhancement. Given that MIME is what makes attachments (or any arbitrary binary data, attached or not) possible, I guess they can live without them too. It&#039;s the same technology that allows web servers to identify content types, so while we&#039;re painting with his particularly tarry brush, I guess we should remove CSS, javascript and images from HTML pages as well. That should keep them happy. With all those removed, we can all retreat to the comfort of the command line where our needs will be served admirably by the likes of the wonderful (no joke) &lt;a href=&quot;http://elinks.or.cz/&quot;&gt;elinks&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
The whole point of the multipart/alternative data type is progressive enhancement. A client is free to select from the alternatives presented and render as best it can, with an option for manual selection (that is, as long as you don&#039;t use Outlook which doesn&#039;t believe in such things). This applies to the common text/plain &amp;gt; text/html combo as much as it would to text/plain &amp;gt; image/jpeg, or perhaps application/pdf &amp;gt; application/vnd.sun.xml.writer. Now if they restricted their comments to text/html only, I might have some sympathy, as that&#039;s just shoddy behaviour on the part of the sender. However, they usually prefer to throw out the baby with the bath water.&lt;br /&gt;
&lt;br /&gt;
To conclude: MIME is a wonderful thing; some people use it badly; get over it. 
    </content:encoded>

    <pubDate>Sun, 02 Mar 2008 21:26:00 +0000</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/55-guid.html</guid>
    <category>email</category>

</item>
<item>
    <title>iPhone icon test generator</title>
    <link>http://marcus.bointon.com/archives/52-iPhone-icon-test-generator.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/52-iPhone-icon-test-generator.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=52</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=52</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    I just came across &lt;a href=&quot;http://vjarmy.com/archives/2008/01/howto_iphone_webclip_icons.php&quot;&gt;this neat trick&lt;/a&gt; for providing custom icons (think favicon.ico, but with a reasonable size, better colour and a proper file format) for web pages for iPhone/iPod touch users. There seemed to be some debate over what exactly the native size is, so &lt;a href=&quot;http://www.synchromedia.co.uk/iphoneicon.php&quot;&gt;I built a test page&lt;/a&gt; to test it. The full-size icon image is also displayed on the page, but that&#039;s only there to show what the phone is starting with.&lt;br /&gt;
After twiddling with this test for a while, I came to the conclusion that there isn&#039;t a native size - it&#039;s somewhere between 59x59 and 60x60 - though 60x60 is about as close as you can get. This lack of native size is interesting, as it implies that the iPhone UI is using resolution independent rendering, which we know OS X can do.&lt;br /&gt;
Bigger sizes do scale more smoothly, but they&#039;re a waste of bandwidth and mean that you lose control of the exact appearance - photographic icons will look very nice, but anything involving single pixels lines will probably suffer badly. If you&#039;re a pixel geek that doesn&#039;t like your images twiddled with and you&#039;ve painstakingly created your icon in Photoshop, you &lt;strong&gt;need&lt;/strong&gt; to know the native size. If anyone finds a perfect image size (which may well not be square), please leave a comment. 
    </content:encoded>

    <pubDate>Fri, 15 Feb 2008 16:15:31 +0000</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/52-guid.html</guid>
    
</item>
<item>
    <title>SunSpider Benchmarks: WebKit Rocks</title>
    <link>http://marcus.bointon.com/archives/50-SunSpider-Benchmarks-WebKit-Rocks.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/50-SunSpider-Benchmarks-WebKit-Rocks.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=50</wfw:comment>

    <slash:comments>11</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=50</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    The WebKit guys have put together a &lt;a href=&quot;http://webkit.org/blog/152/announcing-sunspider-09/&quot;&gt;new Javascript benchmark&lt;/a&gt; under the name &quot;&lt;a href=&quot;http://webkit.org/perf/sunspider-0.9/sunspider.html&quot;&gt;SunSpider&lt;/a&gt;&quot;. It&#039;s intended to go further than simple benchmarks like &lt;a href=&quot;http://celtickane.com/webdesign/jsspeed2007.php&quot;&gt;Celtic Kane&#039;s&lt;/a&gt; and try to emulate real-world tasks. Safari/WebKit has been getting pretty quick on these benchmarks anyway, but this new one really shows its strengths. There are various comments about people&#039;s results in the comments for that post, but no compilation for easy comparison, so I&#039;ve put one together.&lt;br /&gt;
&lt;strong&gt;Updated: added Webkit Win and Opera 9.5b Win&lt;/strong&gt;&lt;br /&gt;
&lt;strong&gt;Updated: Failed to run completely on Opera 9.5b Mac&lt;/strong&gt;&lt;br /&gt;
&lt;strong&gt;Updated: Some stats for Opera 9.5b Mac and IE6&lt;/strong&gt;&lt;br /&gt;
&lt;strong&gt;Updated March 18th: Added Safari 3.1, FF3b4, IE8&lt;/strong&gt;&lt;br /&gt;
&lt;br /&gt;
 &lt;br /&gt;&lt;a href=&quot;http://marcus.bointon.com/archives/50-SunSpider-Benchmarks-WebKit-Rocks.html#extended&quot;&gt;Continue reading &quot;SunSpider Benchmarks: WebKit Rocks&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Wed, 19 Dec 2007 11:58:56 +0000</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/50-guid.html</guid>
    <category>benchmark</category>
<category>firefox</category>
<category>internet explorer</category>
<category>javascript</category>
<category>opera</category>
<category>safari</category>

</item>
<item>
    <title>The Email Standards Project</title>
    <link>http://marcus.bointon.com/archives/49-The-Email-Standards-Project.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/49-The-Email-Standards-Project.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=49</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=49</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    The &lt;a href=&quot;http://www.email-standards.org/&quot;&gt;Email Standards Project&lt;/a&gt; is a worthy effort to try to get email clients to handle HTML email in a consistent way. Many already do pretty well, but there are some big exceptions: Outlook 2007 (with its ancient Word rendering engine), GMail, .Mac, Hotmail and others. Many are opposed to the whole idea of HTML email, but often their resentment is based on the fact that historically email client support has been so bad that they&#039;ve had very poor experiences. Worse is that some senders (not us!) send HTML-only messages, which is certainly something that will drive a &lt;a href=&quot;http://www.mutt.org/&quot;&gt;Mutt&lt;/a&gt; user potty. &lt;a href=&quot;http://www.smartmessages.net/&quot;&gt;Smartmessages&lt;/a&gt; supports sending in plain, html and mixed formats (settable by each individual subscriber), and we ensure that our users get a clean, reliable platform for delivering their creations, so we try to work around the deficiencies of things like MS Exchange.&lt;br /&gt;
&lt;br /&gt;
Generally the poor support in big-name clients has led to a need to develop HTML for email for very much the lowest common denominator, which for the most part means no CSS (unless you&#039;re prepared to tiptoe through the minefields of using it), no images, no scripts, no forms, no attachments. Too many designers think of email as being just like the web, but it&#039;s not - the vast majority of web pages will simply not work as email. These days the only effective way of designing for email is to start out with classic HTML 4.0 with no CSS or images and make your message look good using only type, white space and colour, because this is probably all that 90% (yes, really that much) of your recipients are going to see. You can then sprinkle a few images in for enhancement, but you should have no text in images that is not shown as text. With the advent of Outlook 2007&#039;s big step backwards, it&#039;s no longer possible to use background images, so you can&#039;t have text over images at all. You also can&#039;t rely on alt attributes as image fallbacks, as some big clients don&#039;t display the alt text if images are being suppressed as an anti-spam measure.&lt;br /&gt;
&lt;br /&gt;
Many designers get very uppity about this kind of thing as it means that their palette of options is severely constrained, however, it should really be regarded as a challenge. It&#039;s not too hard to make stuff look good with heavy use of images (see &lt;a href=&quot;http://www.csszengarden.com/&quot;&gt;CSS Zen Garden&lt;/a&gt; for gorgeous examples), but producing stuff that looks good with no images or CSS (or more to the point to still look good when those parts have been ripped out) takes a great deal of skill, experience and appreciation of the medium.&lt;br /&gt;
&lt;br /&gt;
Any effort to try and raise the bar gets our support, so props to the Email Standards Project and to &lt;a href=&quot;http://www.freshview.com/&quot;&gt;Freshview&lt;/a&gt; for starting it. 
    </content:encoded>

    <pubDate>Fri, 07 Dec 2007 10:02:17 +0000</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/49-guid.html</guid>
    
</item>
<item>
    <title>123 Strikes Again</title>
    <link>http://marcus.bointon.com/archives/48-123-Strikes-Again.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/48-123-Strikes-Again.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=48</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=48</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    You may have noticed that some of our sites have not been responding for the last few days. This is because &lt;a href=&quot;http://www.123-reg.co.uk/&quot; &gt;123-reg.co.uk&lt;/a&gt; had a name server outage. They didn&#039;t tell anybody or apologise at all, they just decided that several thousand people could do without their sites for a couple of days. People are generally pretty upset about it - just check out &lt;a href=&quot;http://www.iross.net/blog/2007/11/17/123reg-outage/&quot; &gt;these&lt;/a&gt; &lt;a href=&quot;http://www.tamba2.org.uk/T2/2006/02/24/123-reg-bunch-of-muppets/&quot; &gt;damning&lt;/a&gt; &lt;a href=&quot;http://blogs.cnet.com/8301-13505_1-9819551-16.html&quot; &gt;blog&lt;/a&gt; &lt;a href=&quot;http://digitalconsumption.com/forum/602-123-Reg-DNS-Domain-problems&quot; &gt;entries&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
123 have always been pretty useless, but to date I&#039;ve not found anyone offering a decent professional service that also covered .co.uk domains. 123&#039;s big feature is that they are extremely cheap, unfortunately in every sense. This low price means that many of our customers have registered domains on there that we have ended up managing, so we have inherited their choice of registrar and default DNS host.&lt;br /&gt;
123 have NEVER responded to my requests for support, and I&#039;ve reported major problems with their web interface many times - despite their takeover by pipex, their web interface has not changed at all (though the shiny home page has). It&#039;s not possible to log in to more than one account (something we need to do often) as their authentication system is totally useless - it&#039;s also impossible to log out (yes there is a link, but it doesn&#039;t actually do anything)! At least there are Firefox plugins to work around their ineptitude.&lt;br /&gt;
&lt;br /&gt;
When transferring domains to 123, it&#039;s not possible to set up the DNS before the transfer has completed (or for them to simply retain existing name server settings - they always reset them to theirs), so it&#039;s impossible to transfer a domain to them without downtime and exposure of a nasty parking page on your domain.&lt;br /&gt;
&lt;br /&gt;
Their &quot;managed&quot; hosting service is nothing of the sort. Steer well clear. I &lt;a href=&quot;http://marcus.bointon.com/archives/30-Worlds-worst-Managed-ISP-123-reg.html&quot;&gt;blogged about that&lt;/a&gt; quite a while ago.&lt;br /&gt;
&lt;br /&gt;
All this adds up to something that is a lot less than professional. So from now on we&#039;ll be hosting our domains elsewhere, and suggesting that all our customers do the same.&lt;br /&gt;
&lt;br /&gt;
I&#039;m very happy to see that &lt;a href=&quot;http://www.gandi.net/&quot;&gt;one of the better registrars&lt;/a&gt; I&#039;ve used has finally got .co.uk accreditation. &lt;br /&gt;
They have a pretty and functional web interface, full access to zone files (if you want it), and they&#039;ve answered every support request within a couple of hours (and with a certain Gallic charm). I&#039;ve also had good experiences with &lt;a href=&quot;http://www.enomcentral.com/&quot;&gt;enom.com&lt;/a&gt;, though while they are relatively expensive for uk domains, they have a UK support line that&#039;s not premium rate and is actually staffed by people who can do something about your request! The aforementioned blog post mentions &lt;a href=&quot;http://www.everydns.net/&quot; &gt;Everydns&lt;/a&gt;, which looks like something to bear in mind if price is a real issue. 
    </content:encoded>

    <pubDate>Mon, 19 Nov 2007 09:20:25 +0000</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/48-guid.html</guid>
    
</item>
<item>
    <title>Google Carbon Footprint app launch</title>
    <link>http://marcus.bointon.com/archives/47-Google-Carbon-Footprint-app-launch.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/47-Google-Carbon-Footprint-app-launch.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=47</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=47</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    Over the last year I&#039;ve been involved with the guys at &lt;a href=&quot;http://dgen.net/&quot; &gt;d::gen&lt;/a&gt;. d::gen have put together the &lt;a href=&quot;http://blog.co2.dgen.net/&quot; &gt;AMEE&lt;/a&gt; (Avoiding Mass Extinction Engine) Carbon Calculator, which has since been chosen by DEFRA as the official carbon calculator for the UK, and provides back end for the &lt;a href=&quot;http://actonco2.direct.gov.uk/index.html&quot; &gt;ActOnCO2 site&lt;/a&gt; as well as providing a public repository of official carbon emissions data.&lt;br /&gt;
Today marks &lt;a href=&quot;http://blog.co2.dgen.net/?p=42&quot; &gt;the launch&lt;/a&gt; of the next big thing in AMEE&#039;s short history: &lt;a href=&quot;http://www.google.co.uk/carbonfootprint/&quot; &gt;Google&#039;s Carbon Footprint&lt;/a&gt; application, which is available as a gadget on Google&#039;s UK &lt;a href=&quot;http://www.google.co.uk/ig&quot; &gt;iGoogle&lt;/a&gt; home page.&lt;br /&gt;
The app was developed by &lt;a href=&quot;http://www.avenuea-razorfish.com/&quot; &gt;Avenue A / Razorfish&lt;/a&gt;. My role at d::gen has been to deal with server and application configuration, deployment, hosting and monitoring, database configuration and load testing.&lt;br /&gt;
AMEE continues to grow in flexibility, ability, capacity and content, all while remaining a shining example of the &#039;right way&#039; of running an open-source project.&lt;br /&gt;
Anyway, congratulations d::gen and AMEE, and thanks to Google and Razorfish for using us!&lt;br /&gt;
Now if you&#039;ll excuse me, I have to go and deal with the prospect of being on the receiving end of a link from a Google home page.... 
    </content:encoded>

    <pubDate>Wed, 31 Oct 2007 11:12:46 +0000</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/47-guid.html</guid>
    
</item>
<item>
    <title>Microsoft wants more spam</title>
    <link>http://marcus.bointon.com/archives/46-Microsoft-wants-more-spam.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/46-Microsoft-wants-more-spam.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=46</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=46</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    If you read some of the &lt;a href=&quot;http://postmaster.hotmail.com/&quot; &gt;postmaster docs&lt;/a&gt; on Hotmail/Windows Live, you might get the impression that Microsoft takes the processing of unwanted email seriously. However, this seems to be untrue. &lt;br /&gt;&lt;a href=&quot;http://marcus.bointon.com/archives/46-Microsoft-wants-more-spam.html#extended&quot;&gt;Continue reading &quot;Microsoft wants more spam&quot;&lt;/a&gt;
    </content:encoded>

    <pubDate>Tue, 30 Oct 2007 09:45:28 +0000</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/46-guid.html</guid>
    
</item>
<item>
    <title>Have I told you today how much Mac Minis rock as servers?</title>
    <link>http://marcus.bointon.com/archives/45-Have-I-told-you-today-how-much-Mac-Minis-rock-as-servers.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/45-Have-I-told-you-today-how-much-Mac-Minis-rock-as-servers.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=45</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=45</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    We&#039;re using a cluster of Mac Minis for hosting. They&#039;re running Ubuntu very nicely. I&#039;ve gone on about them before (maybe not on here), but we just got a couple of new ones that use Core2 Duo rather than the older Core Duo models, and wow are they good. How good? Well, for CPU intensive stuff, we&#039;re seeing (per core) over double the performance of our Dell PowerEdge 1850 which sports two dual-core 3.0GHz Xeons (and these are the slower 1.8GHz models!). That&#039;s not bad for &lt;20% of the cost to buy. They are unfeasibly small and really quite cute, plus they only pull about 120W (peak - 65W at idle!), so hosting them is dirt cheap (It&#039;ll cost you less than empty rack space - just ask &lt;a href=&quot;http://mythic-beasts.com/&quot; &gt;Mythic Beasts&lt;/a&gt; whom we highly recommend, and they have minor niggles of the platform under control). Sure the disks are not too fast, and there&#039;s no internal RAID, but who needs RAID when you can have RAIC instead? 
    </content:encoded>

    <pubDate>Fri, 05 Oct 2007 18:12:38 +0100</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/45-guid.html</guid>
    
</item>
<item>
    <title>Munin per-plugin timeouts</title>
    <link>http://marcus.bointon.com/archives/44-Munin-per-plugin-timeouts.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/44-Munin-per-plugin-timeouts.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=44</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=44</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    I had a munin plugin that suddenly stopped reporting, and in the munin-node log there were lots of errors like this:&lt;br /&gt;
&lt;br /&gt;
&lt;tt&gt;2007/06/27-06:50:26 Plugin timeout: myplugin : Interrupted system call&lt;/tt&gt;&lt;br /&gt;
&lt;br /&gt;
So it looks like the plugin is taking too long, but how to extend the timeout? Seems &lt;a href=&quot;http://sourceforge.net/mailarchive/forum.php?thread_name=200705261901.46190.michael.renner%40gmx.de&amp;forum_name=munin-users&quot; &gt;I&#039;m not alone&lt;/a&gt; in wondering this. So I had a rummage in the source of munin-node, and it seems to want a &#039;timeout&#039; parameter in its config. So I added a simple &lt;tt&gt;timeout 60&lt;/tt&gt; to munin-node.conf and it worked! However, that&#039;s a global setting rather than a per-plugin timeout, so I took a flying guess at putting the same directive in my plugin spec in /etc/munin/plugin-conf.d/munin-node like this:&lt;br /&gt;
&lt;br /&gt;
&lt;tt&gt;[myplugin]&lt;br /&gt;
timeout 60&lt;br /&gt;
user root&lt;/tt&gt;&lt;br /&gt;
&lt;br /&gt;
And that worked too! 
    </content:encoded>

    <pubDate>Wed, 27 Jun 2007 22:06:01 +0100</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/44-guid.html</guid>
    
</item>
<item>
    <title>Hackday</title>
    <link>http://marcus.bointon.com/archives/43-Hackday.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/43-Hackday.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=43</wfw:comment>

    <slash:comments>2</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=43</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    Well, Hackday was certainly an experience - the lightning strike and the roof vents opening was really quite disturbing! The lack of WiFi early on was a real pain as it made it very hard to connect projects, people and skills, so I suspect that most hacks were done by people who had arranged something beforehand, or who happened to meet at the bus stop.&lt;br /&gt;
&lt;br /&gt;
Anyway, I got involved, along with Rob, Andy, Edward and James in something that turned into &lt;a href=&quot;http://www.fruitr.co.uk/&quot; &gt;Fruitr&lt;/a&gt; - the search engine for unimaginative chefs. The basic idea was: take a picture of a piece of fruit, submit it to our site, and you&#039;re rewarded with recipes that use that fruit. Rob and James worked on using a C++ image recognition library (not sure which one) from a Pylons Python app, which was driven by statistical matching against images from Flickr that are tagged with &#039;fruitr&#039;. Edward provided API access to his database of recipes courtesy of his site &lt;a href=&quot;http://www.bigmunch.com/&quot; &gt;BigMunch&lt;/a&gt;, and I developed the testing web interface (later rolled into the main python app), and the email (in and out) interface. Andy had an abortive attempt at creating a J2ME app to talk to it, but was hampered by BlueTooth interference, buggy phones and poor mobile reception. We really had it all running by about midnight, and just a final polish was needed in the morning.&lt;br /&gt;
&lt;br /&gt;
I spent much of Sunday looking at APIs to use with &lt;a href=&quot;http://blog.co2.dgen.net/&quot; &gt;AMEE&lt;/a&gt;, without much luck or inspiration, then messed about creating an &lt;a href=&quot;http://en.wikipedia.org/wiki/Quartz_Composer&quot; &gt;Apple Quartz Composer&lt;/a&gt; file that can be used as a screen saver. It grabs images tagged with &#039;hackdaylondon&#039; from Flickr and presents them on faces of a bunch of rotating cubes. One face of the cubes displays live video (assuming you&#039;re on a Mac Book? or similar which has a camera). There is also a spectrum-driven audio bar display, and a rotating Hack Day logo, which is also moved by sound. You can &lt;a href=&quot;http://www.synchromedia.co.uk/hackday/HackSaver.qtz&quot; &gt;download the Quartz composer file&lt;/a&gt;.&lt;br /&gt;
&lt;br /&gt;
I did the presentations for both hacks. For the Fruitr one I just ran out of time - sweaty fingers and trackpads really don&#039;t mix. Because &lt;a href=&quot;http://www.flickr.com/photos/tim_hawkins4/564764975/&quot;  title=&quot;Flickr pic of my demo&quot;&gt;demoing a screen saver&lt;/a&gt; is not too hard, I dressed it up as a load of presentation faux-pas. I hope nobody thought it was for real!&lt;br /&gt;
&lt;br /&gt;
Generally it was all pretty good fun, and it certainly had an excellent atmosphere, not to mention the endless supply of chocolate. Playing doubles tennis on the Wii at 2am was another highlight, along with the &quot;non-showing&quot; of Doctor Who...&lt;br /&gt;
&lt;br /&gt;
I needed to leave before prizes and the Rumble Strips gig, so I missed out on that bit, and at the end of it all, I completely failed to grab a pink bean bag for Z. Oh well, I&#039;ll be back next year! 
    </content:encoded>

    <pubDate>Mon, 18 Jun 2007 21:14:57 +0100</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/43-guid.html</guid>
    
</item>
<item>
    <title>I'm going to hackday!</title>
    <link>http://marcus.bointon.com/archives/40-Im-going-to-hackday!.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/40-Im-going-to-hackday!.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=40</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=40</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    &lt;p&gt;I got my invite for &lt;a href=&quot;http://hackday.org/&quot; &gt;hackday&lt;/a&gt; today.&lt;br /&gt;&lt;br /&gt;
&lt;a href=&quot;http://www.hackday.org&quot; style=&quot;border: none; padding: 0px; margin: 0px&quot;&gt;&lt;img src=&quot;http://l.yimg.com/us.yimg.com/i/us/ydn/hackday/hack_day_pattern_four.gif&quot; alt=&quot;Hack Day: London, June 16/17 2007&quot; width=&quot;180&quot; height=&quot;105&quot; style=&quot;border: none; margin: 0; padding: 0;&quot;&gt;&lt;/a&gt;&lt;br /&gt;&lt;br /&gt;
Anyone else coming?&lt;/p&gt; 
    </content:encoded>

    <pubDate>Sat, 02 Jun 2007 02:00:56 +0100</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/40-guid.html</guid>
    
</item>
<item>
    <title>3Ware RAID rebuilding</title>
    <link>http://marcus.bointon.com/archives/37-3Ware-RAID-rebuilding.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/37-3Ware-RAID-rebuilding.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=37</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=37</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    I&#039;ve had the dubious honour of seeing some RAID failures and rebuilds lately. It&#039;s the kind of thing that doesn&#039;t get written about in the manuals very well, in particular what your RAID will report when it&#039;s having trouble. So, here are a couple of examples from a 3Ware RAID controller using tw_cli software. This is what &lt;tt&gt;tw_cli /c4 show&lt;/tt&gt; displays when we have a dead drive:&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;&lt;br /&gt;
Unit  UnitType  Status         %RCmpl  %V/I/M  Stripe  Size(GB)  Cache  AVrfy&lt;br /&gt;
------------------------------------------------------------------------------&lt;br /&gt;
u0    RAID-1    DEGRADED       -       -       -       149.05    ON     -      &lt;br /&gt;
&lt;br /&gt;
Port   Status           Unit   Size        Blocks        Serial&lt;br /&gt;
---------------------------------------------------------------&lt;br /&gt;
p0     OK               u0     149.05 GB   312581808     G2109NHG            &lt;br /&gt;
p1     DEGRADED         u0     149.05 GB   312581808     G20X1BWG            &lt;br /&gt;
&lt;/pre&gt;&lt;br /&gt;
&lt;br /&gt;
So, we swap the drive, and it looks like this while rebuilding:&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;&lt;br /&gt;
Unit  UnitType  Status         %RCmpl  %V/I/M  Stripe  Size(GB)  Cache  AVrfy&lt;br /&gt;
------------------------------------------------------------------------------&lt;br /&gt;
u0    RAID-1    REBUILDING     89      -       -       149.05    ON     -&lt;br /&gt;
&lt;br /&gt;
Port   Status           Unit   Size        Blocks        Serial&lt;br /&gt;
---------------------------------------------------------------&lt;br /&gt;
p0     OK               u0     149.05 GB   312581808     G2109NHG&lt;br /&gt;
p1     DEGRADED         u0     149.05 GB   312581808     G209Y0HG&lt;br /&gt;
&lt;/pre&gt;&lt;br /&gt;
&lt;br /&gt;
and after a little while...&lt;br /&gt;
&lt;br /&gt;
&lt;pre&gt;&lt;br /&gt;
Unit  UnitType  Status         %RCmpl  %V/I/M  Stripe  Size(GB)  Cache  AVrfy&lt;br /&gt;
------------------------------------------------------------------------------&lt;br /&gt;
u0    RAID-1    OK             -       -       -       149.05    ON     -&lt;br /&gt;
&lt;br /&gt;
Port   Status           Unit   Size        Blocks        Serial&lt;br /&gt;
---------------------------------------------------------------&lt;br /&gt;
p0     OK               u0     149.05 GB   312581808     G2109NHG&lt;br /&gt;
p1     OK               u0     149.05 GB   312581808     G209Y0HG&lt;br /&gt;
&lt;/pre&gt;&lt;br /&gt;
&lt;br /&gt;
There are plenty of obvious strings to match in this output (though there are many other reports available), so it&#039;s a reasonable thing to base a monitoring script on.&lt;br /&gt;
&lt;br /&gt;
It&#039;s nice to see it actually work, and makes me extremely grateful that I bothered getting RAID n the first place. This would be a much unhappier post if I hadn&#039;t. 
    </content:encoded>

    <pubDate>Mon, 14 May 2007 23:09:35 +0100</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/37-guid.html</guid>
    
</item>
<item>
    <title>Dell RAID firmware and lockfile on Ubuntu</title>
    <link>http://marcus.bointon.com/archives/31-Dell-RAID-firmware-and-lockfile-on-Ubuntu.html</link>
            <category>Techie</category>
    
    <comments>http://marcus.bointon.com/archives/31-Dell-RAID-firmware-and-lockfile-on-Ubuntu.html#comments</comments>
    <wfw:comment>http://marcus.bointon.com/wfwcomment.php?cid=31</wfw:comment>

    <slash:comments>0</slash:comments>
    <wfw:commentRss>http://marcus.bointon.com/rss.php?version=2.0&amp;type=comments&amp;cid=31</wfw:commentRss>
    

    <author>marcus@bointon.com (Marcus Bointon)</author>
    <content:encoded>
    Ian P. Christian &lt;a href=&quot;http://lists.us.dell.com/pipermail/linux-poweredge/2005-December/023752.html&quot; &gt;ran into this problem&lt;/a&gt; a while ago:&lt;br /&gt;
&lt;blockquote&gt;On a seperate note, anyone know how to upgrade firmware using Dell&#039;s software &lt;br /&gt;
on a non-RH system?&lt;br /&gt;
&lt;br /&gt;
# ./RAID_FRMW_LX_R107404.BIN&lt;br /&gt;
/root&lt;br /&gt;
which: no lockfile in &lt;br /&gt;
(/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/opt/bin:/usr/i686-pc-linux-gnu/gcc-bin/3.3.6)&lt;br /&gt;
spsetup.sh: Cannot find utilities on the system to execute package.&lt;br /&gt;
Make sure the following utilities are in the path: sed lockfile tail rm mkdir &lt;br /&gt;
chmod ls basename&lt;br /&gt;
/root&lt;br /&gt;
&lt;br /&gt;
&#039;lockfile&#039; is missing - whatever that is!&lt;br /&gt;
&lt;/blockquote&gt;&lt;br /&gt;
&lt;br /&gt;
Lockfile just doesn&#039;t seem to exist outside of RedHat (e.g. lockfile-progs on Debian doesn&#039;t include it), however, you can of course find it on a RedHat system, and I happen to have one handy. I just copied the binary to my Ubuntu installation, where it appeared to run just fine, and allowed the firmware updaters to run ok. Thought someone might like to know. 
    </content:encoded>

    <pubDate>Sat, 28 Apr 2007 21:42:53 +0100</pubDate>
    <guid isPermaLink="false">http://marcus.bointon.com/archives/31-guid.html</guid>
    
</item>

</channel>
</rss>