Matched the documentation of --checksums to the implementation in live-boot

2 files changed, 4 insertions, 4 deletions

diff --git a/manpages/en/lb_config.1 b/manpages/en/lb_config.1
index 2c19a7521..de415dbc8 100644
--- a/manpages/en/lb_config.1
+++ b/manpages/en/lb_config.1
@@ -51,7 +51,7 @@
 .br
 	[\fB\-\-cache\-stages\fR \fISTAGE\fR|\fI"STAGES"\fR]
 .br
-	[\fB\-\-checksums\fR md5|sha1|sha256|none]
+	[\fB\-\-checksums\fR md5|sha1|sha224|sha256|sha384|sha512|none]
 .br
 	[\fB\-\-color]
 .br
@@ -289,8 +289,8 @@ defines if downloaded package indices and lists should be cached which is false
 defines if downloaded packages files should be cached which is true by default. Disabling it does save space consumption in your build directory, but remember that you will cause much unnecessary traffic if you do a couple of rebuilds. In general you should always leave it true, however, in some particular rare build setups, it can be faster to refetch packages from the local network mirror rather than to utilize the local disk.
 .IP "\fB\-\-cache\-stages\fR true|false|\fISTAGE\fR|""\fISTAGES\fR""" 4
 sets which stages should be cached. By default set to bootstrap. As an exception to the normal stage names, also rootfs can be used here which does only cache the generated root filesystem in filesystem.{dir,ext*,squashfs}. This is useful during development if you want to rebuild the binary stage but not regenerate the root filesystem all the time.
-.IP "\fB\-\-checksums\fR md5|sha1|sha256|none" 4
-defines if the binary image should contain a file called md5sums.txt, sha1sums.txt and/or sha256sums.txt. These lists all files on the image together with their checksums. This in turn can be used by live\-boot's built\-in integrity\-check to verify the medium if specified at boot prompt. In general, this should not be false and is an important feature of live system released to the public. However, during development of very big images it can save some time by not calculating the checksums.
+.IP "\fB\-\-checksums\fR md5|sha1|sha224|sha256|sha384|sha512|none" 4
+defines if the binary image should contain a file called XXXsums.txt, where XXX is one of the mentioned checksum types. This file lists all files on the image together with their checksums. This in turn can be used by \fIlive\-boot\fR(7)'s built\-in integrity\-check to verify the medium if specified at boot prompt. In general, this should not be none and is an important feature of live system released to the public. However, during development of very big images it can save some time by not calculating the checksums.
 .IP "\fB\-\-color\fR" 4
 turn on color in the messages.
 .IP "\fB\-\-compression\fR bzip2|gzip|lzip|none" 4
diff --git a/scripts/build/config b/scripts/build/config
index 1a5b8cdf8..6c23cc6a0 100755
--- a/scripts/build/config
+++ b/scripts/build/config
@@ -38,7 +38,7 @@ USAGE="${PROGRAM}   [--apt apt|aptitude]\n\
 \t    [--cache-indices true|false]\n\
 \t    [--cache-packages true|false]\n\
 \t    [--cache-stages STAGE|\"STAGES\"]\n\
-\t    [--checksums md5|sha1|sha256|sha512|none]\n\
+\t    [--checksums md5|sha1|sha224|sha256|sha384|sha512|none]\n\
 \t    [--color]\n\
 \t    [--compression bzip2|gzip|lzip|xz|none]\n\
 \t    [--config GIT_URL::GIT_BRANCH]\n\