neilw said:One thing I noted from the Wikipedia page was that ZFS is case-sensitive. Would Apple switch to a case-sensitive filing system at this juncture? Would people care?
Doctor Q said:You are correct, as I understand it. Filesystems don't concern themselves with the content of file data, only the access to it.
Well, Apple could base things off of a meta data similar to the Info.plist for Application packages. Store ALL documents, say, in their lowercase forms, but include a tag such as userTypedName and then display that, but do the rest of your operations on the (internally) stored lower case name. Cf Address Book which is displayed as "Address Book", although it's actual file name is "Address Book.app" but in Spanish is displayed "Agenda", and in other languages displayed accordingly. Just switch CFBundleName with user-inputted name.gnasher729 said:Case sensitivity is actually a very, very minor detail in a file system. All the file system has to do: Remember a file name as it was given by a user (a case sensitive file system _must_ do this, a case insensitive file system will do it), check whether two file names are the same or not, and lookup a file with a given name. There is actually very little code involved to handle case sensitivity; less than hundred lines of code to be changed if it is designed properly, plus a rather large table mapping uppercase to lowercase for Unicode. So if Apple has the source code for a case-sensitive ZFS, modifying it to work case-insensitive isn't too much work.
Things like sorting files in alphabetical order are done elsewhere anyway. For example, if you switch the preferred language on your Macintosh to a different language, then the order in which files are displayed in a "File Open" dialog has to change. You wouldn't want to change the way files are stored on your harddisk because the user changes their preferred language (what if you have three users logged in at the same time, using three different languages? )
nagromme said:Either way, I'm curious about the benefits of Solaris over OS X. (And/or the anticipated benefits of the NEXT version of Solaris vs. Leopard.)
kalisphoenix said:So in general, if you're interested in Solaris, buy a used UltraSPARC workstation off eBay for ~$100 and install it
ManchesterTrix said:You don't even have to do that. If you have an x86 or x64 system lying around you can download Solaris for free from sun.com and play with it.
kalisphoenix said:Well, the only benefit of Solaris over OS X that comes to my mind is that,
ManchesterTrix said:You don't even have to do that. If you have an x86 or x64 system lying around you can download Solaris for free from sun.com and play with it.
Ummm ... ZFS is 98% kernel code. Solaris comes from a AT&T System V R4 code base. OS X is a splice of FreeBSD and the Mach micro kernel. The port is far more than trivial. Anything that has to do with kernel primitives will be different. When you say "Unix" you are really talking about Unix user land (shell, common posix Unix commands), not the Unix kernel, which is unique to every major Unix vendor to varying degrees.Rocketman said:BTW porting ZFS will take about a week. It already runs and is debugged under a UNIX. Adding a fancy interface will take another month (v1.0 BFD).
Rocketman
Maybe we both have. Still hoping bousozoku will clarify what (s)he meant by VFS.AlmostThere said:A VFS is already used in OS X. Have I missed something along the road?
Greetings here, l_b. I'm lux over there. That thread's died off since our posts, only mentioning this MacRumors thread. Mostly redundant, with the exceptions from people who've read before posting and bring something new to the topic.learning_bird said:Here are some explanations of ZFS features and benefits taken from the comments made on ArsTechnica ( which was the first to pick up the news )
Demoman said:Either you have not used Solaris, or Solaris has improved greatly. I administrated a 2.0-2.4 system for a few years. The day I moved on was one of the happiest in my life.
Doctor Q said:Just to clarify, SunOS was originally based on BSD, but Sun Microsystems then moved to an AT&T SVR4 base while retaining much of the BSD code too.
Theoretically if the file system cared about the content wouldn't it be slow because it would have to check the content.???bousozoku said:Generally, that's true but IBM's OS/400 has historically had a database for a file system and it did care about the content, piece by piece.
The speed of a filesystem is most limited by the speed of disk reads and writes, so much emphasis is placed on avoiding disk accesses wherever possible. A little extra CPU time in between disk activity should make relatively little difference.slooksterPSV said:Theoretically if the file system cared about the content wouldn't it be slow because it would have to check the content.???
kalisphoenix said:There is absolutely not one single facet of its existence in which it beats out OS X, as far as end users are concerned.
Les Kern said:My partner and I just developed an app that uses 448-bit encryption, and struggled to make the WIN end work properly just BECAUSE of "big endian" - "little endian" issue. It added a lot of extra code that I felt wasn't REALLY needed... we may have to sepaprate the platforms as it matures.
I wish interoperabilty were the norm.
I would have thought this could be done independently of any major OS revision. The file system is already in production in another OS and the source is open - and as you note the UFS and FAT32 file systems reflect an underlying modular ability to choose file systems.Marble said:Would integrating ZFS into Mac OS X be very difficult? They seem to have added support for UFS and, if I remember correctly, FAT32 without much major renovation to the kernel (not that I would know, but it seemed easy enough). Would it be any harder to add ZFS to the Mac? If not, why couldn't this be done by the time 10.5 is released?
ktlx said:I agree. Until Solaris 2.5.1, it was a horrible piece of junk. Even after that, I was never really happy with Solaris until Solaris 8 (i.e. Solaris 2.8). For quad processors and up, I don't think there is a better UNIX OS.
VFS means Virtual File System. It is an overarching file system framework that allows any specific file system to be treated as a plug-in beneath it. To an application, all file systems supported under VFS are accessed through its interface. Essentially, there's only one file system door into and out of the OS kernel, instead of a separate door for each file system supported (HFS+, NTFS, FAT32, HSFS, UFS, ...).sjk said:Maybe we both have. Still hoping bousozoku will clarify what (s)he meant by VFS.