On 7/6/20 12:14 PM, Helge Kreutzmann wrote: > Dear linux man page maintainer, > the manpage-l10n project maintains a large number of translations of > man pages both from a large variety of sources (including linux man > pages) as well for a large variety of target languages. > > During their work translators notice different possible issues in the > original (english) man pages. Sometimes this is a straightforward > typo, sometimes a hard to read sentence, sometimes this is a > convention not held up and sometimes we simply do not understand the > original. > > We use several distributions as sources and update regularly (at > least every 2 month). This means we are fairly recent (some > distributions like archlinux also update frequently) but might miss > the latest upstream version once in a while, so the error might be > already fixed. We apologize and ask you to close the issue immediately > if this should be the case, but given the huge volume of projects and > the very limited number of volunteers we are not able to double check > each and every issue. > > Secondly we translators see the manpages in the neutral po format, > i.e. converted and harmonized, but not the original source (be it man, > groff, xml or other). So we cannot provide a true patch (where > possible), but only an approximation which you need to convert into > your source format. > > Finally the issues I'm reporting have accumulated over time and are > not always discovered by me, so sometimes my description of the > problem my be a bit limited - do not hesitate to ask so we can clarify > them. > > I'm now reporting the errors for your project. If future reports > should use another channel, please let me know. > > ** > > Man page: mmap.2 > Issue: and in order → in order > > "For example, suppose that thread A looks through I</proc/E<lt>pidE<gt>/maps> " > "and in order to locate an unused address range that it can map using " > "B<MAP_FIXED>, while thread B simultaneously acquires part or all of that " > "same address range. When thread A subsequently employs B<mmap(MAP_FIXED)>, " > "it will effectively clobber the mapping that thread B created. In this " > "scenario, thread B need not create a mapping directly; simply making a " > "library call that, internally, uses B<dlopen>(3) to load some other shared " > "library, will suffice. The B<dlopen>(3) call will map the library into the " > "process's address space. Furthermore, almost any library call may be " > "implemented in a way that adds memory mappings to the address space, either " > "with this technique, or by simply allocating memory. Examples include " > "B<brk>(2), B<malloc>(3), B<pthread_create>(3), and the PAM libraries E<.UR " > "http://www.linux-pam.org> E<.UE .>" Thanks. Fixed. Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
