Well, I was puzzled. All file systems are created equal under unix.
I've been using unix variants since 1992, and unix as a whole doesn't
care where the file system is, on hd, across the world, or in the
next room. That's why I was wondering why this program was necessary.
I've since done some digging, and it appears OSX does make a
distinction of some sort. Since this program uses a kernel extension
to solve the problem, I'm guessing it has to do with the way block
devices are presented to the os. I'm still convinced it's possible
to get around it without resorting to extra programs, but apparently,
if anyone has figured it out, they're keeping it quiet. :)
So, sorry for the trouble.
I was honestly puzzled why the need of such a program existed, but I
see now it actually is, at least until someone figures out how to
solve the problem without resorting to kernel extensions.
<--- Mac Access At Mac Access Dot Net --->
To reply to this post, please address your message to mac-access@mac-access.net
You can find an archive of all messages posted to the Mac-Access forum at
either the list's own dedicated web archive:
<http://mail.tft-bbs.co.uk/pipermail/mac-access/index.html>
or at the public Mail Archive:
<http://www.mail-archive.com/mac-access@mac-access.net/>.
Subscribe to the list's RSS feed from:
<http://www.mail-archive.com/mac-access@mac-access.net/maillist.xml>
The Mac-Access mailing list is guaranteed malware, spyware, Trojan, virus and
worm-free!
Please remember to update your membership options periodically by visiting the
list website at:
<http://mail.tft-bbs.co.uk/mailman/listinfo/mac-access/options/>
