1 |
Apparently, though unproven, at 16:59 on Monday 16 May 2011, felix@×××××××.com |
2 |
did opine thusly: |
3 |
|
4 |
> On Mon, May 16, 2011 at 04:49:07PM +0200, Alan McKinnon wrote: |
5 |
> > The correct way to use module-rebuild is to run once: |
6 |
> > |
7 |
> > module-rebuild populate |
8 |
> > |
9 |
> > This will search the tree to find out-of-kernel-tree module ebuilds you |
10 |
> > are using and put them in a db or later use. |
11 |
> > |
12 |
> > Every time you emerge and build a new kernel, run: |
13 |
> > |
14 |
> > module-rebuild rebuild |
15 |
> > |
16 |
> > This will build the missing modules for the kernel you just built. |
17 |
> > |
18 |
> > module-rebuild add|del lets you maintain the list as you add and delete |
19 |
> > stuff |
20 |
> |
21 |
> If populate inits the list, are add/del only there to avoid a length |
22 |
> tree search? Otherwise I take it you mean run populate once, then |
23 |
> rebuild after every new kernel, and otherwise do nothing? |
24 |
|
25 |
Correct. populate is the kind of thing you run once at the beginning and never |
26 |
again. add|del is run whenever you need them and rebuild after every new |
27 |
kernel merge (even -r versions) |
28 |
|
29 |
|
30 |
-- |
31 |
alan dot mckinnon at gmail dot com |