All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kelvin Lawson <kelvinl@users.sf.net>
To: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH] update-modules: don't run modutils.sh if systemd is installed
Date: Thu, 16 Feb 2012 01:53:08 +0000	[thread overview]
Message-ID: <jhhni5$rcg$1@dough.gmane.org> (raw)
In-Reply-To: <1325911915-16001-5-git-send-email-steve@sakoman.com>

Hi,

> +# Don't run modutils.sh if systemd is installed
> +if [ $first_time -eq 1 ]&&  [ ! -e /bin/systemctl ]; then
>     /etc/init.d/modutils.sh || true
>   fi

I just came across this and was wondering what the situation is with 
respect to systemd's module loading. Is there actually a mechanism in 
place for populating systemd's /etc/modules-load.d folder?

The "module_autoload_xx" directives populate /etc/modutils but not 
/etc/modules-load.d. As far as I can tell this means that one still 
needs to include the old modutils.sh script to autoload modules (via 
modutils-initscripts package). With this patch, you need to boot the 
system twice in order for the kernel modules to be auto-loaded (because 
update-modules does not reload modutils.sh immediately after adding the 
modules).

Are we in a transition period where module-autoload is not yet 
implemented via the systemd method but update-modules doesn't quite play 
ball properly with that, or is there already a mechanism for populating 
modules-load.d that I haven't found yet? (Other than doing it by hand).

Thanks,
Kelvin.




      parent reply	other threads:[~2012-02-16  2:23 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-07  4:51 [PATCH] update-modules: don't run modutils.sh if systemd is installed Steve Sakoman
2012-01-12  6:28 ` Saul Wold
2012-02-16  1:53 ` Kelvin Lawson [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='jhhni5$rcg$1@dough.gmane.org' \
    --to=kelvinl@users.sf.net \
    --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.