From owner-freebsd-ports-bugs@FreeBSD.ORG Sun Mar 11 12:00:21 2007 Return-Path: X-Original-To: freebsd-ports-bugs@hub.freebsd.org Delivered-To: freebsd-ports-bugs@hub.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 1B19816A508 for ; Sun, 11 Mar 2007 12:00:21 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (freefall.freebsd.org [69.147.83.40]) by mx1.freebsd.org (Postfix) with ESMTP id D03DE13C48D for ; Sun, 11 Mar 2007 12:00:20 +0000 (UTC) (envelope-from gnats@FreeBSD.org) Received: from freefall.freebsd.org (gnats@localhost [127.0.0.1]) by freefall.freebsd.org (8.13.4/8.13.4) with ESMTP id l2BC0KQx033571 for ; Sun, 11 Mar 2007 12:00:20 GMT (envelope-from gnats@freefall.freebsd.org) Received: (from gnats@localhost) by freefall.freebsd.org (8.13.4/8.13.4/Submit) id l2BC0KX6033570; Sun, 11 Mar 2007 12:00:20 GMT (envelope-from gnats) Date: Sun, 11 Mar 2007 12:00:20 GMT Message-Id: <200703111200.l2BC0KX6033570@freefall.freebsd.org> To: freebsd-ports-bugs@FreeBSD.org From: jau@iki.fi (Jukka A. Ukkonen) Cc: Subject: Re: ports/107229: sysutils/coreutils: gcp fails to set default ACL X-BeenThere: freebsd-ports-bugs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: "Jukka A. Ukkonen" List-Id: Ports bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 11 Mar 2007 12:00:21 -0000 The following reply was made to PR ports/107229; it has been noted by GNATS. From: jau@iki.fi (Jukka A. Ukkonen) To: Mathias.Picker@gmx.de (Mathias Picker) Cc: bug-followup@FreeBSD.org Subject: Re: ports/107229: sysutils/coreutils: gcp fails to set default ACL Date: Sun, 11 Mar 2007 13:50:21 +0200 (EET) Quoting Mathias Picker: > > This problem still exists. The update to coreutils 6.7 does nothing to > solve it. Now asking the coreutils mailing list. Apparently the problem is that gcp tries to set the default ACL also on non-directory files. The current FreeBSD manual pages explain that default ACLs are only allowed for directories. And since default a ACL is something a new file or directory created under an existing directory should inherit by default as their initial ACLs, this makes perfect sense. The correct behaviour for gcp would be to either - not even try to set the default ACL for anything else but directories or - ignore the error returned unless the target is a directory. Apparently some other environments allow setting default ACLs for non-directory files and quietly ignore the issue, though, setting the default value makes no sense, because other files can inherit their initial ACLs only from the defaults set to their parent directories. Cheers, // jau .--- ..- -.- -.- .- .- .-.-.- ..- -.- -.- --- -. . -. / Jukka A. Ukkonen, Oxit Ltd, Finland /__ M.Sc. (sw-eng & cs) (Phone) +358-500-606-671 / Internet: Jukka.Ukkonen(a)Oxit.Fi (Home) +358-9-6215-280 / Internet: jau(a)iki.fi v .--- .- ..- ...-.- .. -.- .. .-.-.- ..-. .. + + + + My opinions are mine and mine alone, not my employers. + + + +