Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #204227
| From | Bob McGowan <ramjr0915@gmail.com> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: Taming the "lsblk" command |
| Date | 2019-01-09 08:00 +0100 |
| Message-ID | <xeg0i-7l8-9@gated-at.bofh.it> (permalink) |
| References | <xe6DD-1fQ-13@gated-at.bofh.it> <xeehP-6rN-5@gated-at.bofh.it> <xefQB-7ht-3@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On 1/8/19 10:47 PM, Felix Miata wrote: > 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 What was the content of the script you piped to? Its design would possibly explain this. Bob
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Taming the "lsblk" command Richard Owlett <rowlett@cloud85.net> - 2019-01-08 22:00 +0100
Re: Taming the "lsblk" command Reco <recoverym4n@enotuniq.net> - 2019-01-08 22:20 +0100
Re: Taming the "lsblk" command Jude DaShiell <jdashiel@panix.com> - 2019-01-09 06:10 +0100
Re: Taming the "lsblk" command Richard Owlett <rowlett@cloud85.net> - 2019-01-09 07:30 +0100
Re: Taming the "lsblk" command Felix Miata <mrmazda@earthlink.net> - 2019-01-09 07:50 +0100
Re: Taming the "lsblk" command Bob McGowan <ramjr0915@gmail.com> - 2019-01-09 08:00 +0100
Re: Taming the "lsblk" command Jude DaShiell <jdashiel@panix.com> - 2019-01-09 12:50 +0100
Re: Taming the "lsblk" command Felix Miata <mrmazda@earthlink.net> - 2019-01-09 14:00 +0100
Re: Taming the "lsblk" command David Wright <deblis@lionunicorn.co.uk> - 2019-01-09 15:30 +0100
Re: Taming the "lsblk" command Richard Hector <richard@walnut.gen.nz> - 2019-01-09 09:10 +0100
Re: Taming the "lsblk" command rhkramer@gmail.com - 2019-01-09 14:00 +0100
Re: Taming the "lsblk" command Curt <curty@free.fr> - 2019-01-09 15:00 +0100
Re: Taming the "lsblk" command David Wright <deblis@lionunicorn.co.uk> - 2019-01-09 15:20 +0100
Re: Taming the "lsblk" command Richard Owlett <rowlett@cloud85.net> - 2019-01-09 16:40 +0100
Re: Taming the "lsblk" command Curt <curty@free.fr> - 2019-01-09 18:00 +0100
Re: Taming the "lsblk" command mick crane <mick.crane@gmail.com> - 2019-01-09 17:20 +0100
Re: Taming the "lsblk" command David Wright <deblis@lionunicorn.co.uk> - 2019-01-09 20:10 +0100
Re: Taming the "lsblk" command Michael Stone <mstone@debian.org> - 2019-01-09 22:40 +0100
Re: Taming the "lsblk" command David Wright <deblis@lionunicorn.co.uk> - 2019-01-10 02:00 +0100
Re: Taming the "lsblk" command Michael Stone <mstone@debian.org> - 2019-01-10 13:50 +0100
csiph-web