From: Brian Inglis <Brian.Inglis@SystematicSw.ab.ca>
To: cygwin@cygwin.com
Subject: Re: blockdev.exe is missing in util-linux. How to determine block device size in bash?
Date: Sat, 28 Nov 2020 10:04:55 -0700 [thread overview]
Message-ID: <18bf6c94-f3d1-d3da-a361-d6994472d0f3@SystematicSw.ab.ca> (raw)
In-Reply-To: <e14f4842-1e5c-ced4-2f86-778630dfb15d@gmail.com>
On 2020-11-28 01:08, Basin Ilya via Cygwin wrote:
> Actually I have nothing to add to the subject. blockdev.exe missing in
> util-linux. How to determine block device size in bash?
$ cat /proc/partitions
major minor #blocks name win-mounts
8 0 976762584 sda
8 1 16384 sda1
8 2 976744448 sda2 C:\
8 16 976762584 sdb
8 17 131072 sdb1
8 18 102400 sdb2
8 19 975482161 sdb3 D:\
8 20 577536 sdb4
8 21 465920 sdb5
8 32 0 sdc
--
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 binary units and prefixes, physical quantities in SI.]
next prev parent reply other threads:[~2020-11-28 17:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-28 8:08 Basin Ilya
2020-11-28 17:04 ` Brian Inglis [this message]
2020-12-05 9:43 ` basinilya
2020-12-07 2:59 ` Duncan Roe
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=18bf6c94-f3d1-d3da-a361-d6994472d0f3@SystematicSw.ab.ca \
--to=brian.inglis@systematicsw.ab.ca \
--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).