From: ludo@gnu.org (Ludovic Courtès)
To: David Craven <david@craven.ch>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Linux kernel config maintainablility
Date: Mon, 05 Sep 2016 10:53:58 +0200 [thread overview]
Message-ID: <87fupeohg9.fsf@gnu.org> (raw)
In-Reply-To: <CAL1_imm+mseUCBuXLEAZoBGp1BgFtuDXAVMSV_qqZEeTfZtwXg@mail.gmail.com> (David Craven's message of "Fri, 2 Sep 2016 14:30:11 +0200")
Hi!
David Craven <david@craven.ch> skribis:
> So I'm trying to get a linux-libre-kernel for arm going. For arm there
> is a multi_v7_defconfig we can use. I looked at the existing kernel
> configs we have and can't make heads or tails of them. My question is
> are any kernel options needed specifically for guixsd? And can we make
> it more readable/explicit by using a defconfig + adding the guixsd
> specific configs separately? This would allow people like me to
> understand what's actually needed to get guixsd working ;-)
guix-daemon needs CONFIG_DEVPTS_MULTIPLE_INSTANCES=y and that’s about
it. GuixSD doesn’t have any unusual requirements.
Now, I agree that storing full config files makes it hard to understand
what non-default settings are used. NixOS has a nicer way to express
this, but long ago people thought it might be fragile:
https://lists.gnu.org/archive/html/guix-devel/2014-06/msg00108.html
https://lists.gnu.org/archive/html/guix-devel/2014-09/msg00370.html
https://lists.gnu.org/archive/html/guix-devel/2014-07/msg00044.html
https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/kernel/linux-4.7.nix
https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/kernel/generic.nix
https://github.com/NixOS/nixpkgs/blob/master/pkgs/os-specific/linux/kernel/generate-config.pl
Thoughts?
Ludo’.
next prev parent reply other threads:[~2016-09-05 8:54 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-02 12:30 Linux kernel config maintainablility David Craven
2016-09-05 8:53 ` Ludovic Courtès [this message]
2016-09-05 12:08 ` David Craven
2016-09-11 13:32 ` Ludovic Courtès
2016-09-11 13:37 ` David Craven
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=87fupeohg9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=david@craven.ch \
--cc=guix-devel@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.
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).