Re: kldload vs Statically compiled in kernel

2010-03-16 Thread Alexander Best
sure there are advantages. with a module you can change code in src, recompile the kernel module and then reload it. this lets you test your changes without having to reboot. i also use modules for devices i only attached every now and then, like a usb dongle device for doing bluetooth. i only loa

Re: kldload vs Statically compiled in kernel

2010-03-16 Thread Polytropon
On Tue, 16 Mar 2010 19:37:58 -0500, Brandon Falk wrote: > Hello fellow FreeBSD mates, > > I've always statically compiled in my modules into my kernel, rather > then using kldload, or throwing them in /boot/loader.conf. I'm just > wondering if there are actually any advantages to doing it this

Re: kldload vs Statically compiled in kernel

2010-03-16 Thread Adam Vande More
On Tue, Mar 16, 2010 at 7:37 PM, Brandon Falk wrote: > Hello fellow FreeBSD mates, > > I've always statically compiled in my modules into my kernel, rather then > using kldload, or throwing them in /boot/loader.conf. I'm just wondering if > there are actually any advantages to doing it this way.

kldload vs Statically compiled in kernel

2010-03-16 Thread Brandon Falk
Hello fellow FreeBSD mates, I've always statically compiled in my modules into my kernel, rather then using kldload, or throwing them in /boot/loader.conf. I'm just wondering if there are actually any advantages to doing it this way. Thanks, Brandon Falk __