Re: netgraph.ko vs. compiled in.
On Thu, Jan 01, 2004 at 03:02:41PM -0500, Bill Moran wrote: > Matthew Seaman wrote: > >It's generally best either to kldload all of the netgraph modules you > >require for this purpose or to compile them all into the kernel. One > >way, or the other, but not a mixture of both. > I would go beyond "generally best" and straight into "it doesn't work". > My question is, "Is this fact documented somewhere, and I didn't see it?" > Because, if it's not, I'm going to put together a doc patch and file a PR. Hmmm... I've seen people mention similar effects where various other modules insisting on kldload'ing their dependencies even if they're already in the kernel. They pop up on various mailing lists over time. You may be right in saying "it doesn't work" -- but I have no idea whether that is correct in all cases. I get the feeling that most people will go to great pains to prevent their kernel code doing annoying things like that. Of course, if you compile, say, netgraph into your kernel, your buildkernel run shouldn't produce a separate netgraph.ko module. If there's one in /modules or wherever the equivalent is for 5.x then it's a hangover from a previous kernel. Chances are that if you get rid of the old netgraph.ko then things may well work as you expect. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
Re: netgraph.ko vs. compiled in.
Matthew Seaman wrote: On Thu, Jan 01, 2004 at 02:38:09PM -0500, Bill Moran wrote: If I build a kernel with "options netgraph", in order to use mpd, netgraph.ko is still loaded at boot (with an error) but mpd does not work. You can't simultaneously load a .ko and have the same code compiled into the kernel. _I_ know that. Tell it to whatever part of the system is trying to load the kld. I'm not saying that being unable to load a kld for a service that's already compiled in is an error. I'm saying the fact that mpd tries to load the kld when it's already compiled in is the error. If I build the kernel without netgraph, netgraph.ko loads, along with other netgraph modules required for PPTP, and mpd works like a charm. What I haven't tried yet, is compiling a kernel with all the options for all the netgraph modules I'll need compiled in to see if that works. It's generally best either to kldload all of the netgraph modules you require for this purpose or to compile them all into the kernel. One way, or the other, but not a mixture of both. I would go beyond "generally best" and straight into "it doesn't work". My question is, "Is this fact documented somewhere, and I didn't see it?" Because, if it's not, I'm going to put together a doc patch and file a PR. -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
Re: netgraph.ko vs. compiled in.
On Thu, Jan 01, 2004 at 02:38:09PM -0500, Bill Moran wrote: > If I build a kernel with "options netgraph", in order to use mpd, > netgraph.ko > is still loaded at boot (with an error) but mpd does not work. You can't simultaneously load a .ko and have the same code compiled into the kernel. > If I build the kernel without netgraph, netgraph.ko loads, along with other > netgraph modules required for PPTP, and mpd works like a charm. > > What I haven't tried yet, is compiling a kernel with all the options for all > the netgraph modules I'll need compiled in to see if that works. It's generally best either to kldload all of the netgraph modules you require for this purpose or to compile them all into the kernel. One way, or the other, but not a mixture of both. Cheers, Matthew -- Dr Matthew J Seaman MA, D.Phil. 26 The Paddocks Savill Way PGP: http://www.infracaninophile.co.uk/pgpkey Marlow Tel: +44 1628 476614 Bucks., SL7 1TH UK pgp0.pgp Description: PGP signature
netgraph.ko vs. compiled in.
I'm not sure if this is a bug, or intended behaviour. If the behaviour is intended, documentation improvements may be in order. If I build a kernel with "options netgraph", in order to use mpd, netgraph.ko is still loaded at boot (with an error) but mpd does not work. If I build the kernel without netgraph, netgraph.ko loads, along with other netgraph modules required for PPTP, and mpd works like a charm. What I haven't tried yet, is compiling a kernel with all the options for all the netgraph modules I'll need compiled in to see if that works. This is FreeBSD 4.9. Does anyone know if this is intended behaviour or a bug? If it's intended behaviour, is it in the documentation and I just haven't seen it? -- Bill Moran Potential Technologies http://www.potentialtech.com ___ [EMAIL PROTECTED] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[EMAIL PROTECTED]"
