public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: "Nellis, Kenneth" <Kenneth.Nellis@xerox.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Subject: RE: associating volume labels with drive letters
Date: Fri, 19 Oct 2012 18:45:00 -0000	[thread overview]
Message-ID: <0D835E9B9CD07F40A48423F80D3B5A7002E69D@USA7109MB022.na.xerox.net> (raw)
In-Reply-To: <0D835E9B9CD07F40A48423F80D3B5A70022CCD@USA7109MB022.na.xerox.net>

-----Original Message-----
From: Nellis, Kenneth
From: Mark O'Keefe
> Hi,
>
> Here is a perl script which I believe should do the trick.
>
> It adds:  (for example)
>   DRIVE="C:"
> to the end of the blkid output where the drive letter matches the correct drive location.
>
> Along the same lines I've also played around with a customised version of cygwin that allows the mount
> command to use UUID's to identify the drive letter instead of hard coding into fstab.  This would be useful
> if you wanted specific drives to be mounted to specific locations without dependence on the drive letter.
>
> I haven't extensively tested this, just quickly put it together to give you the idea.
<snip>

Thanx, Mark. Works great!
--Ken Nellis
-----END Original Message-----

The following bash command line provides another way to learn the 
drive letter associated with a given label, in this case the drive 
labeled "CRUZER":

$ echo -e "list volume\nexit" | diskpart | awk '/CRUZER/ {print $3}'
G
$

--Ken Nellis

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

  reply	other threads:[~2012-10-19 18:45 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-25 12:30 Device names in /proc/mounts 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 [this message]
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=0D835E9B9CD07F40A48423F80D3B5A7002E69D@USA7109MB022.na.xerox.net \
    --to=kenneth.nellis@xerox.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).