Jobs was pissed at losing his thunder
Jobs was pised sun stole his thunder about ZFS so did not talk about it. Seems to fit pretty well in to Jobs MO. Rember ATI rage leak anyone?
Apple has apparently admitted its next operating system will utilize Sun Microsystems’ ZFS encrypted file system, contradicting earlier denials. In a display of corporate left-hand/right-hand syndrome, Apple has reportedly confirmed comments made by Sun’s chief executive Jonathan Schwartz last week that Sun’s 128-bit ZFS for …
Is ZFS case-sensitive? If so, it would be a great improvement on HFS and would mean that the standard unix tools actually work correctly instead of getting confused over whether they think a file exists or it doesn't depending on whether or not Apple have got round to hacking that particular util to make it case-insensitive aware.
Oh, and if it would not randomly change the case of a filename from lower to upper case then that would be dandy too!
God I HATE my Mac!
They've written lots of the plumbing for OS X themselves but the important thing is that taking in proven and stable software is often a lot better than writing everything from scratch. Other OS well known software houses have tried that and come up with buggy beta-quality software claiming it to be final.
Apple is really doing the right thing by mixing home-brewed software with proven stuff made by others and this is why they can release a major new OS release, that is stable, so often.
A little more data: Apple now says that ZFS will appear in Leopard but it will be read-only, at least for the moment.
And as for case-sensitivity... yuch. The single dumbest idea I've heard in a long time. The only reason to have case-sensitive filenames is so that you can have 'Readme.txt' 'README.TXT' 'readme.txt' and 'ReAdMe.TxT' in the same directory. Which is an abomination.
Computers are supposed to do things for the convenience of their operators, not the other way around. All of the positive aspects to case-sensitive filesystems are for the computer or the programmer, not for the operator.
Reminds me of a Linux program I once worked on. I was talking to the original author and he said 'Okay, take a look for that in the something.h header file' (I can't remember the real name). So I typed 'vi something.h' (in the project/headers directory) and it opened a file. I said 'I don't see that definition in there,' and he said, 'Oh, it's probably in the capital-something.h'. I said 'What?' and he said 'Try SOMETHING.h, all caps'. Yup, it was in there. He had decided to split the rather long 'something.h' into two files and claimed that this was easier to remember even than 'something1.h' and 'something2.h'.
Oh, and you should have seen the variable names.
I quit the team shortly thereafter.
The ONLY difference between a volume/partition that is formatted as CS or Non-CS is a flag in the directory. Since a Non-CS partition can NOT have file names that would be duplicates if rendered as all lower case, all that SHOULD be needed to go from Non-CS to CS is to flip the flag and update an in-memory tables that show the CS/Non-CS status. An attempt to convert a CS partition to Non-CS is harder and would actually need for the partition to be unmounted (to prevent adds/deletes) while the directory is scanned for duplicate Non-CS file names before the flag is reset or an error message was issued.
Biting the hand that feeds IT © 1998–2021