Apparently, though unproven, at 15:20 on Monday 16 May 2011, fe...@crowfix.com did opine thusly:
> I have an ancient emerge script which does this: > > rm -rf /var/lib/module-rebuild > module-rebuild -C list > > and I do not know why -- did I dream this up myself, or did I inherit > it from somewhere? I do not know. > > At any rate, it seems kind of odd. What is the proper way of using > module_rebuild? It seems to me there are two cases, and maybe that > is why this script has this odd code. If you have just built a brand > new kernel, you might want to rebuild the module list from scratch. > But once you have done that, future emerges only need to keep the > module list up to date. > > And then I realized I don't even know what the module list actually > is. > > Please enlighten me :-O Looks like something you dreamed up. /var/lib/module-rebuild contains a list of installed out-of-tree modules. You delete the entire directory then list it (to prove that it is empty?) I have no idea why you might have wanted to do that back in the day. The correct way to use module-rebuild is to run once: module-rebuild populate This will search the tree to find out-of-kernel-tree module ebuilds you are using and put them in a db or later use. Every time you emerge and build a new kernel, run: module-rebuild rebuild This will build the missing modules for the kernel you just built. module-rebuild add|del lets you maintain the list as you add and delete stuff -- alan dot mckinnon at gmail dot com
