Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!


Click here to return to the 'Create bootable clones via the command line' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Create bootable clones via the command line
Authored by: daveschroeder on Sep 21, '04 10:13:32PM

No, that's only if you're using asr to build a distribution image; most of the removals are recommended but not necessary, by any means, and the desired removals only apply when the image is to be used on entirely different hardware than that on which the image was created, and to work around problems that occurred in earlier versions of Mac OS X.

Simply cloning a volume for use as a writable backup on the same machine does NOT require ANY cleanup, at all, since the OS is to be used on the exact same hardware. Since this article speaks to remote backup, it is inferred that it is to be used on the same machine. The only required cleanup in *any* scenario is BootCache.playlist and volinfo.database, and that's only if you're making an image. And even then, it's still not required, because since 10.2.1, BootCache.playlist and volinfo.database will get properly recreated on any hardware, and all swapfiles will ALWAYS be recreated.

My original post is completely accurate. Yes, definitely follow the documentation, but in this case, the cleanup you speak of does not apply to a volume-to-volume clone: it applies to "a disk image for restoration on another volume".

The example stated for volume cloning (NOT disk image creation) in the man page is:

Volume cloning:
sudo asr -source /Volumes/Classic -target /Volumes/install



[ Reply to This | # ]
Create bootable clones via the command line
Authored by: osxpounder on Sep 22, '04 12:37:13PM

So, if I backup my HD using dave's shorter plan, then change my hardware, I risk not being able to restore from my backup?

---
--
osxpounder



[ Reply to This | # ]
Create bootable clones via the command line
Authored by: daveschroeder on Sep 23, '04 09:47:08AM

No, I have used that exact method hundreds of times on everything from laptops to Xserves to Power Mac G3, G4, and G5 and everything in between, and have NEVER had any issue or anomaly. That's exactly how it's supposed to work, and is perfectly in accordance with the documentation (see my previous post).

The ONLY time ANY cleanup is recommended is if you are making a distribution IMAGE. Swap is deleted to save space, and the volume info stuff was deleted because it could cause kernel panics under certain conditions on different hardware on earlier versions of Mac OS X, but that has all been resolved, so even that doesn't matter any more.

The only command that is needed for any type of hardware (ASSUMING the hardware supports that particular version of Mac OS X[1]) is the single asr command I've described above. Same goes for rsyncx.

[1] Example: the iMac G5 comes with a NEWER version of Mac OS X 10.3.5 (7P35) than the "normal" 10.3.5 (7M34). You wouldn't be able to take a 7M34 clone and boot an iMac G5 with it. When the next point update, e.g., 10.3.6 (if there is a 10.3.6) comes out, it will consolidate all of the updates, making 10.3.6 universal again...until the next new hardware comes out. This is ONLY an issue for new hardware that has a special build of OS X for new hardware support. Other than this specific exception, an install of Mac OS X is always universal, and can be used on everything from an iBook G3 to a Power Mac G5. And even in the case of the "special" builds, if a universal image is desired, it's standard practice to simply use the newest build - even "updating" over an existing installation with the new build is acceptable.



[ Reply to This | # ]