All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marc MERLIN <marc@merlins.org>
To: Shriramana Sharma <samjnaa@gmail.com>
Cc: linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Distro vs latest kernel for BTRFS?
Date: Fri, 22 Aug 2014 07:10:02 -0700	[thread overview]
Message-ID: <20140822141002.GO3875@merlins.org> (raw)
In-Reply-To: <CAH-HCWVMO+NO0B5i0o0gCHBy9dLjc08gcqxT7oEV5WkO2BHvMA@mail.gmail.com>

On Fri, Aug 22, 2014 at 05:29:29PM +0530, Shriramana Sharma wrote:
> Hello. I've seen repeated advices to use the latest kernel. While
> hearing of the recent compression bug affecting recent kernels does
> somewhat warn one off the previous advice, I would like to know what
> people who are running regular distros do to get the latest kernel.
> 
> Personally I'm on Kubuntu, which provides mainline kernels till a
> particular point but not beyond that.
> 
> Do people here always compile the latest kernel themselves just to get
> the latest BTRFS stability fixes (and  improvements, though as a
> second priority)?

First, yeah you want to stay with 3.14 for now until the last bug that's
been found and is integrated in a stable 3.16.

Yes, I compile my own kernels, but that's mostly because that's what one
did in 1993, and that's what I still do now :)

If you're not comfortable compiling your own kernel (mostly getting the
.config options you want/need), you can
1) use a recent enough vendor kernel 
2) use their .config (or /proc/config.gz) as a way to build a new
kernel.

Marc
-- 
"A mouse is a device used to point at the xterm you want to type in" - A.S.R.
Microsoft is to operating systems ....
                                      .... what McDonalds is to gourmet cooking
Home page: http://marc.merlins.org/                         | PGP 1024R/763BE901

  parent reply	other threads:[~2014-08-22 14:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-22 11:59 Distro vs latest kernel for BTRFS? Shriramana Sharma
2014-08-22 12:04 ` Austin S Hemmelgarn
2014-08-22 18:09   ` Duncan
2014-08-22 18:22   ` Rich Freeman
2014-08-22 19:18     ` Austin S Hemmelgarn
2014-08-22 14:10 ` Marc MERLIN [this message]
2014-08-22 16:51 ` Chris Murphy
2014-08-22 17:38 ` Martin Steigerwald
2014-08-25  1:06 ` Qu Wenruo

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=20140822141002.GO3875@merlins.org \
    --to=marc@merlins.org \
    --cc=linux-btrfs@vger.kernel.org \
    --cc=samjnaa@gmail.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 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.