[Meego-architecture] Autoloading modules in startup process

[Nashif, Anas]

Init scripts are the wrong place for this kind of thing, this should be done using udev.

Anas

--
Sent from my phone.


On 2010-12-09, at 10:13, "Carsten Munk" <carsten at maemo.org> wrote:

> Hi,
> 
> We are struggling with some various bugs that require modprobing of
> modules in startup process such as
> http://bugs.meego.com/show_bug.cgi?id=9824 or
> http://bugs.meego.com/show_bug.cgi?id=9057
> 
> Due to size constraints, we can't build-in most modules into a kernel
> and require some kind of autodetection or the likes that loads the
> modules.
> 
> What's the intended way of dealing with situations like this? Could we
> do something smart related to /etc/machinename idea?
> 
> I guess the 'best way' would be having udev do it? And is there some
> good documentation on how this is handled on kernel source basis or
> configuration?
> 
> Or should we go for the horrible way and have a init.d script per
> device/platform that modprobes? :)
> 
> BR
> Carsten Munk
> _______________________________________________
> MeeGo-architecture mailing list
> MeeGo-architecture at lists.meego.com
> http://lists.meego.com/listinfo/meego-architecture
---------------------------------------------------------------------
Intel Corporation (UK) Limited
Registered No. 1134945 (England)
Registered Office: Pipers Way, Swindon SN3 1RJ
VAT No: 860 2173 47

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.