public inbox for linux-xfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Linda Walsh <suse@tlinx.org>
To: SuSE Linux <opensuse@opensuse.org>
Cc: Sujit Karataparambil <sjt.kar@gmail.com>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: grub no longer being maintained? so Suse drops support for XFS boot?
Date: Thu, 11 Jun 2009 23:38:52 -0700	[thread overview]
Message-ID: <4A31F7FC.2020508@tlinx.org> (raw)
In-Reply-To: <921ca19c0906112227m2c834808jd62b15d0203fe4e3@mail.gmail.com>


Re: "Grub supposedly unable to start if /boot is on xfs partition,
    So, because grub is broken, XFS is no longer supported as 
    a boot partition by Novell/SuSE. (!)...

Sujit Karataparambil wrote:
> This is an Known Issue. Grub hangs when used With XFS. You could
> Try Lilo instead. But does the same with my experiance.
---
	Weird.  I've been booting from xfs with lilo, and more
recently, 'grub', from suse 7.x up to 11.1.  

	I haven't any recent probs concerning lilo, but I saw this 
same type of issue and a solution in Ubuntu's bug database (though they
encountered this problem 3 years ago and automatically used a
workaround to not corrupt a user's choice of filesystem.

The issue was Grub not being able to write to the root directory
if it is formatted as an XFS partition.  

The response was Ubuntu's workaround (maybe openSuSE could figure out
how they did this...it is open source...and they could adopt their
solution rather than just throwing up their hands and saying they
don't support XFS).

The Ubuntu installer automatically uses lilo in the case where the
root (or boot) file system is XFS.  Thus no ever sees the problem 
grub has with XFS, they simply use the more primitive, but more 
reliable 'lilo' bootloader.

It's a bit weird to see some people at SuSE prefer to work around
a bootloader bug by disallowing user-desired file systems, rather than
by simply using a bootloader that doesn't have the bug.  
I would have thought that most people would have simply chosen to 
Not use a buggy boot-loader and use a more reliable alternative, over
disallowing file-systems that are unsupported by the buggy-boot loader.

Some folks at Suse must have a real 'thing' for 'grub' to rate it's
importance more highly than users' file system choices...

But I would really suggest that OpenSuse follow Ubuntu's example -- 
just use a bootloader that works.  Don't limit file-system selection 
based on the bugs of a bootloader (same would be true if lilo didn't
work with some filesystem and grub did...use the combinations that
work -- to rigidly disallow anything that grub suggests someone needs
to re-examine their priorities.

FWIW, though, I _am_ using grub, with XFS...but if grub broke, I'd 
switch back to lilo in a heartbeat, NOT reformat my boot or root
partition to accommodate the bootloader's bugs de jour.
 
-linda




	

_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs

  parent reply	other threads:[~2009-06-12  6:38 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12  5:00 grub no longer being maintained? drops support for XFS? Linda A. Walsh
2009-06-12  5:27 ` Sujit Karataparambil
2009-06-12  5:49   ` Jason White
2009-06-12  6:13     ` Sujit Karataparambil
2009-06-12  6:38   ` Linda Walsh [this message]
2009-06-12  9:14     ` grub no longer being maintained? so Suse drops support for XFS boot? Jason White
2009-06-12  9:28     ` Matthias Schniedermeyer
2009-06-12  9:44       ` Michael Weissenbacher
2009-06-12 10:16         ` Jason White
2009-06-12 14:28 ` grub no longer being maintained? drops support for XFS? Eric Sandeen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4A31F7FC.2020508@tlinx.org \
    --to=suse@tlinx.org \
    --cc=opensuse@opensuse.org \
    --cc=sjt.kar@gmail.com \
    --cc=xfs@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox