From: Leo Famulari <leo@famulari.name>
To: Tobias Geerinckx-Rice <tobias.geerinckx.rice@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Adding btrfs-progs
Date: Fri, 12 Feb 2016 17:10:36 -0500 [thread overview]
Message-ID: <20160212221036.GD25757@jasmine> (raw)
In-Reply-To: <CAKFHe2TeK1aRkBfa4TmjmFcHfsmhYce9QERfT7KSpmk=h-PEKA@mail.gmail.com>
On Fri, Feb 12, 2016 at 05:03:16PM +0100, Tobias Geerinckx-Rice wrote:
> On 12 February 2016 at 03:41, Leo Famulari <leo@famulari.name> wrote:
> > Thanks for the patch! Pushed as fc686f9a19.
>
> \o/
>
> > On Wed, Feb 10, 2016 at 05:01:45AM +0100, tobias.geerinckx.rice@gmail.com wrote:
> >> [1]: <http://thread.gmane.org/gmane.comp.gnu.guix.devel/12164>,
> >> although this patch was not based on that one.
>
> I should really stop hacking after 4am. For the record: [1], of course.
>
> Kind regards,
>
> T G-R
>
> [1]: http://thread.gmane.org/gmane.comp.gnu.guix.devel/13164
Oh, now I get it :)
The INSTALL file in the btrfs-progs source distribution describes the
creation of static versions of btrfs utilities. I'm not an expert on
this stuff but I believe that is what is required in the initrd.
Do you think you could investigate this possibility? It's much easier to
do this stuff on GuixSD since you can always rollback (unless you break
GRUB).
prev parent reply other threads:[~2016-02-12 22:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 4:01 Adding btrfs-progs tobias.geerinckx.rice
2016-02-10 4:01 ` [PATCH 1/2] gnu: Add btrfs-progs tobias.geerinckx.rice
2016-02-12 2:43 ` Leo Famulari
2016-02-10 4:01 ` [PATCH 2/2] install: Add btrfs-progs to the image tobias.geerinckx.rice
2016-02-12 2:44 ` Leo Famulari
2016-02-12 9:07 ` Ludovic Courtès
2016-02-12 21:47 ` Leo Famulari
2016-02-12 2:41 ` Adding btrfs-progs Leo Famulari
2016-02-12 16:03 ` Tobias Geerinckx-Rice
2016-02-12 22:10 ` Leo Famulari [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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160212221036.GD25757@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=tobias.geerinckx.rice@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).