The `blkid` tool does not write anything to the probed device, so seeing "overwrite" in the usage text was somewhat disconcerting. Signed-off-by: Benno Schulenberg <bensberg@xxxxxxxxxx> --- misc-utils/blkid.c | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/misc-utils/blkid.c b/misc-utils/blkid.c index d5fe4f1fa..63e61b5fa 100644 --- a/misc-utils/blkid.c +++ b/misc-utils/blkid.c @@ -96,7 +96,7 @@ static void __attribute__((__noreturn__)) usage(void) fputs(_( " -p, --probe low-level superblocks probing (bypass cache)\n"), out); fputs(_( " -i, --info gather information about I/O limits\n"), out); fputs(_( " -H, --hint <value> set hint for probing function\n"), out); - fputs(_( " -S, --size <size> overwrite device size\n"), out); + fputs(_( " -S, --size <size> override device size\n"), out); fputs(_( " -O, --offset <offset> probe at the given offset\n"), out); fputs(_( " -u, --usages <list> filter by \"usage\" (e.g. -u filesystem,raid)\n"), out); fputs(_( " -n, --match-types <list> filter by filesystem type (e.g. -n vfat,ext3)\n"), out); -- 2.48.1
