From owner-freebsd-fs@FreeBSD.ORG Wed Mar 1 18:42:55 2006 Return-Path: X-Original-To: freebsd-fs@FreeBSD.org Delivered-To: freebsd-fs@FreeBSD.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E141816A420 for ; Wed, 1 Mar 2006 18:42:55 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [209.31.154.42]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4BA2443D45 for ; Wed, 1 Mar 2006 18:42:55 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [209.31.154.41]) by cyrus.watson.org (Postfix) with ESMTP id 7529546BB1; Wed, 1 Mar 2006 13:42:19 -0500 (EST) Date: Wed, 1 Mar 2006 18:47:05 +0000 (GMT) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Mark Day In-Reply-To: <5D13DC0E-0ABB-4A3C-B760-18BC2E978DB0@apple.com> Message-ID: <20060301184602.N40707@fledge.watson.org> References: <20060301182001.W40707@fledge.watson.org> <5D13DC0E-0ABB-4A3C-B760-18BC2E978DB0@apple.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-fs@FreeBSD.org Subject: Re: Add a file flag for "hidden" files? X-BeenThere: freebsd-fs@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Filesystems List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 01 Mar 2006 18:42:56 -0000 On Wed, 1 Mar 2006, Mark Day wrote: > On Mar 1, 2006, at 10:22 AM, Robert Watson wrote: > >> I don't see any problem with this. The only flag I know of in FreeBSD that >> might not appear in Mac OS X is the system snapshot flag, which was added >> to UFS after Apple forked from the FreeBSD source. > > Mac OS X is missing both the NOUNLINK and the SNAPSHOT flags. > > Since Mac OS X doesn't implement the functionality corresponding to either > bit, my plan was to leave those #defines commented out in the Mac OS X > headers, with a comment indicating we don't implement that functionality. > I'm a little concerned that an app might see those bits defined, try to use > the functionality, and be surprised when it doesn't work as expected. Sounds good -- as long as they are marked as reserved values in Mac OS X, that should (hopefully) prevent later collisions. >> We have talked about adding a flag to hint the presence of extended ACL >> data also, so that applications know if they should rely solely on stat() >> for protection information, or also call acl_get_{fd,file,link}() to >> receive extended ACL data for ls(1) output. Is your plan to mask hidden >> files solely in user space, or to look at masking it in kernel also? > > I knew I'd forgotten to mention something. The plan is that this bit is > purely a hint to user space. It's up to the application (especially a GUI) > to decide whether to show a hidden file to the user or not. Sounds good. Do you plan to implement a hidden flag only in the user flag range, or also a system hidden flag? Robert N M Watson