Introducing NTFS

A filesystem is the basic scheme for organizing data on a hard disk drive. The common FAT filesystem, supported by just about every operating system, is just too basic for modern operating systems. Microsoft introduced the advanced NTFS filesystem with their Windows NT operating system in 1993. Borrowing from OS/2′s HPFS and VMS’ Files-11, NTFS is a journalling filesystem with many features, including POSIX links, alternate data streams, sparse files, compression, and encryption.

Although just about everything Microsoft produces is maligned by UNIX and Mac geeks, this hatred is unwarranted in the case of the many storage advances coming out of Redmond. Microsoft may be fairly criticized for producing expensive, proprietary systems, but they have dome some amazing things with disks, and NTFS is arguably one of the most advanced filesystems in wide usage. Much of this credit goes to Windows NT architect Dave Cutler, who also led development of DEC VMS, the RISC concepts that became Alpha, and Microsoft’s Azure cloud platform.

Although every version of Windows supports evolutions of the old FAT filesystem, modern iterations increasingly require NTFS. Windows XP allowed either FAT32 or NTFS for booting; Windows Vista could be forced to boot from FAT32; Windows 7 requires NTFS. Therefore, most PC hard disk drives, including external USB drives, now come formatted with NTFS by default.

NTFS on Mac OS X

This leads to issues for Mac users, especially when they dual-boot with Boot Camp or buy external hard disk drives. As mentioned, all versions of Mac OS X since 10.3 “Panther” have included read-only NTFS support, but those wanting full access had two options:

1. Paragon Software’s NTFS for Mac OS X is a full and supported read/write solution. Although available for purchase separately, many hard disk drives like the Seagate GoFlex now include a free copy of Paragon NTFS.
2. The open source NTFS-3G driver has also been ported to Mac OS X, allowing read/write support for free.

Mac OS X 10.6 “Snow Leopard” adds a third alternative: Native read/write support for NTFS. But it’s not as simple as that. Although early betas enabled read/write support by default, it was limited once again to read-only in the final releases.

It is possible and even simple) to enable read/write support with the native Snow Leopard drivers, but this is definitely an “at your own risk” proposition. Users have reported kernel panics when using these methods, and although I have not heard of data corruption, it is possible as well.

The Manual Method: mount_ntfs

Making disks available is called “mounting” in UNIX geek-speak, and mount commands in modern operating systems are like ogres: They have many layers. Plug in a drive, and Mac OS X makes it available for you using a layer cake of commands, but the bottom-most command is “mount”. This simple command-line utility takes a few arguments and attaches a raw disk device to a point in the unified filesystem tree.

When presented an NTFS drive, Mac OS X calls a utility called mount_ntfs that resides in the /sbin directory, and we can call it, too. Although OS X always tells mount_ntfs to mount NTFS drives read-only, we can tell it to enable writing as well by using the “-o rw” flag.

There’s just one problem: Where should we connect the NTFS file system? Mac OS X automatically creates a new directory (called a “mount point” in UNIX-speak) in /Volumes with the name of the filesystem. For example, the GoFlex drive I bought yesterday mounts as “/Volumes/FreeAgent GoFlex Drive” by default. But mount_ntfs won’t create this mount point, so we have to do it.

Here are the steps to mount an NTFS drive read/write from the command line:

1. Plug in the drive and let Mac OS X mount it read-only.
2. Look in Finder to see the name of the drive. For example, my drive mounts with the name “FreeAgent GoFlex Drive” and this is what shows up on the desktop and in Frinder under “Devices”.
3. Open the Terminal application to get command-line access. We’ll use “sudo” which executes commands as the administrator instead of a regular user.
4. Type the following command in Terminal to get necessary information about the drive. Use the drive name you see in Finder in place of “drive name”, and make sure to use quotation marks around it since Terminal treats un-quoted spaces as separators rather than part of the name.

   diskutil info "/Volumes/drive name"

5. Record the “Device Node” entry, which will look something like “/dev/disk4s1″. This is where the raw partition is mapped by the disk subsystem, and where the filesystem driver will read its data.


The diskutil command gives us the "Node Name", which we'll need momentarily

6. Eject the drive, using option-click in Finder or with the hdiutil command in Terminal:

   hdiutil eject "/Volumes/drive name"

7. Now you must create the mount point again. Type the following:

   sudo mkdir "/Volumes/drive name"

