[BUG] 'chmod' broken on FAT32 drive with Cygwin 1.5.19

[Dave Korn]

On 03 February 2006 15:46, Corinna Vinschen wrote:

> On Feb  3 08:42, Jerry D. Hedden wrote:
>> 'chmod' does not work on FAT32 drive under Cygwin 1.5.19
> 
> That's not a bug, it's a "feature" of FAT32.  FAT and FAT32 have no way
> to keep security information.  Convert your filesystem to NTFS if you
> want that.  
> 
> And, just in case somebody mentiones the 'ntea' option:  FAT32 has no
> support for extended attributes. 


On 03 February 2006 16:02, Eric Blake wrote:

>> 'chmod' does not work on FAT32 drive under Cygwin 1.5.19
> 
> Welcome to the wonderful world of FAT32.  (NTFS is MUCH nicer).
> http://cygwin.com/faq/faq-nochunks.html#faq.using.chmod
> There are inherently NO permissions on FAT32, with no way to add it, so
> cygwin fakes success on chmod without doing anything. 


  It occurs to me that that FAQ entry could be better worded to make it clear that FAT != FAT32.  The entry in the UG section on the
$CYGWIN environment variable is already clear, but how about something like the attached, or perhaps it would be even clearer if it
listed which OS versions use which fat versions?



    cheers,
      DaveK
-- 
Can't think of a witty .sigline today....
-------------- next part --------------
A non-text attachment was scrubbed...
Name: faq-patch.diff
Type: application/octet-stream
Size: 1330 bytes
Desc: not available
URL: <http://cygwin.com/pipermail/cygwin/attachments/20060203/d39ac32e/attachment.obj>
-------------- next part --------------
--
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/