I had smashing success migratingraid volumes to a new motherboard by
building a readonly loopback boot-cd rootfs volume, and using
cp -sr /mnt/rescue /mnt/newroot
before building stage2,3; with minor /etc grumbling, the system
bootstrapped flawlessly while still borrowing a few sensitive static
utils where combinations of kernel, gcc and libc could otherwise wreak havoc
I'm very happy with new GUID-based volume mounting and more stable raid
tools, but a CF-based or initrd root available when /lib goes to hell is
an absolute must for supporting fault tolerance.
Chris Gianelloni wrote:
On Tue, 2005-05-17 at 10:33 -0700, Donnie Berkholz wrote:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Chris Gianelloni wrote:
A much better approach would be for there to be a rescue build,
completely independent of the stages, since it doesn't need to mirror
them in any way. It should be extracted (self-extracted?) to something
like /rescue and executed from there, being completely self-contained.
This keeps it from stomping on system files and breaking
collision-protect or doing anything else nasty like hosing configuration
files (ever made the mistake of extracting a stage onto a live
filesystem?) when unpacked.
This sounds a lot like saying, use an initrd, but when you pivot roots
to the live filesystem, leave it mounted somewhere.
Kinda... This wouldn't require a reboot, though. When the user is done,
they simply rm -rf /rescue and their system is clean again.
--
gentoo-dev@gentoo.org mailing list
