From: Bill Unruh <unruh@physics.ubc.ca>
To: David O'Brien <daobrien@redhat.com>
Cc: Karel Zak <kzak@redhat.com>, util-linux@vger.kernel.org
Subject: Re: Bug in lsblk command or man page?
Date: Tue, 5 Jan 2021 09:05:48 -0800 (PST) [thread overview]
Message-ID: <alpine.LMD.2.11.2101050900440.19402@physics.ubc.ca> (raw)
In-Reply-To: <c04e1ccc-4053-bb3e-3479-512f263f679e@redhat.com>
Of course it being "common" does NOT mean that everyone knows the convention,
especially people new to Linux. And is NOT an excuse for the man page being
wrong. So, yes, you should be explicit about it, and not be wrong about it in
the man page.
It is -o list and --output=list
On Wed, 6 Jan 2021, David O'Brien wrote:
> On 1/5/21 8:27 PM, Karel Zak wrote:
>> On Thu, Dec 24, 2020 at 11:14:04AM +1000, David O'Brien wrote:
>>> 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.
>>>
>>
>> This is common getopt_long() behavior where equal sign is usable only for
>> long options (and sometimes for optional arguments).
>>
>> lsblk -o UUID
>> lsblk --output UUID
>> lsblk --output=UUID
>>
>> this is how "=" works in almost all commands and I don't see reason
>> why we need to be explicit about it for "lsblk -o".
>>
>> Karel
>>
> ok. If it's common and expected that's fine. I don't spend a lot of time with this class/type of command and it was just
> new to me and seemed odd.
>
> cheers
> --
> David
> Introvert/Unclubbable/Cool
>
> Red Hat's core values are freedom, courage, commitment, and accountability.
>
>
next prev parent reply other threads:[~2021-01-05 17:12 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 1:14 Bug in lsblk command or man page? David O'Brien
2021-01-05 10:27 ` Karel Zak
2021-01-05 14:08 ` David O'Brien
2021-01-05 17:05 ` Bill Unruh [this message]
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=alpine.LMD.2.11.2101050900440.19402@physics.ubc.ca \
--to=unruh@physics.ubc.ca \
--cc=daobrien@redhat.com \
--cc=kzak@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