On Wed, Dec 10, 2003 at 07:39:58AM +0100, Eduard Bloch wrote:
> Either with dh_make templates or (my favorite ;) with m-a, see
> /usr/share/doc/module-assistant/HOWTO-DEVEL.gz .
I saw somebody else point to this yesterday and now I've read it,
it looks like a good general purpose script. I wi
On Tue, Dec 09, 2003 at 10:07:59PM -0700, Lucas Albers wrote:
> Dude we have cars, don't reinvent the automobile.
> Grsecurity does this already.
Yes this is true, I'm in the process of testing some of my code
now. I've been working on several different modules this is just
an example.
> It
On Wed, Dec 10, 2003 at 07:39:58AM +0100, Eduard Bloch wrote:
> Either with dh_make templates or (my favorite ;) with m-a, see
> /usr/share/doc/module-assistant/HOWTO-DEVEL.gz .
I saw somebody else point to this yesterday and now I've read it,
it looks like a good general purpose script. I wi
On Tue, Dec 09, 2003 at 10:07:59PM -0700, Lucas Albers wrote:
> Dude we have cars, don't reinvent the automobile.
> Grsecurity does this already.
Yes this is true, I'm in the process of testing some of my code
now. I've been working on several different modules this is just
an example.
> It
On Wed, Dec 10, 2003 at 07:39:58AM +0100, Eduard Bloch wrote:
> * Steve Kemp [Tue, Dec 09 2003, 06:21:02PM]:
> > 3. Building on my machine to produce a binary x86 module, and
> >making the binary package Depends: upon kernel-image-2.4.21-386
>
> Better don't make it Depends (use Recom
#include
* Steve Kemp [Tue, Dec 09 2003, 06:21:02PM]:
> 2. Providing it in source form and expecting the user to build it,
>like the nvidia module.
> 3. Building on my machine to produce a binary x86 module, and
Either with dh_make templates or (my favorite ;) with m-a, see
/us
On Wed, Dec 10, 2003 at 07:39:58AM +0100, Eduard Bloch wrote:
> * Steve Kemp [Tue, Dec 09 2003, 06:21:02PM]:
> > 3. Building on my machine to produce a binary x86 module, and
> >making the binary package Depends: upon kernel-image-2.4.21-386
>
> Better don't make it Depends (use Recom
#include
* Steve Kemp [Tue, Dec 09 2003, 06:21:02PM]:
> 2. Providing it in source form and expecting the user to build it,
>like the nvidia module.
> 3. Building on my machine to produce a binary x86 module, and
Either with dh_make templates or (my favorite ;) with m-a, see
/us
Dude we have cars, don't reinvent the automobile.
Grsecurity does this already.
http://www.grsecurity.net and 10,000 times more stuff.
Some sample kernel config options, so you can get a brief overview:
http://www.cs.montana.edu/faq/grsec/
It specifically has tpe, and has been extensivelly vetted f
Dude we have cars, don't reinvent the automobile.
Grsecurity does this already.
http://www.grsecurity.net and 10,000 times more stuff.
Some sample kernel config options, so you can get a brief overview:
http://www.cs.montana.edu/faq/grsec/
It specifically has tpe, and has been extensivelly vetted f
On Tue, Dec 09, 2003 at 02:34:00PM -0500, David Z Maze wrote:
> Steve Kemp <[EMAIL PROTECTED]> writes:
> Is it a patch, or a module? I'd expect that most things come as one
> or the other.
It's purely a module, and can be built with the kernel headers
installed.
> > 2. Providing it in s
Steve Kemp <[EMAIL PROTECTED]> writes:
> What is the recommended way to distribute a kernel module?
>
> I see the options as :
>
> 1. Making a kernel-patch which could be build with
> kernel-package.
Is it a patch, or a module? I'd expect that most things come as one
or the othe
On Tue, Dec 09, 2003 at 02:34:00PM -0500, David Z Maze wrote:
> Steve Kemp <[EMAIL PROTECTED]> writes:
> Is it a patch, or a module? I'd expect that most things come as one
> or the other.
It's purely a module, and can be built with the kernel headers
installed.
> > 2. Providing it in s
Steve Kemp <[EMAIL PROTECTED]> writes:
> What is the recommended way to distribute a kernel module?
>
> I see the options as :
>
> 1. Making a kernel-patch which could be build with
> kernel-package.
Is it a patch, or a module? I'd expect that most things come as one
or the othe
What is the recommended way to distribute a kernel module?
I see the options as :
1. Making a kernel-patch which could be build with kernel-package.
2. Providing it in source form and expecting the user to build it,
like the nvidia module.
3. Building on my machine to p
What is the recommended way to distribute a kernel module?
I see the options as :
1. Making a kernel-patch which could be build with kernel-package.
2. Providing it in source form and expecting the user to build it,
like the nvidia module.
3. Building on my machine to p
16 matches
Mail list logo
