Mailing-List: contact cygwin-help AT sourceware DOT cygnus DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT sourceware DOT cygnus DOT com>
List-Archive: <http://sourceware.cygnus.com/ml/cygwin/>
List-Post: <mailto:cygwin AT sourceware DOT cygnus DOT com>
List-Help: <mailto:cygwin-help AT sourceware DOT cygnus DOT com>, <http://sourceware.cygnus.com/ml/#faqs>
Sender: cygwin-owner AT sourceware DOT cygnus DOT com
Delivered-To: mailing list cygwin AT sourceware DOT cygnus DOT com
From: "Kevin Wright" <kwright AT uk DOT mdis DOT com>
To: "Cygwin" <cygwin AT sourceware DOT cygnus DOT com>
Subject: B20.1: File permissions
Date: Mon, 31 Jan 2000 10:24:14 -0000
Message-ID: <NDBBIBEHNKCJHEABEKOHOEHHCBAA.kwright@uk.mdis.com>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: 7bit
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook IMO, Build 9.0.2416 (9.0.2910.0)
X-MimeOLE: Produced By Microsoft MimeOLE V5.00.2314.1300
Importance: Normal

Can any one explain to me the cygwin philosophy of file permissions ?

I originally ran into trouble with test -w.  ls -l would report a file as
being writable, but test -w would say it wasn't.  When I tried to report
this as a bug, I was told it wasn't a bug but was by design !  Now I've not
seen any documentation anywhere on Unix that says that test -w only reports
files with 3w's as writable, so this must be an inconsistency at least.

Anyway I was informed if I downloaded a later snapshot, and set CYGWIN=ntsec
then this would solve my problem.

Sure enough the ls -l and test -w inconsistency disappeared under these
conditions.  Now I have the marvellous state of affairs where ls -l says a
file is writable and attrib says the file is read only.

Am I alone in trying to mix cygwin with normal NT commands ?

What is wrong with checking NT's and cygwin's version of permissions
throughout the code in a consistent manner ?

The above problems don't seem to fit with this quote from the cygwin FAQ
"What is it ?"

"Even if the development tools are of little to no use to you, you may have
interest in the many standard Unix utilities provided with the package. They
can be used both from the bash shell (provided) or from the standard Windows
command shell. "

Which doesn't state, but implies that cygwin utilities can be used in
conjunction with Windows based utilities.

My initial contact with cygwin was using B17 and I was impressed with the
range of utilities available and the ability to intermix commands.  However
the occasional command crashes when using pipes seemed to get more frequent,
so I upgraded to B20.1.  The command crashes went away, but I still haven't
found a configuration that works for me.

Would purchasing Cygwin 1.0 help to solve my problems ?






--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe AT sourceware DOT cygnus DOT com