Re: symbolic links to /cygdrive/X/xxx with capital letter X

[Corinna Vinschen]

On Jun 12 08:06, Arthur Norman via Cygwin wrote:
> This running on Windows 10 1909 and cygwin has been updated to the latest
> version. The effect was also visible on a freshly installed minimal cygwin
> put on an almost fresh Windows 10 VM.
> 
> Cygwin these days seems to have a behaviour that confuses me regarding the
> case of a disk name:
> 
> > ln -s "/cygdrive/c/Program Files" pf1
> > ln -s "/cygdrive/C/Program Files" pf2
> > ls -l pf*
> lrwxrwxrwx 1 acn1 None 25 Jun 12 07:37 pf1 -> /cygdrive/c/Program Files
> lrwxrwxrwx 1 acn1 None 20 Jun 12 07:37 pf2 -> /mnt/C/Program Files
> > cygpath -ma ./pf1
> C:/cygwin64/home/acn1/pf1
> 
> You see from the above that when I use cygpath to convert from a cygwin name
> the drive letter C: is returned in upper case. When that ends up after
> "/cygdrive" the path behaves as I expect almost everywhere by is treated
> specially for symbolic links. This seems to be a relatively new behaviour
> and it bit me!
> 
> [Use-case: I wanted to convert cygwin paths to be "very absolute" so that eg

If you want "very absolute" paths, use something like

  ln -s /proc/cygdrive/c/...

/proc/cygdrive always exists, even if you change the cygdrive prefix.
It's a virtual symlink to the actual cygdrive prefix.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: symbolic links to /cygdrive/X/xxx with capital letter X

[Wayne Davison]

On Sat, Jun 13, 2020 at 1:50 PM Andrey Repin wrote:
> The cygdrive prefix is resolved, if no other mount points match.
> Since you have /mnt/C mount point, it is resolved first.

I wish it would have resolved it to the cygdrive prefix, because then
it would have worked (and would have been /cygdrive/C/Windows). Maybe
cygwin is getting confused by the WLS ubuntu install I have? It puts
its mounts under /mnt, but cygwin has always used the /cygdrive path.

..wayne..
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: symbolic links to /cygdrive/X/xxx with capital letter X

[Andrey Repin]

Greetings, Wayne Davison!

> On Fri, Jun 12, 2020 at 4:05 AM Andrey Repin wrote:
>> And you've got exactly what you asked for.

> I think you missed the important part of the email. Distilled down,
> this is wrong:

> $ ln -s /cygdrive/C/Windows foo
> $ readlink foo
> /mnt/C/Windows

The cygdrive prefix is resolved, if no other mount points match.
Since you have /mnt/C mount point, it is resolved first.

> The symlink's value changed to a path that doesn't exist on a typical
> install and is now broken. The original /cygdrive/C/Windows path works
> fine as long as you have it mounted to ignore case. Perhaps the
> rewrite (if it is even required) should change it into
> /cygdrive/c/Windows?

You can resolve it to `cygpath --proc-cygdrive`, which is more useful, if you
want a portable solution.


-- 
With best regards,
Andrey Repin
Saturday, June 13, 2020 23:44:47

Sorry for my terrible english...

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: symbolic links to /cygdrive/X/xxx with capital letter X

[Wayne Davison]

On Fri, Jun 12, 2020 at 4:05 AM Andrey Repin wrote:
> And you've got exactly what you asked for.

I think you missed the important part of the email. Distilled down,
this is wrong:

$ ln -s /cygdrive/C/Windows foo
$ readlink foo
/mnt/C/Windows

The symlink's value changed to a path that doesn't exist on a typical
install and is now broken. The original /cygdrive/C/Windows path works
fine as long as you have it mounted to ignore case. Perhaps the
rewrite (if it is even required) should change it into
/cygdrive/c/Windows?

..wayne..
--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: symbolic links to /cygdrive/X/xxx with capital letter X

[Andrey Repin]

Greetings, Arthur Norman!

> This running on Windows 10 1909 and cygwin has been updated to the latest 
> version. The effect was also visible on a freshly installed minimal cygwin 
> put on an almost fresh Windows 10 VM.

> Cygwin these days seems to have a behaviour that confuses me regarding the 
> case of a disk name:

>> ln -s "/cygdrive/c/Program Files" pf1
>> ln -s "/cygdrive/C/Program Files" pf2
>> ls -l pf*
> lrwxrwxrwx 1 acn1 None 25 Jun 12 07:37 pf1 -> /cygdrive/c/Program Files
> lrwxrwxrwx 1 acn1 None 20 Jun 12 07:37 pf2 -> /mnt/C/Program Files
>> cygpath -ma ./pf1
> C:/cygwin64/home/acn1/pf1

> You see from the above that when I use cygpath to convert from a cygwin 
> name the drive letter C: is returned in upper case. When that ends up 
> after "/cygdrive" the path behaves as I expect almost everywhere by is 
> treated specially for symbolic links. This seems to be a relatively new 
> behaviour and it bit me!

> [Use-case: I wanted to convert cygwin paths to be "very absolute" so that 
> eg my home directory is not rendered as /home/acn1 but as 
> /cygdrive/c/cygwin64/home/acn1,

cygpath is not meant to replace realpath/readlink.
And you've got exactly what you asked for.
-m returns Windows path with forward slashes.
-a returns absolute path.

> so I had a few lines of shell script to
> achieve that. I was building a package and I build both a cygwin32 and a 
> cygwin64 version, so the "very absolute" paths are portable between the 
> two worlds, both of which were important when I first set this up. Things 
> recently broke and on investigation it was because somewhere deep in 
> build scripts links to /mnt/C/... had been set up and were not usable. I 
> can of course work round the issue but being confident I have spotted all 
> cases causes me work!]

readlink -e ./pf1

man readlink


-- 
With best regards,
Andrey Repin
Friday, June 12, 2020 14:01:51

Sorry for my terrible english...

--
Problem reports:  https://cygwin.com/problems.html
FAQ:  https://cygwin.com/faq/
Documentation:https://cygwin.com/docs.html
Unsubscribe info: https://cygwin.com/ml/#unsubscribe-simple

Re: symbolic links on Paragon Linux File systems

[Simon Liesenfeld via cygwin]

 Hi Corinnayou are right,I mixed it the symlink with the hard link
the symlink is sl (on file source)

E:\>type sl
source < just the filename as you say>

but the hard link does work (on file source)
E:\>type hl
hallo
erna
otto
hugo

E:\>echo rudi >> source

E:\>type hl
hallo
erna
otto
hugo
rudi

or with cygwin
$pwd/cygdrive/eecho hajo >>source
$ cat hl
hallo
erna
otto
hugo
rudi
hajo



On Monday, December 17, 2018, 8:22:25 PM GMT+1, Corinna Vinschen 
 wrote:  
 
 
Please, do not top-post.


On Dec 17 18:50, Simon Liesenfeld via cygwin wrote:
>  Hi Corinna,
> since you answered your own questionsI can better understand my own
> stupidity.I have created now a hard and a soft link with a native
> linux,then I booted Windows, started the paragon driver,then cygwin 
> programs as well as any dos program perfectly understood the links.

Not in my testing.  I installed the Paragon trial driver and tested
on a filesystem with files and symlinks created by native Linux.  The
symlinks are not understood at all.  From the Windows perspective they
are just plain files with the name of the target file as content.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer  
--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: symbolic links on Paragon Linux File systems

[Corinna Vinschen]

Please, do not top-post.


On Dec 17 18:50, Simon Liesenfeld via cygwin wrote:
>  Hi Corinna,
> since you answered your own questionsI can better understand my own
> stupidity.I have created now a hard and a soft link with a native
> linux,then I booted Windows, started the paragon driver,then cygwin 
> programs as well as any dos program perfectly understood the links.

Not in my testing.  I installed the Paragon trial driver and tested
on a filesystem with files and symlinks created by native Linux.  The
symlinks are not understood at all.  From the Windows perspective they
are just plain files with the name of the target file as content.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer


signature.asc
Description: PGP signature

Re: symbolic links on Paragon Linux File systems

[Simon Liesenfeld via cygwin]

 Hi Corinna,
since you answered your own questionsI can better understand my own stupidity.I 
have created now a hard and a soft link with a native linux,then I booted 
Windows, started the paragon driver,then cygwin  programs as well as any dos 
program perfectly 
understood the links.
Even if cygwin were able to understand its own links on paragon volumes,they 
would not be understood when running the volume by linux again.That does not 
make sense.
May be there is a command line option from paragonto create links.

Thank you so much Corinna.


On Monday, December 17, 2018, 5:57:43 PM GMT+1, Corinna Vinschen 
 wrote:  
 
 On Dec 17 10:34, Corinna Vinschen wrote:
> On Dec 17 08:11, Simon Liesenfeld via cygwin wrote:
> > Hi all
> > 
> > There is a commercial ext3-4 file system driver for windowsLinux File
> > Systems für Windows | Paragon Softwarewhich enable Windows to read an
> > write on native ext3-4 volumes.In General cygwin works perfectly on
> > such volumes,even named pipes work,
> > but Cygwin programs do not interprete those links correctly,which are
> > created on such volumes.whilst symbolic links on native NTFS drives
> > referring files on such volumeswork perfectly.
> > $pwd/cygdrive/e
> > 
> > $ echo hallo > source
> > 
> > $ ln -s source sl
> > 
> > $ cat sl
> > !▒▒source
> 
> Yes, we can't do that without special knowledge of the FS.  The default
> symlinks on Cygwin are only evaluated correctly if the DOS SYSTEM
> attribute is set.  The ext4 driver can't do that, obviously.
> 
> Are the native symlinks on an ext4 FS converted to NTFS symlinks
> on the fly by the driver?  Are they visible as symlinks in Windows
> or Cygwin?
> 
> If so, you could try setting the environment variable CYGWIN to contain
> "winsymlinks:native".  This creates native Windows symlinks rather than
> the special Cygwin POSIX symlinks.  If the driver is handling this
> correctly, it should transparently convert them to ext4 symlinks and
> they should just work.

Answering my own questions:

No, the driver does not handle symlinks gracefully *at all*.

- Existing symlinks on the FS are handled as if they are simple files.
  They are in no way identifiable as symlinks by any Windows client.
  They supposedly only contain the name of the symlink target, which is
  an arbitrary string.  No symlink marker or anything.

- DOS file attributes don't work, so we can't use Cygwin's symlink
  handling, not even by utilizing Windows shortcuts instead of Cygwin
  symlinks.

- Windows native symlinks and transparent conversion to and from ext4
  symlinks is not supported.

- No ACL handling, not even to fake basic POSIX permissions, so we can't
  change the permissions at all.

I don't think it's worth to go to great length supporting Cygwin
symlinks on this FS.  They won't be recognized by your Linux
installation as symlinks anyway and we'd have to perform excessively
slow checks just to recognize them.

As a sidenote, the OSS project Ext2Fsd handles symlinks transparently
via standard Windows functions.  With "CYGWIN=winsymlinks:native" you
can generate real ext4 symlinks transparently.  Even the good old Cygwin
symlink works on Cygwin without programmatic intervention, albeit those
won't be recognized as symlinks by Linux of course.  Unfortunately
Ext2Fsd didn't learn to handle ext4 with the 64bit FS option set yet.
64bit is default for quite some time.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer  
--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: symbolic links on Paragon Linux File systems

[Stefan Baur]

Am 17.12.18 um 19:45 schrieb Stefan Baur:

>> Features implemented and bugfix:
>>
>> 1, FIXME: superblock corruption of EXT4 volumes with 64BIT mode enabled 
>> 2, FIXME: possible corruption by race conditions in buffer-head reapering
>> 3, FIXME: possible deadlock issues (when flushing) caused by BCB locks
>> 4, FIXME: miscellaneous minor updates of Ext2Fsd code base
> 
> Sooo ... if the warning only applies for 0.68 and earlier versions,
> while the current version is 0.69, as the headline says, I'd be tempted
> to believe they fixed that issue.

Ah, dangit, forget what I wrote, at the bottom it says

> Unsupported Ext3/4 features:
> 
>   1, 64BIT mode (to support 2^64 blocks)
[...]

So it's still not supported, it just doesn't damage your superblock any
more.

-Stefan



-- 
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243



signature.asc
Description: OpenPGP digital signature

Re: symbolic links on Paragon Linux File systems

[Stefan Baur]

Am 17.12.18 um 17:57 schrieb Corinna Vinschen:
> As a sidenote, the OSS project Ext2Fsd handles symlinks transparently
> via standard Windows functions.  With "CYGWIN=winsymlinks:native" you
> can generate real ext4 symlinks transparently.  Even the good old Cygwin
> symlink works on Cygwin without programmatic intervention, albeit those
> won't be recognized as symlinks by Linux of course.  Unfortunately
> Ext2Fsd didn't learn to handle ext4 with the 64bit FS option set yet.
> 64bit is default for quite some time.

Hmm, their website says:

> *Ext2Fsd 0.69 released !*
> November 2nd, 2017
> 
> WARNINGS:
> 
> Don't use Ext2Fsd 0.68 or earlier versions with latest Ubuntu or
> Debian systems. Ext2Fsd 0.68 cannot process EXT4 with 64-BIT mode
> enabled, then it could corrupt your data. Very sorry for this
> disaster issue, I'm working on an improvement.
> 
> Features implemented and bugfix:
> 
> 1, FIXME: superblock corruption of EXT4 volumes with 64BIT mode enabled 
> 2, FIXME: possible corruption by race conditions in buffer-head reapering
> 3, FIXME: possible deadlock issues (when flushing) caused by BCB locks
> 4, FIXME: miscellaneous minor updates of Ext2Fsd code base

Sooo ... if the warning only applies for 0.68 and earlier versions,
while the current version is 0.69, as the headline says, I'd be tempted
to believe they fixed that issue.

-Stefan

-- 
BAUR-ITCS UG (haftungsbeschränkt)
Geschäftsführer: Stefan Baur
Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364
Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243



signature.asc
Description: OpenPGP digital signature

Re: symbolic links on Paragon Linux File systems

[Corinna Vinschen]

On Dec 17 10:34, Corinna Vinschen wrote:
> On Dec 17 08:11, Simon Liesenfeld via cygwin wrote:
> > Hi all
> > 
> > There is a commercial ext3-4 file system driver for windowsLinux File
> > Systems für Windows | Paragon Softwarewhich enable Windows to read an
> > write on native ext3-4 volumes.In General cygwin works perfectly on
> > such volumes,even named pipes work,
> > but Cygwin programs do not interprete those links correctly,which are
> > created on such volumes.whilst symbolic links on native NTFS drives
> > referring files on such volumeswork perfectly.
> > $pwd/cygdrive/e
> > 
> > $ echo hallo > source
> > 
> > $ ln -s source sl
> > 
> > $ cat sl
> > !▒▒source
> 
> Yes, we can't do that without special knowledge of the FS.  The default
> symlinks on Cygwin are only evaluated correctly if the DOS SYSTEM
> attribute is set.  The ext4 driver can't do that, obviously.
> 
> Are the native symlinks on an ext4 FS converted to NTFS symlinks
> on the fly by the driver?  Are they visible as symlinks in Windows
> or Cygwin?
> 
> If so, you could try setting the environment variable CYGWIN to contain
> "winsymlinks:native".  This creates native Windows symlinks rather than
> the special Cygwin POSIX symlinks.  If the driver is handling this
> correctly, it should transparently convert them to ext4 symlinks and
> they should just work.

Answering my own questions:

No, the driver does not handle symlinks gracefully *at all*.

- Existing symlinks on the FS are handled as if they are simple files.
  They are in no way identifiable as symlinks by any Windows client.
  They supposedly only contain the name of the symlink target, which is
  an arbitrary string.  No symlink marker or anything.

- DOS file attributes don't work, so we can't use Cygwin's symlink
  handling, not even by utilizing Windows shortcuts instead of Cygwin
  symlinks.

- Windows native symlinks and transparent conversion to and from ext4
  symlinks is not supported.

- No ACL handling, not even to fake basic POSIX permissions, so we can't
  change the permissions at all.

I don't think it's worth to go to great length supporting Cygwin
symlinks on this FS.  They won't be recognized by your Linux
installation as symlinks anyway and we'd have to perform excessively
slow checks just to recognize them.

As a sidenote, the OSS project Ext2Fsd handles symlinks transparently
via standard Windows functions.  With "CYGWIN=winsymlinks:native" you
can generate real ext4 symlinks transparently.  Even the good old Cygwin
symlink works on Cygwin without programmatic intervention, albeit those
won't be recognized as symlinks by Linux of course.  Unfortunately
Ext2Fsd didn't learn to handle ext4 with the 64bit FS option set yet.
64bit is default for quite some time.


Corinna

-- 
Corinna Vinschen
Cygwin Maintainer


signature.asc
Description: PGP signature

Re: symbolic links on Paragon Linux File systems

[Simon Liesenfeld via cygwin]

 Hi Corinna,I 've set in the Control Panel,and  this reflects in bash.I still 
does work.
$ set | grep -i nativeCYGWIN=winsymlinks:native

$ ln -s /cygdrive/e/source sl

$ cat sl
!▒▒/cygdrive/e/source

One can download a 10 days trial version at:
http://dl.paragon-software.com/demo/linuxwin_trial.msi or buy for about 19 € 
On Monday, December 17, 2018, 4:46:37 PM GMT+1, Simon Liesenfeld 
 wrote:  
 
  Hi Corinna,I 've set in the Contrpl Panel,es this reflects in bash.I still 
does work.
$ set | grep -i nativeCYGWIN=winsymlinks:native

$ ln -s /cygdrive/e/source sl

$ cat sl
!▒▒/cygdrive/e/source





On Monday, December 17, 2018, 1:04:21 PM GMT+1, Simon Liesenfeld via cygwin 
 wrote:  
 
  Hi all,
Thank you so much for the response,and nearby for the entire cygwin 
Project.(Best of both worlds)"The devil is in the detail"I admire cygwin so 
much, and I' am overwhelmed
that it can do the named pipes on paragon systemalready.I do not expect cygwin 
to master the symbolic links,it's too much.But if it were able master, I would 
sit on my chair breathless.
One can download paragon 
athttps://www.paragon-software.com/de/home/linuxfs-windows/#
it has a ten days trial period.

 /usr/lib/csih/getVolInfo /cygdrive/e
Device Type    : 7Characteristics    : 20
Volume Name    : <>
Serial Number  : 4229931105
Max Filenamelength : 260
Filesystemname : 
Flags  : 107
  FILE_CASE_SENSITIVE_SEARCH  : TRUE
  FILE_CASE_PRESERVED_NAMES   : TRUE
  FILE_UNICODE_ON_DISK    : TRUE
  FILE_PERSISTENT_ACLS    : FALSE
  FILE_FILE_COMPRESSION   : FALSE
  FILE_VOLUME_QUOTAS  : FALSE
  FILE_SUPPORTS_SPARSE_FILES  : FALSE
  FILE_SUPPORTS_REPARSE_POINTS: FALSE
  FILE_SUPPORTS_REMOTE_STORAGE: TRUE
  FILE_VOLUME_IS_COMPRESSED   : FALSE
  FILE_SUPPORTS_OBJECT_IDS    : FALSE
  FILE_SUPPORTS_ENCRYPTION    : FALSE
  FILE_NAMED_STREAMS  : FALSE
  FILE_READ_ONLY_VOLUME   : FALSE
  FILE_SEQUENTIAL_WRITE_ONCE  : FALSE
  FILE_SUPPORTS_TRANSACTIONS  : FALSE



    On Monday, December 17, 2018, 12:35:02 PM GMT+1, Andrey Repin 
 wrote:  
 
 Greetings, Simon Liesenfeld!

> Hi all

> There is a commercial ext3-4 file system driver for windowsLinux File
> Systems für Windows | Paragon Softwarewhich enable Windows to read an write
> on native ext3-4 volumes.In General cygwin works perfectly on such 
> volumes,even named pipes work,
> but Cygwin programs do not interprete those links correctly,which are
> created on such volumes.whilst symbolic links on native NTFS drives
> referring files on such volumeswork perfectly.
> $pwd/cygdrive/e

> $ echo hallo > source

> $ ln -s source sl

> $ cat sl
> !▒▒source

What doe /usr/lib/csih/getVolInfo say about such volume?


-- 
With best regards,
Andrey Repin
Monday, December 17, 2018 14:28:48

Sorry for my terrible english...  
--
Problem reports:      http://cygwin.com/problems.html
FAQ:                  http://cygwin.com/faq/
Documentation:        http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: symbolic links on Paragon Linux File systems

[Corinna Vinschen]

On Dec 17 12:03, Simon Liesenfeld via cygwin wrote:
>  Hi all,
> Thank you so much for the response,and nearby for the entire cygwin
> Project.(Best of both worlds)"The devil is in the detail"I admire
> cygwin so much, and I' am overwhelmed
> that it can do the named pipes on paragon systemalready.I do not
> expect cygwin to master the symbolic links,it's too much.But if it
> were able master, I would sit on my chair breathless.
> One can download paragon 
> athttps://www.paragon-software.com/de/home/linuxfs-windows/#
> it has a ten days trial period.
> 
>  /usr/lib/csih/getVolInfo /cygdrive/e
> Device Type    : 7Characteristics    : 20
> Volume Name    : <>
> Serial Number  : 4229931105
> Max Filenamelength : 260
> Filesystemname : 
> Flags  : 107
>   FILE_CASE_SENSITIVE_SEARCH  : TRUE
>   FILE_CASE_PRESERVED_NAMES   : TRUE
>   FILE_UNICODE_ON_DISK    : TRUE
>   FILE_PERSISTENT_ACLS    : FALSE
>   FILE_FILE_COMPRESSION   : FALSE
>   FILE_VOLUME_QUOTAS  : FALSE
>   FILE_SUPPORTS_SPARSE_FILES  : FALSE
>   FILE_SUPPORTS_REPARSE_POINTS: FALSE
>   FILE_SUPPORTS_REMOTE_STORAGE: TRUE
>   FILE_VOLUME_IS_COMPRESSED   : FALSE
>   FILE_SUPPORTS_OBJECT_IDS    : FALSE
>   FILE_SUPPORTS_ENCRYPTION    : FALSE
>   FILE_NAMED_STREAMS  : FALSE
>   FILE_READ_ONLY_VOLUME   : FALSE
>   FILE_SEQUENTIAL_WRITE_ONCE  : FALSE
>   FILE_SUPPORTS_TRANSACTIONS  : FALSE

What about my question in https://cygwin.com/ml/cygwin/2018-12/msg00135.html?


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer


signature.asc
Description: PGP signature

Re: symbolic links on Paragon Linux File systems

[Simon Liesenfeld via cygwin]

 Hi all,
Thank you so much for the response,and nearby for the entire cygwin 
Project.(Best of both worlds)"The devil is in the detail"I admire cygwin so 
much, and I' am overwhelmed
that it can do the named pipes on paragon systemalready.I do not expect cygwin 
to master the symbolic links,it's too much.But if it were able master, I would 
sit on my chair breathless.
One can download paragon 
athttps://www.paragon-software.com/de/home/linuxfs-windows/#
it has a ten days trial period.

 /usr/lib/csih/getVolInfo /cygdrive/e
Device Type    : 7Characteristics    : 20
Volume Name    : <>
Serial Number  : 4229931105
Max Filenamelength : 260
Filesystemname : 
Flags  : 107
  FILE_CASE_SENSITIVE_SEARCH  : TRUE
  FILE_CASE_PRESERVED_NAMES   : TRUE
  FILE_UNICODE_ON_DISK    : TRUE
  FILE_PERSISTENT_ACLS    : FALSE
  FILE_FILE_COMPRESSION   : FALSE
  FILE_VOLUME_QUOTAS  : FALSE
  FILE_SUPPORTS_SPARSE_FILES  : FALSE
  FILE_SUPPORTS_REPARSE_POINTS: FALSE
  FILE_SUPPORTS_REMOTE_STORAGE: TRUE
  FILE_VOLUME_IS_COMPRESSED   : FALSE
  FILE_SUPPORTS_OBJECT_IDS    : FALSE
  FILE_SUPPORTS_ENCRYPTION    : FALSE
  FILE_NAMED_STREAMS  : FALSE
  FILE_READ_ONLY_VOLUME   : FALSE
  FILE_SEQUENTIAL_WRITE_ONCE  : FALSE
  FILE_SUPPORTS_TRANSACTIONS  : FALSE



On Monday, December 17, 2018, 12:35:02 PM GMT+1, Andrey Repin 
 wrote:  
 
 Greetings, Simon Liesenfeld!

> Hi all

> There is a commercial ext3-4 file system driver for windowsLinux File
> Systems für Windows | Paragon Softwarewhich enable Windows to read an write
> on native ext3-4 volumes.In General cygwin works perfectly on such 
> volumes,even named pipes work,
> but Cygwin programs do not interprete those links correctly,which are
> created on such volumes.whilst symbolic links on native NTFS drives
> referring files on such volumeswork perfectly.
> $pwd/cygdrive/e

> $ echo hallo > source

> $ ln -s source sl

> $ cat sl
> !▒▒source

What doe /usr/lib/csih/getVolInfo say about such volume?


-- 
With best regards,
Andrey Repin
Monday, December 17, 2018 14:28:48

Sorry for my terrible english...  
--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: symbolic links on Paragon Linux File systems

[Andrey Repin]

Greetings, Simon Liesenfeld!

> Hi all

> There is a commercial ext3-4 file system driver for windowsLinux File
> Systems für Windows | Paragon Softwarewhich enable Windows to read an write
> on native ext3-4 volumes.In General cygwin works perfectly on such 
> volumes,even named pipes work,
> but Cygwin programs do not interprete those links correctly,which are
> created on such volumes.whilst symbolic links on native NTFS drives
> referring files on such volumeswork perfectly.
> $pwd/cygdrive/e

> $ echo hallo > source

> $ ln -s source sl

> $ cat sl
> !▒▒source

What doe /usr/lib/csih/getVolInfo say about such volume?


-- 
With best regards,
Andrey Repin
Monday, December 17, 2018 14:28:48

Sorry for my terrible english...
--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: symbolic links on Paragon Linux File systems

[Corinna Vinschen]

On Dec 17 10:34, Corinna Vinschen wrote:
> On Dec 17 08:11, Simon Liesenfeld via cygwin wrote:
> > Hi all
> > 
> > There is a commercial ext3-4 file system driver for windowsLinux File
> > Systems für Windows | Paragon Softwarewhich enable Windows to read an
> > write on native ext3-4 volumes.In General cygwin works perfectly on
> > such volumes,even named pipes work,
> > but Cygwin programs do not interprete those links correctly,which are
> > created on such volumes.whilst symbolic links on native NTFS drives
> > referring files on such volumeswork perfectly.
> > $pwd/cygdrive/e
> > 
> > $ echo hallo > source
> > 
> > $ ln -s source sl
> > 
> > $ cat sl
> > !▒▒source
> 
> Yes, we can't do that without special knowledge of the FS.  The default
> symlinks on Cygwin are only evaluated correctly if the DOS SYSTEM
> attribute is set.  The ext4 driver can't do that, obviously.
> 
> Are the native symlinks on an ext4 FS converted to NTFS symlinks
> on the fly by the driver?  Are they visible as symlinks in Windows
> or Cygwin?
> 
> If so, you could try setting the environment variable CYGWIN to contain
> "winsymlinks:native".  This creates native Windows symlinks rather than
> the special Cygwin POSIX symlinks.  If the driver is handling this
> correctly, it should transparently convert them to ext4 symlinks and
> they should just work.
> 
> 
> HTH,
> Corinna

Btw., we might be able to do more.  Can you do me a favor and call

  /lib/csih/getVolInfo 
  
and paste the result in your reply to the maling list?  Just for
comparison, it should look roughly like this (example native NTFS):

Device Type: 7
Characteristics: 20020
Volume Name: <>
Serial Number  : 3327928886
Max Filenamelength : 255
Filesystemname : 
Flags  : 3e706ff
  FILE_CASE_SENSITIVE_SEARCH  : TRUE
  FILE_CASE_PRESERVED_NAMES   : TRUE
  FILE_UNICODE_ON_DISK: TRUE
  FILE_PERSISTENT_ACLS: TRUE
  FILE_FILE_COMPRESSION   : TRUE
  FILE_VOLUME_QUOTAS  : TRUE
  FILE_SUPPORTS_SPARSE_FILES  : TRUE
  FILE_SUPPORTS_REPARSE_POINTS: TRUE
  FILE_SUPPORTS_REMOTE_STORAGE: FALSE
  FILE_VOLUME_IS_COMPRESSED   : FALSE
  FILE_SUPPORTS_OBJECT_IDS: TRUE
  FILE_SUPPORTS_ENCRYPTION: TRUE
  FILE_NAMED_STREAMS  : TRUE
  FILE_READ_ONLY_VOLUME   : FALSE
  FILE_SEQUENTIAL_WRITE_ONCE  : FALSE
  FILE_SUPPORTS_TRANSACTIONS  : TRUE

Maybe we can tweak Cygwin to handle the Paragon ext4 driver out of
the box.


Thanks,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer


signature.asc
Description: PGP signature

Re: symbolic links on Paragon Linux File systems

[Corinna Vinschen]

On Dec 17 08:11, Simon Liesenfeld via cygwin wrote:
> Hi all
> 
> There is a commercial ext3-4 file system driver for windowsLinux File
> Systems für Windows | Paragon Softwarewhich enable Windows to read an
> write on native ext3-4 volumes.In General cygwin works perfectly on
> such volumes,even named pipes work,
> but Cygwin programs do not interprete those links correctly,which are
> created on such volumes.whilst symbolic links on native NTFS drives
> referring files on such volumeswork perfectly.
> $pwd/cygdrive/e
> 
> $ echo hallo > source
> 
> $ ln -s source sl
> 
> $ cat sl
> !▒▒source

Yes, we can't do that without special knowledge of the FS.  The default
symlinks on Cygwin are only evaluated correctly if the DOS SYSTEM
attribute is set.  The ext4 driver can't do that, obviously.

Are the native symlinks on an ext4 FS converted to NTFS symlinks
on the fly by the driver?  Are they visible as symlinks in Windows
or Cygwin?

If so, you could try setting the environment variable CYGWIN to contain
"winsymlinks:native".  This creates native Windows symlinks rather than
the special Cygwin POSIX symlinks.  If the driver is handling this
correctly, it should transparently convert them to ext4 symlinks and
they should just work.


HTH,
Corinna

-- 
Corinna Vinschen
Cygwin Maintainer


signature.asc
Description: PGP signature

Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

[Larry Hall (Cygwin)]

On 01/01/2010 04:52 PM, Lee Rothstein wrote:

Will Windows junctions (for the path; plus the file name) work, here, Andy?
(http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx)


NTFS junctions are for directories only..  For files and directories, one could
use "mklink" on Vista and newer, with the caveats mentioned here
. 
Oh and

for all those wondering, this still isn't enough to be a drop-in replacement
for Cygwin's symbolic links unfortunately.  If you're curious about this, see
the email archives for discussions about it.

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

[tuli tanssi]

> You could create a Windows symbolic link using the Windows 'mklink'
> tool though, and it should work both in cmd.exe and in Cygwin.

Thanks for the info and Corinna's quote.

Probably I'll just create windows symlinks like from
c:\users\tuli\bin\gcc.exe to c:\cygwin\bin\gcc-3.exe
so that cygwin updates wouldn't break my modifications.

Cheers,
Tuli

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

[Andy Koppe]

Lee Rothstein:
>> Will Windows junctions (for the path; plus the file name) work, here?

Don't think so, afaik junction points (introduced in Win2000, and
different from Vista/7 symlinks) work correctly for directories only.

