public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Creation of weird WINDOWS-related (sub)directories
Date: Tue, 25 Sep 2018 16:53:00 -0000	[thread overview]
Message-ID: <ac423f75-7d9a-d5b8-6bf7-b7ef4b7d9fe3@t-online.de> (raw)
In-Reply-To: <000301d454e2$c5102a20$4f307e60$@bonhard.uklinux.net>

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

	c:\consoleX\bin

that will not show up as

	/consoleX/bin

but rather as

	/bin
or
	/cygdrive/c/consoleX/bin

> The directory %SystemDrive% occurs at the root of the Cygwin filesystem.
> I cannot work out what activity has triggered it .. ..

A look at the creation time of the directory might provide insightful.

--
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

  parent reply	other threads:[~2018-09-25 16:53 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 [this message]
2018-09-28  5:55   ` L A Walsh
  -- 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=ac423f75-7d9a-d5b8-6bf7-b7ef4b7d9fe3@t-online.de \
    --to=hbbroeker@t-online.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).