| 1 |
Michael Weyershäuser wrote: |
| 2 |
> I usualy start with a kernel with almost everything compiled in (but |
| 3 |
> only things I definitely need), only using modules when I have to |
| 4 |
> (USB for suspend2 comes to my mind). Over time whenever I need |
| 5 |
> something new (filesystem, hardware driver,...) I tend to compile it |
| 6 |
> as a module to avoid a reboot. As I do not upgrade my kernel very |
| 7 |
> often this happens more often than you might think (last upgrade was |
| 8 |
> from 2.6.11 to 2.6.16, on my laptop from 2.6.10 to 2.6.16). |
| 9 |
> |
| 10 |
> I don't really care about the 300k more used memory (hardly worth a |
| 11 |
> thought on systems with 1 GB RAM and more) or the 0.3 seconds faster |
| 12 |
> boot process. Modules just come in handy when it comes to avoiding a |
| 13 |
> reboot. |
| 14 |
|
| 15 |
OK, this seems to confirm something I had suspected but never |
| 16 |
investigated: - that you can compile just a module without the need to |
| 17 |
recompile and install a revised kernel. This is possible? |
| 18 |
|
| 19 |
How? "make modules_install" or the whole thing: "make && make |
| 20 |
modules_install" then just modprobe the new module? |
| 21 |
|
| 22 |
Tony |
| 23 |
-- |
| 24 |
Those who would give up essential Liberty, to purchase a little temporary |
| 25 |
Safety, deserve neither Liberty nor Safety. |
| 26 |
-- Benjamin Franklin |
| 27 |
-- |
| 28 |
gentoo-user@g.o mailing list |
Archives