cvs via Cygwin (W98) to FAT to Linux - permissions

Randall R Schulz
Wed Jun 27 21:10:00 GMT 2001


All I'm saying is what I read in the CVS manual. If you don't have it, I 
strongly recommend you procure one.

Are you using CVS via the pserver protocol, or via direct access? I have 
almost never used it directly, always via the pserver protocol.

Of course, under Cygwin, execute bits are "synthesized" from things like a 
.exe suffix or a #! header line.

Certainly under Linux, there has to be an applicable execute bit to get any 
file executed, whether it's a script or a binary. I'm pretty sure that 
applies to root, too.

Maybe you'll have to examine the source code after all, even if you decide 
to implement your needs outside the CVS command as I originally suggested. 
Some experiments might help clear things up.

Good luck.


At 20:54 2001-06-27, Steve Jorgensen wrote:
>So I'm a little confused (perpetually, it seems).  You're saying cvs never
>deals with the executable bit?  How is it that scripts I receive via cvs
>under Linux are executable by typing ./<scriptname>?
>-----Original Message-----
>From:   Randall R Schulz []
>Sent:   Wednesday, June 27, 2001 8:39 PM
>Subject:        RE: cvs via Cygwin (W98) to FAT to Linux - permissions
>OK. Moving on from a shoot-from-the-hip suggestion, I checked out the CVS
>manual (and old one, admittedly--version 1.9).
>According to section 4.2.2, pg. 16, files in the working copy of the
>repository have permissions "typical for newly created files, except that
>sometimes CVS creates them read-only."
>I take this to mean that the CVS command creates the files with mode 0666
>(or 0444 in the read-only case) and that the prevailing umask value is used
>to pare them down from there.
>Thus, it seems you really have very little to do, in fact. The files are
>either (0666& ~umask) or (0444 & ~umask).
>For a FAT file system volume, then, the only distinction is whether or not
>the read-only attribute is set.
>I don't know the details, but probably cygwin1.dll already handles this?

Unsubscribe info:
Bug reporting:

More information about the Cygwin mailing list