Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com
X-Authentication-Warning: slinky.cs.nyu.edu: pechtcha owned process doing -bs
Date: Fri, 29 Aug 2003 09:41:46 -0400 (EDT)
From: Igor Pechtchanski <pechtcha AT cs DOT nyu DOT edu>
Reply-To: cygwin AT cygwin DOT com
To: Rob Clack <rnc AT sanger DOT ac DOT uk>
cc: cygwin AT cygwin DOT com
Subject: Re: [Fwd: Re: perl test fails]
In-Reply-To: <3F4F371A.1070905@sanger.ac.uk>
Message-ID: <Pine.GSO.4.56.0308290938520.601@slinky.cs.nyu.edu>
References: <3F4F1D8B DOT 9070505 AT sanger DOT ac DOT uk> <20030829095256 DOT GE614 AT emcb DOT co DOT uk>
 <3F4F2BFD DOT 2060408 AT sanger DOT ac DOT uk> <20030829105211 DOT GL614 AT emcb DOT co DOT uk>
 <3F4F371A DOT 1070905 AT sanger DOT ac DOT uk>
Importance: Normal
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

Rob,

Actually, this behavior also depends on the filesystem you use.
CYGWIN=ntsec alone only helps if you have NTFS.  For FAT you also need
"ntea" (i.e., CYGWIN="ntsec ntea" -- be aware that it'll create a large
file in your drive's root directory).  I believe permissions on FAT32 were
broken somehow, but don't recall the details -- just search the archives
for "FAT32 ntea".
	Igor

On Fri, 29 Aug 2003, Rob Clack wrote:

> Thank you Elfyn and Jurgen.  A few moment's thought would have reminded
> me that file permissions are handled differently on NT. ;)
>
> Regards
> Rob
>
> Elfyn McBratney wrote:
> > Rob Clack wrote:
> >
> >>[...]
> >>So there seems to be a couple of weensy buggettes there, though I'm not
> >>suggesting anyone bother to fix them unless they happen to be working
> >>there anyway.  They're not serious bugs, but they did obscure the real
> >>problem and waste quite a lot of my and several other people's time.
> >>
> >>1. chmod should surely change the permissions whatever the contents of
> >>the file, and if it doesn't, it should issue a message.  Silent failure
> >>is not very friendly.
> >
> >
> > If your on an NT variant all you have to do is set CYGWIN=ntsec (If you want
> > support for NT extended attributes you can add `ntea', too).  However, on
> > win9x the `ch*' family of calls retrun success (IIRC), as the underlying OS
> > does not support security in the way NT does.  I might be slightly wrong about
> > the win9x but, though it's documented in either the User's Guide of the FAQ.
> >
> > You can then use `ch{mod,own,grp}' in the same way you would on Linux.
> >
> > -- Elfyn

-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha AT cs DOT nyu DOT edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor AT watson DOT ibm DOT com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton

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