Hard links, however, should work just fine for the problem at hand.


tuli tanssi:
> Actually, in Windows 7, Microsoft has implemented true symbolic links
> (as far as I know).
> Maybe it is also in Vista?
> Anyway, is that (microsoft's true symlinks) feature used in cygwin 1.7?
> Apparently not, since it would solve my problem.

Quoting Corinna Vinschen at
http://sourceware.org/ml/cygwin/2009-11/msg00202.html:

"Cygwin 1.7 does recognize reparse points and especially
the new NTFS6 symlinks.  However, it only reads them, never writes them,
for the reasons repeated by cgf and me a couple of times.  You just
can't use them to store POSIX paths *and* allowing interoperability with
native Win32 processes, plus the nonsense of coupling them with a user
right, plus the super-nonsense only to allow Admins to create them by
default.  All that together makes them worse than Windows shortcuts and
they have not the faintest advantage over Cygwin-only symlinks
implemented as files with the SYSTEM DOS attribute set."

You could create a Windows symbolic link using the Windows 'mklink'
tool though, and it should work both in cmd.exe and in Cygwin.

Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

[tuli tanssi]

> Will Windows junctions (for the path; plus the file name) work, here, Andy?
> (http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx)
>
> (Admittedly, a kludge, but this is Windows, after all. ;-))
>
> Lee

