On Fri, Apr 08, 2005 at 02:28:32PM +0200, Arjan van de Ven wrote: > On Fri, Apr 08, 2005 at 02:20:37PM +0200, Axel Thimm wrote: > > No, it's not, if you want to replace it with something better. > > even "something better" really should be built into the kernel... > (and I'd like to say that I'm sceptical about "something better" :) > > > > > > So please give another, more realistic example.... > > > > You are the kernel guru, never seen any non-hardware modules? ;) > > > > Choosing netfilter/netscheduling modules also comes to mind ... > > netscheduling should be autoloaded on use; eg when you in rules for it... > netfilter.. most of them should be autoloaded on use too... "should"? There is no way to autodetect that you want to have certain nat/conntrack module or a specific scheduler. Anyway there is demand for such a mechanism (the threads on this and bugzillas are witnesses), and there will always be, so let's better think on how and not why. -- Axel.Thimm at ATrpms.net
Attachment:
pgptIy9Pq7NrE.pgp
Description: PGP signature
