unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Mark H Weaver <mhw@netris.org>
To: Dmitry Nikolaev <cameltheman@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: Enable modules in Linux configuration.
Date: Mon, 31 Jul 2017 07:57:11 -0400	[thread overview]
Message-ID: <87pocgzunc.fsf@netris.org> (raw)
In-Reply-To: <CAH3JXcEGXTXfQ0fy4ijGHcDZ51mB10TJ5EfPNz6V+yshbDpNFg@mail.gmail.com> (Dmitry Nikolaev's message of "Sat, 29 Jul 2017 22:33:00 +0300")

Hi again,

Dmitry Nikolaev <cameltheman@gmail.com> writes:

> How do I enable Reiser4 module in Linux configuration? As far as I
> know I need to add "REISER4_FS=m" to .config after running "make
> defconfig", but before "make".

Sorry, I realize that I didn't answer this question in my last message.
It might be sufficient to merely add "REISER4_FS=m" to

  gnu/packages/aux-files/linux-libre/<version>-<arch>.conf

in the Guix source tree.  However, if there are other configuration
options that need to be changed to accommodate Reiser4, then this might
not be enough.

The more general method is to unpack a copy of the linux-libre source
tree, copy the appropriate config file from the Guix source tree to
.config in the top-level linux-libre source, run "make oldconfig" (or
whichever *config target you prefer) to update the config, and then copy
the updated .config file back to the Guix source tree.

A good way to unpack the source is to run "guix build -S linux-libre"
(or your own variant package), and then "tar xf" on the returned file
name.

A good way to make sure you have the necessary software in your
environment to run "make oldconfig" is to run "guix environment
linux-libre" and then work within the spawned shell.

      Mark

  parent reply	other threads:[~2017-07-31 11:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-29 19:33 Enable modules in Linux configuration Dmitry Nikolaev
2017-07-30  9:33 ` ng0
2017-07-30 18:11 ` Joshua Branson
2017-07-30 18:18   ` ng0
2017-07-31 11:45 ` Mark H Weaver
2017-07-31 11:57 ` Mark H Weaver [this message]
2017-07-31 21:39 ` Marius Bakke
2017-08-02 14:37   ` Joshua Branson

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=87pocgzunc.fsf@netris.org \
    --to=mhw@netris.org \
    --cc=cameltheman@gmail.com \
    --cc=help-guix@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).