[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49CE3186.8090903@garzik.org>
Date: Sat, 28 Mar 2009 10:17:42 -0400
From: Jeff Garzik <jeff@...zik.org>
To: Stefan Richter <stefanr@...6.in-berlin.de>
CC: Mark Lord <lkml@....ca>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Matthew Garrett <mjg59@...f.ucam.org>,
Alan Cox <alan@...rguk.ukuu.org.uk>,
Theodore Tso <tytso@....edu>,
Andrew Morton <akpm@...ux-foundation.org>,
David Rees <drees76@...il.com>, Jesper Krogh <jesper@...gh.cc>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: Linux 2.6.29
Stefan Richter wrote:
> Jeff Garzik wrote:
>> Mark Lord wrote:
> [store browser session]
>>> fsync() isn't going to affect that one way or another
>>> unless the entire kernel freezes and dies.
>> ...which is one of the three common crash scenarios listed (and
>> experienced in the field).
>
> To get work done which one really cares about, one can always choose a
> system which does not crash frequently. Those who run unstable drivers
> for thrills surely do it on boxes on which nothing important is being
> done, one would think.
Once software is perfect, there is definitely a lot of useless crash
protection code to remove.
Jeff
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists