| 1 |
felix@×××××××.com writes: |
| 2 |
|
| 3 |
> At any rate, it seems kind of odd. What is the proper way of using |
| 4 |
> module_rebuild? It seems to me there are two cases, and maybe that |
| 5 |
> is why this script has this odd code. If you have just built a brand |
| 6 |
> new kernel, you might want to rebuild the module list from scratch. |
| 7 |
> But once you have done that, future emerges only need to keep the |
| 8 |
> module list up to date. |
| 9 |
|
| 10 |
Whatever. With a recent portage you just emerge @module-rebuild, that's what |
| 11 |
I use. There's also @x11-module-rebuild, for recompiling Xorg stuff when |
| 12 |
xorg-server is updated. |
| 13 |
|
| 14 |
Wonko |
Archives