From: Karel Zak Date: Wed, 25 Feb 2026 10:58:16 +0000 (+0100) Subject: hexdump: (man) document byte order dependency in multi-byte formats X-Git-Tag: v2.43-devel~39 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=cfacc42d7e877966590ffc6a04a52675c920dbb2;p=thirdparty%2Futil-linux.git hexdump: (man) document byte order dependency in multi-byte formats Addresses: https://github.com/util-linux/util-linux/issues/4072 Signed-off-by: Karel Zak --- diff --git a/text-utils/hexdump.1.adoc b/text-utils/hexdump.1.adoc index 77ab798cf..612bfcca0 100644 --- a/text-utils/hexdump.1.adoc +++ b/text-utils/hexdump.1.adoc @@ -217,6 +217,8 @@ Further output by such format strings is replaced by an equivalent number of spa If no format strings are specified, the default display is very similar to the *-x* output format (the *-x* option causes more space to be used between format units than in the default output). +Note that the default format and the *-x*, *-d*, and *-o* options use multi-byte format units that are displayed in the system's native byte order (endianness). This means the same input may produce different output on little-endian (e.g., x86, ARM64) and big-endian (e.g., s390x) systems. For byte-order independent output, use single-byte formats such as *-b*, *-c*, *-C*, or *-X*. + == EXIT STATUS *hexdump* exits 0 on success and > 0 if an error occurred.