>> Now, trying to document all of the architecture-specific details in >> the man page is difficult, and would probably be confusing to the >> reader. But, a warning to the reader is probably in order. I've added >> the following text below the structure definition: >> >> Note: the order of fields in the stat structure varies somewhat >> across architectures. In addition, the definition above does >> not show the padding bytes that may be present between some >> fields on various architectures. Consult the the glibc and >> kernel source code if you need to know the details. >> >> Seem okay to you? > I do appreciate your point. And I agree it is very valid. Man page is > not and should not become an overloaded document with all the platform > specific caveats. But I also see it valuable to clearly explain where > the document is not absolutely precise and what sources should be > further consulted for the details. > > Your proposed change looks perfect to me. > > Thank you very much for you time! Your welcome. Thanks for the report. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/ -- 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
