From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] rfc: /etc/init.d/modules loading modules defined in files
Date: Tue, 16 Aug 2016 19:16:53 -0500 [thread overview]
Message-ID: <20160817001653.GB18485@linux1.gaikai.biz> (raw)
In-Reply-To: <8760r0tgd7.fsf@kestrel.kyomu.43-1.org>
[-- Attachment #1: Type: text/plain, Size: 1026 bytes --]
On Tue, Aug 16, 2016 at 06:59:32PM -0500, Matthias Maier wrote:
>
> On Tue, Aug 16, 2016, at 18:49 CDT, Matthias Maier <tamiko@gentoo.org> wrote:
>
> > On Tue, Aug 16, 2016, at 18:20 CDT, William Hubbs <williamh@gentoo.org> wrote:
> >
> >> All,
> >>
> >> I have received a request to implement a feature in OpenRC to allow
> >> multiple software packages to drop files in a directory, /etc/modules.d
> >> for example, which would define modules the /etc/init.d/modules script
> >> would load.
>
> One more point, /etc/modules.d was used back in the old update-modules
> times. So, maybe we should avoid the directory due to historic reasons
> [1].
Sure, the directory name was just an example.
I was thinking of doing something a little more elaborate so that I
could support all of the module/version/etc combinations documented in
/etc/conf.d/modules, but I'm open to making the behaviour compatible
with what systemd does; that would be a good case probably for doing it
that way.
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2016-08-17 0:17 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-16 23:20 [gentoo-dev] rfc: /etc/init.d/modules loading modules defined in files William Hubbs
2016-08-16 23:49 ` Matthias Maier
2016-08-16 23:59 ` Matthias Maier
2016-08-17 0:16 ` William Hubbs [this message]
2016-08-17 6:59 ` [gentoo-dev] " Martin Vaeth
2016-08-17 12:33 ` Mike Gilbert
2016-08-17 13:04 ` Martin Vaeth
2016-08-19 11:19 ` [gentoo-dev] " Thomas Deutschmann
2016-08-18 14:02 ` NP-Hardass
2016-08-18 17:58 ` William Hubbs
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160817001653.GB18485@linux1.gaikai.biz \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox