renaming MacPorts' install directory - how to handle the TM backup(s)?

Brandon Allbery allbery.b at
Sun Sep 7 10:16:50 PDT 2014

On Sun, Sep 7, 2014 at 1:14 PM, René J.V. <rjvbertin at> wrote:

> On Sunday September 07 2014 10:24:09 Brandon Allbery wrote:
> > from overwriting a file (you'd want to break the hardlink first if you
> only
> > want it to affect that backup, and for that-backup-and-forward you'd need
> > to re-hardlink the later backups with the original inode number).
> A mv (rename) shouldn't change the inode, if at least the operation works
> the same way as on a more standard FS (without directory hardlinks :))

Yes, I was saying any operation other than actually writing the file should
be safe, and then saying what would be needed in the
actually-writing-the-file case to make it safe.

brandon s allbery kf8nh                               sine nomine associates
allbery.b at                                  ballbery at
unix, openafs, kerberos, infrastructure, xmonad
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the macports-users mailing list