RE: suggestion

[root <evpopkov@carry.neonet.lv>]

> IMHO, we should start with the latest kernel in order not to do what is
> already done...

 OK, but what  is already done? And what  are we going to do?  We know that
kernel code  is designed,  written, released,  reviewed, tested  and fixed.
It's passing all these stages already.
 Where is the  place for LKAP? Somewhere around `reviewed'  and `tested', I
believe.  Note  that currently  the  code  is  already being  examined  and
checked. If we see  our role in doing something that no  one is doing, then
we probably need to  `innovate' :) We can start reading the  code in a loud
to the plants to see whether they grow faster.
 We will be  doing what is already  done, all the time,  otherwise why this
project? 2.4.x will stabilize and mature,  sooner or later, like 2.0.x did,
so why bother?


---

 "Teddy - I suppose Mummy and Daddy are real, aren't they?"
 Teddy said, "You ask such silly questions, David. Nobody knows what
'real' really means. Let's go indoors."

 Brian W. Aldiss, Supertoys Last All Summer Long


Kernel-audit:  discussion list for security and the linux kernel
Archive:       http://mail.nl.linux.org/kernel-audit/