Improve lsblk output #16
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Please compare the following outputs: ❯ lsblk /dev/sda NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS sda 8:0 0 1,8T 0 disk └─sda1 8:1 0 1,8T 0 part /media/jkirk/Transcend ❯ lsblk -f /dev/sda NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS sda └─sda1 ntfs Transcend 96EC52DAEC52SNIP 102,7G 94% /media/jkirk/Transcend ❯ lsblk -o +LABEL,PARTLABEL,UUID,FSTYPE,SERIAL /dev/sda NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS LABEL PARTLABEL UUID FSTYPE SERIAL sda 8:0 0 1,8T 0 disk S36VJ9EGB0SNIP └─sda1 8:1 0 1,8T 0 part /media/jkirk/Transcend Transcend 96EC52DAEC52SNIP ntfs Option `-f, --fs` outputs info about filesystems. This option is equivalent to -o NAME,FSTYPE,FSVER,LABEL,UUID,FSAVAIL,FSUSE%,MOUNTPOINTS. FSAVAIL and FSUE% could be added to my custom output list, but on a Grml system the devices are usually not mounted and even if they are, we have already capture the df output. IMHO, PARTLABEL and SERIAL are more interesting in this regard.
zeha
approved these changes
Sep 1, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Please compare the following outputs:
❯ lsblk /dev/sda
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 1,8T 0 disk
└─sda1 8:1 0 1,8T 0 part /media/jkirk/Transcend
❯ lsblk -f /dev/sda
NAME FSTYPE FSVER LABEL UUID FSAVAIL FSUSE% MOUNTPOINTS
sda
└─sda1 ntfs Transcend 96EC52DAEC52SNIP 102,7G 94% /media/jkirk/Transcend
❯ lsblk -o +LABEL,PARTLABEL,UUID,FSTYPE,SERIAL /dev/sda
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS LABEL PARTLABEL UUID FSTYPE SERIAL
sda 8:0 0 1,8T 0 disk S36VJ9EGB0SNIP
└─sda1 8:1 0 1,8T 0 part /media/jkirk/Transcend Transcend 96EC52DAEC52SNIP ntfs
Option
-f, --fsoutputs info about filesystems.This option is equivalent to -o NAME,FSTYPE,FSVER,LABEL,UUID,FSAVAIL,FSUSE%,MOUNTPOINTS.
FSAVAIL and FSUE% could be added to my custom output list, but on a Grml system the devices are usually not mounted and even if they are, we have already capture the df output.
IMHO, PARTLABEL and SERIAL are more interesting in this regard.