in reply to File::Find and recursive chmod on Win32?

Windows file systems don't have all thos bits. perlfunc says:

Perl was born in Unix and can therefore access all common Unix system calls. In non-Unix environments, the functionality of some Unix system calls may not be available, or details of the available functionality may differ slightly. The Perl functions affected by this are:

-X, binmode, chmod, chown, . . .

For more information about the portability of these functions, see perlport and other available platform-specific documentation.

perlport says chmod is . . .

Only good for changing "owner" read-write access, "group", and "other" bits are meaningless. (Win32)

Update: I misunderstood and apologize for the pedantry. I'll keep looking and let you know if I find something.


I humbly seek wisdom.
  • Comment on Re: File::Find and recursive chmod on Win32?

Replies are listed 'Best First'.
Re^2: File::Find and recursive chmod on Win32?
by jmmistrot (Sexton) on Sep 12, 2007 at 21:02 UTC
    Thanks for the response... My issue isn't the number of available bits and Unix parity.. Coming from a Unix background I do understand the vagaries of Win32 vs. *nix file systems.. it is rather and issue of chmod working as advertised in the context of the File::Find helper function as documented on CPAN (perldocs)... If I use chmod on its own it behaves as expected (only setting the owner bits ala Win32)... If I wrap chmod in a helper function, as in my posted example, and pass the function pointer to File::Find no bits are set at all... The function is getting called.. but no effect.