8. Finally, use mount_ntfs to mount the drive read/write using the following command. Use the node name you spotted above and the mount point you just created:

   sudo mount_ntfs -o rw /dev/disk?s? "/Volumes/drive name"

9. When you’re done, you can use the Finder, the hdiutil command, or just about anything else to eject the drive. Make sure your mount point is deleted as well!

This method is great for occasional NTFS use, which is frankly all Mac users should need. If you intend to use a drive frequently, I highly recommend reformatting it with the native HFS+ filesystem since it will be fully-supported by the operating system.

The Per-Drive Method

Let’s say you have an NTFS drive you frequently need to mount read/write and find the above method too much of a hassle. Maybe it’s your Boot Camp drive, or perhaps it’s a USB hard disk drive you share with a Windows-using colleague. It is possible to tell Mac OS X to always mount a given NTFS drive read/write using its native driver using the following commands. However, I recommend investing in the Paragon driver for this use case, since it’s fully-supported!

Like all UNIX systems, Mac OS X uses a configuration file to determine what it should do with certain drives. This file, called “fstab” and located in “/etc”, is not present by default but will override the “read-only” flag on a per-drive basis if found. This allows a drive to always be mounted read/write without any hassle.

1. Get the drive name as in step 2 above.
2. Open Terminal and type the following command to edit the /etc/fstab file:

   sudo nano /etc/fstab



Adding a line in /etc/fstab will make Mac OS X always mount a single drive in read/write mode

3. “Nano” is a command-line editing program. Add the following line to the file (and don’t forget the quotes around the drive name if it contains spaces!)

   LABEL="drive name" none ntfs rw

4. Now type control-x to save and exit, type y for yes, and hit enter.
5. After a reboot, Mac OS X should automatically mount any drive with that label as read/write

Note that this can also be done using the NTFS UUID of the drive, but this isn’t present on every drive to LABEL works better. Also, some have reported needing multiple reboots to make it work. I have no idea why.

The Permanent Universal Method

It is also possible to permanently modify how Mac OS X calls the mount_ntfs command to always mount every NTFS drive in read/write mode. Again, I will point out that this isn’t necessarily a great idea since Apple doesn’t support using the driver in this way. But here it is!

1. Open Terminal. We won’t need the drive name or Node Name since this applies to every NTFS drive.
2. Rename the mount_ntfs command to something else by typing the following:

   sudo mv /sbin/mount_ntfs /sbin/mount_ntfs_orig

3. Create a shell script called mount_ntfs using the Nano editor:

   sudo nano /sbin/mount_ntfs

4. This script will simply call mount_ntfs with the “-o rw” flag every time it’s used. Type the following in Nano:

   #!/bin/sh
   /sbin/mount_ntfs_orig -o rw "$@"

5. Type control-x to save and exit, type y for yes, and hit enter.
6. Now we’ll fix the permissions on this new file so it’s owned by root and group wheel:

   sudo chown root:wheel /sbin/mount_ntfs

7. Finally, we make the shell script executable:

   sudo chmod 755 /sbin/mount_ntfs

8. Now every time OS X encounters an NTFS drive, it will mount it read/write by calling this script rather than the “mount_ntfs” executable it thinks it’s using.

Note that future OS updates might “break” this method by replacing the /sbin/mount_ntfs command, or it could cause other issues. But it works for now and doesn’t even require a reboot.

Stephen’s Stance

I’m hesitant to recommend that casual Mac users employ any of these methods to access NTFS drives. Each requires superuser access and careful typing. You can easily mess up your system this way, and unsupported uses of the NTFS driver might result in data loss.

If you aren’t comfortable with this kind of mucking-about or intend to frequently write to NTFS drives, I highly suggest installing NTFS-3G or Paragon’s NTFS driver. In fact, the best method is simply to go buy a Seagate GoFlex drive and use the Paragon driver that comes with it!

But hackers and geeks like me want to know how to do this. This is why I decided to document it here.

Note: Some of these links include affiliate codes that help pay for this blog. For example, buying an Amazon Kindle with this link sends a few bucks my way! But I don't write this blog to make money, and am happy to link to sites and stores that don't pay anything. I like Amazon and buy tons from them, but you're free to buy whatever and wherever you want.

© sfoskett for Stephen Foskett, Pack Rat, 2010. | How To Write To Windows NTFS Drives In Mac OS X 10.6 “Snow Leopard”
This post was categorized as Apple, Personal, Terabyte home. Each of my categories has its own feed if you'd like to filter out or focus on posts like this.

