On Sunday 09 May 2004 23:31, Eben King wrote:
> OK, I hosed my system tonight, but got it back. I have two identical hard
> drives, and every night I copy one to the other with a cron job. I tried
> to compile a module tonight (reiserfs.o), and wound up with a system that
> stopped its boot early, complaining about an unrecognized symbol in some
> module (I forget which one). I recovered it by copying the entire
> /lib/modules/2.4.22 hierarchy from the backup to the original. Yay, the
> backup proved its worth. Now, if I hadn't rebooted (and uncovered the
> error) and the backup was remade with the faulty module, I'd have been
> screwed.
>
> What is the "correct" (i.e., nondestructive) way of recovering from such a
> situation? Reinstalling the distribution would be destructive, as there
> are copious files I've changed.
You are essentially doing it. You use one hard drive for fiddling and the
other contains the stable binaries.
This archive was generated by hypermail 2.1.3 : Fri Aug 01 2014 - 20:29:07 EDT