On 31/10, Erik Mouw wrote: | Why don't you just make a libc wrapper for the unlink(2) system call? | (A modified libc.so should do as well). That way it will work for all | of your applications on all filesystems. Because this won't take care of the journal, which may contain an extra copy of the previously written data. Also in transactional filesystems, overwriting data doesn't guarantee that the data is written in the same place: it will typically be written at another place and then the metadata will be updated afterwards. You have no control about that at user level, since you can't hook into the block freeing routine. Thanks for the reference btw :) - To unsubscribe from this list: send the line "unsubscribe linux-ext4" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