1. Open Terminal
2. As I mentioned in the article, No 64-Bit Snow Leopard Kernel For You!, only Macs with 64-bit EFI firmware will run Snow Leopard’s kernel in 64-bit mode out of the box. Check if your system is compatible by typing the following command

   ioreg -l -p IODeviceTree | grep firmware-abi

3. If it says “EFI64″, your system is capable of easily booting into 64-bit Snow Leopard. Otherwise, you need to go looking for a more-complicated method.
4. You can test this capability by rebooting and holding down the “6″ and “4″ keys through the grey Apple screen. Check System Profiler (in the “Software” section) to see if you’re running a 64-bit kernel.
5. Now let’s set the kernel configuration files to boot in 64-bit mode by default. Type the following command from Terminal (you’ll need to enter your password when prompted):

   sudo defaults write \

   /Library/Preferences/SystemConfiguration/com.apple.Boot \

   'Kernel Flags' 'arch=x86_64'

6. Finally, let’s set the NVRAM to boot in 64-bit mode as well. Type this command:

   sudo nvram boot-args="arch=x86_64"

7. Now you’re set. Your system will always boot in 64-bit mode. To get it to run 32-bit, just hold “3″ and “2″ through the Apple screen on reboot.

That’s it! You’ve now got a 64-bit Mac!

My iMac now boots in 64-bit mode by default!

© sfoskett for Stephen Foskett, Pack Rat, 2010. | How To Boot Snow Leopard in 64-Bit Mode
This post was categorized as Apple. Each of my categories has its own feed if you'd like to filter out or focus on posts like this.

Note: It looks like Apple now has the correct drivers available for direct download and upgrade. None of this should be required anymore.

Got a Hewlett Packard printer? Got Snow Leopard? Apple and HP report that the OS X 10.6 install DVD includes all required drivers and software, but it didn’t work for me. I went to look for the driver software on the Apple and HP web sites and you will find a list of supported printers, including many, many HP models. But the support article (entitled “HP Printer Drivers for Mac OS X v10.6“) redirects to the Ricoh drivers, and the HP drivers are MIA.

Poking around the site and trying different URLs, I am pleased to report that I have located the missing driver package! HP printer drivers for Mac OS X 10.6 Snow Leopard may be found here: http://support.apple.com/downloads/DL907/en_US/HewlettPackardPrinterDrivers2.0.dmg Note that this driver package is labeled “2.0″ but it includes the version 3.0 HP drivers which are (allegedly) included in the install DVD.

HP officially states that users should not use their Leopard software (Scan Pro, etc) under Snow Leopard. Indeed, users should uninstall any existing HP software and use the included drivers and software. Like the previous Apple drivers, this install interferes with HP’s scanner functions anyway, so they won’t work.

So, to sum up, users of Snow Leopard should uninstall any existing HP software and install the official Apple software through Software Update or from the support web site. You should then be able to print and scan (through Preview) for compatible HP devices.

© sfoskett for Stephen Foskett, Pack Rat, 2009. | Located! Missing HP Printer Driver For Snow Leopard
This post was categorized as Apple. Each of my categories has its own feed if you'd like to filter out or focus on posts like this.

The Snow Leopard kernel refuses to boot in 64-bit mode on most Macs. Should you care?

There is clearly a ton of interest in Mac OS X 10.6, Snow Leopard: My Snow Leopard features hardware compatibility chart had over 20,000 visitors in just three days! But one chart element is generating an inordinate amount of interest: Whether or not Snow Leopard can boot in 64-bit mode.

Snow Leopard is a solid but visually unremarkable update to Apple’s OS X family. Although there are many new technical features, it’s not loaded with flash. In fact, even experienced Mac users would be hard-pressed to notice that their system had even been updated!

As I mentioned in that post, I was most-interested in the potential to use Grand Central Dispatch and OpenCL to accelerate my system’s performance. Both features are supported on most Macs built over the last year or two, and they create a great foundation for future development. QuickTime X is interesting as well, though only Nvidia 9400M-based Macs (like my 2009 Mini) support it’s hardware-accelerated H.264 capabilities. The fact that so much of the operating system has been re-written using these modern capabilities is probably the biggest Snow Leopard feature.

Snow Leopard Does Not Boot 64-Bit…

I wasn’t all that concerned about whether the OS X kernel booted in 32-bit or 64-bit mode, but was intrigued to find that Snow Leopard boots with a 32-bit kernel on every Mac other than the rack-mount Xserve.

