From: "L. A. Walsh" <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: Is it OK to mount cygdrive on / ? (usually, but may not be as portable).
Date: Sat, 04 Feb 2017 22:51:00 -0000 [thread overview]
Message-ID: <58965AF8.2040007@tlinx.org> (raw)
In-Reply-To: <45557206.20170204173939@yandex.ru>
Andrey Repin wrote:
> Accessing drive letters directly from inside Cygwin is often
> considered a grey area.
----
How is it grey?
> Too much may happen on this border. You have to clearly understand, how Cygwin interact with other system, to avoid issues.
>
----
I.e. if you think you may have programs that also want to use
/bin /usr, /sbin, /lib /etc, there could be conflicts.
> If you want to access Windows path, recommended route lies through the use of
> cygpath utility to convert native paths to the Cygwin scheme. Et vice versa.
>
I wouldn't recommend that -- it's too hard to type:
/> ls -d $(cygpath S:\Music\Anime)
ls: cannot access S:MusicAnime: No such file or directory
/> ls -d $(cygpath 'S:\Music\Anime')
/s/Music/Anime/
...(vs.)
/> ls -d /s/Music/Anime
/s/Music/Anime/
-or-
ls -d $(cygpath \\ishtar\Music)
ls: cannot access /ishtarMusic: No such file or directory
/> ls -d $(cygpath '\\ishtar\Music')
//ishtar/Music/
---
Much easier just to type "//hostname/Share".
--
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:[~2017-02-04 22:51 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-03 21:09 Is it OK to mount cygdrive on / ? Rustam
2017-02-03 21:33 ` Wells, Roger K.
2017-02-04 14:50 ` Andrey Repin
2017-02-04 22:51 ` L. A. Walsh [this message]
2017-02-05 8:50 ` Is it OK to mount cygdrive on / ? (usually, but may not be as portable) Andrey Repin
2017-02-05 20:24 ` Is it OK to mount cygdrive on / ? cyg Simple
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=58965AF8.2040007@tlinx.org \
--to=cygwin@tlinx.org \
--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).