10.2.2 out in three weeks.
Here is the link.
<a href="http://www.eweek.com/article2/0,3959,634711,00.asp"; target="_blank">http://www.eweek.com/article2/0,3959,634711,00.asp</a>;
<a href="http://www.eweek.com/article2/0,3959,634711,00.asp"; target="_blank">http://www.eweek.com/article2/0,3959,634711,00.asp</a>;
Comments
<strong>Here is the link.
<a href="http://www.eweek.com/article2/0,3959,634711,00.asp"; target="_blank">http://www.eweek.com/article2/0,3959,634711,00.asp</a></strong><hr></blockquote>;
Intersting: The article said a jouraling file systems is part of this version.
Journaling and metadata aren't tied together, particularly when you have a nice layered file system stack like OS X's Virtual File System.
Note that this runs *on top of* HFS+. They just created a journaling file filter.
'Just', I say, tongue firmly in cheek. Kudos to the Fruit Guys.
I can confirm that journaling is in the 6F-betas that are seedet to developers.
Run 'diskutil' and see for yourselves.
<strong>Probably nothing.
Journaling and metadata aren't tied together, particularly when you have a nice layered file system stack like OS X's Virtual File System.
Note that this runs *on top of* HFS+. They just created a journaling file filter.
'Just', I say, tongue firmly in cheek. Kudos to the Fruit Guys.</strong><hr></blockquote>
Right. My point being that if "just created" is tongue in cheek, then clearly it was a big task, no? Does that preclude the possibility of Dominic having been working on metadata simultaneously, or did that take a backseat to journaling work?
<strong>Probably nothing.
Journaling and metadata aren't tied together...</strong><hr></blockquote>
Ever since Rhapsody was promised (as the successor to OS 7.5 then), Apple has been working on adding journaling AND metadata to their filing structure. In Apple's mind, the two have always been tied together - and the reason why Labels hasn't been available in OSX hitherto, as you yourself pointed out.
Now it's going to be a totally different ballgame, and the virtualization of data structures can finally be released: linking data according to the individual user's associations, doing common-language search, using sound or pictures as tags and search criteria, etc
Not only will this add enterprise-strength security and stability to OSX, it will give user-intuitivity to the present-day way of computing: finding and experiencing data. Scoring in two very different ballgames with one swat!
Apple is finally getting ahead of MS, in the area it has lost the most: operating system usability. But why does it come so quickly? why not keep it until the next MAJOR release? Interesting....
engpjp
<strong>
Apple is finally getting ahead of MS, in the area it has lost the most: operating system usability. But why does it come so quickly? why not keep it until the next MAJOR release? Interesting....
engpjp</strong><hr></blockquote>
Well you have to turn it on via CLI, I would guess that it will be easier to turn on in 10.3, not to mention more fine tuned... WWDC 2003 should be good...
<strong>the performance hit doesn't sound so cool <img src="graemlins/hmmm.gif" border="0" alt="[Hmmm]" /> </strong><hr></blockquote>
Funny, I and others, say on /., have read that as a 10-15% performance hit on *disk access*, not on overall system performance. Huge difference.
As for the performance hit... 10-15% hit, that's all?! Wow! Stellar acheivement! Kudos to the X-B guy and Apple team who worked the magic.
<strong>From this discussion, I get an idea of what a journaled fs is, but could someone explain it to me? Why is it good?</strong><hr></blockquote>
Journaled filesystems keep track of what changes are about to be made to files, and what changes *have* been made to files.
This gets you robustness (less file corruption - in fact, darned near impossible at the filesystem level), speed (no more waiting for fsck to check your entire system at startup if anything went wrong), and in many implementations, a history (roll back changes to a file to a previous version).
The best explanation I've seen was on Slashdot, which I'll paraphrase here:
Imagine a library, and each night a librarian goes around with a stack of books and puts them back on the shelves. At the end of this task, she writes down in the log all the books she put back.
Now, one night, in the middle of this task, she has a heart attack.
How is the replacement librarian supposed to find all the books that were put back? They'd have to check each and every book in the library against the 'checked in and put back' list, and all those not on the list would be the ones that the dead librarian had done that night.
Now imagine instead that the first librarian carries a notepad around with her, with a list of the books to be put back that night, and as she puts each one back, she marks it off the list.
Now, when she keels over, the replacement just has to look at the notepad.
That's a journaled filesystem. It keeps detailed track of changes to files before and after they occur.
Filesystem corruption is extremely difficult to have happen, and if it does, it's easy and quick to fix. You can literally pull the power cord in the middle of a large file write with a journaled filesystem, and when the power comes back on, it will continue the write, and you'll be on your way.
[quote]<strong>How will it help w/ searches?</strong><hr></blockquote>
It won't. It has NOTHING to do with file metadata, regardless of what some folks are saying.
I don't have sufficient expertise, however, to judge whether it is a good move for Apple to hang on to the HFS+ format as basis for the future plans (there are those that call HFS+ "antiquated" and "inefficient"), and I have no information as to whether the programmers have managed to structure "Elvis" etc so that they will be able to slide a new FS "underneath" it at a later date...
engpjp
Elvis Filing System