linux-btrfs.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Pottage <david@chrestomanci.org>
To: Cyril Scetbon <cyril.scetbon@free.fr>,
	linux-btrfs <linux-btrfs@vger.kernel.org>
Subject: Re: Using Btrfs with Ubuntu 14.04
Date: Tue, 12 Aug 2014 17:02:40 +0100	[thread overview]
Message-ID: <53EA3AA0.9080607@chrestomanci.org> (raw)
In-Reply-To: <8951EA18-525B-43F4-8B8E-499611A69465@free.fr>


On 12/08/14 08:46, Cyril Scetbon wrote:
> Hi guys,
>
> Can you tell me if there are any pitfalls to use Btrfs under Ubuntu 14.04 (Btrfs 3.12). Are there any well known bug that are only fixed later ? Please, send me links just to check if it could hurt or not ..
You should probably install the latest kernel, as otherwise if you 
report any issue to this list the first thing people will ask you to do 
is to update.

Follow the instructions here:
https://wiki.ubuntu.com/KernelTeam/GitKernelBuild

It is not hard, but it will take a while. I would allow at least an hour 
to build a kernel package unless you are on the latest fast hardware. It 
could also take a long time to git clone the kernel unless your internet 
conection is fast.

On step 2, I suggest you clone from the stable reposistory instead of 
Linus's bleeding edge repsitory. The sable clone URL is: 
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git

Good luck !

-- 
David Pottage





  parent reply	other threads:[~2014-08-12 16:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-08-12  7:46 Using Btrfs with Ubuntu 14.04 Cyril Scetbon
2014-08-12 15:34 ` Timofey Titovets
2014-08-13 11:50   ` nivw
2014-08-14 19:39     ` Cyril Scetbon
2014-08-12 16:02 ` David Pottage [this message]
2014-08-14 11:37 ` Chris Samuel
2014-08-14 19:49   ` Cyril Scetbon

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=53EA3AA0.9080607@chrestomanci.org \
    --to=david@chrestomanci.org \
    --cc=cyril.scetbon@free.fr \
    --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).