• The Author - Bart Busschots

  
  • About
  • On Twitter
  • On LinkedIn
  • On Flickr
  
  

• Contents

  • About Bart
  • Podcasting
  • Photography
  
  

• Search

  
  

• Recently Blog Posts

  • Photo of the Week 119 & 120 – Two New Muses
  • Photo of the Week 118 – No. 186 Steaming West
  • Photo of the Week 116 & 117 – Big Summer Skies
  • Some Thoughts on Composition
  • Review of Money3 by Jumsoft

• Blog Categories

  • 42
  • Computers
    • Linux, GNU & FOSS
    • Mac
    • Security
    • Software Development
      • Databases
      • Java
      • Web Development
    • The Internet
    • Windows
  • Harry Potter
  • Local History
  • Photography
    • Photo of the Week
  • Polemics, Morality & Politics
  • Science & Astronomy
    • Observers Log
  • Suggested Reading
  
  

• RSS Feeds

  • All Blog Posts
  • Only Computer Related Posts
  • Only Photography Related Posts
  • Photo of the Week
  
  

• Links

  • Daring Fireball - A straight-talking Apple blog
  • Des Traynor - Blog by fellow NUIM PhD Student Des Traynor
  • Planet MiNDS> - Agregation of blogs by members of the NUI Maynooth IT Society
  • Security Now - A must for all computer power users
  • The NosillaCast - A tech geek podcast with an ever-so-slight Macintosh bias
  • Worse Than Failure - Curious perversions in IT – a blog all programmers should read
  • XKCD - A webcomic just for nerds

• Creative Commons

  The posts on this blog are licensed under Creative Commons Attribution, Noncommercial, No Derivative Works 3.0 License

  

I’ve lost count of the amount of Twitter clients I’ve tried, and none are perfect. There may well be a client out there that does everything I need exactly how I want it to, but I’ve yet to find it. In recent times I’ve settled on Syrinx because it ticks most of the boxes, but it’s not perfect. I haven’t been actively search for a new client, but I’ve still been keeping my ears open. Hence, when Tim Verpoorten talked about Itsy on a recent episode of the Mac Review Cast I decided to give it a go.

Read more

I recently moved to a new machine (a hand-me-down G5 20″ iMac), and when it came to installing my new apps I decided I’d had enough of Adobe AIR and the whole idea of web apps pretending (poorly) to be native apps. I like OS X, and I want the full power of OS X in my apps. I also like how OS X apps all look and work similarly to each other. You just don’t get that with AIR apps like Twhirl (which had been my Twitter client up to that point). Not long before I got my new Mac listener Scott had contributed a short review of Syrinx to the NosillaCast, so I decided to give it a go.

I took and instant liking to the app because it’s a proper OS X app, because it uses the OS X keychain to securely save my password, and because it has Growl support. The fact that it’s free also helps of course! I’ve been using it for a month or so at this stage, and I’m still happy enough with it to keep it as my current client on all three of my Macs. It’s also under very active development at the moment with updates coming out regularly, so I have high hopes for this app’s future.

Read more

A few years ago I did a similar tutorial for installing mod_jk on OS X 10.4 Tiger, but yesterday I discovered that those instructions do not work for Leopard. It took my quite a bit of googling and trial an error, but I’ve found a solution that works, which I’m going to share here. This solution is, in my opinion, a best practices solution, and does not involve any changes to your core apache configuration file (httpd.conf). These instructions are for the default install of Apache 2.2 that comes pre-installed on OS X 10.5 Leopard. I can verify that these instructions work for Tomcat 5.0.30, but I would be 99% sure they should also work un-changed for Tomcat 5.5.X and Tomcat 6.0.X.

Read more

NOTE: Although this post references experiences I have had in work, the opinions expressed here are mine and mine alone.

If you follow me on Twitter you may have noticed my anti-RHEL (RedHat Enterprise Linux) outbursts today. I could keep twittering to try make my point, but sometimes 140 characters is just not enough, so I figured I’d blog about it instead and then tweet out the link to the blog post when I’m done.

In work we run two kinds of Linux servers, RedHat Enterprise Linux, and CentOS. We pay for RedHat, we don’t pay for CentOS (because it’s free). CentOS is based off the RedHat code base, but has some of the fancy stuff stripped out. Clearly, you would expect RHEL to give you the better experience since it has more features and you pay for support. Unfortunately, in my experience that’s just not how things are shaping up. CentOS has been completely problem and stress free (as well as financially free), while RHEL has not been such a smooth ride. Sure, most of the time it works just fine, but it definitely generates more stress for me than CentOS does, and that’s paid-for stress!

Read more

