Log in

No account? Create an account

Dear Apple iTunes people.

1. You made the laptop computer.
2. You made the OS running on the laptop computer.
3. You made the iTunes program running on the OS on the laptop computer.
4. You made the iPod.
5. You made the OS running on the iPod.
6. You even made the frigging dock cable plugging the iPod into the computer.

Thu Sep 10 22:51:05 ernie \[0x0-0x1d01d\].com.apple.iTunes[309] : Child process initialized.
Thu Sep 10 22:51:13 ernie AppleMobileBackup[326] : BackupAgent starting up...
Thu Sep 10 22:51:13 ernie \[0x0-0x1d01d\].com.apple.iTunes[309] : Child process initialized.
Thu Sep 10 22:51:13 ernie \[0x0-0x1d01d\].com.apple.iTunes[309] : 2009-09-10 22:51:13.395 AppleMobileBackup\[326:903\] BackupAgent starting up...
Thu Sep 10 23:00:15 ernie com.apple.launchd.peruser.502[131] (com.apple.AddressBook.abd) : The following job tried to hijack the service "com.apple.AddressBook.abd" from this job: \[0x0-0x20020\].com.apple.AddressBook.abd
Thu Sep 10 23:00:18 ernie PreferenceSyncClient[338] : Error: Can't get session for client com.apple.PreferenceSync, bailing
Thu Sep 10 23:00:36 ernie SyncServer[342] : \[110ed0\] |SyncManager|Warning| removing client com.apple.Mail.Notes from plan because I couldn't send it a sync alert
Thu Sep 10 23:05:17 ernie \[0x0-0x1d01d\].com.apple.iTunes[309] : Child process initialized.

How the fuck could you ever pretend this crap is appropriate to ship to your paying customers? This shit is fucking ridiculous.


PS: I don't think that object instance has a string repr method or whatever you call it in your crazy Objective C.


Dear Steve

Why is it, ever since I upgraded to omg new exciting iTunes 8, does it insist that every time it opens, my AppleTV has FIVE HUNDRED FUCKING SONGS TO SYNC?

Is that what the fancy new GENIUS says? That I need to resync gigs of music I've already synced over?

Fucking fail. You guys have srsly blown it.


Fucking Apple and their 10.5.3 update

First off, please digg this.


I made the mistake of installing it on my Macbook. It rendered wireless networking useless. My link (to a god damned Apple Time Capsule, for christs sake) bounces up and down every 5 to 10 seconds. I had no problems with wireless networking before I installed the updater, and Denise's Macbook (right next to me on the couch) which is not updated, has no problems seeing the same Airport.

I even tried installing the downloadable 10.5.3 Combo Updater, but it did not resolve the problem.


Update: I deleted my network from the 'preferred networks' list (which I tried before) and then went in and deleted the WPA key from my Keychain. This seems to have fixed it.