Much pre-launch discussion revolved around whether or not a given system was even capable of booting in 64-bit mode. There are three critical elements that determine whether a given machine will boot a 64-bit Snow Leopard kernel:

1. All system hardware must have 64-bit drivers, including the CPU, chipset, and peripheral chips. The 64-bit kernel exclusively uses 64-bit kexts (drivers), and these are rarer than the 32-bit ones used by Leopard.
2. It must use 64-bit EFI (firmware). Even though EFI32 can technically boot a 64-bit operating system just fine, Apple will not allow this. Only Macs made over the last few years include EFI64.
3. Apple must allow the system to boot in 64-bit mode. This is the most confusing. Many Macs will not boot Snow Leopard in 64-bit mode even though they are brand new, have no unusual hardware, and include EFI64. This includes all non-Pro MacBooks and Mac Minis.

So there you have it. No matter what you do, Snow Leopard will not boot with a 64-bit kernel and kexts on the majority of Macs. One could understand if there was a lack of drivers or some other technical limitation, as is the case with older Macs, the but this is not the case for the latest MacBook and Mac Mini systems. They won’t boot with a 64-bit kernel because the kernel refuses to boot.

The only Mac model that boots with a 64-bit kernel by default is the 2008 and 2009 Xserve (Xserve2,1 and Xserve3,1) running Snow Leopard Server. The following Macs can boot in 64-bit mode in non-server Snow Leopard if you hold down the 6 and 4 keys on boot or if you modify your “/Library/Preferences/SystemConfiguration/com.apple.Boot.plist” file as described at Netkas:

If your Mac is not included in this list, you will not be able to boot Snow Leopard in 64-bit mode. MacBook and Mac Mini models definitely will not boot into 64-bit Snow Leopard. The later Unibody MacBook Pros (5,3 and 5,4) are not listed, and it is not known if they work or not.

…But Why Do You Care?

Why do enthusiasts care so much about the “bitness” of their hardware and software? Geeks have been arguing over the merits of “bigger-bits” for decades. I remember Mac users claiming PCs were inferior because Macs used true 16-bit Motorola CPUs while PCs were stuck with an 8-bit bus. The gaming world did much to foster 64-bit mania, with Atari claiming their Jaguar was the first 64-bit console, and Nintendo even naming theirs the “N64″. But does it really matter?

In theory, a 64-bit operating system should make most-effective use of 64-bit CPUs, increasing performance and maximum addressable RAM. In the case of Intel CPUs, there are many improvements when running the 64-bit (x64) instruction set instead of legacy 32-bit (IA-32) mode. So, from a hardware perspective, 64 bits is definitely superior.

But Mac OS X can run 64-bit applications regardless of the bitness of the kernel. I am writing this post in 64-bit Safari running on a 32-bit Snow Leopard kernel. Many of the applications I normally run are 64-bit in Snow Leopard, including Safari, Mail, and the Finder. This last is important: All Snow Leopard users get a speedy 64-bit ground-up rewrite of Finder, which is their main operating system experience.

32-bit Snow Leopard runs 64-bit versions of many applications, including Safari, QuickTime X, iCal, Mail, and the Finder itself. Notable 32-bit apps include Microsoft Office, iTunes, and iPhoto.

Therefore, regardless of which kernel mode you have booted into, many of your daily activities will use full 64-bit applications. 64-bit versions of iTunes, iPhoto, and Microsoft Office might be nice, but they’re the exception not the rule, and I expect to see these move up to 64-bit soon.

Why do so many Macs not use the 64-bit version of Snow Leopard? One reason is compatibility: The 64-bit kernel requires a full set of 64-bit drivers, and these may have been lacking at launch. Another reason might be that these systems would not see much benefit from running a 64-bit operating system since they are limited to 4 GB of RAM. I would not be at all surprised if later point-revisions of OS X 10.6 enable booting in 64-bit mode by default, at least for the machines listed above and newer models. Those of us with older machines (like this MacBookPro3,1) might never see it, though.

I should note that there are a few 64-bit features lacking in 32-bit Snow Leopard. But some applications, including VMware Fusion, will not run at all under a 64-bit Snow Leopard kernel. And there is the question of driver compatibility. I am not an Apple apologist or fanboy, but I do use Macs 100% of the time for business and pleasure. I think it stinks that Apple now lags behind Microsoft in the race to provide a 64-bit desktop operating system. But the decision is understandable and it has little impact on the daily lives of end users.