As some of you probably know, I’m a long-time Thunderbird user, from back when it still had the cool blue Phoenix logo, and when what we now call FireFox had only just changed from being called Phoenix to FireBird. In other words, from when Mozilla still looked at BOTH their browser AND their mail client as being important products. Since those days I’ve watched in horror as Mozilla first neglected Thunderbird, and then abandoned it. While FireFox has gone from strength-to-strenght, Thunderbird has languished. The project was effectively thrown out of Mozilla and left to fend for itself. It also lost its lead author, and has stagnated. It’s a good mail client, but it’s behind the times. It’s missing simple features like a tabbed interface, and FireFox 3’s new, non-retarded, way of dealing with problem security certs. For all these reasons I was very excited to see the announcement of a beta version of Postbox this week. It’s a fork of Thunderbird being led by Thunderbird’s old lead, so in many ways, it’s a glimpse of where Thunderbird could have been, had it not been neglected by Mozilla. It definitely is a beta, but it’s a glimmer of hope at long-long-last!

Read more

As you can probably guess by the list of previous photos of the week, I’m not really into black & white photography. However, I do dabble occasionally, and particularly enjoy playing with the channel mixer to get more dramatic and contrasty images. This is my favourite black & white conversion so far. This shot of the Moon over the top of the spire of the Gunne Chapel (AKA the College Chapel) on the St. Patrick’s College Campus (AKA NUI Maynooth South Campus) in Maynooth, Ireland. The black & white conversion was done using the channel mixer in the GIMP (a free cross-platform image editor). It was shot during the day, but made more dramatic by turning the blue channel right down to zero so the sky goes black.

on Flickr – Full-Size

• Camera: Nikon D40
• Lens: Nikon DX AFS 55-200mm
• Exposure: 1/250 sec
• Focal Length: 200mm
• Focal Ratio: F22
• ISO: 800
• Camera Mode: Aperture Priority
• Processing: Converted to black & white using the channel mixer in the GIMP

My Myers Briggs personality profile insists that I "prefer economy of effort", you can probably translate that to "is a lazy sod". Because of this I like automating repetitive tasks. It all started when I wanted a quick and easy way to prepare my images for posting to my website. I wanted them resized with my URL and the Creative Commons icon added in, and I wanted to be able to process a whole directory of images in one go. I started by playing around with the GD libs in PHP, but soon realised it would be quicker and easier to use Perl to shell out to the command line tools from Image Magick. At the time I wrote a post on my choice to do this which also contained the initial code. That code has been expanded and evolved since, and now includes functions for rendering nice (in my opinion) borders and titles on my better images. If you want to see examples checkout the Photo of the Week category on this blog..

Technorati Tags: Perl, Image Magick, script, programming, image processing

Read more

This is just a quick guide to getting BibTeX to work in a LaTeX document. This is not meant to be an introduction to BibTeX for someone who's never heard of it, but rather a cheat-sheet for those of us who don't use it quite often enough to remember the details without a little help.

First you need to create and manage your bibliography database (.bib file). You could do this by hand, but if you're on OS X I'd highly recommend BibDesk. Much simpler.

Secondly, you insert citations in the document using the \cite{} command. Each entry in your bibliography database has a separate citation key, you use this key to insert a reference. For example, if my bibliography database contained a reference with a citation key 'Busschots2008' I'd insert a citation to that reference with the command:

Thirdly, you need to include your bibliography in your document. To do this you need to set a style for it, and then include it. If you're not sure what style to use start with plain. Assuming your bibliography database is in a file called Sample.bib, you'd include it with the following code (notice that you don't add .bib to the end of the file name):

Finally, to render the document you now need to run your document through both BibTex and LaTeX in the following order:

1. latex
2. bibtex
3. latex
4. latex

This week it was announced that one of the core protocols that holds the internet together is fundamentally flawed. The problem is not with someone's implementation of the protocol, but with the actual protocol itself. It's hard to over-state just how big a deal this is. At the moment the details of the vulnerability are being kept secret to give the world time to patch, but you can get some technical information from the advisory issued by the US Cert. On Tuesday all the major DNS server vendors released patches at the same time. This is un-heard of, nothing like this has ever happened before in the history of the internet. That alone should bring home just how big this is.

Although the good-guys have successfully kept the details of the flaw secret to date, despite the large numbers of organisations involved, the reality is that the bad guys are frantically trying to figure this out as I type. It's not a matter of if they'll figure it out, but when. The security community have bought us time. That time should not be squandered, but used to protect the internet as a whole, and to protect ourselves.

Internet, Security, DNS, Critical Vulnerability

Read more

I've been recommending FireFox for years now. In fact, I've been using it as my primary browser since it was called FireBird. It has been a more secure and a more feature-rich choice for years. (If you're interested in the security aspects then you might enjoy reading a recent article I wrote for the International Mac Podcast blog comparing Safari and FireFox from a security point of view.) What got me hooked on FireBird was it's plugin architecture. The idea of being able to customise my browser really appealed to me and as FireBird has grown into FireFox the list of available plugins has grown too. No other browser is as expandable as FireFox. If you can think of it, the chances are someone's written a plugin for it!

However, FireFox has long suffered from two major shortcomings, memory leaks you could pilot a large ship through, and a non-native look. FireFox has been chewing up insane amounts of RAM for years, and has always looked like a fish out of water, particularly on OS X. These two problems are both fixed in FireFox 3 and if that was all they'd done I'd be recommending it highly, but they've done much more.

Technorati Tags: internet, browser, FireFox, FireFox 3

Read more

keep looking »