From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: Device names in /proc/mounts
Date: Thu, 28 Jul 2011 11:22:00 -0000 [thread overview]
Message-ID: <20110728112154.GB16913@ednor.casa.cgf.cx> (raw)
In-Reply-To: <9B10FEAACF062F48A095880A451FF0590380B9DAEF@DEMCHP99E84MSX.ww902.siemens.net>
On Thu, Jul 28, 2011 at 10:18:26AM +0200, Schwarz, Konrad wrote:
>As far as I understand, Cygwin mount knows about
>- fixed mounts /, /usr/bin, /usr/lib
>- user-defined mounts taken from /etc/fstab, /etc/fstab.d, and the command-line
>- Win32 drive letters implicitly mounted under /cygdrive
>
>The last case is actually handled by Windows, as you point out.
>
>What would be the problem (otherwise than backwards compatibility) in using
>Cygwin device names in this last case?
The above is inaccurate and misleading. Cygwin's mount utility is a mapping
between windows paths and posix paths. That's it. The "drive letters" above
could be anything that Windows maps to a drive letter. A drive does not
necessarily directly map to a physical device.
>For the second case (and the first, should you so desire), you could use
>the /cygdrive prefix or //server/share notation, as above.
/cygdrive is a user-settable value. Some users use other values like
"/dev" instead of /cygdrive. Some people get rid of the /cygdrive
entirely and just map to /a. We're not going to introduce this level of
recursive confusion to the mount table handling.
Please give it a rest. We're not changing the mount table for you.
cgf
--
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:[~2011-07-28 11:22 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-25 12:30 Schwarz, Konrad
2011-07-25 14:01 ` Corinna Vinschen
2011-07-27 8:15 ` Schwarz, Konrad
2011-07-27 8:35 ` Schwarz, Konrad
2011-07-27 9:41 ` Corinna Vinschen
2011-07-27 11:19 ` Christopher Faylor
2011-07-28 8:18 ` Schwarz, Konrad
2011-07-28 11:22 ` Christopher Faylor [this message]
2011-07-29 7:46 ` Schwarz, Konrad
2011-07-29 9:21 ` Corinna Vinschen
2011-07-29 13:34 ` Schwarz, Konrad
2011-07-29 20:16 ` Corinna Vinschen
2011-07-30 4:53 ` Christopher Faylor
2011-07-30 8:18 ` Corinna Vinschen
2011-08-01 13:10 ` Nellis, Kenneth
2011-08-01 13:22 ` Christopher Faylor
2011-08-06 23:53 ` pb w/ cygpath -w /dev/sdXY (was Re: Device names in /proc/mounts) Cyrille Lefevre
2011-08-07 11:38 ` Corinna Vinschen
2012-09-13 16:27 ` associating volume labels with drive letters Nellis, Kenneth
2012-09-26 6:22 ` Mark O'Keefe
2012-09-26 13:43 ` Nellis, Kenneth
2012-10-19 18:45 ` Nellis, Kenneth
2012-10-19 18:52 ` Corinna Vinschen
2011-07-29 21:28 ` Device names in /proc/mounts Buchbinder, Barry (NIH/NIAID) [E]
2011-07-25 15:07 ` Christopher Faylor
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=20110728112154.GB16913@ednor.casa.cgf.cx \
--to=cgf-use-the-mailinglist-please@cygwin.com \
--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).