From owner-freebsd-fs@freebsd.org  Tue Jan  5 02:24:05 2016
Return-Path: <owner-freebsd-fs@freebsd.org>
Delivered-To: freebsd-fs@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org
 [IPv6:2001:1900:2254:206a::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 8342BA62026
 for <freebsd-fs@mailman.ysv.freebsd.org>; Tue,  5 Jan 2016 02:24:05 +0000 (UTC)
 (envelope-from sef@kithrup.com)
Received: from kithrup.com (Kithrup.COM [64.142.31.202])
 (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 48F4E1CE8
 for <freebsd-fs@freebsd.org>; Tue,  5 Jan 2016 02:24:04 +0000 (UTC)
 (envelope-from sef@kithrup.com)
Received: from kithrup.com (localhost [127.0.0.1])
 by kithrup.com (8.14.4/8.14.4) with ESMTP id u052O349097374;
 Mon, 4 Jan 2016 18:24:03 -0800 (PST) (envelope-from sef@kithrup.com)
Received: (from sef@localhost)
 by kithrup.com (8.14.4/8.14.4/Submit) id u052O3jo097373;
 Mon, 4 Jan 2016 18:24:03 -0800 (PST) (envelope-from sef)
Date: Mon, 4 Jan 2016 18:24:03 -0800 (PST)
From: Sean Eric Fagan <sef@Kithrup.COM>
Message-Id: <201601050224.u052O3jo097373@kithrup.com>
To: rmacklem@uoguelph.ca
Subject: Re: Monitoring FS changes
Cc: freebsd-fs@freebsd.org
In-Reply-To: <416747176.149128068.1451960539354.JavaMail.zimbra@uoguelph.ca>
X-BeenThere: freebsd-fs@freebsd.org
X-Mailman-Version: 2.1.20
Precedence: list
List-Id: Filesystems <freebsd-fs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-fs/>
List-Post: <mailto:freebsd-fs@freebsd.org>
List-Help: <mailto:freebsd-fs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-fs>,
 <mailto:freebsd-fs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Tue, 05 Jan 2016 02:24:05 -0000

>Just wondering how they handle the case of multiple hard links in different directories?

You get back _a_ name, not necessarily _the_ name.  And I believe (although
I'd have to check the code) an error if the file is open-unlinked.

Although then xnu has support for getting the next hard link (this is pretty
HFS+ specific, mind you).