Util-Linux package development
 help / color / mirror / Atom feed
From: David O'Brien <daobrien@redhat.com>
To: util-linux@vger.kernel.org
Subject: Bug in lsblk command or man page?
Date: Thu, 24 Dec 2020 11:14:04 +1000	[thread overview]
Message-ID: <ed3332cf-794f-b0d3-caca-16fb65dfd5ac@redhat.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 1050 bytes --]

I don't know if this is expected or not, but it seems very odd:

# lsblk -o=UUID /stratis/labpool/labfs
lsblk: unknown column: =UUID

[root@serverb ~]# lsblk -o UUID /stratis/labpool/labfs
UUID
0118efb8-66fe-406a-837c-725961bdad4d

[root@serverb ~]# lsblk --output=UUID /stratis/labpool/labfs
UUID
0118efb8-66fe-406a-837c-725961bdad4d


From the man(8) page:
-o, --output list
              Specify which output columns to print.  Use --help to get
              a list of all supported columns.  The columns may affect
              tree-like output.  The default is to use tree for the
              column 'NAME' (see also --tree).

              The default list of columns may be extended if list is
              specified in the format +list (e.g., lsblk -o +UUID).

There is no mention of "=" being required, causing failures, etc. I found this quite frustrating.

I'm on Fedora 32.

Thanks.
-- 
David
Introvert/Unclubbable/Cool

Red Hat's core values are freedom, courage, commitment, and accountability.


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]

             reply	other threads:[~2020-12-24  1:15 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-24  1:14 David O'Brien [this message]
2021-01-05 10:27 ` Bug in lsblk command or man page? Karel Zak
2021-01-05 14:08   ` David O'Brien
2021-01-05 17:05     ` Bill Unruh
2021-01-06 12:03       ` Karel Zak

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=ed3332cf-794f-b0d3-caca-16fb65dfd5ac@redhat.com \
    --to=daobrien@redhat.com \
    --cc=util-linux@vger.kernel.org \
    /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