kconfig's file handling (was: XFS: how to NOT null files on fsck?)

[Oswald Buddenhagen]

heya,

read the attachement first (put on your asbestos underwear first ;).
not exactly news to me, but somehow i never got to fixing it ...

care needs to be taken to preserve file permissions and symlinks.

there are a few cases where the 'write temp file + rename' mechanism is
impossible to apply, though, as we are forced to overwrite the original
file: when we have no write permission in the directory the file lives
in, or if we write a foreign file (and are not supposed to grab
ownership). in these cases we cannot ensure integrity, but at least we
could prevent partial writes by first filling up the old file with
newlines up to the new size - the out of space error would occur while
the old data is still intact.

any takers? waldo?

greetings

-- 
Hi! I'm a .signature virus! Copy me into your ~/.signature, please!
--
Chaos, panic, and disorder - my work here is done.
-------------- next part --------------
An embedded message was scrubbed...
From: Tim Connors <tconnors at astro.swin.edu.au>
Subject: Re:  XFS: how to NOT null files on fsck?
Date: Tue, 13 Jul 2004 20:27:30 +1000
Size: 3916
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20040713/0b925112/attachment.eml>