On Wed, 2002-02-27 at 17:33, Alan Cox wrote:
> > /root/.bashrc /etc/fstab'), wouldn't 'cp' (or most any other app) first
> > unlink the first file (/etc/fstab), then create and write the new one?
>
> Unlikely - It will truncate it and write over it. Try strace cp 8)
Excellent, then I am totally missing something!
Then truncate would have to be implemented, for the very limited case of
using 'cp'. ;-)
The mount option ('undeltrunc?') would have to be implemented. However,
I just looked at the strace of vi for fun, and then remembered that it
uses a temporary file which is unlinked after the save. Considering the
amount of truncates and unlinks that could potentially happen on a
system, .undelete would undoubtedly fill up quickly. Filtering files
going into .undelete could be an option, but this would be kludgey to
put into the kernel, even for a daemon.
What is your opinion of having a mount option of 'undel' and a mount
option of 'undeltrunc'? The defaults for mount would be to not do
either. This way you could do something like:
mount -o undel / # saves unlink, not truncated
mount /var # does not save truncated or unlink
mount -o undel,undeltrunc /home # saves unlink and truncated
A cron job or user daemon (or filter of some sort) could monitor those
directories that were mounted with undel.
Jamie
-- Email: jstrand1@rochester.rr.com GPG/PGP ID: 26384A3A Fingerprint: D9FF DF4A 2D46 A353 A289 E8F5 AA75 DCBE 2638 4A3A
- 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/
This archive was generated by hypermail 2b29 : Thu Feb 28 2002 - 21:00:40 EST