From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from smtp-out-no.shaw.ca (smtp-out-no.shaw.ca [64.59.134.12]) by sourceware.org (Postfix) with ESMTPS id 754813857C64 for ; Fri, 24 Jul 2020 16:26:05 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.3.2 sourceware.org 754813857C64 Authentication-Results: sourceware.org; dmarc=none (p=none dis=none) header.from=SystematicSw.ab.ca Authentication-Results: sourceware.org; spf=none smtp.mailfrom=brian.inglis@systematicsw.ab.ca Received: from [192.168.1.104] ([24.64.172.44]) by shaw.ca with ESMTP id z0WIjovOT62brz0WJjdyfw; Fri, 24 Jul 2020 10:26:04 -0600 X-Authority-Analysis: v=2.3 cv=LKf9vKe9 c=1 sm=1 tr=0 a=kiZT5GMN3KAWqtYcXc+/4Q==:117 a=kiZT5GMN3KAWqtYcXc+/4Q==:17 a=IkcTkHD0fZMA:10 a=jChkm-x5hCMFubTIiR0A:9 a=QEXdDO2ut3YA:10 Reply-To: cygwin@cygwin.com Subject: Re: Relating device names in /dev/ to drive letters in Windows. To: cygwin@cygwin.com References: From: Brian Inglis Autocrypt: addr=Brian.Inglis@SystematicSw.ab.ca; prefer-encrypt=mutual; keydata= mDMEXopx8xYJKwYBBAHaRw8BAQdAnCK0qv/xwUCCZQoA9BHRYpstERrspfT0NkUWQVuoePa0 LkJyaWFuIEluZ2xpcyA8QnJpYW4uSW5nbGlzQFN5c3RlbWF0aWNTdy5hYi5jYT6IlgQTFggA PhYhBMM5/lbU970GBS2bZB62lxu92I8YBQJeinHzAhsDBQkJZgGABQsJCAcCBhUKCQgLAgQW AgMBAh4BAheAAAoJEB62lxu92I8Y0ioBAI8xrggNxziAVmr+Xm6nnyjoujMqWcq3oEhlYGAO WacZAQDFtdDx2koSVSoOmfaOyRTbIWSf9/Cjai29060fsmdsDLg4BF6KcfMSCisGAQQBl1UB BQEBB0Awv8kHI2PaEgViDqzbnoe8B9KMHoBZLS92HdC7ZPh8HQMBCAeIfgQYFggAJhYhBMM5 /lbU970GBS2bZB62lxu92I8YBQJeinHzAhsMBQkJZgGAAAoJEB62lxu92I8YZwUBAJw/74rF IyaSsGI7ewCdCy88Lce/kdwX7zGwid+f8NZ3AQC/ezTFFi5obXnyMxZJN464nPXiggtT9gN5 RSyTY8X+AQ== Organization: Systematic Software Message-ID: <5e6fd378-7800-4422-5f63-5d6dc0796029@SystematicSw.ab.ca> Date: Fri, 24 Jul 2020 10:26:02 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:68.0) Gecko/20100101 Thunderbird/68.10.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-CA Content-Transfer-Encoding: 7bit X-CMAE-Envelope: MS4wfHlaSpyR0DeRMahL7WOTJy6u6QnJi8Q9LTLpESV1mfxTvtdoAVMAFwUfvmbGoFSoAF007X0PYbQbNenM6HHMr41yAZwAIe7iibjIaatQoTckBBdesXNg D4Dz9Ui57LPp8xKTqh/0/9fNhKcQyO5iZ17KLESnUT/z/QR7I3stQZLWEMxOjZALD50GZovy7dzvcw== X-Spam-Status: No, score=-8.1 required=5.0 tests=BAYES_00, KAM_DMARC_STATUS, KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_LOW, RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL, SPF_HELO_NONE, SPF_NONE, TXREP autolearn=no autolearn_force=no version=3.4.2 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on server2.sourceware.org X-BeenThere: cygwin@cygwin.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: General Cygwin discussions and problem reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 24 Jul 2020 16:26:06 -0000 On 2020-07-23 03:36, Hamish McIntyre-Bhatty via Cygwin wrote: > 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? $ cygcheck -p blkid Found 17 matches for blkid .htaccess - libblkid-devel-2.32.1-1 - libblkid-devel: Block device ID library (development) libblkid-devel-2.33.1-1 - libblkid-devel: Block device ID library (development) libblkid-devel-2.33.1-2 - libblkid-devel: Block device ID library (development) .htaccess - libblkid1-2.32.1-1 - libblkid1: Block device ID library (runtime) libblkid1-2.33.1-1 - libblkid1: Block device ID library (runtime) libblkid1-2.33.1-2 - libblkid1: Block device ID library (runtime) util-linux-debuginfo-2.32.1-1 - util-linux-debuginfo: Debug info for util-linux util-linux-debuginfo-2.33.1-1 - util-linux-debuginfo: Debug info for util-linux util-linux-debuginfo-2.33.1-2 - util-linux-debuginfo: Debug info for util-linux util-linux-2.32.1-1-src - util-linux-src: Collection of basic system utilities (source) util-linux-2.33.1-1-src - util-linux-src: Collection of basic system utilities (source) util-linux-2.33.1-2-src - util-linux-src: Collection of basic system utilities (source) util-linux-2.32.1-1 - util-linux: Collection of basic system utilities util-linux-2.33.1-1 - util-linux: Collection of basic system utilities util-linux-2.33.1-2 - util-linux: Collection of basic system utilities $ which blkid /sbin/blkid $ cygcheck -f /sbin/blkid util-linux-2.33.1-2 Everyone has util-linux installed as it is in the Base category. Someone has to provide the system interfaces in a POSIX compliant manner or at least similar to Linux and BSD to port the libraries. You can find most info under /proc/registry/ (even /proc/registry/HKEY_PERFORMANCE_DATA/{@,Costly,Global}/ - explore with ls and regtool) and there are Windows dynamic system objects under /proc/sys/ e.g. /proc/sys/ Device/ and /proc/sys/DosDevices/Global/ (explore with ls and od/xxd). Note: You need an elevated admin shell to use most device tools and see a lot of /proc/sys/. Hack at it, sir! -- Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada This email may be disturbing to some readers as it contains too much technical detail. Reader discretion is advised. [Data in IEC units and prefixes, physical quantities in SI.]