From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-0.8 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, RCVD_IN_DNSWL_NONE autolearn=ham autolearn_force=no version=3.4.2 Received: from minnie.tuhs.org (minnie.tuhs.org [45.79.103.53]) by inbox.vuxu.org (OpenSMTPD) with ESMTP id e3a90296 for ; Thu, 1 Aug 2019 18:27:13 +0000 (UTC) Received: by minnie.tuhs.org (Postfix, from userid 112) id 78EE09BA92; Fri, 2 Aug 2019 04:27:12 +1000 (AEST) Received: from minnie.tuhs.org (localhost [127.0.0.1]) by minnie.tuhs.org (Postfix) with ESMTP id 14E1F9BA7E; Fri, 2 Aug 2019 04:26:51 +1000 (AEST) Authentication-Results: minnie.tuhs.org; dkim=pass (1024-bit key; unprotected) header.d=kilonet.net header.i=@kilonet.net header.b="gEQcSfog"; dkim-atps=neutral Received: by minnie.tuhs.org (Postfix, from userid 112) id 4760D9BA7F; Fri, 2 Aug 2019 04:26:48 +1000 (AEST) Received: from p3plsmtpa07-04.prod.phx3.secureserver.net (p3plsmtpa07-04.prod.phx3.secureserver.net [173.201.192.233]) by minnie.tuhs.org (Postfix) with ESMTPS id BCCA19BA7E for ; Fri, 2 Aug 2019 04:26:47 +1000 (AEST) Received: from medusa.kilonet.net ([72.69.11.12]) by :SMTPAUTH: with ESMTPA id tFmnhkh5kuzy7tFmohqAyY; Thu, 01 Aug 2019 11:26:47 -0700 Received: from [199.89.231.101] (ender.kilonet.net [199.89.231.101]) by medusa.kilonet.net (8.14.8/8.15.1) with ESMTP id x71IQj1m029135 for ; Thu, 1 Aug 2019 14:26:45 -0400 (EDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kilonet.net; s=default; t=1564684005; bh=gUjPpHdxqcAIUpfo0t3D2uVa6VkNlpXxISaV/xUTFgc=; h=Subject:To:References:From:Date:In-Reply-To; b=gEQcSfoghaM1RcRXK192bcSpi57kPMusS+RiBdpTkNQufwzGhgSIpdkUBZISL6S6I 0cZxunOEBJ/3s4oNj0lo+IA/xlNIrZ1Sn0aPmz+zSkT7qh6BRGvUsUG84/Xz38ZzSy H9n6SNEiCA0N5JK2jzETXD+OyDPtsS5T2BhsUgkY= To: tuhs@minnie.tuhs.org References: <201908011235.x71CZP2B035023@tahoe.cs.Dartmouth.EDU> From: Arthur Krewat Message-ID: Date: Thu, 1 Aug 2019 14:26:37 -0400 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.8.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit Content-Language: en-US X-CMAE-Envelope: MS4wfPMl07SNLeZ85yHG7XR8iYVvREWi4WqAXFUWw4r87HioGZ82ZeB0Yqx52osVhW7mNczH/9rF85l0xnXgAbtA98QpxhNpxuIJqLa6lanAtWe7W+nmidEm EwYXckDKxWmbo3OqutFhaNNsuNXC0T44qITZR83zXu3s4Np+KpQElrPF Subject: Re: [TUHS] Who's behind the UNIX filesystem permission X-BeenThere: tuhs@minnie.tuhs.org X-Mailman-Version: 2.1.26 Precedence: list List-Id: The Unix Heritage Society mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: tuhs-bounces@minnie.tuhs.org Sender: "TUHS" On 8/1/2019 1:01 PM, Nemo Nusquam wrote: > On 08/01/19 08:35, Doug McIlroy wrote (in part): >> Yet clean as the idea of groups >> was, it has been used only sporadically (in my experience). > Interesting... we used groups extensively (qa, staging, dev, research, > release, ...) but never ACLs. I've had occasion to use groups extensively in various places I've consulted. Defense Contractors, educational institutions, etc. That, and quotas. I've used Solaris ZFS ACLs, and Linux ACLs to solve many problems. There's always an exception to the UNIX rule when it comes to owner/group/world, and trying to corral users into that paradigm is not always fruitful. Although, in one case, a common storage area with both the setgid and setuid bit on the parent, and various Engineering departments writing files and directories to it, was a really cool solution to a problem although it used secondary groups as well. art k.