Re: A place to start

[Daniel Taylor <dante@plethora.net>]

On the contrary, if we can get enough eyes it gets better.

200 people, 4500 .c and .h files, that's about 23 files per person.

Yuk.
That's a lot of code to look at, but since more than half of this
is in the .h files that means an average of 10 .c files per person.

Still quite a bit of work, but doable as long as things are blocked
up by subsystem. Only about a quarter of the total [ch] files are drivers,
so if we focus on a particular architecture first, it is possible that we
can get useful work done with fewer people or fewer files per person.


Daniel Taylor                Embedded and custom Linux integration.
dante@plethora.net           (612)747-1609

On Sun, 11 Jun 2000, Tom Vogt wrote:

> "Bechtolsheim, Stephan" <sbechtol@chi.navtech.com> wrote:
> > 1. Use the newest kernel
> 
> this means keeping up with changes. of which there's quite a lot between
> Linux kernels releases.
> 
> the other alternative is freezing it. choose one specific kernel and audit
> that.
> 
> 
> -- 
> Welcome to the Information Superspyway
> 
> Kernel-audit:  discussion list for security and the linux kernel
> Archive:       http://mail.nl.linux.org/kernel-audit/
> 


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