Hi Erich;

Am Mittwoch, 31. August 2011, 08:59:07 schrieb Erich Titl:
> Hi Folks
> 
> I am trying to reduce the footprint of the modules.lrp archive. I looked
> at /lib/modules and found a completely unstructured module directory.
> 
> Is there a reason why we do that? 

Up to version 3 it was filled with only a dozen by default and a few more if 
the user installed additional hard- and software that needs other modules  - 
not as cluttered as today; easy to understand and only needing an easy 
algorithm to load modules.

This changed with the "autodetection and autoloading" feature (supporting more 
hardware and packages out of the box) in Bering-uClibc 4.

Andrew put a lot effort to make that work and besides the "cosmetic" 
disadvantage it seems to work pretty well. In fact it's a lot easier to get a 
Bering-uClibc box up and running mostly without any user action.

> This is so different from any other
> Linux distribution that it is difficult to compare. Some of the modules
> are easily recognized by name, but others are not and it makes it easier
> to remove something when one knows what functionality lies behind a
> certain module.
> 
> I would like you to reconsider this decision.

I understand that modules.lrp is too big once a box is configured, but pls be 
carefully removing modules, as they may be needed by others running a different 
setup.

A better approach may be to reduce modules.lrp once a box is installed and 
configured, as we do with keyboard.lrp. There we look what keyboard map is 
needed and remove others. A similar way would be a script that looks for 
loaded modules and removes the unused ones.

kp

------------------------------------------------------------------------------
Special Offer -- Download ArcSight Logger for FREE!
Finally, a world-class log management solution at an even better 
price-free! And you'll get a free "Love Thy Logs" t-shirt when you
download Logger. Secure your free ArcSight Logger TODAY!
http://p.sf.net/sfu/arcsisghtdev2dev

_______________________________________________
leaf-devel mailing list
leaf-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/leaf-devel

Reply via email to