[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Taming the "lsblk" command



On Wed, 9 Jan 2019, Felix Miata wrote:

> Date: Wed, 9 Jan 2019 01:47:24
> From: Felix Miata <mrmazda@earthlink.net>
> To: debian-user@lists.debian.org
> Subject: Re: Taming the "lsblk" command
> Resent-Date: Wed,  9 Jan 2019 06:47:41 +0000 (UTC)
> Resent-From: debian-user@lists.debian.org
>
> Jude DaShiell composed on 2019-01-09 00:04 (UTC-0500):
>
> > lsblk -l -o name,label | sort | script
>
> I tried exactly that on Buster multiple times, and always get the following:
>
> root@gb250:~# NAME  LABEL
> bash: NAME: command not found
> root@gb250:~# sda
> bash: sda: command not found
> root@gb250:~# sda10 k25p10deb10
> bash: sda10: command not found
> root@gb250:~# sda11 k25p11deb10fat
> bash: sda11: command not found
> root@gb250:~# sda12 k25p12Ubionic
> bash: sda12: command not found
> root@gb250:~# sda13
> bash: sda13: command not found
> root@gb250:~# sda14
> bash: sda14: command not found
> root@gb250:~# sda15
> bash: sda15: command not found
> root@gb250:~# sda16
> bash: sda16: command not found
> root@gb250:~# sda1  K25P01ESP
> bash: sda1: command not found
> root@gb250:~# sda2  k25p02swap
> bash: sda2: command not found
> root@gb250:~# sda3  k25p03res
> bash: sda3: command not found
> root@gb250:~# sda4  k25p04usrlcl
> bash: sda4: command not found
> root@gb250:~# sda5  k25p05home
> bash: sda5: command not found
> root@gb250:~# sda6  k25p06pub
> bash: sda6: command not found
> root@gb250:~# sda7  k25p07stw
> bash: sda7: command not found
> root@gb250:~# sda8  k25p08s150
> bash: sda8: command not found
> root@gb250:~# sda9  k25p09s151
> bash: sda9: command not found
> root@gb250:~# sr0
> bash: sr0: command not found
> root@gb250:~# exit
>
That can happen if bash doesn't find sort in its default binary
directory.  Could be pointing bash directly at sort will clear the
command not found error out of the output.

-- 


Reply to: