From: L A Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com, fergus@bonhard.uklinux.net
Subject: Re: Creation of weird WINDOWS-related (sub)directories
Date: Fri, 28 Sep 2018 05:55:00 -0000 [thread overview]
Message-ID: <5BADC248.7050009@tlinx.org> (raw)
In-Reply-To: <ac423f75-7d9a-d5b8-6bf7-b7ef4b7d9fe3@t-online.de>
On 9/25/2018 9:53 AM, Hans-Bernhard Bröker wrote:
> Am 25.09.2018 um 17:16 schrieb Fergus:
>
>> Unintentionally I have confounded the discussion. The directory named
>> "consoleX" is my home-grown Cygwin root directory.
>> (Others' preferred locationname might be "cygwin" or "mycygwin" or
>> whatever.)
>
> That does not explain anything, actually. Cygwin's own root directory
> is always '/'. The one you speak of would be the windows-side
> installation root directory (c:\cygwin or c:\cygwin64 by default), but
> that would never show up like that from inside cygwin. I.e. while you
> do have
----
So the root of the cygwin drive is '/', so what would happen
if a cygwin program tried to expand a windows path, with a windows
variable in it, like '%SystemDrive%'.... Seems to me that
whatever that program is, it *IS* running under cygwin and using
a windows path with the win-var unexpanded.
If I understand correctly, the weird dir is at absolute
(from windows C:\) path:
C:/consoleX/%SystemDrive%/ProgramData/Microsoft/Windows/Caches
or, inside cygwin, you see:
/%SystemDrive%/ProgramData/Microsoft/Windows/Caches
yes? Doesn't matter _that_ much, I'd just work
around it by moving it aside and creating a symlink in windows
from %SystemDrive% => C:\. Hopefully whatever is creating
it won't delete the symlink. If it does, you can retry
the command specifying /j to make a windows junction.
(in cmd.exe, you should be able to type mklink /h for help).
Note, in windows, mklink, the order is mklink <to> <from> (sorta
backwards from normal *nix conventions).
If you were curious and a bit daring,
you could put an empty %systemdrive% directory
there instead of the one it was using and make it read-only & set
the system attribute. Then whatever is trying to write into
it should fail and hopefully you'll see an error message...
to set read-only and
system with the attrib command try
attrib +r +s <filename>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
next prev parent reply other threads:[~2018-09-28 5:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-25 15:16 Fergus
2018-09-25 15:33 ` Marco Atzeri
2018-09-25 15:35 ` Andrey Repin
2018-09-25 16:53 ` Hans-Bernhard Bröker
2018-09-28 5:55 ` L A Walsh [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-09-25 14:05 Fergus
2018-09-25 14:43 ` Marco Atzeri
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=5BADC248.7050009@tlinx.org \
--to=cygwin@tlinx.org \
--cc=cygwin@cygwin.com \
--cc=fergus@bonhard.uklinux.net \
/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).