Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm
List-Subscribe: <mailto:cygwin-subscribe@sources.redhat.com>
List-Archive: <http://sources.redhat.com/ml/cygwin/>
List-Post: <mailto:cygwin@sources.redhat.com>
List-Help: <mailto:cygwin-help@sources.redhat.com>, <http://sources.redhat.com/ml/#faqs>
Sender: cygwin-owner@sources.redhat.com
Delivered-To: mailing list cygwin@sources.redhat.com
Message-ID: <000401c09d19$2812ae30$d938a8c0@Hadfield>
From: "Mark Hadfield" <m.hadfield@niwa.cri.nz>
To: "Corinna Vinschen" <cygwin@cygwin.com>
References: <20010221232921.X908@cygbert.vinschen.de> <000a01c09c73$7a43ce10$d938a8c0@Hadfield> <20010221212656.F7576@redhat.com> <00e601c09d10$379e4250$d938a8c0@Hadfield> <20010222220507.C908@cygbert.vinschen.de>
Subject: Re: Symlinks, executability, system attribute, etc (was Re: [ANNOUNCEMENT])
Date: Fri, 23 Feb 2001 10:48:13 +1300
Organization: NIWA
MIME-Version: 1.0
Content-Type: text/plain;
	charset="Windows-1252"
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 5.50.4133.2400
X-MimeOLE: Produced By Microsoft MimeOLE V5.50.4133.2400

Hi Corinna (et al)

> There's already no need to look into the file when `ntsec' is used
> on NTFS drives. In that case you simply set the x bit.

Thanks. I have avoided ntsec for 2 reasons:

* One of my hard disks is FAT32 (delivered that way by Compaq) and I noted
the warnings in the user's guide about ntsec vs FAT32 volumes. I've been
thinking about converting the disk and maybe will do soon.

* The case where looking in to the file is a real killer for me involves
files on a Unix file system served by Samba. So ntsec will have no effect
here, right? As I understand it Samba is converting the original Unix file
security information to DOS-type for the client then Cygwin is going thru
all sorts of hoops to reconstruct it. (Perhaps Samba can be configured to
serve up NTFS-style info for NT clients--I'll look into it. Perhaps an NFS
client could do this--I'll look into that too!)

P.S. I've used Cygwin for approx 5 years (since b17.1???) and it's been
invaluable. It was flaky a few years ago, but these days its quality has
improved markedly, owing--I suspect--to the incremental release model plus a
lot of effort by the Cygnus/Red Hat team. For the last couple of years it's
"just worked" for me and I haven't had to look under the hood much. I hope
my newbie-ish questions and suggestions aren't too irritating.

P.P.S. Your boss is a bit grumpy, isn't he?

Cheers

---
Mark Hadfield
m.hadfield@niwa.cri.nz  http://katipo.niwa.cri.nz/~hadfield
National Institute for Water and Atmospheric Research


--
Want to unsubscribe from this list?
Check out: http://cygwin.com/ml/#unsubscribe-simple

