update-modules, do we need it anymore?

update-modules, do we need it anymore?

[Laurentiu Palcu]

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?

Thanks,
Laurentiu

Re: update-modules, do we need it anymore?

[Phil Blundell]

On Tue, 2013-01-08 at 16:41 +0200, Laurentiu Palcu wrote:
> 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?

As you say, it's just a historical relic.  It's already optional in
oe-core: you can turn it off by omitting update-modules from your
DISTRO_FEATURES.  I would certainly recommend that any modern distro
does that.

p.

Re: update-modules, do we need it anymore?

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 1249 bytes --]

On Tue, Jan 8, 2013 at 9:41 AM, Laurentiu Palcu
<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 ?

Cheers,

Bruce


>
> Thanks,
> Laurentiu
>
> _______________________________________________
> Openembedded-core mailing list
> 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"

[-- Attachment #2: Type: text/html, Size: 2078 bytes --]

Re: update-modules, do we need it anymore?

[Laurentiu Palcu]

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"

Re: update-modules, do we need it anymore?

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 2439 bytes --]

On Thu, Jan 10, 2013 at 8:59 AM, Laurentiu Palcu
<laurentiu.palcu@intel.com>wrote:

>
>
> 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...
>

I don't have any use for the rest of update-modules, so I don't disagree on
that point. I'd just like to see a form of autoload support be continued if
anything happens to update-modules. But since update-modules isn't
mandatory, I suppose nothing drastic will happen to it regardless, but
having
a modern equivalent would be nice :)

Bruce


>
> 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"
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 3818 bytes --]

Re: update-modules, do we need it anymore?

[Laurentiu Palcu]

On 01/10/2013 04:10 PM, Bruce Ashfield wrote:
> I don't have any use for the rest of update-modules, so I don't disagree on
> that point. I'd just like to see a form of autoload support be continued if
> anything happens to update-modules. But since update-modules isn't
> mandatory, I suppose nothing drastic will happen to it regardless, but
> having
> a modern equivalent would be nice :)
> 
Just to be clear on this. Even if update-modules is removed, modules
will still be autoloaded by modutils.sh which is run in rcS.d. Also,
/etc/init.d/modutils.sh can be run separately.

Thanks,
Laurentiu

Re: update-modules, do we need it anymore?

[Bruce Ashfield]

[-- Attachment #1: Type: text/plain, Size: 1180 bytes --]

On Thu, Jan 10, 2013 at 9:24 AM, Laurentiu Palcu
<laurentiu.palcu@intel.com>wrote:

>
>
> On 01/10/2013 04:10 PM, Bruce Ashfield wrote:
> > I don't have any use for the rest of update-modules, so I don't disagree
> on
> > that point. I'd just like to see a form of autoload support be continued
> if
> > anything happens to update-modules. But since update-modules isn't
> > mandatory, I suppose nothing drastic will happen to it regardless, but
> > having
> > a modern equivalent would be nice :)
> >
> Just to be clear on this. Even if update-modules is removed, modules
> will still be autoloaded by modutils.sh which is run in rcS.d. Also,
> /etc/init.d/modutils.sh can be run separately.


Right, but the files that it reads are generated in kernel.bbclass, right ?
If so, the generation of those files is tied to update-modules being in the
DISTRO_FEATURES and available. So if update-modules is removed, we
want to update the kernel.bbclass to have a different generation of the
autoload config files.

Bruce


>


> Thanks,
> Laurentiu
>



-- 
"Thou shalt not follow the NULL pointer, for chaos and madness await thee
at its end"

[-- Attachment #2: Type: text/html, Size: 2134 bytes --]