From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: Compatibility matrix kernel/tools
Date: Fri, 7 Nov 2014 03:38:23 +0000 (UTC) [thread overview]
Message-ID: <pan$d2077$fec7cdea$56b28895$45042d2e@cox.net> (raw)
In-Reply-To: 50788B41-C5FA-40B7-BFE8-008A85AB5669@free.fr
Cyril Scetbon posted on Thu, 06 Nov 2014 10:21:47 +0100 as excerpted:
>>> On Wed, Nov 05, 2014 at 09:57:31PM +0100, Cyril Scetbon wrote:
>>>>
>>>> Where can I find the compatibility matrix to know which btrfs-tools
>>>> version should work with a chosen linux kernel ?
> Thank you guys for this status ! I think you should add it somewhere in
> the documentation cause I'm pretty sure this is a repeated question from
> users.
Looking backward it hasn't been that much of a FAQ, because (despite what
various commercial distros were willing to support for money) as far as
the list was concerned btrfs was experimental (and is currently still not
fully stable), so the very strong recommendation has always been, and
remains now altho the strength of the recommendation is gradually fading
as btrfs stabilizes, that users should always run the latest kernel as
otherwise they are missing fixes for known problems that may well bite
them if they don't.
Similarly but not as critically and with some differences for userspace.
One difference was that until fairly recently userspace didn't have
regular releases, so users of an after all experimental filesystem were
expected to run git snapshots either built themselves and updated
regularly, or from the distro, provided the distro updated their
snapshots at least a couple times a year. Older versions were mainly
missing features for the online stuff (as Chris mentioned), and users
were told they'd obtain best results for the offline stuff with current
live-git (where the master branch was and is release-maturity-only code)
or with specific testing patches.
Looking forward, however, as btrfs matures and stabilizes and as part of
that process the btrfs community and documentation begins to accommodate
users who routinely run years outdated code for the stability, and who
expect to do the same thing with btrfs, this question is as you
suggested, certain to BECOME a FAQ.
So adding it "somewhere", with the most appropriate initial "somewhere"
likely being the user documentation section FAQ on the wiki, is indeed a
good idea.
But it's a wiki and as such the expectation is that users themselves do
the editing. Go right ahead. Chris Mason's authoritative explanation's
a great start. =:^)
OTOH if you're like me you're more comfortable on the list, and editing
the wiki is a big hassle. The information will probably get there
eventually either way, but if you do it you make sure it's done /now/,
not whenever someone else gets to it. So if you are comfortable updating
the wiki, by all means do so, but if not, well, I've never done so
either, so...
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
prev parent reply other threads:[~2014-11-07 3:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-05 20:57 Compatibility matrix kernel/tools Cyril Scetbon
2014-11-05 21:45 ` Hugo Mills
2014-11-06 1:51 ` Qu Wenruo
2014-11-06 5:29 ` Anand Jain
2014-11-06 9:21 ` Cyril Scetbon
2014-11-07 3:38 ` Duncan [this message]
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='pan$d2077$fec7cdea$56b28895$45042d2e@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=linux-btrfs@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.