From: "Jason Self" <jason@bluehome.net>
To: guix-devel@gnu.org
Subject: [PATCH] Kernel Configuration
Date: Wed, 24 Sep 2014 13:53:36 -0700 (PDT) [thread overview]
Message-ID: <1411592014.19369@bluehome.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 461 bytes --]
Hello, I wanted to make sure that I was doing this correctly before
committing anything. It seems that it's best to have all of the
kernel's config stuff centrally located. Plus, all of these are
already enabled in the normal config, and I'd argue in a better way.
For example: CONFIG_VIRTIO_BLK should be built in, not a module. Doing
it as a module can cause difficulties when running in a VM in some
cases and the normal config already has it as a built-in.
[-- Attachment #1.2: 0001-gnu-linux-libre-Configuration-options-should-be-spec.patch --]
[-- Type: application/octet-stream, Size: 2064 bytes --]
From aec034aab287ce3ba84139be6f773d0a6144f2f1 Mon Sep 17 00:00:00 2001
From: Jason Self <j@jxself.org>
Date: Wed, 24 Sep 2014 11:37:37 -0700
Subject: [PATCH 1/1] gnu: linux-libre: Configuration options should be
specified in the configuration file.
* gnu/packages/linux.scm (linux-libre): Configuration options should be specified in the configuration file.
Signed-off-by: Jason Self <j@jxself.org>
---
gnu/packages/linux.scm | 18 ------------------
1 file changed, 18 deletions(-)
diff --git a/gnu/packages/linux.scm b/gnu/packages/linux.scm
index 3e19c35..110e1f3 100644
--- a/gnu/packages/linux.scm
+++ b/gnu/packages/linux.scm
@@ -215,24 +215,6 @@ for SYSTEM, or #f if there is no configuration for SYSTEM."
(chmod ".config" #o666))
(system* "make" "defconfig"))
- ;; Appending works even when the option wasn't in the
- ;; file. The last one prevails if duplicated.
- (let ((port (open-file ".config" "a")))
- (display (string-append "CONFIG_NET_9P=m\n"
- "CONFIG_NET_9P_VIRTIO=m\n"
- "CONFIG_VIRTIO_BLK=m\n"
- "CONFIG_VIRTIO_NET=m\n"
- ;; https://lists.gnu.org/archive/html/guix-devel/2014-04/msg00039.html
- "CONFIG_DEVPTS_MULTIPLE_INSTANCES=y\n"
- "CONFIG_VIRTIO_PCI=m\n"
- "CONFIG_VIRTIO_BALLOON=m\n"
- "CONFIG_VIRTIO_MMIO=m\n"
- "CONFIG_FUSE_FS=m\n"
- "CONFIG_CIFS=m\n"
- "CONFIG_9P_FS=m\n")
- port)
- (close-port port))
-
(zero? (system* "make" "oldconfig"))
;; Call the default `build' phase so `-j' is correctly
--
1.7.9.5
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next reply other threads:[~2014-09-24 20:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-24 20:53 Jason Self [this message]
2014-09-24 22:05 ` [PATCH] Kernel Configuration Ludovic Courtès
2014-09-24 23:13 ` Jason Self
2014-09-25 16:00 ` Ludovic Courtès
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=1411592014.19369@bluehome.net \
--to=jason@bluehome.net \
--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).