Actually, in Windows 7, Microsoft has implemented true symbolic links
(as far as I know).
Maybe it is also in Vista?
Anyway, is that (microsoft's true symlinks) feature used in cygwin 1.7?
Apparently not, since it would solve my problem.

Tuli

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

[Lee Rothstein]

Andy Koppe wrote:

2009/12/30 Larry Hall (Cygwin):

I've been using gcc and other tools in older versions of cygwin with
32-bit Windows XP and Vista from windows command prompt (cmd.exe)
without problems. But now I'm using 64-bit Windows 7, and some command
line tools like gcc.exe do not work anymore (from cmd.exe). They do
work ok from Cygwin's bash.



[...]
 Another [solution] might be to set "winsymlinks" in the CYGWIN
environment
variable  and recreate
the symlinks you want that way.


That won't work. The option causes symlinks to be represented by
Windows shortcuts, which do work in Explorer, but not in cmd.exe where
they appear as .lnk files instead. (Lame, eh?)


Will Windows junctions (for the path; plus the file name) work, here, Andy?
(http://technet.microsoft.com/en-us/sysinternals/bb896768.aspx)

(Admittedly, a kludge, but this is Windows, after all. ;-))

Lee


--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

[Andy Koppe]

2009/12/30 Larry Hall (Cygwin):
>> I've been using gcc and other tools in older versions of cygwin with
>> 32-bit Windows XP and Vista from windows command prompt (cmd.exe)
>> without problems. But now I'm using 64-bit Windows 7, and some command
>> line tools like gcc.exe do not work anymore (from cmd.exe). They do
>> work ok from Cygwin's bash.

> [...]
> Another [solution] might be to set "winsymlinks" in the CYGWIN
> environment
> variable  and recreate
> the symlinks you want that way.

That won't work. The option causes symlinks to be represented by
Windows shortcuts, which do work in Explorer, but not in cmd.exe where
they appear as .lnk files instead. (Lame, eh?)

Andy

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

[tuli tanssi]

> This is a known limitation of the symbolic links in Cygwin 1.7. The solution 
> is ...

Thanks for the info. I'll try one of your workarounds.

Cheers,
Tuli

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Symbolic links problem with cygwin 1.7.1 in 64-bit Win7 Command Prompt

[Larry Hall (Cygwin)]

On 12/30/2009 08:30 AM, tuli tanssi wrote:

Hi,

I've been using gcc and other tools in older versions of cygwin with
32-bit Windows XP and Vista from windows command prompt (cmd.exe)
without problems. But now I'm using 64-bit Windows 7, and some command
line tools like gcc.exe do not work anymore (from cmd.exe). They do
work ok from Cygwin's bash.

The message I get when trying to run gcc in cmd.exe is: "Access is denied."

Anyway, only some tools don't work, e.g. 'ls' works ok from cmd.exe.

I noticed that all cygwin tools that are actually symbolic links to
somehere else (just like /bin/gcc.exe and some others) are the
problematic tools.
Also /bin/gcc.exe has System rights (as seen by Attrib command of
windows), while tools that do work have only Archive rights.

So the I guess the problem is related to how symbolic links are
created and with what rights.

Anyone else tried this? Any solutions?


This is a known limitation of the symbolic links in Cygwin 1.7.  The solution
is to invoke the command directly ('gcc-3.exe' or 'gcc-4.exe' in this case) or
create your own batch file wrappers or DOS aliases to point to the proper
alternative.  Another might be to set "winsymlinks" in the CYGWIN environment
variable  and recreate
the symlinks you want that way.  The clear downside to this approach is that
it won't handle international characters in file names/paths properly.  As a 
result

one might guess this is not the recommended solution.  And one would be
right! ;-)

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Symbolic links on NTFS with real symbolic links

