From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-lj1-x22f.google.com (mail-lj1-x22f.google.com [IPv6:2a00:1450:4864:20::22f]) by sourceware.org (Postfix) with ESMTPS id 526333857C49 for ; Fri, 2 Oct 2020 16:47:25 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 526333857C49 Received: by mail-lj1-x22f.google.com with SMTP id y4so1719293ljk.8 for ; Fri, 02 Oct 2020 09:47:25 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=kaoPF8+oAisj7WRAl2zRip/3QLgqxyGqtsBXR1uINjk=; b=kll9rBQ5K0nchcseszTJj/f4g1knkSkBJWtE8PzTA+iPWxlePRh21IsoLuzgrg8xbm hVvhIaA+2KCEfBkt6v1PL0KMQ6dkF1fHzHtQejkO9MdpWc/fwiQeYVllWf6ZDpqptDGJ muhYKw4cK5wPTaHJ6fgexTva1DqFWjABlm/p2R6tDE4cud0vUSxms6ZUIOcr5vCyM15J pVggmJNuCQtRNhM2KgBGGGSHtyksTIHBrRk1h/tLTwaYTBaN/njuTOK7QpvYLBIwvU4k zPfCF2O0/fkCiI1SV94gUSn8eeC1CsqD9yQMK8Yz0Orc1eRplmXIGLrA66WbBcIAOkgu i52w== X-Gm-Message-State: AOAM5319LP+/e8fOmE1P4E5tl0pmVIxHydDoumpHATljvR1KZn92VoR8 Vtu3pLz51jdQhehZPhmxvyMhVDtFDGA9PgyzyQ/20uSJJLIM6A== X-Google-Smtp-Source: ABdhPJwenY9DALgwk8saHY7BnTcMJndahMleKDeY3N/2qt+XyM4wsM4Ow2sw4ELXJ+Zl0fqENVAL9PsydHdyi/PgLL8= X-Received: by 2002:a2e:808b:: with SMTP id i11mr1040075ljg.366.1601657243779; Fri, 02 Oct 2020 09:47:23 -0700 (PDT) MIME-Version: 1.0 References: In-Reply-To: From: vinay Hegde Date: Fri, 2 Oct 2020 22:17:12 +0530 Message-ID: Subject: Re: Problem with tar version 1.29 (in Cygwin 3.6 64 bit) in extracting sym-link files To: moss@cs.umass.edu Cc: cygwin@cygwin.com Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-2.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP autolearn=ham autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 02 Oct 2020 16:47:26 -0000 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 On Fri, Oct 2, 2020 at 9:13 PM Eliot Moss 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