© sfoskett for Stephen Foskett, Pack Rat, 2009. | No 64-Bit Snow Leopard Kernel For You!
This post was categorized as Apple, Computer History. Each of my categories has its own feed if you'd like to filter out or focus on posts like this.

Mac OS X 10.6 "Snow Leopard" deliveries begin on August 28!

Although Apple’s web site clearly states that Snow Leopard “Delivers on August 28th,” it is unclear if other sources will be so punctual. We definitely expect Apple Stores to have plenty of stock on Friday morning, but what of Amazon.com pre-orders? Will they also deliver on Friday, or will those of us who pre-ordered there have to wait a few days for this undercover upgrade?

Who Gets What

Snow Leopard is really a major jump forward in terms of advanced hardware and software integration. It brings Grand Central, OpenCL, full 64-bit mode, and QuickTime X along with Exchange support and many tweaks. But many of these features are highly hardware-dependent, so not all Mac users will get everything.

Here’s a cheat sheet I put together based on Apple’s documentation:

This table is based on the following facts:

1. Snow Leopard only supports Intel-based Macs. PowerPC Macs need not apply.
2. Booting Snow Leopard in 64-bit mode requires 64-bit EFI, and many pre-2007 Macs have only a 32-bit EFI. You can check your Mac (and help me fix my table) by typing “ioreg -l -p IODeviceTree | grep firmware-abi” in a Terminal window. If it says “EFI64″, your system is capable of running 64-bit Snow Leopard (though it can still run 64-bit apps). But Snow Leopard defaults to 32-bit mode on ALL Macs other than the Xserve at this point, and no one is sure why!
3. Grand Central Dispatch requires a multi-core CPU. This eliminates the original base-model 2006 Mac Mini, since it used a single-core CPU.
4. OpenCL requires newer Nvidia or the ATI graphics chips. This leaves out many pre-2008 models and some iMac and Mac Pro configurations. Check Apple’s list if you’re not sure.
5. QuickTime H.264 Hardware Acceleration only works with the Nvidia 9400M chipset. This leaves out many pre-2008 machines and even the latest Mac Pros, though they probably have enough horsepower on their own.

Finally, if you’re excited about the new Microsoft Exchange support in Mail.app, iCal, and the Address Book be warned! In order for any of this to work, your server must be running Microsoft Exchange Server 2007 Service Pack 1 Update Rollup 4. And most companies still aren’t updated that far!

Update: Check my follow-up post on 64-bit Snow Leopard for more about this controversial aspect!

I’m Updating!

I held off on Amazon and placed my own order this morning with Apple. I’m with Mark Twomey:Upgrading to Snow Leopard is a safe day-1 activity. Most of the updates amount to new under-the-hood features and the OS has been through round after round of testing. Unlike the massive shift from Tiger to Leopard (which I missed, being a late switcher), Snow Leopard ought to be a lesser upgrade.

Why make the update at all? Here are a few of my reasons:

1. It’s cheap: Just $29 to update a single Mac, or $49 for up to five. Compared to Microsoft’s (expired) “limited-time-only” (and incredibly complicated) Windows 7 upgrade, Apple sets out a red velvet carpet.
2. It’s easy: There’s just one version of Mac OS X, and any system running OS X 10.5 “Leopard” can update to full-on Snow Leopard. There are no editions and no conflicts updating from 32-bit to 64-bit (like Windows 7).
3. It future-proofs your (Intel) Mac: Mac developers have a long history of quickly leveraging new OS X features since Mac users have a long history of quickly upgrading. Snow Leopard adds cool stuff like Grand Central and OpenCL that my Intel- and Nvidia-based Macs ought to be able to leverage. See below if your Mac can use these, too!

Sure, there aren’t any amazing features like Time Machine to set the world on fire. But the Snow Leopard update is still a slam-dunk for any Intel-based Mac user! My Late-2007 MacBook Pro will get everything but H.264 acceleration and my 2009 Mac Mini is all set to go!

Updated with Mac Mini and Xserve information. Keep the suggestions coming and test that EFI! Picked up, colorized, and reused (with permission) by the excellent Ed Bott in his ZDNet column!

Note: Some of these links include affiliate codes that help pay for this blog. For example, buying an Amazon Kindle with this link sends a few bucks my way! But I don't write this blog to make money, and am happy to link to sites and stores that don't pay anything. I like Amazon and buy tons from them, but you're free to buy whatever and wherever you want.

