Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

2021-01-13 Thread Matt D. via Cygwin
On Tue, Jan 12, 2021 at 5:20 PM Andrey Repin wrote: > > Again, the properties are read BY SYSTEM at the moment the link is created. > In other words, Windows is unable to create a link to nonexistent > (unreachable) target (not directly, at least). This is false. Links can be created arbitrarily

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

2021-01-12 Thread Matt D. via Cygwin
Operations like cp and rsync etc. should still work. The type of symbolic link to be created can be read from the file attributes of the one being copied. On Mon, Jan 4, 2021 at 10:46 AM Jeffrey Altman via Cygwin wrote: > > On 1/4/2021 10:27 AM, Matt D. via Cygwin (cygwin@cygwin.com)

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

2021-01-04 Thread Matt D. via Cygwin
bolic links. It does not have a problem creating links to any target with the default Cygwin (non-Windows) symbolic links. On Mon, Jan 4, 2021 at 7:30 AM Eliot Moss wrote: > > On 1/4/2021 5:36 AM, Matt D. via Cygwin wrote: > > Did you try any of my test cases? This can't and doesn't work

Re: Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

2021-01-04 Thread Matt D. via Cygwin
r_a/a' -> 'folder_b/a' cp: cannot create symbolic link 'folder_b/a': No such file or directory $ cp -Pv folder_a/a folder_b/ 'folder_a/a' -> 'folder_b/a' cp: cannot create symbolic link 'folder_b/a': No such file or directory On Sun, Jan 3, 2021 at 12:00 AM Brian Inglis wrote: > > On 2021-01-0

Native symbolic link behavior is broken and makes backups using Cygwin command line tools impossible

2021-01-02 Thread Matt D. via Cygwin
I have a folder with a lot of native Windows symbolic links. I want to copy this folder. I cannot rsync or cp this folder due to Cygwin being unable to create symbolic links without also wanting to verify the link target. This can be demonstrated: $ ln -s a b ln: failed to create symbolic link

How to ensure that /bin takes priority over System32 with "bash -c"?

2020-10-31 Thread Matt D. via Cygwin
I have Cygwin's /bin directory configured to be available on my login environment PATH by default. This behavior is inherited when I run a bash login shell: $ where sort C:\cygwin\bin\sort.exe C:\Windows\System32\sort.exe But if I run the following script from a Windows command prompt: C:\>

Re: Error: "-gThe system cannot find the file specified." When bash script containing "cut" is run from cmd

2020-10-31 Thread Matt D. via Cygwin
Please ignore this. There was an error in my test case. -- 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

Error: "-gThe system cannot find the file specified." When bash script containing "cut" is run from cmd

2020-10-31 Thread Matt D. via Cygwin
Simple Bash script: > #!/bin/bash > > cut Save as "testme.sh" in C:\ or elsewhere. Open a Windows command prompt and type: > cmd /c bash -c /c/testme.sh I get the following error: > -gThe system cannot find the file specified. This only seems to trigger when bash is running as a child