[Corinna Vinschen]

On Oct 29 02:40, Larry Hall (Cygwin) wrote:
> On 10/29/2009 01:26 AM, Neil Mowbray wrote:
> >Dear Folks,
> >
> >On NTFS systems that support real symbolic links (eg those with Vista)
> >the comand ln -s does *not* create a native symbolic link merely an old
> >style shortcut.
> >
> >Will ln -s be chansed to support native symbolic links?
> 
> No, not until, at least, native symbolic links don't require
> elevated privileges to
> use.

And even then, no.  We need symlinks which support POSIX style content.
Native Windows symlinks are just reparse points with a special symlink
tag.  The path stored in them is expected to be a Win32 path.

Actually the target path is stored twice.  The "SubstituteName" is a
native NT path, the "PrintName" is just some UI string, in theory.  If
you use CMD's mklink command, the "PrintName" is filled with the Win32
path.

This looks like a neat way to use a symlink for POSIX paths.  Since
"SubstituteName" already contains the native NT path, just store the
POSIX path in "PrintName".  Unfortunately this doesn't work.  For some
reason the Win32 API requires the "PrintName" to contain the Win32 path,
otherwise you'll get "The system cannot find the file specified." error
messages.  And it also doesn't work the other way around.  If the
"PrintName" contains a valid Win32 path, and "SubstituteName" contains
the POSIX path, you *still* get the "The system cannot find..." error.

