A quick warning for those of you running Tiger Server: the latest security update edits the LaunchDaemon plist for named (BIND/DNS), relocating it from /usr/bin to /usr/sbin. However, at the same time, it disables it.
That means that, after install and restart, your DNS server will not work: you'll need to turn it back on using launchctl or the Server Admin tool.
No sooner said than patched!
For those who haven't heard me blather at length about all things SuperDuper! and Shirt Pocket, there's a 45 minute interview of me up at MacVoices.
Remember: the game rules require you to drink every time you hear me say "Um", "Uh" or audibly gesticulate. Do not play while driving.
My friend Jonas Salling has started blogging again, and that's always a good thing.
He's got some recent posts up there as he tests the WiFi support for Clicker, and the results may surprise you!
Jonas is one of the hardest working developers out there, and he never settles for less than absolute excellence when releasing new stuff.
The long-in-development Clicker 3.5 is no exception, and it looks like it's getting really close to release. That's good news for all the fans of Clicker, since a great product is getting a lot better. And I'm sure he has many cool things in store moving forward as well.
Welcome back, Jonas -- looking forward to more posts!
A little tip for those of you who might have installed Seagate SATA drives into your 3GB/s capable G5, MacPro, NAS device, or whatever.
Looks like recent Seagate drives ship with a jumper installed that limits the drive to 1.5GB/s speeds. While the jumper is documented in the User's Guide that ships with retail packs, it's specifically mentioned as something you might need to install if you have trouble with the drive. And OEM drives don't have any documentation at all.
To get 3GB/s, the jumper should not be present on the outer pins of the jumper block. So -- if you've got one of these drives, check it out: you might get that drive humming along twice as fast!
Apple can sometimes make small changes that have unexpected consequences.
Take Partition Schemes, for example.
This is the kind of thing most Mac users never think about. You buy a drive, plug it in, drive comes up, things work.
Done.
What you probably don't know is that most drives came partitioned and formatted for Windows, even when the drive is listed as "Mac Compatible", typically using Master Boot Record as the partition scheme and FAT32 as the format.
Before OSX 10.4.6 or so, this wasn't a big deal, at least for SuperDuper! Since FAT32 isn't appropriate for storing Mac files with full fidelity (and has various other issues, like file size limits, etc), we would instruct the user to erase the drive, using HFS+ (Mac OS Extended) as the format. Disk Utility wouldn't allow HFS+ volumes to be hosted on Master Boot Record partitioned drives, and so the user would need to select the drive, rather than the volume, and erase that way. No big deal.
Then, the Intel Macs came out, and with them, 10.4.6.
To help with something-or-other (probably to allow HFS+ and FAT32 volumes to be hosted on the same drive in separate partitions for Boot Camp users), Apple decided to change Disk Utility so that it allows HFS+ volumes to be hosted on Master Boot Record partitioned disks. Which I'm sure didn't seem like a big deal: in fact, it's quite convenient, and had probably been requested as a feature over the years.
All that's great, except for one thing: Macs don't support starting up from Master Boot Record volumes.
This is clearly not a big deal for most users. But, for SuperDuper! users (and, I'm sure, for those who use similar applications) it's been a big problem: drives that look like they should act as startup volumes won't, and the reason is really obscure.
Suddenly, users who used to use Disk Utility to erase a drive now have to head to the Partition tab (which doesn't even appear if you select the volume instead of the hosting drive), click Options, understand the 3 partition types, and partition their drive appropriately.
So, this one small change -- allow HFS+ volumes on Master Boot Record partitioned drives -- ends up having a pretty big impact on users with external drives. This is mostly due to its implementation (and lack of documentation).
Worse, users aren't steered to the right choice by Disk Utility. In fact, the default is to do the absolutely wrong thing for most: retain a Windows partition scheme.
This probably hasn't had much of an impact on Apple's support, but it's sure hurt here!
tv is in the house -- two of them, actually -- and, well, it's good!
I'm not using it for music much -- my library is much too large for this device, and navigation of large collections, as has been said elsewhere, is quite lacking.
That said, for video material -- movies, tv shows, etc -- it works great. Playback starts quickly, even when streamed, and looks quite good. It's lacking in the audio department (it's really too bad that so much of this material, both movies and TV, encoded with Dolby Digital in full 5.1 or 7.1 surround, are reduced to ancient Dolby Surround playback, with no LFE channel, no split surrounds... much less impact), but visually things look quite reasonable.
It works great with netTunes, too, as you'd expect. As I've said many times, I run with a headless server, and it contains all my music and other content. With netTunes, it's trivial to connect to the server using a laptop while seated on the couch, and "pair" the tv with the server, change the synchronization information, purchase TV shows to be viewed -- all remotely.
I'm happy that the approach I took years ago -- truly remote controlling iTunes with its own interface -- continues to work with new versions of iTunes, and continues to prove it was the right way to go, moving forward with iTunes as iTunes itself changes.
Anyway, great stuff.
One expensive but potentially useful tip: you can use a scan converter to convert from Component input to regular Y/C (S-Video) or Composite, should you not have a component/HDMI capable TV. One example is the TV One AVT-3190 ($389). Expensive, but cheaper than replacing your TV...
The other day, I was pushing at the limits of my existing Infrant ReadyNAS NV
You see, the ReadyNAS uses Infrant's proprietary X-RAID. X-RAID basically RAID 6RAID 5 (see comments, below) with the ability to dynamically increase the total size of the RAID as well.
So, not only will the ReadyNAS run with a single drive faiure (and hot-rebuild the drive), it can dynamically increase the size of the RAID set as well. So, all I had to do was:
Buy four drives of the appropriate size. I went from four 250GB drives with a total size of about 700GB, to four 500GB drives with a total size of about 1.6TB.
The reason you don't get "all" the space on the drives is because redundant information is spread across each drive that allows any drive that goes "down" to be replaced and rebuilt with no data loss.
With the ReadyNAS on, and in use, pull out the first of the four drives.
Yeah. Scary. But that's what to do!
Unscrew the four screws that attach the SATA drive to the tray from and attach it to the new.
Slide the new drive into place.
At this point, the ReadyNAS will automatically rebuild the data that was on the original drive on this new drive. All of this has been done with the unit on and operating.
Wait for the rebuild to complete (it'll send you email when it's done).
Repeat with the next drive.
Yeah. That's it. When you're done, you do need to restart the ReadyNAS to get the volume to expand, but that can be postponed until you're ready to do it... and that's the only time the unit is "down".
Pretty cool, eh?
(Yeah, I know I sound like a pitchman for Infrant, but I'm honestly not affiliated with them in any way at all. I just think it's a great product.)
Many of you probably know that, for some reason, iSight cameras can get into a weird state where they start causing serious errors with FireWire drives.
The symptoms usually include a bunch of I/O errors while copying to a FireWire drive: failed copies, flaky behavior, crashes. All of this goes away if you power off, disconnect the iSight, wait a while and power back up.
Sometimes, the iSight stops working with iChat (it says the camera's in use when it's not, or the light comes on, but you don't get any picture), and in it was in that second state today when I had a kernel panic.
No data was lost, I'm happy to say, but I decided that I've had enough of this. Since 10.4.9 supports USB cameras, I've switched to a Logitech QuickCam Ultra Vision
It's not as elegant as the original iSight (it's fixed focus, horizontal format, a bit gaudy), but it's got a nice wide angle lens, built in microphone, works with any monitor, and seems reliable. Plug the thing in, and it works.
Given that you can't buy "real" iSights any more, and based on direct experience, I give it a thumbs-up.
Sorry, iSight. I'll miss you!
When the new Airport Extreme Base Station came out, I was happy to see that it had some support for attached USB drives. It's a reasonable (though not perfect) way to share data in a home/SOHO situation, and I figured people would be using it to back up with SuperDuper! So -- to help out...
A few things to point out right off the bat:
As you've likely seen elsewhere, the Airport Disks are not fast. Don't expect blazing speeds: wired, I've seen a maximum of about 1.5MB/s.
The AEBS gets very, very cranky if you get to a disk full situation. I've seen it crash more than once. Don't do that.
Remember that HFS+ drives are made available through AFP, and FAT32 through SMB.
Don't format any drives you're going to use with SuperDuper! as FAT32: use HFS+ (and partition properly for the Mac processor type you're using -- GUID for Intel, Apple Partition Map for Power PC).
Make sure to connect a power supply to the drive.
As general advice, please don't cheap out when you get an external drive. Really. Get one with a real Oxford chipset, USB/FireWire if possible in case you want to attach it directly to your Mac.
Don't expect miracles. This is an inexpensive solution, and it behaves like one. If you want a real NAS, I suggest an Infrant ReadyNAS NV+: it's faster, redundant, recoverable. I'll have another post about the ReadyNAS soon.
Remember, this is a first generation ("Rev A") product. It's likely to go through teething pains. Don't rely on them as your only backup!
You'll note that your Airport Disks don't show up in the SuperDuper! pop-ups. This is by design: we can't currently copy directly to or from a network volume due to authentication/permission/metadata issues.
Instead, you'll follow the steps in Backing up over a network in the SuperDuper! User's Guide (Help > User's Guide), and back up to a read/write sparse image stored on the Airport Disk.
We often get asked why SuperDuper! can't back up directly to a network volume. What most people don't realize is that, for security reasons, you can't directly authenticate as "root" over a network, and that means it's not possible to store files with system ownership on a network drive.
An image, on the other hand, acts as a "local drive", and can be authenticated against, even though it's stored remotely. This ensures that your files are backed up with full fidelity, including proper ownership and permissions. And since it's formatted as HFS+, it avoids various situations that can ensue trying to emulate HFS+ semantics and metadata storage on a non-HFS+ drive, while still storing in a native, non-proprietary, Mac-native format.
I'd suggest doing your first full backup directly to the USB drive, rather than over the network. This'll be a lot faster. You can then connect the drive to the base station, and re-select the image using the "Disk Image..." choice in SuperDuper!'s destination drive pop-up. (Note that although the image will be grey, you can still pick it, and ignore the "overwrite" warning. Yes, I know that UI sucks.)
That should do it: enjoy the base station!
You know, it’s pretty rare that I post up here about netTunes, mostly because… well… it just works, and there’s not much to say other than “Whoa! Cool!"… which gets a bit boring.
But, every so often I’ll get a question about how it’s possible to access commands that aren’t available in the main window—for example, Store > Check for Purchases...
So, from the department of obscure features, let’s get this done!
Normally, you’d access things like this with an onscreen control or keyboard shortcut. For example, to access iTunes’ Preferences, you can press Cmd+y (an alternate for Cmd+,) and it’ll come right up. And you can add a playlist with the + button in the main window. But Check for Purchases doesn’t have a keyboard shortcut or button, and so it’s not available in netTunes.
But there’s hope! In Tiger, you can add your own keyboard shortcuts using the Keyboard & Mouse preference pane. Open that up, switch to the Keyboard Shortcuts tab and click the + button. Set the Application pop-up to iTunes, then enter the full, properly capitalized text of the menu item (in this case, Check for Purchases..., including the ...). Choose a shortcut key (like Cmd+Opt+C).
Save, then quit and restart iTunes and poof! You can now Check for Purchases in netTunes on the client!
