According to that thread, certain models of MacBook Pro (pretty much all models after the “late 2007″, or MacBookPro3,1) can be upgraded to more than their officially supported 4GiB RAM, some models supporting 6GiB, others 8GiB. Not one to blindly trust the first online source I saw, I did a bit more research and it seemed that a number of people had had success upgrading their machines to 6GiB RAM and OWC are even selling 6/8GiB upgrade kits for such machines.

As the price of 4GiB SO-DIMMs is fairly reasonable, I decided to upgrade my “late 2007″ model from 4GiB to 6GiB (the maximum that would work without severe performance degradation). As I was already a little suspicious about the RAM I had installed, I decided to replace the existing pair of 2GiB SO-DIMMs with new 2GiB and 4GiB modules. The price for the pair was just over £130 (~$210), which I thought was pretty reasonable.

Installation was straightforward – remove the battery, unscrew the memory door (using a Philips #0 screwdriver), pop out the existing RAM and replace it.

After booting up, “About This Mac” displayed the following:

In the three weeks since the upgrade the machine has been rock solid, even with over 10GiB RAM allocated (the joys of running several virtual machines on it). Definitely a recommended upgrade.

For a limited time all international subscriptions to the print edition of Linux Journal will be reduced to the low price of $49.50 for 1 year (a savings of over 30% off the regular price) AND upgraded to include a free digital subscription. As a special bonus you will also receive Linux Journal’s System Administration Special Issue free of charge.

I’ve been a Linux Journal subscriber since the late 90s and can recommend it as one of the better general-interest computer publications. To take advantage of the special offer, visit the Linux Journal site. It seems the promo code to take part in this offer is M96INTL.

Update: Fixed the link to the subscription page, courtesy of Mark at Linux Journal. Whoops!

Being out of warranty (it was purchased about 16 months ago – let me not start ranting about batteries that fail after such a short period of light to medium use), I looked around for repair options. Replacement batteries are fairly easy to come by, but the Nano isn’t the easiest piece of hardware to disassemble. Having learned the hard way, I’m really not a big fan of repairing mobile phones and similar devices myself – I always end up snapping a piece of plastic or bending something beyond repair. Taking that into consideration, I decided to look online for someone to do the battery replacement.

Apple themselves will replace the battery for the princely sum of £46.13 (including shipping), which seems just a tad pricey – a new fourth generation 8GB iPod Nano costs only £107. The well-known Juice Your iPod will perform the service for a much more reasonable $32 (excluding shipping), but it seems a little silly to ship an iPod half way around the world to have its battery replaced. I then came across UK iPod Repairs, who’ll do the replacement for a reasonable £30, excluding shipping. I’ve placed an order with them and will be sending them the iPod tomorrow. According to the site, I should get the repaired item back by the middle of next week – expect an update once that’s happened.

Update:Unfortunately the problem wasn’t the battery, it was the logic board. As a replacement would’ve cost in the region of £80, I ended up buying a replacement fourth generation Nano for her (£105).

Andrew Doran has prepared a presentation (PDF) giving a high level overview of changes in 5.0 . Some highlights include:

• Journaling enhancements to FFS (WAPBL)
• Finer-grained locking on SMP systems
• A new kernel module system
• Vastly improved ACPI support
• Many ports using X.Org instead ofXFree86

All in all, this is probably one of the most significant releases in the project’s history – kudos to all involved.

Following the Moleskine-friendly fountain pen recommendations on the 43Folders wiki, last week I ordered a LAMY safari (fine nib) and a bottle of Noodler’s black ink. So far, I’m quite impressed – the safari definitely doesn’t feel like a sub $20 pen and, if it does go missing, it’s cheap enough to replace without me smarting at the cost.

I ordered the LAMY from Cult Pens and the ink from Niche Pens – both orders arrived promptly and I have no hesitation in recommending both sellers. One thing to remember – the safari doesn’t come with a converter to allow for the use of bottled ink so it must be purchased separately.

When I rebooted, I spotted the first problem – GRUB presented me with the kernels from 8.10 (2.6.27.*) but not the 9.04 kernel (2.6.28.*). During the installation I had elected not to overwrite GRUB’s menu.lst, thinking that it would still get updated when the kernel package was configured. Oddly, that didn’t happen. My solution was to edit /boot/grub/menu.lst and add entries for the 9.04 default kernel (doing a dpkg-reconfigure on the kernel package would probably also have fixed it).

Once I had booted the correct kernel, I tackled the second problem – X didn’t work. With 8.10 I had been using the proprietary VIA DRM kernel module, which enabled hardware-accelerated 3D on the 2133′s Chrome9 chipset, but it didn’t work with the updated 9.04 kernel. I moved my /etc/X11/Xorg.conf out of the way and restarted X, which then started correctly with sane defaults (newer releases of X.Org no longer require a configuration file). Rather pleasingly, the OpenChrome driver being used by X.Org started with the correct 1280×768 resolution. The one downside of not using the VIA module is that compiz et al. don’t work – not a big issue for now and one that should be rectified once VIA update their DRM kernel module for 9.04′s kernel. One possible workaround is to boot the most recent kernel from 8.10 (which is still installed), but I haven’t tried that yet.

The third problem, and the most annoying, relates to the 2133′s Broadcom wireless. With 8.10 I had been using ndiswrapper and it worked perfectly. For some reason, as soon as I tried to connect to my home wireless network after upgrading to 9.04, WPA authentication failed (I kept getting prompted for my key and the key I entered was never saved). I then switched to using the Broadcom STA driver, which authenticates successfully, but exhibits a few problems of its own – it often looses the connection to my access point and sometimes doesn’t work correctly after resuming from a suspend. I’m going to switch back to using ndiswrapper to see if it’ll work with a bit more coaxing.

Overall, I’m reasonably happy with the upgrade – other than the issues mentioned above, it went smoothly and the system is working well. The only issue that’s really causing me pain at the moment is the wireless (but then it is Broadcom…).

After struggling for several hours with a flash drive that refused to boot no matter what I did, I discovered an interesting fact – most bootloaders won’t boot from flash drives that have 2048-byte sectors. Of course, the flash drive I was using had 2048-byte sectors… Using a flash drive with 512-byte sectors worked perfectly first time.

Depending on operating system, it may not be that easy to tell the sector size of the flash drive. If using a Unix system, you should see something useful in the kernel ring buffer (displayed by dmesg) when you insert the drive.

A non-bootable drive will display something like:
sd 9:0:0:0: [sdh] 258687 2048-byte hardware sectors (530 MB)
or
sd0: 505 MB, 126 cyl, 64 head, 32 sec, 2048 bytes/sect x 258687 sectors

A bootable one will look something like:
sd 11:0:0:0: [sdh] 2061816 512-byte hardware sectors (1056 MB)
or
sd0: 1006 MB, 1006 cyl, 64 head, 32 sec, 512 bytes/sect x 2062328 sectors

There are a number of sellers offering the same plan for roughly half price on eBay, $199 Buy It Now. Positive feedback for these sellers is close to 100% and, as AppleCare is a worldwide warranty, it seems like a smart move to buy from them, rather than from Apple. Read the auctions more closely and things start to sound a little fishy though. The majority of the sellers who sell a lot of AppleCare packages provide the serial number electronically, rather than providing the retail package or any official paperwork from Apple. Only the serial number is required to activate the warranty, but surely the retail package should be available, if requested? Although the serial number provided may activate the warranty, how do we know that it wasn’t generated by a serial number generator?

I think in this case I’m going to be more prudent and pay a little bit more to buy an AppleCare plan that comes in the proper retail package – there are a number of sellers on eBay offering them and they’re also available from a number of reputable online retailers. The prices aren’t as low, but at least I’ll be more comfortable that I’m buying a legitimate product.

For example:

[0] mj@majestic:~/tmp$ mount |grep home
/dev/mapper/data-home on /home type xfs (rw)
[0] mj@majestic:~/tmp$ mkdir test
[0] mj@majestic:~/tmp$ ls -ld test
drwxr-sr-x 2 mj mj 6 Jun 18 15:28 test
[0] mj@majestic:~/tmp$ touch -t 200801011530 test
[0] mj@majestic:~/tmp$ ls -ld test
drwxr-sr-x 2 mj mj 6 Jan 1 15:30 test
[0] mj@majestic:~/tmp$ stat test
File: `test'
Size: 6 Blocks: 0 IO Block: 4096 directory
Device: fd00h/64768d Inode: 951267331 Links: 2
Access: (2755/drwxr-sr-x) Uid: ( 1000/ mj) Gid: ( 1000/ mj)
Access: 2008-01-01 15:30:00.000000000 +0000
Modify: 2008-01-01 15:30:00.000000000 +0000
Change: 2008-06-18 15:29:08.173750666 +0100
[0] mj@majestic:~/tmp$ mv test test1
[0] mj@majestic:~/tmp$ ls -ld test1
drwxr-sr-x 2 mj mj 6 Jan 1 15:30 test1
[0] mj@majestic:~/tmp$ mv test1 ..
[0] mj@majestic:~/tmp$ ls -ld ../test1
drwxr-sr-x 2 mj mj 6 Jun 18 15:30 ../test1
File: `../test1'
Size: 6 Blocks: 0 IO Block: 4096 directory
Device: fd00h/64768d Inode: 951267331 Links: 2
Access: (2755/drwxr-sr-x) Uid: ( 1000/ mj) Gid: ( 1000/ mj)
Access: 2008-01-01 15:30:00.000000000 +0000
Modify: 2008-06-18 15:30:02.814078187 +0100
Change: 2008-06-18 15:30:02.814078187 +0100


I’d never seen this happen before, so I tried to reproduce the behaviour on systems using ext3, UFS and HFS+ filesystems. None of them updated the moved directory’s mtime when the parent directory changed, which is what one would expect. XFS does have an active mailing list, so I reported my findings and was quickly provided with a patch that fixed the problem. Kudos to the XFS developers for providing a fix so quickly.

Rather odd that no-one had spotted this behaviour in the past though…

As long as the fresh bootstrap is done using the same parameters as used originally (prefix, database directory, etc), everything should work as before.

I tested this a short while ago on an OS X 10.5 system using a pkgsrc -current tree and it worked perfectly.

Special meal requests cannot be made for travel on any of the following services: all UK Domestic flights, Euro Traveller flights from the UK to Paris, Luxembourg, Dusseldorf, Jersey, Cologne, Amsterdam & Brussels, and passengers travelling on any flight on a stand-by or waitlist basis.

That’s rather poor (and rather strange, if you ask me). Heck, in South Africa BA even have extra vegetarian meals on their domestic flights for those who haven’t requested them in advance. I’m not at all impressed, but unfortunately BA seem to be the only airline that fly from Gatwick to Manchester.

Update: If you ask, they do have vegetarian meals onboard, even if you can’t pre-book one.

For those in the area, we’re now living in Horley, Surrey (near Gatwick).

Something odd that we’ve both noticed is that when we put a 450Mhz CPU into a machine that we didn’t receive with a 450Mhz CPU, it wouldn’t boot up. There’s no mention of CPU speed jumpers in the service manual, so we both put it down to different motherboard revisions, phases of the moon and the lack of a chicken sacrifice.

A few days ago I discovered the Sun 450 MHz UltraSPARC-II Module Upgrade guide, which details the CPU speed jumper settings for the Ultra 60 (see pages 3-5 and 3-6). Bah. Why doesn’t Sun bother documenting these things in the service manual?

All mail for my various domains is delivered to the primary MX, which is a hosted server sitting in the US running Debian GNU/Linux (unfortunately my hosting provider doesn’t support NetBSD). It runs postfix and makes use of a variety of checks within postfix itself as well as postgrey for greylisting. I use a fairly conservative list of RBLs and, in conjunction with greylisting, they stop most spam from being accepted. Why postfix? Well, I stopped using sendmail over ten years ago, and although I’ve had good results with Exim in the past, these days I’m just most comfortable with postfix and it suits my needs perfectly.

The RBLs I use:

• zen.spamhaus.org
• cbl.abuseat.org
• list.dsbl.org

Once mail has been received by my primary MX, it is delivered to local mailboxes, one per user. None of the users read their mail from the US server, however. All the mail is downloaded to the local mail server via SSL-secured POP3 and accessed here, either locally or via IMAP. The local mail server is a Sun Ultra 2 running NetBSD/sparc64 3.1_STABLE.

Software I’m using on the local mail server:

• postfix
• dovecot for IMAP (over SSL) access. There are a number of IMAP/POP3 servers available, but I chose Dovecot because of its clean design, good security record and flexible support for mail storage, amongst other things.
• amavisd-new with spamassasin (with razor and Bayesian filtering enabled) and clamav for content filtering
• getmail to download mail from the US server
• mailgraph for simple reporting

All of the above are available in pkgsrc. As I have already done any RBL-based checks on the MX, I don’t do any of them locally.