Leopard Pics

[giza]

And I'm talking about OS/X Leopard, due out next Spring. Here are some pictures of their banners from the WWDC. (Originally seen at http://www.engadget.com/2006/08/07/apple-mac-pro-hands-on/ and http://www.engadget.com/2006/08/07/live-from-wwdc-2006-steve-jobs-keynote/)













One new feature of Leopard is "Time Machine", also known as "rsync with a graphical front end". It offers version control, the ability to "go back in time", and the ability to automatically store data offsite on a central server. It looks pretty cool, and I'm glad that there's finally going to be version control integrated with the OS.





"Spaces", also known as "virtual desktops" for those who have used X Windows is another UNIX tradition that I'm glad to see in OS/X.




Woo!

Comments

[thefoxes.livejournal.com]

Systems 6 through 8.1 never ever crashed. :p Nowadays you have to have Applecare or else.

[giza.livejournal.com]

Again, I will say: huh?

AppleCare is mainly about the hardware. You don't NEED AppleCare to deal with any software issues that come up. Not that I've had any come up. At least not with OS/X itself.

[wildw0lf.livejournal.com]

And most software issues I've seen were actually caused by one of several issues:

1. Corrupt file permissions, in which case you run repair permissions, and repair disk.

2. Random OSX crashes, which is usually caused by bad blocks on the hard disk.

3. If you value your data NEVER RUN File Vault. If you decide to turn this on, and your hard drive develops bad blocks and/or fails to boot completely into MacOS X, you CAN NOT use Target mode to recover the data, as the files have been encrypted, and the drive will not show.

[giza.livejournal.com]

I don't think I've ever seen #1 happen. I can't even figure out HOW this happens in the first place. Unless a user manually started playing with permissions on system files.

No argument on #2. Bad blocks will kill just about anything.

I'm in agreement on #3. It's a cool idea, but causes substantial risks that users might not be aware of.

[rustitobuck.livejournal.com]

You can still mount the FileVault sparse image in target mode. When you're not logged in, it's in /Users/user/user.sparseimage, and if you crashed while logged in, it's in /Users/.user

The password for the sparseimage is your login password.

If a block in the sparseimage is corrupted, well, that's the same as having a corrupt block in a file anyway. Backups are a good idea.

Sparseimages were kinda risky back in, oh, 10.2 days, but they've been pretty solid for me.