Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Laurentiu Palcu <laurentiu.palcu@intel.com>
To: Bruce Ashfield <bruce.ashfield@gmail.com>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: update-modules, do we need it anymore?
Date: Thu, 10 Jan 2013 15:59:27 +0200	[thread overview]
Message-ID: <50EEC93F.9060802@intel.com> (raw)
In-Reply-To: <CADkTA4NFq_EoFY8H800ewKQMWEOMjfroqT0t3okRKJz5jEYZzw@mail.gmail.com>



On 01/10/2013 03:45 PM, Bruce Ashfield wrote:
> 
> 
> 
> On Tue, Jan 8, 2013 at 9:41 AM, Laurentiu Palcu
> <laurentiu.palcu@intel.com <mailto:laurentiu.palcu@intel.com>> wrote:
> 
>     Hi all,
> 
>     While working on making all postinstalls run on host, I saw that we
>     still use update-modules script. However, neither the kmod modprobe nor
>     the busybox one read /etc/modules.conf file anymore which is created by
>     update-modules script. Both scan /etc/modprobe.d/*.conf files.
> 
>     So, does anybody know why do we still have it around? Most modern
>     distributions declared update-modules as obsolete and /etc/modules.conf
>     doesn't exist anymore. Am I missing something?
> 
> 
> I've been using the autoload functionality (not heavily, but from time
> to time) 
> that is currently tied to update-modules. I did a quick scan of the
> alternatives
> in oe-core, and didn't immediately see that the same thing is possible via
> kmod. Is that the case, or am I missing something as well ?
This autoload functionality seems to be provided by
/etc/init.d/modutils.sh which is explicitly called from update-modules
script. However, modutils.sh resides in modutils-initscripts.bb recipe.
So, I personally see not use for update-modules anymore...

Thanks,
Laurentiu
> 
> Cheers,
> 
> Bruce
>  
> 
> 
>     Thanks,
>     Laurentiu
> 
>     _______________________________________________
>     Openembedded-core mailing list
>     Openembedded-core@lists.openembedded.org
>     <mailto:Openembedded-core@lists.openembedded.org>
>     http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
> 
> 
> 
> 
> -- 
> "Thou shalt not follow the NULL pointer, for chaos and madness await
> thee at its end"



  reply	other threads:[~2013-01-10 14:14 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-08 14:41 update-modules, do we need it anymore? Laurentiu Palcu
2013-01-08 14:50 ` Phil Blundell
2013-01-10 13:45 ` Bruce Ashfield
2013-01-10 13:59   ` Laurentiu Palcu [this message]
2013-01-10 14:10     ` Bruce Ashfield
2013-01-10 14:24       ` Laurentiu Palcu
2013-01-10 14:57         ` Bruce Ashfield

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=50EEC93F.9060802@intel.com \
    --to=laurentiu.palcu@intel.com \
    --cc=bruce.ashfield@gmail.com \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox