From: Andrey Repin <anrdaemon@yandex.ru>
To: "Mainz, Roland" <Roland.Mainz@rovema.de>, cygwin@cygwin.com
Subject: Re: /usr/bin/realpath cannot handle UNC paths ?
Date: Fri, 29 Sep 2023 23:05:15 +0300 [thread overview]
Message-ID: <227912446.20230929230515@yandex.ru> (raw)
In-Reply-To: <AM5PR0502MB3075FC8E067A62375F69E06292C1A@AM5PR0502MB3075.eurprd05.prod.outlook.com>
Greetings, Mainz, Roland!
> ----
> We're trying to use UNC paths (e.g. //server/home/xyz/), but some of our
> scripts fail when /usr/bin/realpath is used.
> Example:
> ---- snip ----
> $ uname -a
> CYGWIN_NT-10.0-19045 WINGRENDEL01 3.4.9-1.x86_64 2023-09-06 11:19 UTC x86_64 Cygwin
> $ realpath "$PWD"
> realpath:
> //crawlinghorror_ipv6/home/rmainz/tmp/projekt_kraken/try11_rde/RDE-Development/build_windows10_msnfs_ipv6: No such file or directory
> ---- snip ----
> Bug or feature ?
> ----
$ pwd
//DAEMON-EC.DARKDRAGON.LAN/D
$ echo "$PWD"
//DAEMON-EC.DARKDRAGON.LAN/D
$ which realpath
/bin/realpath
$ /bin/realpath "$PWD"
//DAEMON-EC.DARKDRAGON.LAN/D
--
With best regards,
Andrey Repin
Friday, September 29, 2023 23:04:17
Sorry for my terrible english...
prev parent reply other threads:[~2023-11-06 17:30 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <a0f1e420-ae48-49a3-9300-c56f1948ad9b.8d485f54-9f47-42b0-bdcb-9635fbf663c3.f4d03fc7-7271-4dda-9819-8a6d839d14d6@emailsignatures365.codetwo.com>
[not found] ` <a0f1e420-ae48-49a3-9300-c56f1948ad9b.93e247b8-206a-49dd-b71c-9240681180cb.f8a0c42a-0aa6-492e-9fa9-cb8871cc779e@emailsignatures365.codetwo.com>
[not found] ` <a0f1e420-ae48-49a3-9300-c56f1948ad9b.e52b7f5f-5a09-4346-99f8-a6591191169c.50aab2c7-ebcb-479e-bd07-49d0153a95f2@emailsignatures365.codetwo.com>
2023-09-28 12:24 ` Mainz, Roland
2023-09-29 20:05 ` Andrey Repin [this message]
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=227912446.20230929230515@yandex.ru \
--to=anrdaemon@yandex.ru \
--cc=Roland.Mainz@rovema.de \
--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).