I know it's a pain, but you have to spend money to download Apple's betas, that is, pay their developer fee. If, however, this might inspire you to do this, you should know that zfs will run (read and write) on the latest build of Leopard, as Apple has (somewhat cryptically) said. Apple also has a "non-disclosure" clause on their developer memberships, but they appear to have already made a number of public statements about zfs in Leopard. So, here's a generic (and clumsy) way to enable kernel extensions on a BSD system, of which Leopard is a variant (actually, it runs over a version of Darwin). And zfs is a kernel extension, and can be loaded like any other. The zpool and zfs commands below you already know if you follow this thread.
Try this in terminal: % cd /System/Library/Extensions % ls -alF | less # This will show you all the kernel extensions, *.kext, in a pager [hit the space bar to page forward; on the last page you should see: ... drwxr-xr-x 3 root wheel 102 ... ntfs.kext/ drwxr-xr-x 3 root wheel 102 ... smbfs.kext/ drwxr-xr-x 3 root wheel 102 ... udf.kext/ drwxr-xr-x 3 root wheel 102 ... webdav_fs.kext/ drwxr-xr-x 3 root wheel 102 ... zfs.kext/ (END) # hit "q"; this gets you back to the terminal ... If you see zfs.kext, then the installer did indeed put it on your system. Then: % sudo kextload zfs.kext password: # enter your admin password; if that doesn't work, become root with su You will get some error messages about the cache, probably from the files Extensions.kextcache and Extensions.mkext. But, zfs will load (at least it will on a G5 dual 2.7). zfs, zpool, now work, and man zfs, man zpool will give you a man page. As far as I can tell, this is the process to load a kernel extension on any BSD system, of which Mac OS X/Darwin is one (the others are FreeBSD, NetBSD, OpenBSD). HOWEVER, be aware that finder in almost any version of OSX tries to automount every possible file system. Leopard does this as well; unlike zfs and zpool under Solaris, Leopard automounts any pool created or imported with zpool, and sets the mountpoint under /Volumes, WITHOUT running zfs create, or set mountpoint: % zpool create zpool01 disk1 Automatically mounts in the finder and has the directory: /Volumes/zpool01 Again, this happens WITHOUT RUNNING zfs, which is quite different from Solaris. You will have to fiddle with permissions, and you might have to do something like: sudo chmod -R /Volumes/zpool01 a+rwx to make the entire pool writable (or some variant, g+rwx, etc.). But it will work. I haven't tried using zfs quota, set mountpoint=, set share=, but set compression=on seems to work, but I don't see much compression going on. On reboot (or after a crash, which is frequent on beta builds) the finder will, initially, not have the zfs kernel extension enabled, and will ask if you want to format the disk (or slice, or however you set it up). Click "ignore"; DO NOT FORMAT THE DISK. zfs already has, but the finder doesn't know it yet. Repeat the kernel extension commands above. Then run: zpool import -f poolname You can also try zpool scrub, but I'm not sure if that helps. You should have all the files you copied on the zfs system before the crash (but no promises; mine were, but maybe yours will not). You can try "safe boot" with Leopard (hold down the shift key on boot), and that might disable some problematic kernel extensions. If someone knows how to modify Extensions.kextcache and Extensions.mkext, please let me know. After the bugs are worked out, Leopard should be a pretty good platform. Hope this helps. G.W. This message posted from opensolaris.org _______________________________________________ zfs-discuss mailing list zfs-discuss@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
