From: Hamish McIntyre-Bhatty <hamishmb@live.co.uk>
To: The Cygwin Mailing List <cygwin@cygwin.com>
Subject: Re: Relating device names in /dev/ to drive letters in Windows.
Date: Thu, 23 Jul 2020 12:29:02 +0100 [thread overview]
Message-ID: <AM0PR05MB4898B9298AE51474FA513B4FE7760@AM0PR05MB4898.eurprd05.prod.outlook.com> (raw)
In-Reply-To: <AM0PR05MB4898BE767E2785150F88507BE7760@AM0PR05MB4898.eurprd05.prod.outlook.com>
[-- Attachment #1.1.1: Type: text/plain, Size: 1217 bytes --]
On 23/07/2020 10:36, Hamish McIntyre-Bhatty wrote:
> Hi all,
>
> I have noticed that after plugging in a USB drive, device files appear
> in /dev that correlate to the partitions on the drive.
>
> This is great because it means things like ddrescue can work in Cygwin,
> but I'm not yet sure how to relate these to the drives Windows sees.
> None of the standard Linux tools I use to gather system information
> (lsblk, blkid, lshw) seem to be available on Cygwin. I'm guessing this
> is because they won't work because there's no kernel or low level
> hardware access or something like that. Does anyone know how to do this?
>
> Hamish
>
Just replying to note that I found
https://www.cygwin.com/cygwin-ug-net/using-specialnames.html, which
covers some of my question.
However, some things (like build in CD/DVD drives) don't show up in
/proc/partitions, so that's still not ideal. Also is there any way I can
get Make/Model and similar information from Cygwin?
I know I can use WMIC or PowerShell for this, but I'm assuming having a
Cygwin package depending on those is a big no-no, even as an alternate
code path if they are detected?
Sorry for all the newbie questions!
Hamish
[-- Attachment #1.1.2: 0x87B761FE07F548D6.asc --]
[-- Type: application/pgp-keys, Size: 3235 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-23 11:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-23 9:36 Hamish McIntyre-Bhatty
2020-07-23 11:29 ` Hamish McIntyre-Bhatty [this message]
2020-07-24 8:45 ` Corinna Vinschen
2020-07-24 16:26 ` Brian Inglis
2020-07-27 11:24 Hamish McIntyre-Bhatty
2020-07-27 12:44 ` Corinna Vinschen
2020-07-27 13:10 ` Brian Inglis
[not found] <mailman.96674.1595867913.8982.cygwin@cygwin.com>
2020-07-28 21:36 ` Hamish McIntyre-Bhatty
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=AM0PR05MB4898B9298AE51474FA513B4FE7760@AM0PR05MB4898.eurprd05.prod.outlook.com \
--to=hamishmb@live.co.uk \
--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).