Hi all,
I just updated from cygwin 1.7.32 to 1.7.35,
and now file permissions are calculated differently,
which breaks fetchmail for me:
Here are the Windows permissions:
(no permissions for Domain Users / Domänen-Benutzer)
$ cacls fetchmailrc.txt
D:\fetchmail\fetchmailrc.txt NT-AUTORIT.T\SYST
On Sun, 4 Dec 2005, Corinna Vinschen wrote:
http://support.microsoft.com/default.aspx?scid=kb;en-us;117258
is interesting...
This is certainly interesting. Using this in Cygwin would require to
change the path handling to using UNICODE, though, which is a major
undertaking since the path han
[please cc me on replies]
On Thu, 1 Dec 2005, Martin Koeppe wrote:
8. CreateHardLink() Windows API [cygwin] [ActivePerl]
==
The CreateHardLink() Windows API function isn't apparently able to create
hardlinks on network drives, wh
Hello,
[please cc me on replies]
while playing around with a Windows server (2003), a Linux server
(2.6.11) with Samba (3.0.14a) and a Windows client (2000) with both
Interix Services for Unix (SFU) (3.5) and Cygwin (1.5.19pre20051130)
installed, I encountered the following problems or incon
On Sun, 27 Nov 2005, Corinna Vinschen wrote:
And I ask why such an assumption is necessary at all.
In the Windows API there is a function GetVolumeInformation
which is supported from Win95 on and reports FILE_SUPPORTS_OBJECT_IDS
when inode numbers are valid.
Nope. Object IDs are not inode nu
Hello,
while using cygwin and interix/sfu in parallel, I noticed a
"misfeature" in cygwin: inode numbers for files on network shares
aren't shown correctly.
I have a win2003 server with interix and created some hard linked
files. Then I shared these to a win2000 client with both interix and
6 matches
Mail list logo
