From: Brice Waegeneire <brice@waegenei.re>
To: guix-devel@gnu.org
Subject: Kernel module configuration service
Date: Fri, 15 May 2020 19:31:51 +0000 [thread overview]
Message-ID: <be23e87735406423b0d6d3d017ebbc5c@waegenei.re> (raw)
Hello Guix,
I'm working on the future 'kernel-module-configuration-service-type'[0]
(KMCS) and I need some guidance. This service will be a one stop shop
for
all kernel module related configuration by doing the following 4 things:
1. Generate a config directory for modrope to use
2. Load loadable kernel module by extending
'kernel-module-loader-service'
3. Configure built-in module by being a new source for
'operating-system-kernel-arguments'
4. Add loadable kernel modules to the kernel profile by being a source
for
'operating-system-kernel-loadable-modules'
ATM I need help with point number 1 in regard to putting in place the
config directory for modprobe. To do so I need to change
'%modprobe-wrapper' into a procedure to take the configuration directory
as
an argument, since the directory will now come from '/gnu/store/'
instead
of '/etc/'. The problem is that the wrapper is currently put in place by
'%linux-bare-metal-service' which is an essential service, so it seems
that
KMCS will have to become one too. Looking around at some essential
service
most of them are straight forward and don't extend services like
'kernel-module-loader-service-type' (which itself extend
'shepherd-root-service-type').
What are the guidelines to add a service to the essential-services? Can
KMCS become an essential-service? Any other remarks/idea?
[0]: https://issues.guix.info/40274#18
Have a good day,
- Brice
next reply other threads:[~2020-05-15 19:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-15 19:31 Brice Waegeneire [this message]
2020-05-26 20:34 ` Kernel module configuration service Danny Milosavljevic
2020-05-26 20:39 ` Danny Milosavljevic
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=be23e87735406423b0d6d3d017ebbc5c@waegenei.re \
--to=brice@waegenei.re \
--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).