From: "Buchbinder, Barry (NIH/NIAID) [E]" <BBuchbinder@niaid.nih.gov>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>,
"'Schwarz, Konrad'" <konrad.schwarz@siemens.com>
Subject: RE: Device names in /proc/mounts
Date: Fri, 29 Jul 2011 21:28:00 -0000 [thread overview]
Message-ID: <0105D5C1E0353146B1B222348B0411A20A1A123DF3@NIHMLBX02.nih.gov> (raw)
In-Reply-To: <9B10FEAACF062F48A095880A451FF05903819B331A@DEMCHP99E84MSX.ww902.siemens.net>
Schwarz, Konrad sent the following at Friday, July 29, 2011 9:34 AM
>> > Given a volume label, how does one figure out where the
>> corresponding
>> > volume has been mounted into the Cygwin namespace?
>>
>> We're not mounting volumes, we're mounting Win32 paths.
>> There is no direct correspondence between volumes and Cygwin
>> mount points.
>
>When a person inserts removable media (USB memory stick, optical disk,
>...), Windows assigns a more-or-less random drive letter. Cygwin
>automatically makes this drive letter available under /cygdrive/ (or
>whatever the user has renamed /cygdrive to).
>
>Given a (unique) volume label or disk UUID, blk_id(8) on both Linux and
>Cygwin tells you the disk and partition in /dev/sdXY format.
>
>In Linux, you can look up the mount point for device /dev/sdXY in
>/proc/mounts or in the output of mount(8). Thus, given a volume label,
>you can figure out where to access the files on the volume.
>
>How do you do that in Cygwin?
One could use a windows tool to get the volume. Here is a possible start.
/c> echo '
n' | cmd /c label h:
Volume in drive H: is CIFS.HOMEDIR
Volume label (ENTER for none)?
Delete current volume label (Y/N)? n
/c>
Good luck.
- Barry
Disclaimer: Statements made herein are not made on behalf of NIAID.
--
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-29 21:28 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
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 ` Buchbinder, Barry (NIH/NIAID) [E] [this message]
2011-07-25 15:07 ` Device names in /proc/mounts 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=0105D5C1E0353146B1B222348B0411A20A1A123DF3@NIHMLBX02.nih.gov \
--to=bbuchbinder@niaid.nih.gov \
--cc=cygwin@cygwin.com \
--cc=konrad.schwarz@siemens.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).