On Thu, Feb 22, 2007 at 12:42:12PM -0800, Paul Eggert wrote: > "Robert Millan [ackstorm]" <[EMAIL PROTECTED]> writes: > > > How about attempting to write it, and if that fails then unlink ? > > (preferably > > checking the errno code for this condition) > > That doesn't sound right; it'd mean the result of installing (say) > /bin/bash would differ depending on whether someone currently happened > to be executing Bash. I think I'd rather have the unlink specified by > a command-line option of some sort. (We can argue about what the > default should be....).
Now that I think of it, overwriting the same inode isn't good either, since we can't garantee that the change will be atomical (and datafiles currently in used can have an intermediate "corrupted" state). Can we have it remove the link, and then reset all other links from the old inode to the new one, or is that completely insane? -- Robert Millan ACK STORM, S.L. - http://www.ackstorm.es/ _______________________________________________ Bug-coreutils mailing list [email protected] http://lists.gnu.org/mailman/listinfo/bug-coreutils
