From owner-freebsd-hackers@freebsd.org  Sat Mar  3 15:45:39 2018
Return-Path: <owner-freebsd-hackers@freebsd.org>
Delivered-To: freebsd-hackers@mailman.ysv.freebsd.org
Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1])
 by mailman.ysv.freebsd.org (Postfix) with ESMTP id 961DEF4616C
 for <freebsd-hackers@mailman.ysv.freebsd.org>;
 Sat,  3 Mar 2018 15:45:39 +0000 (UTC) (envelope-from kib@freebsd.org)
Received: from kib.kiev.ua (kib.kiev.ua [IPv6:2001:470:d5e7:1::1])
 (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits))
 (Client did not present a certificate)
 by mx1.freebsd.org (Postfix) with ESMTPS id 0B68686E43;
 Sat,  3 Mar 2018 15:45:38 +0000 (UTC) (envelope-from kib@freebsd.org)
Received: from tom.home (kib@localhost [127.0.0.1])
 by kib.kiev.ua (8.15.2/8.15.2) with ESMTPS id w23FjMAa025959
 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO);
 Sat, 3 Mar 2018 17:45:25 +0200 (EET) (envelope-from kib@freebsd.org)
DKIM-Filter: OpenDKIM Filter v2.10.3 kib.kiev.ua w23FjMAa025959
Received: (from kostik@localhost)
 by tom.home (8.15.2/8.15.2/Submit) id w23FjM60025956;
 Sat, 3 Mar 2018 17:45:22 +0200 (EET) (envelope-from kib@freebsd.org)
X-Authentication-Warning: tom.home: kostik set sender to kib@freebsd.org using
 -f
Date: Sat, 3 Mar 2018 17:45:22 +0200
From: Konstantin Belousov <kib@freebsd.org>
To: "Robert N. M. Watson" <robert.watson@cl.cam.ac.uk>
Cc: Alex Richardson <alexrichardson315@gmail.com>,
 "<cl-capsicum-discuss@lists.cam.ac.uk>" <cl-capsicum-discuss@lists.cam.ac.uk>, 
 Mariusz Zaborski <oshogbo@freebsd.org>,
 Justin Cormack <justin@specialbusservice.com>, freebsd-hackers@freebsd.org
Subject: Re: [capsicum] unlinkfd
Message-ID: <20180303154522.GH3194@kib.kiev.ua>
References: <20180302183514.GA99279@x-wing>
 <CAK4o1Wyk54chHobhUkb2PBUtaWOF2rDv6tkX_bFGY6D331xUqw@mail.gmail.com>
 <17DE0BFF-42A2-4CD7-B09C-ABA2606C4041@cl.cam.ac.uk>
 <CAEeofcjZAq_3Q7O5N-JHPZxW9HufofRgteFRta9U+zAqn1RnvQ@mail.gmail.com>
 <1ED213FC-D0CA-46D9-B6D1-EA261F2B80F5@cl.cam.ac.uk>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1ED213FC-D0CA-46D9-B6D1-EA261F2B80F5@cl.cam.ac.uk>
User-Agent: Mutt/1.9.3 (2018-01-21)
X-Spam-Status: No, score=-2.9 required=5.0 tests=ALL_TRUSTED,BAYES_00
 autolearn=ham autolearn_force=no version=3.4.1
X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on tom.home
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.25
Precedence: list
List-Id: Technical Discussions relating to FreeBSD
 <freebsd-hackers.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers/>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
 <mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 03 Mar 2018 15:45:39 -0000

On Sat, Mar 03, 2018 at 12:16:34PM +0000, Robert N. M. Watson wrote:
> (3) Want capability-based access to a persistent hierarchal namespace
> full of files. This is well served by the current at(2) system calls
> along with filesystems, although there are API gaps (e.g., a lack of
> unlinkat(2) in FreeBSD).

Why do you claim this ?  We have unlinkat(2).