| 1 |
> > I've been puzzling a bit lately over the best way to manage my kernel. |
| 2 |
> > I've always tried to keep it as minimal as possible, and I only |
| 3 |
> > enable things as I need them. I also don't build modules from the |
| 4 |
> > kernel at all. |
| 5 |
> > |
| 6 |
> > Is there a better way to go? I'm starting to think it might be better |
| 7 |
> > to build every single module and let the system load them as it needs |
| 8 |
> > them. |
| 9 |
> > |
| 10 |
> > - Grant |
| 11 |
> |
| 12 |
> well, from my point of view: |
| 13 |
> |
| 14 |
> everything needed for booting: in kernel |
| 15 |
> everything needed all the time: in kernel |
| 16 |
> everything that needs a good kicking once in a while (usb, sound): modules |
| 17 |
> everything that needs parameters: modules |
| 18 |
> everything that is not needed all the time: module |
| 19 |
|
| 20 |
So you don't leave anything unbuilt? Is there any real disadvantage |
| 21 |
to that as long as you modularize as much as possible? It sounds |
| 22 |
delightfully simple to go that route. That would be a really portable |
| 23 |
kernel too. |
| 24 |
|
| 25 |
- Grant |
| 26 |
-- |
| 27 |
gentoo-user@g.o mailing list |
Archives