Has anyone put any thought into putting restrictions on what a module
can modify when loaded into the kernel? If there is, say, ever binary
third party driver support and this is provided without source some
restrictions on what kernel data this module can link to and modify
when loaded might be a
From: "Kris Kennaway" <[EMAIL PROTECTED]>
>I'm not sure what the point of this would really be..nor how you
could
>enforce it. Perhaps you should submit a proof of concept ;-)
>
>Kris
With more thought I suppose this would be a lot more effort than I had
first thought, and a different out come fo
From: "Poul-Henning Kamp" <[EMAIL PROTECTED]>
> I have created a patch which goes a long way to clean up the the
> usage of the API. The patch is generated
automatically
> and the objectfiles are identical if line numbers are preserved by
> breaking style(9).
>
> You can find the script and the
