From: Brice Waegeneire <brice@waegenei.re>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org,
Guix-devel <guix-devel-bounces+brice+lists=waegenei.re@gnu.org>
Subject: Re: 01/02: services: Allow modprobe to use "/etc/modprobe.d".
Date: Wed, 08 Apr 2020 14:06:02 +0000 [thread overview]
Message-ID: <38f2f725816aafc3e8d9c27b6e051cb0@waegenei.re> (raw)
In-Reply-To: <87pncjbpu6.fsf@gnu.org>
Hello,
On 2020-04-07 09:35, Ludovic Courtès wrote:
> Brice Waegeneire <brice@waegenei.re> skribis:
>> On 2020-04-05 21:15, Ludovic Courtès wrote:
>>> guix-commits@gnu.org skribis:
>>> Looking at this, I was wondering if it would be possible to not use
>>> /etc/modprobe.d and instead have a way to tell the modprobe wrapper
>>> to
>>> pass “-C /gnu/store/…-modprobe.d”, which would contain the right
>>> thing.
>>>
>>> Thoughts?
>>
>> What's the issue with using /etc/modrpobe.d?
>
> In general, use of the global file system name space isn’t great: it’s
> ambiguous (compare to a /gnu/store reference) and doesn’t work well
> upon
> rollback or reconfigure (things that refer to /etc end up referring to
> the “new” /etc after reconfigure, even though that might not actually
> work.)
>
> Conversely, “-C /gnu/store/…-modprobe.d” unambiguously refers to the
> intended directory.
>
> WDYT?
It's good with me, I'll do as suggested -using the environment variable-
when implementing “kernel-module-configuratuion-service-type”.
- Brice
prev parent reply other threads:[~2020-04-08 14:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200405110749.5469.24356@vcs0.savannah.gnu.org>
[not found] ` <20200405110750.E368020A26@vcs0.savannah.gnu.org>
2020-04-05 21:15 ` 01/02: services: Allow modprobe to use "/etc/modprobe.d" Ludovic Courtès
2020-04-06 7:54 ` Brice Waegeneire
2020-04-06 9:29 ` Bengt Richter
2020-04-08 14:03 ` Brice Waegeneire
2020-04-07 9:35 ` Ludovic Courtès
2020-04-08 14:06 ` Brice Waegeneire [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=38f2f725816aafc3e8d9c27b6e051cb0@waegenei.re \
--to=brice@waegenei.re \
--cc=guix-devel-bounces+brice+lists=waegenei.re@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@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).