From: Pádraig Brady
Date: Fri, 27 Jun 2025 14:02:50 +0000 (+0100) Subject: doc: cksum: --check: improve supported formats description X-Git-Tag: v9.8~286 X-Git-Url: http://git.ipfire.org/?a=commitdiff_plain;h=7c2729cb5821ce3a96dfe064a529218e10215368;p=thirdparty%2Fcoreutils.git doc: cksum: --check: improve supported formats description * doc/coreutils.texi (cksum common options): Reorder and tweak the info to make it clearer that --check does not support the legacy crc output from the cksum command. Reported at https://bugs.debian.org/1108363 --- diff --git a/doc/coreutils.texi b/doc/coreutils.texi index 865ceff050..e05d3faf74 100644 --- a/doc/coreutils.texi +++ b/doc/coreutils.texi @@ -4204,13 +4204,17 @@ for reading standard input when standard input is a terminal. Read file names and checksum information (not data) from each @var{file} (or from standard input if no @var{file} was specified) and report whether the checksums match the contents of the named files. -The input to this mode is usually the output of -a prior, checksum-generating run of the command. - -Three input formats are supported. Either the default output -format described above, the @option{--tag} output format, -or the BSD reversed mode format which is similar to the default mode, +The input to this mode is usually the output of a prior, +checksum-generating run of the command. However the +@command{cksum} command does not support @option{--check} +with the legacy output format from the @samp{sysv}, @samp{bsd}, +@samp{crc} or @samp{crc32b} algorithms. + +Three input formats are supported. Either the "untagged" output format, +the "tagged" output format, or the BSD reversed mode format +which is similar to the "untagged" output format but doesn't use a character to distinguish binary and text modes. +@xref{cksum output modes} for details of these formats. For the @command{cksum} command, the @option{--check} option supports auto-detecting the digest algorithm to use, @@ -4236,8 +4240,6 @@ If any listed file cannot be opened or read, if any valid line has a checksum inconsistent with the associated file, or if no valid line is found, @command{cksum} exits with nonzero status. Otherwise, it exits successfully. -The @command{cksum} command does not support @option{--check} -with the older @samp{sysv}, @samp{bsd}, @samp{crc} or @samp{crc32b} algorithms. @item --ignore-missing @opindex --ignore-missing