Re: A place to start

[David Ford <david@kalifornia.com>]

If we do it section by section, it's not very hard to keep up, even with
daily releases of kernels.  All we need to do is keep a list of when
"drivers/net/arp.c" was last audited and the md5sum of the file.  As long as
that md5sum doesn't change, the value of our audit remains the same as we
placed on it.

-d
p.s.  can the tail on the list messages include sub/unsub address please?


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.

--
"The difference between 'involvement' and 'commitment' is like an
eggs-and-ham breakfast: the chicken was 'involved' - the pig was
'committed'."


begin:vcard 
n:Ford;David
x-mozilla-html:TRUE
org:<img src="http://www.kalifornia.com/images/poweredbylinux.gif">
adr:;;;;;;
version:2.1
email;internet:david@kalifornia.com
title:Blue Labs Developer
x-mozilla-cpt:;-26528
fn:David Ford
end:vcard