Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Lets hope there are major changes to core apps!

SL brought rewrites of Finder and Quicktime into 64 bit Cocoa, perhaps its finally time to bring iTunes, iLife, iWork etc up to date :)

Lets hope

Some UI improvements will be most welcome.

Dont know what else can be brought over from iOS...we already have QuickTime and Core Location...what else is there? FaceTime into iChat would be a given....
 
How about making Time Machine BOOTABLE. That way if your internal HD dies, you can boot off your external HD until you get your internal HD replaced. Then you can backup your new internal HD with Time Machine again. Then boot off your new internal HD and never really skip a beat.
 
How about making Time Machine BOOTABLE. That way if your internal HD dies, you can boot off your external HD until you get your internal HD replaced. Then you can backup your new internal HD with Time Machine again. Then boot off your new internal HD and never really skip a beat.

That is why I use Carbon Copy Cloner.
 
How about making Time Machine BOOTABLE. That way if your internal HD dies, you can boot off your external HD until you get your internal HD replaced. Then you can backup your new internal HD with Time Machine again. Then boot off your new internal HD and never really skip a beat.

Anyone can "make Time Machine bootable" in a sense. Simply install Mac OS on the same volume (or on another partition of the same disk) that the Backups.backupd folder lives on.

Naturally, this requires that the backup disk itself must be bootable in the first place: i.e., the filesystem needs to be of the HFS+ flavor (which Time Machine already necessitates), as well as being initialized with a GUID partition scheme (which Intel Macs already necessitate)... and, it needs to be directly connected to the Mac via FireWire or USB. (i.e., we cannot boot off some disk image file sitting on a NAS, or a Time Capsule over Wi-Fi).

