unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: Brice Waegeneire <brice@waegenei.re>
Cc: guix-devel@gnu.org
Subject: Re: Kernel module configuration service
Date: Tue, 26 May 2020 22:34:23 +0200	[thread overview]
Message-ID: <20200526223423.136e45b7@scratchpost.org> (raw)
In-Reply-To: <be23e87735406423b0d6d3d017ebbc5c@waegenei.re>

[-- Attachment #1: Type: text/plain, Size: 1908 bytes --]

Hi Brice,

On Fri, 15 May 2020 19:31:51 +0000
Brice Waegeneire <brice@waegenei.re> wrote:

> (1) Generate a config directory for modrope to use
> (2) Load loadable kernel module by extending 'kernel-module-loader-service'
[...]
> 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.

I think that essential services are just services that aren't randomly
restarted or removed by Guix while the system is running.

Also, a user shouldn't need to touch (swap out) essential services.

I envision that mostly other services would extend the KMCS--so it
shouldn't matter that user can't touch the KMCS essential service.

That said, maybe still good to have a field in the <operating-system> record
that lets the user specify manual kernel module configuration amendments.

The kernel module configuration directory should be there as early as possible
in the boot process since the kernel can invoke modprobe whenever it wants.

Definitely don't wait for shepherd (or even more stuff) to start up.

> 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').

Oops.

> What are the guidelines to add a service to the essential-services? Can
> KMCS become an essential-service? Any other remarks/idea?

If necessary one can always not do (2)--although it would be nice to do it.
But if it means waiting for shepherd, nope.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2020-05-26 20:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-05-15 19:31 Kernel module configuration service Brice Waegeneire
2020-05-26 20:34 ` Danny Milosavljevic [this message]
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=20200526223423.136e45b7@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=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).