So there are two problems:

- Only users with administrator permissions can create native symlinks.

- Due to the way they are used in the Win32 API, there's no way to
  use them with POSIX paths *and* Win32 paths for interoperability.
  So why bother?

> >Also rm  removes the target of the symbolic link not the link file.
> >Is this what you want?
> 
> Please provide a simple test case with the associated information requested
> by .  I cannot reproduce this behavior.  Of
> course, I'm using Cygwin 1.7  on Windows 7.

Yes, indeed.  Cygwin 1.5 doesn't recognize native symlinks and
consequentially the unlink() function didn't use the
FILE_OPEN_REPARSE_POINT flag to open the file for deletion.


Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Project Co-Leader  cygwin AT cygwin DOT com
Red Hat

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Symbolic links on NTFS with real symbolic links

[Larry Hall (Cygwin)]

On 10/29/2009 01:26 AM, Neil Mowbray wrote:

Dear Folks,

On NTFS systems that support real symbolic links (eg those with Vista)
the comand ln -s does *not* create a native symbolic link merely an old
style shortcut.

Will ln -s be chansed to support native symbolic links?


No, not until, at least, native symbolic links don't require elevated 
privileges to

use.


Also rm  removes the target of the symbolic link not the link file.
Is this what you want?


Please provide a simple test case with the associated information requested
by .  I cannot reproduce this behavior.  Of
course, I'm using Cygwin 1.7  on Windows 7.
You may want to see if you can reproduce the behavior on 1.7 before
reporting it though, since 1.5 isn't going to be updated anymore.  FWIW, if
you don't care for the Windows shortcut-style symlinks, my guess is you'll
be less enthused with the "new" special text file that 1.7 uses.  Them's the
breaks. ;-)

