Christian Trefzer wrote:
On Mon, Aug 07, 2006 at 01:09:42PM -0400, David Masover wrote:
Christian Trefzer wrote:
Few people keep a 32MB ext2 for /boot purposes these days, so it
really is imperative that grub can read kernel images off a reiser4
/.
I think there are patches, but I do keep a 32 meg ext3 for /boot,
because it seems like no matter what FS I choose, there's some sort of
caveat involving Grub. I know when installing XFS as a root FS on
Ubuntu, it talks about Grub problems...
New installations is what I had in mind there. People see they could use
something fancy, but their bootloader-du-jour won't take it. Bummer. The
warning message is the only thing keeping folks from running into a
broken installation. No good.
A warning isn't good? Would you rather it be an error? Some people
would like to test Grub's XFS support...
It's not necessarily broken, just potentially unreliable, and difficult
to work with (you have to set arcane mount options or somesuch). Same
for ReiserFS3, by the way.
Really, while Grub is useful, it's a rather large duplication-of-code
effort. XOSL is even moreso, especially considering it doesn't support
Linux or multiboot natively -- it must boot Grub or Lilo in order to run
Linux or HURD. Why aren't we using kexec for this already?
I mean, having Grub support everything would be nice, but if you're
reformatting anyway, I don't think it's that imperative.
Yeah, _if_ you are s.o. who knows how to turn a partition table upside
down without losing a single bit of data.
It's called "backup and restore." Or did you have a different idea for
how to convert an existing installation to another root FS, or do a
fresh installation without nuking your partitions anyway?
