From owner-freebsd-fs@FreeBSD.ORG Wed Mar 1 18:32:54 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 C830716A420; Wed, 1 Mar 2006 18:32:54 +0000 (GMT) (envelope-from mday@apple.com) Received: from mail-out3.apple.com (mail-out3.apple.com [17.254.13.22]) by mx1.FreeBSD.org (Postfix) with ESMTP id CAFE643D64; Wed, 1 Mar 2006 18:32:52 +0000 (GMT) (envelope-from mday@apple.com) Received: from relay6.apple.com (a17-128-113-36.apple.com [17.128.113.36]) by mail-out3.apple.com (8.12.11/8.12.11) with ESMTP id k21IWqNb023021; Wed, 1 Mar 2006 10:32:52 -0800 (PST) Received: from [17.202.43.217] (doomsday.apple.com [17.202.43.217]) by relay6.apple.com (Apple SCV relay) with ESMTP id 54BD928D; Wed, 1 Mar 2006 10:32:52 -0800 (PST) In-Reply-To: <20060301182001.W40707@fledge.watson.org> References: <20060301182001.W40707@fledge.watson.org> Mime-Version: 1.0 (Apple Message framework v749) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: <5D13DC0E-0ABB-4A3C-B760-18BC2E978DB0@apple.com> Content-Transfer-Encoding: 7bit From: Mark Day Date: Wed, 1 Mar 2006 10:32:37 -0800 To: Robert Watson X-Mailer: Apple Mail (2.749) X-Brightmail-Tracker: AAAAAA== 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:32:54 -0000 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. > 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. -Mark