From: "Arkadiusz Miśkiewicz" <arekm@maven.pl>
To: xfs@oss.sgi.com
Subject: Re: Which xfsprogs version to which kernel version
Date: Wed, 2 Dec 2015 18:07:47 +0100 [thread overview]
Message-ID: <201512021807.47703.arekm@maven.pl> (raw)
In-Reply-To: <565E826D.6040301@sandeen.net>
On Wednesday 02 of December 2015, Eric Sandeen wrote:
> >> How about just checking running kernel version before enabling this by
> >> default?
> >
> > The btrfs solution? No thanks.
>
> Another option is to export features the running kernel can handle in
> sysfs & mkfs accordingly - but then somebody mkfs's under one kernel,
> boots another kernel, and gets different mkfs's, possibly fails to mount,
> etc... magically changing defaults is a nightmare. yeah, at some point
> you have to realize that you cannot save everyone from themselves. ;)
Don't change default. Warn instead about mkfs using feature not supported by
current kernel.
> >> While this is some implementation effort, it may help to reduce
> >> questions on this mailing list. And as you see distro problem or not:
> >> People still ask here. :)
>
> Like Dave said - not very often at all.
Had one complain about the problem on pld lists.
> -Eric
--
Arkadiusz Miśkiewicz, arekm / ( maven.pl | pld-linux.org )
_______________________________________________
xfs mailing list
xfs@oss.sgi.com
http://oss.sgi.com/mailman/listinfo/xfs
next prev parent reply other threads:[~2015-12-02 17:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-26 10:21 Which xfsprogs version to which kernel version aluno3
2015-11-26 12:26 ` Emmanuel Florac
2015-11-26 13:18 ` aluno3
2015-11-26 13:50 ` Brian Foster
2015-11-26 14:36 ` aluno3
2015-11-27 15:22 ` Brian Foster
2015-11-30 8:37 ` aluno3
2015-11-30 9:51 ` Carlos Maiolino
2015-11-30 21:41 ` Dave Chinner
2015-12-01 8:30 ` Martin Steigerwald
2015-12-01 20:26 ` Dave Chinner
2015-12-02 5:32 ` Eric Sandeen
2015-12-02 17:07 ` Arkadiusz Miśkiewicz [this message]
2015-12-02 21:14 ` Dave Chinner
2015-12-03 16:29 ` 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=201512021807.47703.arekm@maven.pl \
--to=arekm@maven.pl \
--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