-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Tom Eastman wrote: | I'm about to go from gentoo-dev-sources-2.6.9-r9 to 2.6.10, but I was | wondering just what would happen if I simply went through my kernel config | and compiled absolutely *everything* that can be a module, as a module. | | In my head, this would make things tidier, but obviously there would be | stumbling blocks...
I can't see why this would make things tidier. In general compiling stuff as a module is useful if you want or need to have different system setups without the need to switch kernels (like one kernel supports wifi, the other one doesn't). Otherwise, assuming your hardware doesn't change frequently, compiling *everything* as a module won't make too much sense (IMHO).
| For example: I guess I would need to work out exactly which modules are | required at boot time (e.g. filesystem ones, I assume) and create an initrd | that would set them up for me. I've never actually made an initrd so I | have no idea how hard this would be.
It is not that hard, but you can simply avoid it... ;)
| What do people think? Does it seem like a good idea? Or is it just | immensely stupid?
I vote for the latter. :D
Regards,
Karsten -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.6 (GNU/Linux) Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCAYMTgUNlsZQzobwRAqPeAJ9MkhRirUCU1APWVLN0ZZYHz+hRqgCfaiGg 5csO/JlBsq0tSzzn72bMrNI= =VHIk -----END PGP SIGNATURE-----
-- [email protected] mailing list
