When describing e_ident, most of the EI_xxx defines mention the exact byte number. This is useful when manually hacking an ELF with a hex editor. However, the last few fields don't do this which means you have to count things up yourself. Add a single world to each so you don't have to do that. Signed-off-by: Mike Frysinger <vapier@xxxxxxxxxx> --- man5/elf.5 | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/man5/elf.5 b/man5/elf.5 index 8427244..e08987d 100644 --- a/man5/elf.5 +++ b/man5/elf.5 @@ -241,7 +241,7 @@ Two's complement, big-endian. .TP .PD 0 .BR EI_VERSION -The version number of the ELF specification: +The seventh byte is the version number of the ELF specification: .\" .Bl -tag -width "EV_CURRENT" -compact .RS 12 .TP 14 @@ -255,7 +255,7 @@ Current version. .\".El .TP .BR EI_OSABI -This byte identifies the operating system +The eighth byte identifies the operating system and ABI to which the object is targeted. Some fields in other ELF structures have flags and values that have platform-specific meanings; @@ -332,7 +332,7 @@ Stand-alone (embedded) ABI. .RE .TP .BR EI_ABIVERSION -This byte identifies the version of the ABI +The ninth byte identifies the version of the ABI to which the object is targeted. This field is used to distinguish among incompatible versions of an ABI. The interpretation of this version number -- 1.8.1.2 -- To unsubscribe from this list: send the line "unsubscribe linux-man" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
