<div dir="ltr"><div class="gmail_extra"><div class="gmail_quote">On Thu, Mar 5, 2015 at 9:13 AM, Jan Stary <span dir="ltr"><<a href="mailto:hans@stare.cz" target="_blank">hans@stare.cz</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">> Those aren't hardlinks, but /tmp is a symlink to /private/tmp. Your<br>
> vim just happens to realpath(3) before saving, it seems.<br>
<br>
</span>It's not a symlink, they have the same inode number.<br>
A symlink would look like this:<br></blockquote></div><br>Your observation would be valid if the file /tmp/whatever were symlinked. But it's not that specific file, but the directory /tmp that is symlinked. Naturally, anything within it is going to have the same inode number whether accessed via the symlink /tmp or the real path /private/tmp.</div><div class="gmail_extra"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr"><div>brandon s allbery kf8nh sine nomine associates</div><div><a href="mailto:allbery.b@gmail.com" target="_blank">allbery.b@gmail.com</a> <a href="mailto:ballbery@sinenomine.net" target="_blank">ballbery@sinenomine.net</a></div><div>unix, openafs, kerberos, infrastructure, xmonad <a href="http://sinenomine.net" target="_blank">http://sinenomine.net</a></div></div></div>
</div></div>