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: Sun, 11 Sep 2016 15:32:08 +0200 [thread overview]
Message-ID: <87vay2lfzb.fsf@gnu.org> (raw)
In-Reply-To: <CAL1_imkigh21wP_rNc86+4brs6HFXRUiZQ1PykbqJ6uUs0PEOw@mail.gmail.com> (David Craven's message of "Mon, 5 Sep 2016 14:08:11 +0200")
Hi David,
David Craven <david@craven.ch> skribis:
>> I was hoping we could come up with a way to generate a kernel config,
>> either based on ‘allmodconfig’ or something like what NixOS does [0],
>> but I’ve become pretty convinced that this would be difficult at best.
>
> What difficulties did you encounter with using allmodconfig as a basis?
I forgot the details, but maybe the list archive has some info.
>> NixOS has a nicer way to express this, but long ago people thought it might be fragile.
>
> I agree that how nixos does it seems a little fragile. From what I've
> heard the kernel settings and their defaults change frequently with
> each release. This is why I think relying on the kernel devs to
> provide reasonable defaults makes more sense IMO.
>
> I'd like to make it easy to build custom kernels, I remember using an
> auto detect config feature a while back when using arch. But before
> working on that I need to actually transition to guixsd...
Heh. :-)
Ludo’.
next prev parent reply other threads:[~2016-09-11 13:32 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
2016-09-05 12:08 ` David Craven
2016-09-11 13:32 ` Ludovic Courtès [this message]
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=87vay2lfzb.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).