© sfoskett for Stephen Foskett, Pack Rat, 2009. | Mac OS X 10.6 “Snow Leopard”: In Our Hands August 28!
This post was categorized as Apple, Personal. Each of my categories has its own feed if you'd like to filter out or focus on posts like this.

Snow Leopard will be here in September, but ZFS and iSCSI are AWOL

Apple wowed its fans and impressed its critics with a successful worldwide developer conference keynote yesterday. Along with much obvious focus on iPhone OS 3.0 and the new speedier iPhone 3GS, the company turned the spotlight on new Mac hardware and the next version of OS X, Snow Leopard. This is a lower-profile OS release than the last two (Tiger and Leopard), as indicated by the lower price ($29) and derivative name. But although there are many few features under the hood, Snow Leopard does little to move the ball forward from a storage perspective. ZFS and iSCSI, two long-rumored features, are notably absent.

Apple first teased both ZFS and iSCSI support back in the Tiger days, and these features were rumored for Leopard but absent on launch. Leopard Server had included read-only ZFS support, but even this level is support is reportedly absent in Snow Leopard. An iSCSI initiator was present in early Leopard builds but never showed up again, even in Snow Leopard. Still, the spread of the iSCSI protocol in the SMB market that has taken to Apple’s server products as well as Microsoft’s successful iSCSI initiator software suggested that an iSCSI initiator might become a Snow Leopard feature, at least in the server version.

Apple’s reduced focus on ZFS is understandable. Although it offers some compelling advantages, especially in server environments, it would bring little to the laptop/desktop market. In fact, ZFS is not really all that useful on the typical end-user Mac, with a single hard disk drive and a raft of removables attached with USB or FireWire. On the other hand, iSCSI support would have been increasingly welcome even in the consumer world as products like Drobo and Iomega add iSCSI as an option. The lack of a built-in initiator marginalizes the Mac in the emerging Ethernet SAN world, leaving vendors like Drobo to go it alone.

© sfoskett for Stephen Foskett, Pack Rat, 2009. | Snow Leopard Is Stingy With The Storage Love
This post was categorized as Apple, Enterprise storage. Each of my categories has its own feed if you'd like to filter out or focus on posts like this.

Snow Leopard is coming - will iSCSI finally tag along?

ZFS wasn’t the only AWOL storage technology in Apple’s OS X 10.5 – early builds of Leopard included a built-in iSCSI initiator. When the operating system was finally released in October of 2007, both ZFS and iSCSI were quietly dropped, making room for 300 other features Apple felt were more prime-time-ready.

With the next major OS X release, 10.6 “Snow Leopard”, just around the corner, many have wondered if iSCSI will join the reanimated ZFS support. Sadly, there has been no word from Apple on the fate of their iSCSI initiator. But silence does not necessarily tell a tale at the always-circumspect company, so hope springs eternal for the iSCSI faithful. If the rousing success of Microsoft’s iSCSI initiator is any indication, Apple is seriously missing out!

In the mean time, those seeking iSCSI connectivity within Mac OS X do have third-party options to consider:

• Studio Network Solutions offers a free (as in beer) iSCSI initiator for OS X Tiger and Leopard. The globalSAN iSCSI Initiator is the client-side portion of their SANmp storage sharing solution, and purports to support most of the required protocols. In practice, however, the company cannot support other targets than their own. globalSAN failed to mount any LUNs from my Windows Storage Server iSCSI test rig, and reports claim mixed results from EqualLogic and EMC SANs besides.
• ATTO Technology sells a commercial iSCSI initiator for OS X, Xtend SAN, and reports here are very favorable. Although the $195 price puts it out of reach for home users, corporations wishing to connect Leopard systems to an iSCSI SAN should look no further.
• Another commercial option is SmallTree Software’s abcSAN. Listed at $150, abcSAN lists EqualLogic among its functional targets, but the standalone initiator is nowhere to be found on SmallTree’s web site. They also have an ATA-over-Ethernet (AoE) solution for the true nerds in the audience!
• Ardis may also sell an iSCSI initiator for OS X.

All in all, iSCSI on OS X is in a sorry state of affairs. If only Apple had released the initiator seen in early Leopard builds! Let’s all hope Snow Leopard brings iSCSI to the party at last!

© sfoskett for Stephen Foskett, Pack Rat, 2009. | Will Snow Leopard Finally Bring iSCSI To The Mac?
This post was categorized as Apple. Each of my categories has its own feed if you'd like to filter out or focus on posts like this.