Actually the really savvy admin, or patch/fix script author, would perform a sanity check on
files to be removed by the patch, opening it, fstat()ing it, chmod() it to remove SUID/SGID
bits, unlink()ing it, and checking to ensure that the next fstat() returns a link count of
zero. If that fails (someone else has a hard link to it) then over-write the file contents
with an program which does the following:
* syslog()s the user and the command argument
* optionally warns the user that they are attempting to use an out-dated version of the
program (and advising them against using hard links to system binaries in general?)
* optionally wraps the new binary (execve()'s it) or exits