--
Larry Hall  http://www.rfk.com
RFK Partners, Inc.  (508) 893-9779 - RFK Office
216 Dalton Rd.  (508) 893-9889 - FAX
Holliston, MA 01746

_

A: Yes.
> Q: Are you sure?
>> A: Because it reverses the logical flow of conversation.
>>> Q: Why is top posting annoying in email?

--
Problem reports:   http://cygwin.com/problems.html
FAQ:   http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info:  http://cygwin.com/ml/#unsubscribe-simple

Re: Symbolic links and file tests in perl

[Brian Dessent]

Scott Webster Wood wrote:

> I tried doing a if(-l $file) where $file was the name of a symbolically 
> linked directory in the current working directory and it returned a false.  
> Doing a (-d $file) returned true.

I can't reproduce this:

$ mkdir foo; ln -s foo bar

$ perl -e 'print "yes\n" if (-l "bar");'
yes

Please provide a testcase that demonstrates the problem.

> Is there any way to work around this and then retrieve the real path of a 
> symbolically linked directory under cygwin?

$ perl -e 'print readlink("bar")'
foo

Brian

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

RE: Symbolic links with cvs

[Igor Pechtchanski]

Ugh, top-posting...  Reformatted.

On Fri, 2 Dec 2005, Akshay Dua wrote:

> > From: Igor Pechtchanski [mailto:[EMAIL PROTECTED]
> > Sent: Friday, December 02, 2005 6:43 PM
> > To: Akshay Dua
> > Cc: [EMAIL PROTECTED]

<http://cygwin.com/acronyms/#PCYMTNQREAIYR>.  Thanks.

> > Subject: Re: Symbolic links with cvs
> >
> > On Fri, 2 Dec 2005, Akshay Dua wrote:
> >
> > > Hello,
> > >
> > > Unfortunately, we have .lnk files in our source control
> > > [snip]
> > > U thirdparty/OPENSSL-0.9.7-BETA3/Makefile.lnk
> > > cvs checkout: cannot stat Makefile.lnk: No such file or directory
> >
> > As soon as you check out a .lnk file, it becomes a symlink, and Cygwin
> > will attempt to read the file that the symlink refers to.  If that
> > file doesn't exist (e.g., hasn't been checked out yet), any operations
> > on the symlink will fail (it will be a dangling link).  This is not a
> > Cygwin-specific issue (unless the .lnk in the name is an unfortunate
> > coincidence).  If you really are trying to commit a symlink to cvs,
> > the CVS manual says that this is not supported:
> > <http://ximbiot.com/cvs/manual/cvs-1.12.13/cvs_15.html>.
>
> Thanks so much for your reply.
>
> Is there a way to tell Cygwin to stop converting (or treating) .lnk
> files as symlinks?

Larry already mentioned it: add "nowinsymlinks" to your CYGWIN variable.

> The thing is my colleagues with the same version of Cygwin do not have
> this problem. In their case Cygwin treats the .lnk file as a plain file
> rather than a symbolic link and hence does not follow it. I wonder why
> this behavior exists on my machine.

Hmm...  For a .lnk file to be treated as a symlink, it has to also be
marked read-only (and "system", I think)...

> The only thing I can think of, is that I set and then unset
> CYGWIN=ntsec. I don't know if that changed something. Before that I had
> whatever is enabled by default and in fact was not observing the above
> behavior even when I checked out .lnk files.

Heh.  Check that the directory you're checking out to still has Windows
(inherited) permissions...  Maybe that's your problem.

> The issue really is that since .lnk files are treated as symbolic links,
> they appear as locally modified to CVS because in one case the links are
> followed (locally) and in the other case they aren't (in the
> repository).
>
> Any suggestions on how I can get the old behavior back?

You still haven't answered whether they are *supposed* to be symlinks...
If they are, see the CVS manual -- what you're doing is non-portable, and
you can't expect it to work.  Subject to change at any time.  If they are
regular files that just happened to have the .lnk extension, you may have
a shot with the options above.

Another thing that would be useful for people on this list to be able to
help you is the output of "cygcheck -svr", as requested in the Cygwin
problem reporting guidelines at <http://cygwin.com/problems.html>.  Please
make sure to attach the output, rather than including it inline.  That
would also answer the question of whether you have something unusual in
your environment.
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

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

RE: Symbolic links with cvs

[Akshay Dua]

I looked at two of the other configurations, the CYGWIN environment
variable is not set at all. So they are all running default configs.

Thanks again,
Akshay

> -Original Message-
> From: Larry Hall (Cygwin) [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 02, 2005 7:07 PM
> To: Akshay Dua
> Subject: Re: Symbolic links with cvs
> 
> Akshay Dua wrote:
> > Thanks so much for your reply.
> >
> > Is there a way to tell Cygwin to stop converting (or treating) .lnk
> > files as symlinks? The thing is my colleagues with the same version
of
> > Cygwin do not have this problem. In their case Cygwin treats the
.lnk
> > file as a plain file rather than a symbolic link and hence does not
> > follow it. I wonder why this behavior exists on my machine.
> >
> > The only thing I can think of, is that I set and then unset
> > CYGWIN=ntsec. I don't know if that changed something. Before that I
had
> > whatever is enabled by default and in fact was not observing the
above
> > behavior even when I checked out .lnk files.
> >
> > The issue really is that since .lnk files are treated as symbolic
links,
> > they appear as locally modified to CVS because in one case the links
are
> > followed (locally) and in the other case they aren't (in the
> > repository).
> >
> > Any suggestions on how I can get the old behavior back?
> 
> 
> You may want to check if your colleagues have "nowinsymlinks" set in
their
> CYGWIN environment variable
> <http://cygwin.com/cygwin-ug-net/using-cygwinenv.html>.
> 
> 
> --
> Larry Hall  http://www.rfk.com
> RFK Partners, Inc.  (508) 893-9779 - RFK Office
> 838 Washington Street   (508) 893-9889 - FAX
> Holliston, MA 01746

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

RE: Symbolic links with cvs

[Akshay Dua]

Thanks so much for your reply.

Is there a way to tell Cygwin to stop converting (or treating) .lnk
files as symlinks? The thing is my colleagues with the same version of
Cygwin do not have this problem. In their case Cygwin treats the .lnk
file as a plain file rather than a symbolic link and hence does not
follow it. I wonder why this behavior exists on my machine.

The only thing I can think of, is that I set and then unset
CYGWIN=ntsec. I don't know if that changed something. Before that I had
whatever is enabled by default and in fact was not observing the above
behavior even when I checked out .lnk files.

The issue really is that since .lnk files are treated as symbolic links,
they appear as locally modified to CVS because in one case the links are
followed (locally) and in the other case they aren't (in the
repository).

Any suggestions on how I can get the old behavior back?

Thanks
Akshay

