Date: Wed, 1 Mar 2006 12:24:50 -0800 From: Mark Day <mday@apple.com> To: Robert Watson <rwatson@FreeBSD.org> Cc: freebsd-fs@FreeBSD.org Subject: Re: Add a file flag for "hidden" files? Message-ID: <3CABEB63-FFC3-42DC-97F1-FE79ADA96B66@apple.com> In-Reply-To: <20060301184602.N40707@fledge.watson.org> References: <DBD69E00-A9CB-45BA-8398-2A662D18D781@apple.com> <20060301182001.W40707@fledge.watson.org> <5D13DC0E-0ABB-4A3C-B760-18BC2E978DB0@apple.com> <20060301184602.N40707@fledge.watson.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mar 1, 2006, at 10:47 AM, Robert Watson wrote:
>>> 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?
Just in the user flag range.
-Mark
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CABEB63-FFC3-42DC-97F1-FE79ADA96B66>