| 
      
      
      From: Geert U. <ge...@li...> - 2001-06-17 09:55:07
      
     | 
| On Sun, 17 Jun 2001, Ken Tyler wrote:
> On Sun, 17 Jun 2001, Geert Uytterhoeven wrote:
> > I'm suffering from the same problem w.r.t. writing corrupted data to my DDS-1
> > under 2.4.x: so far ik _looks_ like it doesn't happen under 2.2.17, but I can't
> > prove it due to the nature of statistics. It's much easier to prove a problem
> > is there (you need only one `true' report), then proving the problem is not
> > there (you need infinite `false' reports). In the mean time I found one problem
> > under 2.2.19 too, so either it got introduced between 2.2.17 and 2.2.19, or it
> > does happen under 2.2.17 too.
> 
> I know what you're saying, Carl Popper and philosophy of science etc,
> repeated observations of sunrise every morning is no proof that it will
> rise tomorrow morning.
Actually sometimes the Sun doesn't rise in the morning due to an opaque moon
being in between :-)
> So you're saying that running the suggested make loop under 2.2.10
> overnight is not worth doing because it can't *prove* the absence of the
> problem ?
> 
>              2.2.10 make -j 10        2.4.5 make -j 10 
> 
> success           10                       0
> 
> fail               0                      10
> 
> comes pretty close to convicing me, where would you put your money ?
Sounds sufficiently convincing to me.
> Something else occured to me, is it possible that one of the daemons or
> some chron job splats something ?
Even then it's a kernel bug. Apps should not be able to crash the kernel.
Gr{oetje,eeting}s,
						Geert
--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- ge...@li...
In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
							    -- Linus Torvalds
 |