Date: Thu, 2 Mar 2006 10:07:00 -0500
From: Christopher Faylor <cgf-no-personal-reply-please AT cygwin DOT com>
To: cygwin AT cygwin DOT com
Subject: Update for the "Why doesn't chmod work?" section of the FAQ?
Message-ID: <20060302150700.GA18527@trixie.casa.cgf.cx>
Reply-To: cygwin AT cygwin DOT com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.11
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

The current FAQ has this entry:

  4.15. 	Why doesn't chmod work?

  ntsec will allow UNIX permissions in Windows NT on NTFS file systems.
  This is on by default (a recent change).

  ntea works on NTFS and FAT but it creates a huge, undeletable file on
  FAT filesystems.

  (The ntsec and ntea settings are values for the CYGWIN environment
  variable.  See the Cygwin User's Guide at
  http://cygwin.com/cygwin-ug-net/cygwin-ug-net.html for more information
  on this variable and its settings.)

  There is no solution at all for Windows 9x.

  If you have an application that requires a certain permission mode on a
  file, you may be able to work around this requirement by modifying the
  application's source code.  For a hint, based on work done by Corinna
  Vinschen for OpenSSH, see this message from the cygwin mailing list:
  http://cygwin.com/ml/cygwin/2000-11/msg01176.html.

I think the above really should be revamped.  It doesn't really answer
the question but, instead, goes right into discussing "ntsec" as if the
user will automatically know what this is.  I think the reference to a
2000 mailing list entry could probably be dropped, too.

Anyone care to give this a shot?

cgf

--
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/