On Tue, 2008-02-26 at 10:46 -0500, Przemek Klosowski wrote:
> > The big advantage of a separate /boot partition in Jay Hart's case is
> > that it can be shared between multiple OS versions that otherwise have
> > distinct filesystems, which simplifies the grub.conf setup: all
> > entries refer to different vmlinuz/initrd entries on the same boot
> > partition.
> And if Distribution B says: We OWN /boot so WIPE all "TRASH" currently
> sitting there. You then lose the ability to easily boot/recover your
> other operating systems.
> On our critical systems we have a duplicate of the /boot partition on
> a different disk, so that we can still boot up in case of a hardware
> or software failure. This requires manual intervention of course.
> Of course your setup with chainloaders is cute, too, and I like the idea
> of a readily-available rescue, except I did set up a net boot server and
> boot into RIP from across the net.
> I do recommend having either local or remote memtest: assuming you
> have the memtest image in /boot, the GRUB entry is simply
> title memtest-3.1a
> root (hd0,0)
> kernel /memtest31a
And it still fits in under 80 megs since "memtest 31a" is included on
the RIP ISO.
And yes I do set up a local "Trivial File Transfer Protocol server"
using the attached default file and files from the site and a few other
The "local recsue/install real boot partition" is real handy for the
server and traveling laptops.
With the addition a "grub.exe" (also from the RIP CD) i can rescue
almost any i386 based laptop that can be attached to my local net.
Description: Text document
Ma-linux mailing list