Messages in this thread | | | From | Tim Connors <> | Subject | Re: XFS: how to NOT null files on fsck? | Date | Tue, 13 Jul 2004 20:27:30 +1000 |
| |
Chris Wedgwood <cw@f00f.org> said on Tue, 13 Jul 2004 02:53:00 -0700: > at which point you've stomped on your file. it's non uncommong for > KDE to do this (even though the window would apparently be very small)
KDE is a peice of shit with regards to file handling.
It seems they never learnt the lessons of writing files in Unix that have been learnt over the last 30 years.
How the hell can you afford to hose your entire WM because KDE decides to write some obscure file at some time when the NFS servers just happen to be temporarily down? What ever happened to the standard practice of write to temp file, then atomic rename? What ever happened to making backups of critical files before overwriting them? Furrfu.
Makes me glad I use a much more sane WM, but I pity those 3 users in the space of a few minutes who lost all of their settings.
BTW, I have submitted the occasional bug to Debian because packages will cause dataloss to an /etc file if the disk happens to run out at the wrong moment (quite a common occurence for me). Furrfu people - this is so bloody simple to get right.
-- TimC -- http://astronomy.swin.edu.au/staff/tconnors/ The prolonged application of polysyllabic vocabulary infallibly exercises a deleterious influence on the fecundity of expression, rendering the ultimate tendancy apocryphal. - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
| |