From: David Haller <gentoo@dhaller.de>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] openrc : autoload kernel modules
Date: Thu, 14 Dec 2017 21:30:52 +0100 [thread overview]
Message-ID: <20171214203052.bmvxkj7wudt4l3my@grusum.endjinn.de> (raw)
In-Reply-To: <5d127de0-72fd-4f01-bef3-17aefa37158b@gentoo.org>
Hello,
On Thu, 14 Dec 2017, Michael Orlitzky wrote:
>On 12/14/2017 12:43 PM, Helmut Jarausch wrote:
>>
>> I have added the following lines to /etc/conf.d/modules
>>
>> modules="enhanceio"
>> modules="enhanceio_lru"
>> modules="enhanceio_fifo"
>> modules="enhanceio_rand"
>>
>
>"modules" is a variable name, and it's being overwritten on each line.
>The /etc/init.d/modules script does something like
>
> for module in $modules; do
> load $module
> done
>
>but in your case, "modules" will contain only the last thing you set it
>to, namely modules="enhanceio_rand".
Does openrc-run (or the old way) support adding to strings? I.e.:
====
modules+=" foo"
modules+=" bar"
====
or must one use
====
modules="${modules} foo"
modules="${modules} bar"
====
or must it even be one single string? Does that support embedded
linebreaks?
I think this should be documented better in the file.
-dnh
PS: I've had the opposite problem: modules automatically got loaded
and I blacklisted them in /etc/modprobe.d/*.conf ;)
--
I find all proselytisation to be misguided at least. The way I see it, it's
not the Enlightened or the Chosen trying to save me or anyone, but just some
meme trying to survive in the great war for brain real estate.
-- Maarten Wiltink
next prev parent reply other threads:[~2017-12-14 20:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-14 17:43 [gentoo-user] openrc : autoload kernel modules Helmut Jarausch
2017-12-14 18:11 ` [gentoo-user] " Hartmut Figge
2017-12-14 19:09 ` Alexander Kapshuk
2017-12-14 18:43 ` [gentoo-user] " Michael Orlitzky
2017-12-14 18:48 ` Mick
2017-12-14 19:30 ` Helmut Jarausch
2017-12-14 20:30 ` David Haller [this message]
2017-12-14 22:09 ` Michael Orlitzky
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=20171214203052.bmvxkj7wudt4l3my@grusum.endjinn.de \
--to=gentoo@dhaller.de \
--cc=gentoo-user@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