From: Gabriel de Perthuis <g2p.code-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Giovanni Lenzi
<public-giovanni.lenzi-Re5JQEeQqe8AvxtiuMwx3w-wOFGN7rlS/M9smdsby/KFg@public.gmane.org>
Cc: linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: bcache on ubuntu
Date: Sat, 11 May 2013 00:50:56 +0200 [thread overview]
Message-ID: <518D79D0.5030702@gmail.com> (raw)
> Hi,
> I want to use bcache on ubuntu.
>
> I saw that I have to download it from git with git clone command. Is it right?
>
> I never recompiled a kernel. Is it so hard?
>
> What kind of steps am I supposed to do, if I have a fresh ubuntu installation?
It's a bit early for this.
Before building a kernel, try your hand at building and installing bcache-tools.
Building the kernel is more time consuming, and you'll need bcache-tools
installed before the kernel so that it gets picked up for your boot.
Once that's done, have a look at https://wiki.ubuntu.com/KernelTeam/GitKernelBuild
Experimental 3.10 kernels will also appear sometime next week[1]. Assuming they
have bcache enabled, you don't really have to built it yourself, you just need to
deal with experimental releases and the chance of trouble.
That's enough to let you play with bcache. Converting your installation to
bcache is not something I'd recommend to someone who has never done this sort of
hacking, because if the kernel turns out to be unstable you'll be stuck with it
to access your data.
[1]: http://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D
next reply other threads:[~2013-05-10 22:50 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-10 22:50 Gabriel de Perthuis [this message]
-- strict thread matches above, loose matches on Subject: below --
2013-05-11 6:36 bcache on ubuntu Giovanni Lenzi
2013-05-11 7:56 ` Gabriel de Perthuis
2013-05-10 10:28 Giovanni Lenzi
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=518D79D0.5030702@gmail.com \
--to=g2p.code-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=linux-bcache-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=public-giovanni.lenzi-Re5JQEeQqe8AvxtiuMwx3w-wOFGN7rlS/M9smdsby/KFg@public.gmane.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