> -Original Message-
> From: Igor Pechtchanski [mailto:[EMAIL PROTECTED]
> Sent: Friday, December 02, 2005 6:43 PM
> To: Akshay Dua
> Cc: cygwin@cygwin.com
> Subject: Re: Symbolic links with cvs
> 
> On Fri, 2 Dec 2005, Akshay Dua wrote:
> 
> > Hello,
> >
> > Unfortunately, we have .lnk files in our source control so I cannot
> > avoid the following problem. When I try to checkout a symbolic link
> > file, something happens to it and cvs is unable to stat it to set
> > necessary file information. Its almost like cygwin changed the name
of
> > the file from under CVSs' feet. Can anyone help?
> >
> > U thirdparty/OPENSSL-0.9.7-BETA3/Makefile.lnk
> > cvs checkout: cannot stat Makefile.lnk: No such file or directory
> > cvs checkout: cannot set time on Makefile.lnk: No such file or
directory
> > cvs checkout: cannot stat Makefile.lnk: No such file or directory
> 
> As soon as you check out a .lnk file, it becomes a symlink, and Cygwin
> will attempt to read the file that the symlink refers to.  If that
file
> doesn't exist (e.g., hasn't been checked out yet), any operations on
the
> symlink will fail (it will be a dangling link).  This is not a
> Cygwin-specific issue (unless the .lnk in the name is an unfortunate
> coincidence).  If you really are trying to commit a symlink to cvs,
the
> CVS manual says that this is not supported:
> <http://ximbiot.com/cvs/manual/cvs-1.12.13/cvs_15.html>.
> 
> HTH,
>   Igor
> --
>   http://cs.nyu.edu/~pechtcha/
>   |\  _,,,---,,_  [EMAIL PROTECTED]
> ZZZzz /,`.-'`'-.  ;-;;,_  [EMAIL PROTECTED]
>  |,4-  ) )-,_. ,\ (  `'-' Igor Pechtchanski, Ph.D.
> '---''(_/--'  `-'\_) fL   a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!
> 
> If there's any real truth it's that the entire multidimensional
infinity
> of the Universe is almost certainly being run by a bunch of maniacs.
/DA

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

Re: Symbolic links with cvs

[Igor Pechtchanski]

On Fri, 2 Dec 2005, Akshay Dua wrote:

> Hello,
>
> Unfortunately, we have .lnk files in our source control so I cannot
> avoid the following problem. When I try to checkout a symbolic link
> file, something happens to it and cvs is unable to stat it to set
> necessary file information. Its almost like cygwin changed the name of
> the file from under CVSs' feet. Can anyone help?
>
> U thirdparty/OPENSSL-0.9.7-BETA3/Makefile.lnk
> cvs checkout: cannot stat Makefile.lnk: No such file or directory
> cvs checkout: cannot set time on Makefile.lnk: No such file or directory
> cvs checkout: cannot stat Makefile.lnk: No such file or directory

As soon as you check out a .lnk file, it becomes a symlink, and Cygwin
will attempt to read the file that the symlink refers to.  If that file
doesn't exist (e.g., hasn't been checked out yet), any operations on the
symlink will fail (it will be a dangling link).  This is not a
Cygwin-specific issue (unless the .lnk in the name is an unfortunate
coincidence).  If you really are trying to commit a symlink to cvs, the
CVS manual says that this is not supported:
.

HTH,
Igor
-- 
http://cs.nyu.edu/~pechtcha/
  |\  _,,,---,,_[EMAIL PROTECTED]