What a bucket of fail, Apple. :(


Time Capsule, part 3

A quick update since I am thinking about it right now on the Time Capsule.

It's still working like a dream with my MacOS 10.5 machines. And I am comfortable enough with 10.5 that I'll soon be upgrading my straggler 10.4 mac in the edit suite. I have my fingers crossed that Final Cut Studio and my CS2 Photoshop and After Effects will cope.

I sidestepped the wierd rsync/cifs bug that was causing my Fedora Core 5 box's backups to fail by using Gnu tar instead. There are advantages and costs to using either- rsync to cifs wasn't preserving file ownerships and modes, but the backups were easier to access for restores than lumps of tarfile (I back up in chunks, seperate tar archives for things like /etc, /usr/local, individual home directories, etc). So that's finally off my to-do list, and my home server is now backed up. I'd like to use Gnu tar's incremental 'snapshots' when I get a chance, but it seems to cross the line of where complexity will likely cause me to poke myself in the eye.

I also have my AppleTV mounting a share off the Time Capsule. The AppleTV has the hack that allows me to load additional kernel modules from 10.4.9, so I have it mounted via appleshare, which seemed more logical than smbfs, which the AppleTV also does. Combined with the ATVFiles appliance and my Perian/Flip4Mac install, I can plonk pretty much any video file I want on the Time Capsule share and watch it on the AppleTV. Apple should officially support this integration, but whatevers.

Alpha geek out.


Time Capsule update

So I realized this morning that the thing I hate more than anything when I'm researching a problem online is a blog post from some douche with the same problem, who's obviously made progress but not bothered to post an update about it. So here is an actual update on my first Apple Time Capsule impressions.

I posted originally about wireless connection drops. At the time, my wife and I were both still running 10.4.11 on our Macbooks. Since then, I've upgraded them both to 10.5.2, and since the upgrade, wireless connectivity has been flawless. No wierd drops at all. I hope Apple backports the driver fixes to 10.4!

Since we've upgraded to 10.5.2, we're both running Time Machine. It has been perfect. Until now I would have refused to believe that backups could be so simple to configure, schedule and run. I did the initial backup over wireless after reading on the Apple support forums that some folks had problems doing the initial over wired and subsequent runs over wireless. There seems to be some wierdness with Time Capsule named disk user accounts and when the Time Machine disk image names get MAC addresses appended to their filenames, but I'm probably talking out my ass here. The upshot is that Time Machine is working great with the Time Capsule.

The other issue I had with the Time Capsule was a wierd failure rsyncing backups from my Fedora Core 5 Linux machine over a cifs mount. The rsync would stall, operations on the cifs mount would fail with 'host down' errors; and the Time Capsule would hang trying to reboot via Airport Utility. I just installed the newly-available Time Capsule 7.3.1 firmware this morning, and it looks like the problem still exists.

There's been progress though- with 7.3, interrupting an rsync would stick the Time Capsule into a state where it stopped servicing cifs, and a rebooot from Airport Utility would hang, requiring a hard power cycle. This morning I verified that the reboot hang is fixed. Now if I can just figure out how to reboot it again from the office..


Time Capsule first impressions

I got to play with my new Apple Time Capsule over the weekend, and I have some mixed feelings about it.

The good news is that for simple configurations, the setup is entirely automagic. The Airport Utility is smart enough to snarf your wireless settings, including WPA passphrases from your Keychain, and set up the Time Capsule to replace your existing access point. There are also wizard-driven config options for adding it to your wired network via ethernet, and via WDS to an existing wireless network.

The bad news is that as expected, anything more complex is a battle. Like with the Airport Extreme (the Time Capsule really is just an Airport Extreme with a built-in SATA disk), there is no way to disable DHCP if you want NAT. My workaround was to create a single IP DHCP pool, and 'reserve' it for a DHCP ID that I don't use on my network. This allows me to continue using the awesome Nominum DCS running on a Linux box as my DHCP server.

The wireless seems to be a little flaky. I noticed frequent drops in wireless on my Macbook that seem correlated to WPA key rotation on the Time Capsule. There is a key rotation interval configuration option in the Airport Utility, but it seems to be ignored. This could be a deal-breaker for me since my old trusty $50 Linksys WRT54G running OpenWRT does a much more reliable job as an AP (albeit without 802.11n).

As a NAS, the Time Capsule should work great in an all-MacOS environment. I did some light benchmarking with the AJA KONA System Test, a standard benchmarking utility from the digital video production industry. It does throughput tests on a range of file size reads and writes. When I get the time, I plan to hit the Time Capsule with Bonnie. I connected my Macbook directly to a Gigabit Ethernet port on the Time Capsule. For sequential reads/writes at least, the Time Capsule seems to do a decent job.

Here are the results when mounting the Time Capsule via Appleshare:

  MB       MB/sec
           Read      Write      
128.0      15.0      10.4      
256.0      15.0      10.6      
512.0      15.0      9.9      
1024.0     15.0      9.3      
2048.0     14.7      8.8      
4096.0     14.9      8.7

Here are the results when mounting the Time Capsule via CIFS (Windows file sharing):

  MB       MB/sec
           Read      Write      
128.0      11.1      8.6      
256.0      11.8      9.2      
512.0      12.5      9.0      
1024.0     12.4      9.3      
2048.0     12.5      9.1      
4096.0     12.3      9.2    

Now the really bad news. I mounted the Time Capsule via CIFS on my Fedora Core 5 machine, and tried backing it up with rsync. No matter what I tried, the rsync would stall after about 8000 io operations. Opening another shell and simply trying an 'ls' on the cifs-mounted directory would fail with a 'Host is down' error. Trying to SMB mount it from my Macbook at that point would simply time out.

It gets worse- once the Time Capsule is in this state, restarting it from the Airport Utility would fail. The Time Capsule's status LED would go orange before restarting, indicating an error condition. I don't know what the error is, since at that point, the Airport Utility no longer sees it; and the Time Capsule doesn't syslog any errors. The only way to fix it in this state is a hard power cycle.

Because of this, I suspect the problem lies with the Time Capsule, and not the CIFS support on my linux box. I will confirm and follow up with additional tests pushing the same rsync traffic from my Macbook cifs-mounting the Time Capsule.

Since I bought the Time Capsule to backup my home machines (Two Macbooks, a G4 Desktop, and my Linux box) and its failing to work for 1/4th of what I wanted it to do, I think that I should probably return it. $514 is a lot for a device that isn't working right. On the other hand, hopefully, maybe, Apple will fix the problem and release updated firmware. I could probably tolerate the SMB problem if the wireless was more solid. But I don't think that I can justify half a kilobuck for an AP/NAS that does neither job particularly well.