Hi, Greg Wooledge wrote: > > unicorn:~$ sudo lsblk -o +UUID
David Wright wrote: > You shouldn't require root for either blkid or lsblk, > though the former needs a path, and does include a > warning that the information may be read from cache. This depends highly on the age of the system. On Debian 8 you don't get much UUID from the system disks without the permission to read them. On Debian 10 lsblk seems to depend mostly on udev's assessment. > > ├─sda1 8:1 0 260M 0 part /boot/efi 4C30-7972 The universe must be small where this FAT UUID is unique. > One question about lsblk, though: why does it always > use the xterm width to format the output, regardless of > whether you redirect the output and the value of COLUMNS. For me on Debian 10 it does not care about the terminal size. If i request a few sometimes lengthy fields from lsblk -h i get 206 bytes per line (plus newline) printed to stdout: $ lsblk -o NAME,KNAME,FSTYPE,LABEL,UUID,PARTTYPE,PARTLABEL,PARTUUID,MODEL,SIZE | head -1 | wc -c 207 In the newest version of the man page https://sources.debian.org/src/util-linux/2.37.2-4/misc-utils/lsblk.8/#L179 i see an option which is not in the Debian 10 man page: \fB\-w\fP, \fB\-\-width\fP \fInumber\fP .RS 4 Specifies output width as a number of characters. The default is the number of the terminal columns, and if not executed on a terminal, then output width is not restricted at all by default. This option also forces \fBlsblk\fP to assume that terminal control characters and unsafe characters are not allowed. The expected use\-case is for example when \fBlsblk\fP is used by the \fBwatch\fP(1) command. Have a nice day :) Thomas
