From: Sjoerd <sjoerd@sjomar.eu>
To: linux-btrfs@vger.kernel.org
Subject: Re: Btrfs progs release 4.1
Date: Wed, 24 Jun 2015 22:26:05 +0200 [thread overview]
Message-ID: <2238718.GK9ft1D4VD@hoefnix> (raw)
In-Reply-To: <20150623144501.GE6761@twin.jikos.cz>
On Tuesday 23 June 2015 16:45:01 David Sterba wrote:
> On Tue, Jun 23, 2015 at 11:03:47AM +0200, Sjoerd wrote:
> > On Monday 22 June 2015 17:00:23 David Sterba wrote:
> > > btrfs-progs 4.1 have been released (in time with kernel 4.1). Unusual
> > > load
> > > of changes.
> >
> > Would it be beneficial to update when using older kernels (3.19.x in my
> > case)? I can't upgrade to kernel 4.1 since my nvidia (propriety) drivers
> > won't support it (yet) :(
>
> The userspace tools do not depend on kernel and can be safely used with
> older kernels, so I'd recommend to update.
>
> https://btrfs.wiki.kernel.org/index.php/FAQ#Do_I_have_to_keep_my_btrfs-progs
> _at_the_same_version_as_my_kernel.3F --
Thanks for the link...I updated it...The updated version breaks the
btrfsQuota.sh and btrfsQuota.py script from the wiki though :(
https://btrfs.wiki.kernel.org/index.php/Quota_support
I can live with that though ;)
Cheers,
Sjoerd
next prev parent reply other threads:[~2015-06-24 20:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-22 15:00 Btrfs progs release 4.1 David Sterba
2015-06-22 16:18 ` Goffredo Baroncelli
2015-06-22 18:01 ` David Sterba
2015-06-22 18:18 ` qgroup limit clearing, was " Christian Robottom Reis
2015-06-22 18:18 ` Christian Robottom Reis
2015-06-22 23:55 ` Tsutomu Itoh
2015-06-23 1:55 ` Qu Wenruo
2015-06-23 12:42 ` David Sterba
2015-06-22 20:45 ` Martin Steigerwald
2015-06-23 12:53 ` David Sterba
2015-06-23 9:03 ` Sjoerd
2015-06-23 9:18 ` Qu Wenruo
2015-06-23 14:45 ` David Sterba
2015-06-24 20:26 ` Sjoerd [this message]
2015-06-25 13:03 ` David Sterba
2015-09-09 1:34 ` Qu Wenruo
2015-09-09 3:24 ` Qu Wenruo
2015-09-09 10:35 ` Vytautas D
2015-09-09 11:25 ` Duncan
2015-09-09 13:26 ` David Sterba
2015-09-09 13:25 ` David Sterba
2015-09-09 14:01 ` Austin S Hemmelgarn
2015-09-10 0:50 ` Qu Wenruo
2015-09-09 13:19 ` David Sterba
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=2238718.GK9ft1D4VD@hoefnix \
--to=sjoerd@sjomar.eu \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).