David Brown wrote:
On Sun, Aug 10, 2008 at 02:11:50PM -0700, Andrew Lentvorski wrote:
Because a full restore *never works*. Invariably, when you need a
full restore, you don't have the same hardware. When you do the full
restore, the OS craps its pants because something changed.
What brain damaged OS is that?
Linux, TYVM.
The worst I could imagine is needing to use a fresh kernel. But, since
I can boot from a rescue disk, chroot into the new machine and pretty
much fix anything, it shouldn't be a problem.
Uhh, that doesn't count as a "restore" then. In fact, "fixing things
up" is often more work than just reinstalling. Especially if you have a
well automated install process.
Only in the land of Linux would "rescue disk, chroot, recompile modules,
and update the kernel" be considered part of a "restore".
Those are the kind of days that make me long for 20+ year old operating
systems like VMS.
-a
--
[email protected]
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-list
