DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:from:to:subject:date:message-id:references
	:in-reply-to:content-type:content-id:content-transfer-encoding
	:mime-version; q=dns; s=default; b=aZUH0qbpCmDywO2rMRSmZxNY+omcQ
	hguP/WIG00IefVJEq5YrjynkvKhRqJtSWj0fH6uIkHWnqVeq80GTGPKT2BQaJLPz
	cGnfAxQ0b4xAlsBEXHGzVg9FLIsBrXyxx39dOWMjXrQ/tDrCfTD7ZfB8E09fm3Vy
	cI7WsDFNJVHHIk=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
From: Bill Zissimopoulos <billziss AT navimatics DOT com>
To: "cygwin AT cygwin DOT com" <cygwin AT cygwin DOT com>
Subject: Re: BSD file flags support in Cygwin?
Date: Tue, 14 Nov 2017 19:17:47 +0000
Message-ID: <D6307C50.F768%billziss@navimatics.com>
References: <D62F6895.F75A%billziss AT navimatics DOT com> <20171114100658 DOT GH6054 AT calimero DOT vinschen DOT de>
In-Reply-To: <20171114100658.GH6054@calimero.vinschen.de>
received-spf: None (protection.outlook.com: navimatics.com does not designate permitted sender hosts)
spamdiagnosticoutput: 1:99
spamdiagnosticmetadata: NSPM
Content-Type: text/plain; charset="utf-8"
Content-ID: <8A227856A3A813438EB8A7848676E273 AT namprd07 DOT prod DOT outlook DOT com>
MIME-Version: 1.0
X-MS-Exchange-CrossTenant-Network-Message-Id: 94b853ea-650d-4d7a-9219-08d52b946425
X-MS-Exchange-CrossTenant-originalarrivaltime: 14 Nov 2017 19:17:47.4693 (UTC)
X-MS-Exchange-CrossTenant-fromentityheader: Hosted
X-MS-Exchange-CrossTenant-id: 21071be9-4f9a-413b-89ac-8353a5d2410a
X-MS-Exchange-Transport-CrossTenantHeadersStamped: CY1PR07MB2200
X-IsSubscribed: yes
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from base64 to 8bit by delorie.com id vAEJI7n1025914

Corinna, thanks for your answer.

My question was largely to confirm my understanding as I probably do not
have time to produce such a patch currently. For the benefit of the
discussion and to assist any future attempts at doing this:

Chflags(2) and friends would be relatively easy to implement. OTOH the
BSD’s and OSX use stat(2) to report file flags in st_flags. Since Cygwin
lacks an st_flags field, we would have to somehow change struct stat to
accommodate it. Do you have guidance on how to handle such a change? Would
you even want such a change? [I suspect not.]

[I know some OS’es have had to deal with stat(2) changes over the years,
but I am not as familiar with Cygwin history.]

Bill


On 11/14/17, 2:06 AM, Corinna Vinschen wrote:

>On Nov 13 23:21, Bill Zissimopoulos wrote:
>> Does Cygwin have any support for BSD file flags (UF_* flags, such as
>> UF_HIDDEN, etc.)? These flags are often used to provide support for
>> Windows file attributes (FILE_ATTRIBUTE_*, such as
>>FILE_ATTRIBUTE_HIDDEN).
>> 
>> OSX and FreeBSD provide such support during stat(2) and chflags(2). I
>> expect that Cygwin does not have such support, but wanted to
>>double-check.
>> 
>> 
>>https://www.freebsd.org/cgi/man.cgi?query=chflags&apropos=0&sektion=2&man
>>pa
>> th=FreeBSD+11.1-RELEASE+and+Ports&arch=default&format=html
>
>No, we don't support this.  We couldn't support it via stat anyway,
>only via the extra chflags function group.  Patches welcome, as
>long as it's the entire group of functions so chflags(1) compiles
>OOTB.
>
>
>Corinna
>
>-- 
>Corinna Vinschen                  Please, send mails regarding Cygwin to
>Cygwin Maintainer                 cygwin AT cygwin DOT com
>Red Hat


--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple