From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 1/6] kernel.bbclass: populate /etc/modules-load.d/ with module_autoload entries too
Date: Mon, 26 Mar 2012 12:25:22 +0100 [thread overview]
Message-ID: <1332761122.28414.109.camel@ted> (raw)
In-Reply-To: <20120323231116.GC4604@jama.jama.net>
On Sat, 2012-03-24 at 00:11 +0100, Martin Jansa wrote:
> On Sat, Mar 24, 2012 at 12:00:04AM +0100, Andreas Oberritter wrote:
> > On 23.03.2012 13:56, Martin Jansa wrote:
> > > * /etc/modules-load.d/foo.conf is used by systemd like /etc/modutils/foo was with sysvinit
> >
> > Martin,
> >
> > the man-page[1] for modules-load.d says that packages should install
> > .conf files to /usr/lib/modules-load.d, because /etc/modules-load.d is
> > reserved for the system administrator. Did you take this into account
> > when you decided to support /etc/modules-load.d?
>
> You're right, /usr/lib/modules-load.d could be possibly better option.
> I've used /etc mostly because I was using it since my first systemd
> image (so I was sure it works) and I don't remember seeing /usr/lib in
> man page when I was reading it back then (probably overlooked or
> forgot).
>
> Is it worth updating update-modules (maybe teaching update-modules to
> look into all possible systemd directories too)?
I think in our case, we'd need to have /lib/modules-load.d
and /usr/lib/modules-load.d depending on whether the module was meant to
load without /usr being mounted. Using /etc for now seems to make most
sense although it probably wouldn't hurt for the script to look at the
other locations.
Cheers,
Richard
next prev parent reply other threads:[~2012-03-26 11:34 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 12:56 [PATCH 0/6] kernel.bbclass updates Martin Jansa
2012-03-23 12:56 ` [PATCH 1/6] kernel.bbclass: populate /etc/modules-load.d/ with module_autoload entries too Martin Jansa
2012-03-23 23:00 ` Andreas Oberritter
2012-03-23 23:11 ` Martin Jansa
2012-03-26 11:25 ` Richard Purdie [this message]
2012-03-26 18:44 ` Darren Hart
2012-03-23 12:56 ` [PATCH 2/6] kernel.bbclass: use symlinks for modutils files Martin Jansa
2012-03-26 18:46 ` Darren Hart
2012-03-26 18:58 ` Martin Jansa
2012-03-26 22:05 ` Richard Purdie
2012-03-23 12:56 ` [PATCH 3/6] kernel.bbclass: use better number for KERNEL_PRIORITY Martin Jansa
2012-03-23 12:56 ` [PATCH 4/6] kernel.bbclass: fix extra + in kernelrelease Martin Jansa
2012-03-23 13:24 ` Bruce Ashfield
2012-03-23 13:31 ` Martin Jansa
2012-03-26 16:02 ` Martin Jansa
2012-03-26 16:05 ` Martin Jansa
2012-03-26 16:25 ` Bruce Ashfield
2012-03-26 17:29 ` [PATCH] kernel.bbclass: touch .scmversion also in ${S} Martin Jansa
2012-03-26 18:32 ` Bruce Ashfield
2012-03-23 12:56 ` [PATCH 5/6] update-modules: update script to read /etc/modules-load.d/ directory Martin Jansa
2012-03-23 14:37 ` [PATCHv2 " Martin Jansa
2012-03-23 12:56 ` [PATCH 6/6] kernel.bbclass: don't create /etc/modutils/* Martin Jansa
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=1332761122.28414.109.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=openembedded-core@lists.openembedded.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.