From owner-freebsd-stable@FreeBSD.ORG Sat Jun 11 23:08:20 2005 Return-Path: X-Original-To: stable@freebsd.org Delivered-To: freebsd-stable@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 603B116A41C for ; Sat, 11 Jun 2005 23:08:20 +0000 (GMT) (envelope-from bfoz@bfoz.net) Received: from sccrmhc13.comcast.net (sccrmhc13.comcast.net [204.127.202.64]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1722443D55 for ; Sat, 11 Jun 2005 23:08:19 +0000 (GMT) (envelope-from bfoz@bfoz.net) Received: from [192.168.0.5] (c-24-6-134-233.hsd1.ca.comcast.net[24.6.134.233]) by comcast.net (sccrmhc13) with ESMTP id <2005061123081801600du1bpe>; Sat, 11 Jun 2005 23:08:19 +0000 Message-ID: <42AB6EE1.7070405@bfoz.net> Date: Sat, 11 Jun 2005 16:08:17 -0700 From: Brandon Fosdick User-Agent: Mozilla Thunderbird 1.0.2 (X11/20050326) X-Accept-Language: en-us, en MIME-Version: 1.0 To: =?ISO-8859-1?Q?Bj=F6rn_K=F6nig?= References: <42AA2B21.8040708@bfoz.net> <42AA761B.5020909@cs.tu-berlin.de> In-Reply-To: <42AA761B.5020909@cs.tu-berlin.de> X-Enigmail-Version: 0.91.0.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 8bit Cc: stable@freebsd.org Subject: Re: ACL not supported on 5.4? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 11 Jun 2005 23:08:20 -0000 Björn König wrote: > Hello Brandon, > > I get the same error messages if ACL are not enabled. I just want to > make sure that you didn't overlook the part of the handbook where it > says that you have to enable it. It seems that's exactly what happened. Thanks for pointing it out. > By the way, the option -k won't work on non-directories at all, see also > the manpage of setfacl. Ok, then the handbook needs fixing because it says "The -k flag will remove all of the currently defined ACLs from a file or file system", which would seem to imply that it works on files. Naturally I would have known better if I had read the man page, but I didn't. Are handbook bugs handled through send-pr like everything else? Thanks