public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Eliot Moss <moss@cs.umass.edu>
Cc: cygwin@cygwin.com
Subject: Re: Problem with tar version 1.29 (in Cygwin 3.6 64 bit) in extracting sym-link files
Date: Fri, 2 Oct 2020 14:14:44 -0400	[thread overview]
Message-ID: <fe78814f-dd17-fa71-98a9-5430cc6d0eec@cs.umass.edu> (raw)
In-Reply-To: <CAB848Xsa7scnz3P7Z46k0ECsFv97VdEEbXzTqVd8bZzDZ1SaDQ@mail.gmail.com>

On 10/2/2020 12:47 PM, vinay Hegde wrote:
> Hi Eliot Moss,
> Thank you very much for the quick response & the information.It really helped.
> I just set 'CYGWIN=winsymlinks:lnk' & I am now able to open sym-link
> file. Both 'CYGWIN=winsymlinks:lnk' & 'CYGWIN=winsymlinks' are working
> for me.
> But it creates a shortcut(not the regular file). Hope it won't impact
> my existing setup.
> 
> But both  'CYGWIN=winsymlinks:native' (which is default I believe) &
> 'CYGWIN=winsymlinks:nativestrict' are not working for me. Just to
> understand, In what OS environment/File System 'native' will work?
> 
> Regards
> Vinay Hegde

I run Windows 10 and that works for me.  Of course below, jcontrol should
be an actual file, while ControlPanel will be a symlink to it.  (That
particular name might behave oddly under Windows, because the Control
Panel is a built in thing!)

Not sure what else to say about the different forms.  The lnk form, as
I recall, builds a Cygwin-specific thing that Cygwin understands but
Windows tools will not - they'll just think its a small ordinary file
(its has within it, a few "magic" bytes then the name of the target
file).  You _want_ a short-cut, right?  ControlPanel -> jcontrol _is_
a link.

So I admit I am not fully understanding your post.

Also, on this list, the custom is to bottom-post (or intersperse) replies,
not to top-post.

Regards - EM

> On Fri, Oct 2, 2020 at 9:13 PM Eliot Moss <moss@cs.umass.edu> wrote:
>>
>> On 10/2/2020 11:26 AM, vinay Hegde via Cygwin wrote:
>>> Hi Cygwin Team,
>>> In Cygwin 3.6, I am facing an issue while using tar.exe for extracting
>>> .tar.z file.
>>>
>>> Issue summary:
>>> When I use 'tar.exe' to extract the .tar.z file, it extracts all files
>>> including symlinks. But symlink file size will be 0KB & it throws
>>> error 'The file cannot be accessed by the system', if I try to open in
>>> any Windows editor like notepad or notepad++
>>>
>>> Below are the details:
>>> -   OS: Windows 2019
>>> -   Cygwin version installed: 3.6 (tar version: 1.29)
>>> -   Command used to extract the tar file is: tar -zxvf jre64.tar.Z
>>> -   'ls -l' on the extracted directory shows:
>>> lrwxrwxrwx  1 etbuild Domain Users      8 Jul 10  2017 ControlPanel -> jcontrol
>>> -rwxr-xr-x+ 1 etbuild Domain Users   7734 Mar 15  2017 java
>>> -rwxr-xr-x+ 1 etbuild Domain Users 128791 Mar 15  2017 javaws
>>> -rwxr-xr-x+ 1 etbuild Domain Users   6264 Mar 15  2017 jcontrol
>>>
>>> -     As you can see 'ControlPanel' is a symlink file with 0KB
>>> (8Bytes) size. This file, I cannot open in any Windows editor. It
>>> throws error like ''The file cannot be accessed by the system'
>>>
>>> -    However, I can open this file in vi editor or I can 'cat' this.
>>>
>>> -    Earlier, I was using Cygwin version 1.7 (tar version: 1.27) & in
>>> that, this issue was not there. Symlink file size was 1KB & I could
>>> open it with any Windows editor.
>>>
>>> Please suggest what needs to be done to fix this issue.
>>
>> Hi, Vinay - Cygwin can use, and create, a variety of forms of links.  Some of these are understood
>> by Windows tools, some not.  I suggest you read in the Cygwin documentation about symlinks and
>> decide what kind are best for you.  Then you'll need to set that up, delete the existing link, and
>> re-create it.  I personally run with CYGWIN=winsymlinks:native, but as we say in Internet land, YMMV.
>>
>> Regards - Eliot Moss

  reply	other threads:[~2020-10-02 18:14 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02 15:26 vinay Hegde
2020-10-02 15:43 ` Eliot Moss
2020-10-02 16:47   ` vinay Hegde
2020-10-02 18:14     ` Eliot Moss [this message]
2020-10-04 10:28     ` Andrey Repin
2020-10-05 15:23       ` Hamish McIntyre-Bhatty
2020-10-05 17:29         ` Brian Inglis
2020-10-07 20:33           ` Hamish McIntyre-Bhatty

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fe78814f-dd17-fa71-98a9-5430cc6d0eec@cs.umass.edu \
    --to=moss@cs.umass.edu \
    --cc=cygwin@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).