unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Giovanni Biscuolo <g@xelera.eu>
To: Danny Milosavljevic <dannym@scratchpost.org>,
	Jelle Licht <jlicht@fsfe.org>
Cc: guix-devel@gnu.org
Subject: Re: Loading modules built using linux-module-build-system
Date: Tue, 22 Oct 2019 08:52:37 +0200	[thread overview]
Message-ID: <87ftjluv9m.fsf@roquette.mug.biscuolo.net> (raw)
In-Reply-To: <20191021204857.5dff6e9b@scratchpost.org>

Hi Danny,

Danny Milosavljevic <dannym@scratchpost.org> writes:

[...]

> A user package (for example if referred to by a system service) would
> propagate-input the kernel module package it requires.

Yes! \O/

[...]

> The limitation of it not be possible for a regular user to add kernel
> modules is OK I think.

When I wear the regular user hat I would simply like to forget about
kernel modules, letting the service use (reference a package) whatever
kernel module it needs to do the job

> That's where I draw the line--a normal profile has no business adding
> Linux kernel modules to kernel space in the first place.

I agree, that is a system level profile business

[...]

AFAIU sounds like a good plan, sorry I just canno help here :-S

Thanks! Gio'

-- 
Giovanni Biscuolo

Xelera IT Infrastructures

      parent reply	other threads:[~2019-10-22  6:53 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-08 22:50 Loading modules built using linux-module-build-system Jelle Licht
2019-10-21 15:30 ` Jelle Licht
2019-10-21 18:27 ` Danny Milosavljevic
2019-10-21 18:49   ` Danny Milosavljevic
2019-10-21 21:39     ` Danny Milosavljevic
2019-10-22 12:24       ` Ludovic Courtès
2019-11-14 16:31         ` Danny Milosavljevic
2019-11-17 20:35           ` Ludovic Courtès
2019-12-22 20:06             ` Danny Milosavljevic
2019-12-30 18:55               ` Ludovic Courtès
2019-10-22  6:52     ` Giovanni Biscuolo [this message]

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=87ftjluv9m.fsf@roquette.mug.biscuolo.net \
    --to=g@xelera.eu \
    --cc=dannym@scratchpost.org \
    --cc=guix-devel@gnu.org \
    --cc=jlicht@fsfe.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).