ZZZzz /,`.-'`'-.  ;-;;,_[EMAIL PROTECTED]
 |,4-  ) )-,_. ,\ (  `'-'   Igor Pechtchanski, Ph.D.
'---''(_/--'  `-'\_) fL a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

If there's any real truth it's that the entire multidimensional infinity
of the Universe is almost certainly being run by a bunch of maniacs. /DA

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

RE: symbolic links on Samba-mounted drive

[Dave Korn]

> -Original Message-
> From: cygwin-owner On Behalf Of Steve Kelem
> Sent: 23 December 2004 18:32

> I'm running the latest Cygwin on WinXP SP2. I have coreutils-5.2.1-3 
> installed.
> 
> I have a Linux directory mounted via Samba.

http://cygwin.com/faq/faq_3.html#SEC66 help any?


cheers, 
  DaveK
-- 
Can't think of a witty .sigline today


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

Re: Symbolic Links

[Corinna Vinschen]

On Dec 15 21:58, Elliott Wilcoxon wrote:
> NTFS also supports hard links, and there's a program that comes with 
> Windows that lets you make them (searching WinXP Pro's Help and Support 
> Center for 'hardlink' gives the relevant entries).  The result would 
> then be that it would work in both Cygwin and Windows (all programs), 
> although it can be confusing if you're not used to thinking of file 
> system-y stuff.

Hardlinks don't work for directories, only for files.

Corinna

-- 
Corinna Vinschen  Please, send mails regarding Cygwin to
Cygwin Developermailto:[EMAIL PROTECTED]
Red Hat, Inc.

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

Re: Symbolic Links

[Elliott Wilcoxon]

NTFS also supports hard links, and there's a program that comes with 
Windows that lets you make them (searching WinXP Pro's Help and Support 
Center for 'hardlink' gives the relevant entries).  The result would 
then be that it would work in both Cygwin and Windows (all programs), 
although it can be confusing if you're not used to thinking of file 
system-y stuff.

Elliott Wilcoxon

Brian Dessent wrote:

Dan Adams wrote:

My question was, is there any way to use the cygwin links, not the windows
ones, to also be able to work in the open dialog box in MS Office products
like excel for example. As I said, it is working in windows explorer. The
only reason why I was mentioning about the windows links is because they
were working in excel and I figured it would be a good example.


If your filesystem is NTFS (and $deity hope it is, as FAT32 hurts like
something awful) then you can try fooling around with its built in
symbolic links, which are called junctions in the parlance.  There are
no built-in tools to do this but the venerable Mark Russinovich again
comes to the rescue with his freeware: 

from :

Junction

Win2K's version of NTFS supports directory symbolic links, where a
directory serves as a symbolic link to another directory on the
computer. For example, if the directory D:\SYMLINK specified
C:\WINNT\SYSTEM32 as its target, then an application accessing
D:\SYMLINK\DRIVERS would in reality be accessing
C:\WINNT\SYSTEM32\DRIVERS. Directory symbolic links are known as NTFS
junctions in Win2K. Unfortunately, Win2K comes with no tools for
creating junctions - you have to purchase the Win2K Resource Kit, which
comes the linkd program for creating junctions. I therefore decided to
write my own junction-creating tool: Junction. Junction not only allows
you to create NTFS junctions, it allows you to see if files or
directories are actually reparse points. Reparse points are the
mechanism on which NTFS junctions are based, and they are used by
Win2K's Remote Storage Service (RSS), as well as volume mount points. 

If you want to view reparse information, the usage for Junction is the
following: 

Usage: junction [-s]  

-s	Recurse subdirectories. 

If you want to create or delete a junction, use Junction like this: 

Usage: junction [-d]  [] 

To delete a junction specify the -d switch and the junction name. 

Download Junction (16KB) 

Download Junction Source (22 KB) 

I have not tried this but it sounds like it might be helpful for you.  I
have no idea how Cygwin would interact with one of these, but since it's
layered on top of Windows' kernel NTFS driver I would expect that it
would treat them just as any other app would, i.e. do the right thing.
Brian

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

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

Re: Symbolic Links

[Brian Dessent]

Dan Adams wrote:
> 
> My question was, is there any way to use the cygwin links, not the windows
> ones, to also be able to work in the open dialog box in MS Office products
> like excel for example. As I said, it is working in windows explorer. The
> only reason why I was mentioning about the windows links is because they
> were working in excel and I figured it would be a good example.

If your filesystem is NTFS (and $deity hope it is, as FAT32 hurts like
something awful) then you can try fooling around with its built in
symbolic links, which are called junctions in the parlance.  There are
no built-in tools to do this but the venerable Mark Russinovich again
comes to the rescue with his freeware: 

from :

Junction

Win2K's version of NTFS supports directory symbolic links, where a
directory serves as a symbolic link to another directory on the
computer. For example, if the directory D:\SYMLINK specified
C:\WINNT\SYSTEM32 as its target, then an application accessing
D:\SYMLINK\DRIVERS would in reality be accessing
C:\WINNT\SYSTEM32\DRIVERS. Directory symbolic links are known as NTFS
junctions in Win2K. Unfortunately, Win2K comes with no tools for
creating junctions - you have to purchase the Win2K Resource Kit, which
comes the linkd program for creating junctions. I therefore decided to
write my own junction-creating tool: Junction. Junction not only allows
you to create NTFS junctions, it allows you to see if files or
directories are actually reparse points. Reparse points are the
mechanism on which NTFS junctions are based, and they are used by
Win2K's Remote Storage Service (RSS), as well as volume mount points. 

If you want to view reparse information, the usage for Junction is the
following: 

Usage: junction [-s]  

-s  Recurse subdirectories. 

If you want to create or delete a junction, use Junction like this: 

Usage: junction [-d]  [] 

To delete a junction specify the -d switch and the junction name. 

Download Junction (16KB) 

Download Junction Source (22 KB) 
>>

I have not tried this but it sounds like it might be helpful for you.  I
have no idea how Cygwin would interact with one of these, but since it's
layered on top of Windows' kernel NTFS driver I would expect that it
would treat them just as any other app would, i.e. do the right thing.

Brian

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

Re: Symbolic Links

[Dan Adams]

My question was, is there any way to use the cygwin links, not the windows
ones, to also be able to work in the open dialog box in MS Office products
like excel for example. As I said, it is working in windows explorer. The
only reason why I was mentioning about the windows links is because they
were working in excel and I figured it would be a good example.

-- 
Dan Adams - [EMAIL PROTECTED]
http://www.infochi.com


"Christopher Faylor" <[EMAIL PROTECTED]> wrote in
message news:[EMAIL PROTECTED]
> On Mon, Dec 15, 2003 at 01:16:16PM -0700, Dan Adams wrote:
> >When I try to use a windows shortcut file in cygwin it doesn't seem to
work.
>
> Correct.  It is not supposed to work.  Cygwin understands cygwin
shortcuts.
> Windows understand windows and cygwin shortcuts.
> --
> Please use the resources at cygwin.com rather than sending personal email.
> Special for spam email harvesters: send email to [EMAIL PROTECTED]
> and be permanently blocked from mailing lists at sources.redhat.com
>




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

Re: Symbolic Links

[Christopher Faylor]

On Mon, Dec 15, 2003 at 01:16:16PM -0700, Dan Adams wrote:
>When I try to use a windows shortcut file in cygwin it doesn't seem to work.

Correct.  It is not supposed to work.  Cygwin understands cygwin shortcuts.
Windows understand windows and cygwin shortcuts.
--
Please use the resources at cygwin.com rather than sending personal email.
Special for spam email harvesters: send email to [EMAIL PROTECTED]
and be permanently blocked from mailing lists at sources.redhat.com

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

Re: Symbolic Links

[Dan Adams]

When I try to use a windows shortcut file in cygwin it doesn't seem to work.
In the example that I tried, misc.lnk is the name of the shortcut from
windows.

[EMAIL PROTECTED] ~/Finance>ls
Auto.xlsCopy of Daniel Adams.mny  Financial Plan.doc  Insurance
Inventory.doc  Stock Stats.xls  stock.xls
Bills.xls   Daniel Adams.mny  Fraud Hotline 1800.doc  Misc.lnk
other
Checks.xls  Distribution.xls  History.xls Paychecks.xls
personal.mdb
[EMAIL PROTECTED] ~/Finance>cd Misc.lnk
Misc.lnk: Not a directory.

That is the attempt I did, with the output. Do I need to do something
specific to get this to work?

Dan

"Paul Kraus" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> I have not tested this but per the docs on cygwin site the new version
> does follow windows shortcut link files.
>
> > -Original Message-
> > From: [EMAIL PROTECTED]
> > [mailto:[EMAIL PROTECTED] On Behalf Of Dan Adams
> > Sent: Monday, December 15, 2003 2:39 PM
> > To: [EMAIL PROTECTED]
> > Subject: Re: Symbolic Links
> >
> >
> > Part of the reason I am interested in this, I guess I forgot
> > to say is to be able to have both Windows and Cygwin
> > recognize the links. If I use the windows shortcut creation,
> > cygwin doesn't recognize it. If I use the cygwin thing below,
> > excel doesn't recognize it, but windows does.
> >
> > Dan
> >
> > "Dan Adams" <[EMAIL PROTECTED]> wrote in message
> > news:[EMAIL PROTECTED]
> > > Hi, I have been using the symbolic links feature of cygwin to link
> > > from
> > one
> > > folder to another in my system. I know that is not a big beneficial
> > > use of cygwin, but it is one that adds to the benefit of cygwin. I
> > > also use
> > cygwin
> > > for other stuff.
> > >
> > > I was wondering, does anyone know is something specific is
> > needed to
> > > be
> > able
> > > to link from one folder to another, for example I am linking from
> > > C:\My Documents to D:\Finance in a link file called other. Honestly
> > > this works
> > in
> > > the file manager part of windows explorer, one desire I
> > have ot this
> > > would be to be able to use this in Microsoft Excel by
> > clicking on the
> > > "My Documents" link on the left side and then by opening the folder
> > > called "other" in the file list. The only problem with this
> > is that by
> > > using the command "ln -s "D:\Finance" other" does not
> > actually let the
> > > folder show
> > up
> > > in excel. Is this possible, or is this maybe a future feature that
> > > will be implemented? If it is in the feature, I know I would
> > > appreciate the
> > ability.
> > >
> > > Dan Adams - [EMAIL PROTECTED]
> > > http://www.infochi.com
> > >
> > >
> > >
> > >
> >
> >
> >
> >
> > --
> > 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/
> >
>
>




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

RE: Symbolic Links

[Paul Kraus]

I have not tested this but per the docs on cygwin site the new version
does follow windows shortcut link files.

> -Original Message-
> From: [EMAIL PROTECTED] 
> [mailto:[EMAIL PROTECTED] On Behalf Of Dan Adams
> Sent: Monday, December 15, 2003 2:39 PM
> To: [EMAIL PROTECTED]
> Subject: Re: Symbolic Links
> 
> 
> Part of the reason I am interested in this, I guess I forgot 
> to say is to be able to have both Windows and Cygwin 
> recognize the links. If I use the windows shortcut creation, 
> cygwin doesn't recognize it. If I use the cygwin thing below, 
> excel doesn't recognize it, but windows does.
> 
> Dan
> 
> "Dan Adams" <[EMAIL PROTECTED]> wrote in message 
> news:[EMAIL PROTECTED]
> > Hi, I have been using the symbolic links feature of cygwin to link 
> > from
> one
> > folder to another in my system. I know that is not a big beneficial 
> > use of cygwin, but it is one that adds to the benefit of cygwin. I 
> > also use
> cygwin
> > for other stuff.
> >
> > I was wondering, does anyone know is something specific is 
> needed to 
> > be
> able
> > to link from one folder to another, for example I am linking from 
> > C:\My Documents to D:\Finance in a link file called other. Honestly 
> > this works
> in
> > the file manager part of windows explorer, one desire I 
> have ot this 
> > would be to be able to use this in Microsoft Excel by 
> clicking on the 
> > "My Documents" link on the left side and then by opening the folder 
> > called "other" in the file list. The only problem with this 
> is that by 
> > using the command "ln -s "D:\Finance" other" does not 
> actually let the 
> > folder show
> up
> > in excel. Is this possible, or is this maybe a future feature that 
> > will be implemented? If it is in the feature, I know I would 
> > appreciate the
> ability.
> >
> > Dan Adams - [EMAIL PROTECTED]
> > http://www.infochi.com
> >
> >
> >
> >
> 
> 
> 
> 
> --
> 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/
> 


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

Re: Symbolic Links

[Dan Adams]

Part of the reason I am interested in this, I guess I forgot to say is to be
able to have both Windows and Cygwin recognize the links. If I use the
windows shortcut creation, cygwin doesn't recognize it. If I use the cygwin
thing below, excel doesn't recognize it, but windows does.

Dan

"Dan Adams" <[EMAIL PROTECTED]> wrote in message
news:[EMAIL PROTECTED]
> Hi, I have been using the symbolic links feature of cygwin to link from
one
> folder to another in my system. I know that is not a big beneficial use of
> cygwin, but it is one that adds to the benefit of cygwin. I also use
cygwin
> for other stuff.
>
> I was wondering, does anyone know is something specific is needed to be
able
> to link from one folder to another, for example I am linking from C:\My
> Documents to D:\Finance in a link file called other. Honestly this works
in
> the file manager part of windows explorer, one desire I have ot this would
> be to be able to use this in Microsoft Excel by clicking on the "My
> Documents" link on the left side and then by opening the folder called
> "other" in the file list. The only problem with this is that by using the
> command "ln -s "D:\Finance" other" does not actually let the folder show
up
> in excel. Is this possible, or is this maybe a future feature that will be
> implemented? If it is in the feature, I know I would appreciate the
ability.
>
> Dan Adams - [EMAIL PROTECTED]
> http://www.infochi.com
>
>
>
>




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