Simply put: if the backup disk being used is bootable to begin with, then just install Mac OS on it. (i'd recommend using the actual system dvd to do that, just as we would to install to our hd... but cloning might also work).
 
Anyone can "make Time Machine bootable" in a sense. Simply install Mac OS on the same volume (or on another partition of the same disk) that the Backups.backupd folder lives on.

Naturally, this requires that the backup disk itself must be bootable in the first place: i.e., the filesystem needs to be of the HFS+ flavor (which Time Machine already necessitates), as well as being initialized with a GUID partition scheme (which Intel Macs already necessitate)... and, it needs to be directly connected to the Mac via FireWire or USB. (i.e., we cannot boot off some disk image file sitting on a NAS, or a Time Capsule over Wi-Fi).

Simply put: if the backup disk being used is bootable to begin with, then just install Mac OS on it. (i'd recommend using the actual system dvd to do that, just as we would to install to our hd... but cloning might also work).

CCC, Déjà vu and SD backup programs just clones your bootable HD onto another empty HD to start with. There's no installing of the Mac OSX required on the empty HD. Just make sure that your empty HD is formatted correctly and that's it.

I see no reason why Time Machine couldn't do all of that too.
 
My Wish list for the update:

1. OS 10.7 (Lion) of course!!
2. New macbook airs? maybe ones with an iOS overlay in place of dashboard and a 11.1 in touchscreen - so you could pretty much use it as a "docked" ipad.
3. New macbooks (either using the new sandy bridge, or speed bumped)
4. Possibly a smaller iPad? (to give the Air it's rightful place in the line)
5. Will we see TRIM support for SSD's in 10.7?

Fingers crossed :) any comments/criticisms accepted :D

:apple: forever, Death to Windows.


EDIT: of course, a new iLife and iWork ('11 version) are expected :)
 
CCC, Déjà vu and SD backup programs just clones your bootable HD onto another empty HD to start with. There's no installing of the Mac OSX required on the empty HD. Just make sure that your empty HD is formatted correctly and that's it.

I see no reason why Time Machine couldn't do all of that too.

Because...
  • Cloning is inferior to installing (just count the the threads where clones fail to boot and/or especially they often fail to be able to repair the original disk when booted from the clone).

  • And because cloning copies tons of stuff we don't need for an emergency boot partition (docs, iPhoto, Thai fonts, Cannon printer drivers, Garage Band audio samples). Waste of time and space.
Better to just custom install an ultra-clean stripped down OS for emergencies... add DiskWarrior and forget the rest.

The proper tool for installing is Installer.app. If one must clone (not the best idea for emergency booting, but), then Apple provides Disk Utility... or, use one of the other apps you just mentioned.

Time Machine is already doing some very sophisticated and specialized stuff. There's absolutely no call to clutter its interface with functions that already exist in (seemingly) a zillion other places.

BTW, whether one clones or installs... check it with Disk Warrior at least once and verify that it actually is bootable *and* that we can run repair operations on the original while booted from the clone. [as mentioned, sometimes that doesn't work... because the utility perceives some connection between the two, and refuses to proceed. Yeah... and sometimes it works just fine. If you want a coin toss situation, go with a clone.]
 
How about making Time Machine BOOTABLE. That way if your internal HD dies, you can boot off your external HD until you get your internal HD replaced. Then you can backup your new internal HD with Time Machine again. Then boot off your new internal HD and never really skip a beat.
Let me take another crack at that... because the first time i only tackled bootability in a "one-dimensional" sense.

I totally dig the SuperDuper philosophy. The whole "get right back to work in minutes even though the HD is irrepairably fried and needs replacing" concept is excellent.

But i doubt that concept can always be applied so easily to the depths with which Time Machine might deal. For one thing: inside that Backups.backupd folder may reside backups for several different bootable volumes. [perhaps not a frequent occurrence with basic "one-Mac" owners... but certainly possible in a household of Macs, or even a single user with multiple Macs and/or multiple bootable partitions on each Mac perhaps. (e.g., all my Macs have 2 OS partitions minimum).]

If so... then which of those possible bootable backup volumes should Time Machine choose to make bootable on the backup disk? Nevermind how for now, but which? And then, how would it manage such decisions in a simple fashion? For example, should that pref be easily toggled by any user once set?

Much of the principle behind the technique Time Machine is using *requires* those files to be nestled together in those dated subfolders deep down in Backups.backupd for efficiency. So what you're really asking for is to have it implement two completely different tasks consecutively. (i.e., it would need to constantly maintain 2 "current" backups: one bootable, and one just the way it does now). And should the bootable version be updated every hour as well... or just daily?

Naw. Doesn't seem practical, as the various possibilities start making the overall process too complex (for both user and program). Just let Time Machine do that one thing it does. If a user wants to maintain a separate bootable, fully up-to-date clone (by using a utility other than Time Machine), to prepare for unrepairable disk failures...fine. All the better in fact. Each program to its own purpose.
 
tin-foil_365.jpg
 
You hit the nail on the head - it is woefully underpowered and port starved. For this you have overpaid. Compared to the MBP 13" you've gotten a little less weigh and volume, but the same footprint and only 0.25" less thickness.

The fact is that there are not many people are willing to that that lousy deal, and so the MBA has sold poorly. Thankfully it looks like Apple has come to it's senses and is releasing an actually small machine.
You're missing the point, it is not as poor performance wise as you seem to think- everyday tasks run very well on it, and it is not a little less weight and volume it is a lot less when you are carrying it around on a daily basis. Underpowered and Port Starved? Well the point is that the MBA is aimed at your average person- I have never needed more power or any more ports then it has. The MBP does an excellent job of serving the people that need the power and ports, and the MBA does an excellent job of serving the people that need a light and small machine. Why you think only one has to be good and both can't is beyond me.
 
You're missing the point, it is not as poor performance wise as you seem to think- everyday tasks run very well on it, and it is not a little less weight and volume it is a lot less when you are carrying it around on a daily basis. Underpowered and Port Starved? Well the point is that the MBA is aimed at your average person- I have never needed more power or any more ports then it has. The MBP does an excellent job of serving the people that need the power and ports, and the MBA does an excellent job of serving the people that need a light and small machine. Why you think only one has to be good and both can't is beyond me.

You're missing the point. You're giving up performance and ports, or paying a lot for the performance you get, and getting a machine that isn't that much smaller. Yes it's lighter but it's the same foot print and only 0.25" less than a MBP 13". It's form over function, it's a pointless tradeoff for something that gives the illusion of being smaller with its daft tapering. Hopefully Apple will correct this with the 11.6" form factor.
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.