public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Vaeth <martin@mvath.de>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: rfc: /etc/init.d/modules loading modules defined in files
Date: Wed, 17 Aug 2016 06:59:25 +0000 (UTC)	[thread overview]
Message-ID: <slrnnr82qe.n2i.martin@lounge.imp.fu-berlin.de> (raw)
In-Reply-To: 20160817001653.GB18485@linux1.gaikai.biz

William Hubbs <williamh@gentoo.org> wrote:
>
> but I'm open to making the behaviour compatible
> with what systemd does

Since openrc already supports tmpfiles.d,
support for modules-load.d would be natural.
In fact, this is already done for quite a while in

https://github.com/vaeth/firewall-mv/blob/master/openrc/conf.d/modules

The last line supports modules-load.d:

modules=$(sed -n -e '/^[^;#]/p' /etc/modules-load.d/*.conf \
	/usr/lib/modules-load.d/*.conf 2>/dev/null || : )

For compatibility with other init systems one should perhaps not
extend the format of modules-load.d: If one also wants to e.g.
support args for modules, this should perhaps be done in
a separate directory. /etc/modprobe.d already exists for this,
but one might still source another directory which contains
only files added to /etc/conf.d/modules



  reply	other threads:[~2016-08-17  6:59 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
2016-08-17  6:59       ` Martin Vaeth [this message]
2016-08-17 12:33         ` [gentoo-dev] " 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=slrnnr82qe.n2i.martin@lounge.imp.fu-berlin.de \
    --to=martin@mvath.de \
    --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