From: Michael Weissenbacher <mw@dermichi.com>
To: Matthias Schniedermeyer <ms@citd.de>
Cc: Linda Walsh <suse@tlinx.org>,
Sujit Karataparambil <sjt.kar@gmail.com>,
SuSE Linux <opensuse@opensuse.org>, xfs-oss <xfs@oss.sgi.com>
Subject: Re: grub no longer being maintained? so Suse drops support for XFS boot?
Date: Fri, 12 Jun 2009 11:44:23 +0200 [thread overview]
Message-ID: <4A322377.5020403@dermichi.com> (raw)
In-Reply-To: <20090612092825.GA16974@citd.de>
Hi!
> OTOH as long as you can live with a separate boot-partition, what's the
> problem of formating it with ext2. fsck-times for a single/double-digit
> MB boot-partition are negligible.
I've always been using a small seperate ext2 Partition for /boot, since i've found this to be the most robust solution. Also when other Filesystems like reiser4 or btrfs come in play. I'd say XFS support in Grub is nice to have, but not a must.
Maybe the distributions should just default to an ext2 Partition for /boot. That would keep most people happy, wouldn't it?
just my 2c
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2009-06-12 9:44 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 ` grub no longer being maintained? so Suse drops support for XFS boot? Linda Walsh
2009-06-12 9:14 ` Jason White
2009-06-12 9:28 ` Matthias Schniedermeyer
2009-06-12 9:44 ` Michael Weissenbacher [this message]
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=4A322377.5020403@dermichi.com \
--to=mw@dermichi.com \
--cc=ms@citd.de \
--cc=opensuse@opensuse.org \
--cc=sjt.kar@gmail.com \
--cc=suse@tlinx.org \
--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