X-Recipient: archive-cygwin AT delorie DOT com DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 6AADB3857C79 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=cygwin.com; s=default; t=1602594041; bh=fww88ckwew2Zy5YVv1mBEjqZh8jyW9grdrEv6ivrydQ=; h=Date:Subject:To:List-Id:List-Unsubscribe:List-Archive:List-Post: List-Help:List-Subscribe:From:Reply-To:From; b=rQ+PxAa2t/aDODvrI5b/OWvZKyBYQ+5Q7EGpO7La/g5qGjA4kKT2etWjb8vFXWM45 4cEcUrAPD4pNlytUUMvIsvdOicc1etARBE1vl7PU1lqzaTNalCj9/TSxvnxmBKfgIv VJIEAfmt7Z7SBuhFDCg2Q2GU7LcqdybcjpTjb1R4= X-Original-To: cygwin AT cygwin DOT com Delivered-To: cygwin AT cygwin DOT com DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org A2EBC3857C79 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:from:date:message-id:subject:to; bh=lQ5bpiGzjwxk/png+lK31fp0LT44Q23iDoakYT8nRV0=; b=FUgPNopCJmqbYgAivplYlY6DyG3fmX9E7JCI1awCkvK6e2KBazVgY1uKOvJ3UXzpxt lBQQA3/ho55JHlUYlM25kp2ZY4rnFaQNOxoerRqBJjN5OrBdBeFVzCr6DLTMtfCwD6IU xloSJW1FNuPLS8ZAZU2NhPfWgVMCapb7mGCsb/hG+NlIXxuVQinuNVYSPVuLHODbYDWh ujJw1LGvbBXQLSFqs/lM0MXTI+LxTL/qRKDoEM1Y1m0zqKuD2Loe4r7OZZEShKHqa4JH 6fZSiJ5W/HqsIEE0cXwpxlXNvxA4zZslWiba4GdUjKY/fu+5EvKXRNwIYlzpRjbXgTt9 idPw== X-Gm-Message-State: AOAM530LSQ2M408IgnfOEmBjCAHD3gvznL4ZHIfb5lt5iCSCBziIDDyc 0Pw2EgsjtNL4/ipwttYC5dbdUs5UjcTUCtrFUMzI+D9w1ZWdWt9D X-Google-Smtp-Source: ABdhPJy2v4DPWovuIPH4pELIRQG/xsR/tAjh0O2oF0+weQRyoP2nAIKLk2uyBu7IhhVr85YtMPGjd9toyhcfSe9Dftc= X-Received: by 2002:a2e:b602:: with SMTP id r2mr3575217ljn.106.1602594036767; Tue, 13 Oct 2020 06:00:36 -0700 (PDT) MIME-Version: 1.0 Date: Tue, 13 Oct 2020 18:30:25 +0530 Message-ID: Subject: Problem with cp.exe (in Cygwin 3.6 64 bit): permission preserve To: cygwin AT cygwin DOT com X-Spam-Status: No, score=-2.4 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 AT cygwin DOT com X-Mailman-Version: 2.1.29 List-Id: General Cygwin discussions and problem reports List-Archive: List-Post: List-Help: List-Subscribe: , From: vinay Hegde via Cygwin Reply-To: vinay Hegde Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "Cygwin" Hello Cygwin Team, We are upgrading Cygwin from 1.7.31 32 bit to 3.6 64 bit. With the earlier version, 'cp -fp' command used to work without any error. Now, we get an error like, 'cp: preserving permissions for not supported. Here is my understanding about ACLs & File permission in Cygwin: Windows ACLs will be translated/mapped to POSIX like in Cygwin (This includes user, group & permissions). Cygwin uses some logic to implement this (using Solaris API, using SFU, ACEs accumulated for the 'access allowed' etc.) I understand that, POSIX style is introduced from version 1.7.34. If my understanding is correct, prior to version 1.7.34, it was using UNIX like permission(not POSIX). In both cases (UNIX/POSIX), permission preserve has no real meaning. To disable this translation(to UNIX/POSIX), we had to set 'nontsec' CYGWIN variable in old Cygwin and we have to set 'noacl' in /etc/fastab for the new Cygwin But my question here is, 'cp -fp' was working with Cygwin 1.7.31. Why it is NOT working now with Cygwin 3.6? Note: We were NOT using 'nontsec' before & now, it's equivalent 'noacl' is also not used. If I use 'noacl' in the cygwin, 'cp -fp' doesn't complain. Regards Vinay Hegde -- 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