Re: Change in logical link behaviour

[Rainer Emrich <rainer@emrich-ebersheim.de>]

[-- Attachment #1.1: Type: text/plain, Size: 1754 bytes --]

Am 03.03.2020 um 17:41 schrieb Corinna Vinschen:
> On Mar  3 17:05, Rainer Emrich wrote:
>> Am 03.03.2020 um 16:49 schrieb Corinna Vinschen:
>>> On Mar  3 15:31, Corinna Vinschen wrote:
>>>> On Mar  3 15:19, Rainer Emrich wrote:
>>>>> Am 03.03.2020 um 14:39 schrieb Corinna Vinschen:
>>>>>> Aha!  So powershell does not show the 'l'.
>>>>> The most important thing is the difference between cygwin 3.0.7 and
>>>>> cygwin 3.1.4. For cygwin 3.0.7 the link indicator is shown even in
>>>>> powershell on Windows 7 but not with cygwin-3.1.4. And believe me, the
>>>>> only difference is the cygwin version.
>>>>
>>>> I may believe you, but believe me that Cygwin has no influence on
>>>> what powershell shows.  See the output of cmd /c dir /a.  The file
>>>> is a native symlink.
>>>
>>> ...and for kicks I just tried this on W7 under Cygwin 3.0.7.  The output
>>> is the same as I pasted in https://cygwin.com/ml/cygwin/2020-03/msg00043.html
>>>
>>> No 'l' mode flag, no 6th column in the mode output:
>>>
>>> Mode                LastWriteTime     Length Name
>>> ----                -------------     ------ ----
>>> -a---        03.03.2020     16:47          0 bar
>>>
>>>
>> For me it's different. That's realy strange.
>>
>> Ok, so I can't rely on powershell here. Is there a recommended procedure
>> for what I try in a script?
>>
>> Check if the current cygwin environment is able to create native symlinks.
> 
> Unless I'm missing some new and shiny Windows onboard tool, that's
> surprisingly tricky without creating your own executable checking just
> that.  Off the top of my head I don't see any other way than calling cmd
> /c dir and some awk or sed hacking.
Thank you, that's what I thought.

Rainer


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]