Select Page

Spotlaser

Spotlight is the supposedly all-singing-and-dancing desktop search tool from Apple, it is pretty neat and supports a ton of useful things relating to meta data and so forth, I’ve blogged about it before showing how you can use it on the command line to gain access to these functions.
On the GUI side of things it’s a bit crap, you have the top-right spotlight box that you can type into and it features a pretty dismal command language for doing power searches. You can also use Finders tool to do finds using Spotlight, it’s OK I guess but not kewl enough to convince me to actually integrate Spotlight into my daily life.
I toyed with writing a GUI frontend to Applescript this last weekend and got pretty far, you could restrict searches, do AND or OR searches, date matches and the like, and it would open the results in the Finder find interface but coding Applescript GUI’s doesn’t really excite me so I didn’t go further with it.
Today over at FreeMacWare.com I saw mention of Spotlaser and it’s pretty sweet, its a full frontend to all the features of Spotlight and using it you can really see what is possible, hopefully Apple will soon introduce their own advanced front-end to Spotlight, till then, Spotlaser is the way to go.


Above is a screenshot of it in action, its donationware, so grab a copy now.

New iMac

I mentioned the other day in the comments of my Ubuntu post that my girlfriend decided to get herself a iMac, this weekend we went to pick it up from the Apple store in Regents Street.
After the traumatising walk through soho carrying a computer in my arms when we got it home all seemed fine to begin with, but then when it came time to test out the iSight the thing was dead. It produced either pure white or pure green but nothing else.
I was really dreading taking it back as it would mean she would be without a computer for a while and just general be a total pain, I searched the Apple support forums and they got me nowhere but then I searched the forums and came across someone who had the same problem, they unplugged their iMac from the wall for 30 seconds and that fixed it, I did the same and voila, one happy mac.
So not too bad, but still a bit infuriating.


While we were there I also picked up a iPod Nano for Emma, I’ve not really looked at these in detail before and must say it’s a very sexy bit of kit. Though comparing it to my 3 year old iPod I have doubts about the build quality, for example the plug where the power/doc goes in doesn’t nicely click into place it’s more a matter of forcing it in, not sure if that is normal but it sure is annoying.

FreeBSD Stability

I’m in the middle of decomissioning some old sites and thought I’d post some info about our FreeBSD 4.x based firewalls that we were running.
Barry and Neil put these together when they were still with iTouch, they are FreeBSD machines running ipfw, modified natd, IPSec and jails for nameservers using bind. They’ve proven incredibly reliable more reliable than anything I’ve every seen before, first some uptimes:

4.3-RELEASE-p28 FreeBSD 4.3-RELEASE-p28 #0
8:56AM up 1175 days, 14:25, 1 user, load averages: 0.01, 0.00, 0.00 4.3-RELEASE FreeBSD 4.3-RELEASE #3: Thu Aug 9 08:24:10 SAST 2001 8:55AM up 1353 days, 13:07, 1 user, load averages: 0.07, 0.03, 0.00 4.3-RELEASE FreeBSD 4.3-RELEASE #3: Thu Aug 9 08:24:10 SAST 2001 8:57AM up 1636 days, 12:16, 2 users, load averages: 0.01, 0.02, 0.00

That last machine was put in the 2nd day I arrived in the UK almost 4.5 years ago now. There has been a few security issues since these were put in, the biggest were Bind issues and a IPSec issue, but none of them really huge deals for us due to the nature of these issues.
Some packet counts through their diverts:

11000 14873464727  9086343964578 divert 8668 ip from any to any via sf0
11010 2694675129 2230790516204 divert 8668 ip from any to any via sf2
11020 21332945704 16515209189995 divert 8668 ip from any to any via sf1
11030 2190579388 1838075424554 divert 8668 ip from any to any via em1
11040 31142270005 26337236597684 divert 8668 ip from any to any via sf3
11000 12363062208 6728197633745 divert 8668 ip from any to any via fxp0 11050 13585672383 7625773331834 divert 8668 ip from any to any via sf0 11075 1672241479 943217267415 divert 8668 ip from any to any via sf1 11000 9709855806 3616673887622 divert 8668 ip from any to any via fxp0 11010 15438460240 7026578427847 divert 8668 ip from any to any in recv sf0 11015 18623997883 6347362524481 divert 8668 ip from any to any out xmit sf0 11020 7574307452 2981257820300 divert 8668 ip from any to any in recv sf1 11025 6957613786 2361008898017 divert 8668 ip from any to any out xmit sf1 11030 5520959014 1551914815579 divert 8668 ip from any to any in recv sf2 11035 8724539029 2097991945468 divert 8668 ip from any to any out xmit sf2 11040 2988122935 604858451646 divert 8668 ip from any to any in recv sf3 11045 3930006137 632095496483 divert 8668 ip from any to any out xmit sf3 11050 3842161713 3177937890519 divert 8668 ip from any to any in recv fxp1 11055 4106903810 3282379599303 divert 8668 ip from any to any out xmit fxp1

These aren’t the bussiest machines by far, but they moved quite a bit of data, keep in mind these counters were probably reset quite a few times over the time to aid in debugging problems. One interface in the top bunch has done 23 TB.
I don’t really like these long uptime machines, they are a constant cause of worry for me, you dont know if all the configs were saved, you dont know if they’ll ever come up after a reboot etc, once you’ve gone over 500 days I think you’re pretty much at a point where rebooting machines becomes a bit of a worry to me, as these are/were firewalls the problem is much worse since the impact of them not booting or configs going missing would be massive, arranging downtime though isn’t always easy either, but I think worth the effort in hind sight.

Apache Vulnerability

This morning came news of a remote exploitable vulnerability in Apache mod_rewrite, the exploit is pretty difficult and requires weird setups on your side, but you should be upgrading all your kit.
More info at Secunia

A vulnerability has been reported in Apache HTTP Server, which potentially can be exploited by malicious people to compromise a vulnerable system.
The vulnerability is caused by a off-by-one error in mod_rewrite and can be exploited to cause a one-byte buffer overflow.
Successful exploitation may crash the web server process or allow execution of arbitrary code.

Ubuntu is great.

So world and dog is nagging on about Ubuntu, how great it is and how they are switching from <insert anything on the planet> to Ubuntu.
I happened to have a spare 300gig drive lying around so I gave 6.06 a go. My machine is over 2 years old, its practically from the ark, you’d expect things to Just Work.
After install, screen resolution is absolutely dismal, slow refresh rate and random crashes while trying to set to a better resolutoin. Already here you’ve lost a large chunk of users.
Anyway, so I go off looking on Google using Firefox, it opens up with the familiar look of Firefox complete with Mycroft search box, except the search box does nothing by default, you can type into it, hit enter but nothing happens, by default it doesn’t search, have to go fiddle with it to get it working.
Came across a post, that points to another post that points to Wiki for getting ATI cards going. I basically had to do this in a terminal:

sudo apt-get update
sudo apt-get install linux-restricted-modules-$(uname -r)
sudo apt-get install xorg-driver-fglrx
sudo depmod -a
sudo aticonfig --initial
sudo aticonfig --overlay-type=Xv

and then reboot.
Yes, this distro is going places if it can’t even support a crap old ATI Radeon card out of the box and require new users to do stuff in terminals just to get rid of a headache inducing low refresh rate.
Get Real, your grandmother is not going to do this. Give her a Mac and the thing just works.