> >The question is motivated by the following scenario:
> >I am using a 3rd party kernel module that I really do
> >not trust, and it exhibits strange behavior when I use
> >their free functions.
>
> If it's a *KERNEL* module, you have a whole different problem.
> Calling execv() will not likely free up memory leaked in the kernel.
>
That is, unfortunately, what I thought would be the case. Thanks
for the response.
Re: Another kernel releated GPL ? ... It is not GPL or LGPL. ... Simple scenario.... Take a memory allocator - if I put a malloc implementation in the kernel... the usual system calls/C library stuff not only is the law probably ... (Linux-Kernel)
Re: Another kernel releated GPL ? ... Simple scenario.... Now suppose I have a device driver that is part kernel and part user ... the usual system calls/C library stuff not only is the law probably ... Where is this "explicit statement" found ... (Linux-Kernel)
Tracking for Multiple Machines ...scenario is one in which there's a variety of hardware and functions, ...echo "This is really going to take some time, ... echo "Building kernel for $." ... (freebsd-questions)
Re: Unable to boot kernel on ANY Compaq system ... > Scenario 1: ... > a kernel panic in scenario 2. ... if I replace the kernel on the install disk with one I've ... > I were to boot via rescue and replace the installed kernel with mine, ... (Fedora)
