On 4/19/20 8:48 AM, Helge Kreutzmann wrote: > > Dear manpages maintainers. > the manpage-l10n project maintains a large number of translations of > man pages both from a large variety of sources (including manpages) as > well for a large variety of target languages. > > During their work translators notice different possible issues in the > original (english) man pages. Sometiems 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 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 translate 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. As requested, each > issue is sent in an unique mail for easier tracking on your side. If > future reports should use another channel, please let me know. > > ** > > Inconsistent spelling of multithreaded vs. multi-threaded > > a) > "Prior to Linux 2.6.28, SELinux did not allow threads within a multi-threaded " > "process to set their security context via this node as it would yield an " > "inconsistency among the security contexts of the threads sharing the same " > "memory space. Since Linux 2.6.28, SELinux lifted this restriction and began " > "supporting \"set\" operations for threads within a multithreaded process if " > "the new security context is bounded by the old security context, where the " > "bounded relation is defined in policy and guarantees that the new security " Thanks. Fixed. > b) > "In SELinux, this file is used to get the security context of a process. " > "Prior to Linux 2.6.11, this file could not be used to set the security " > "context (a write was always denied), since SELinux limited process security " > "transitions to B<execve>(2) (see the description of I</proc/[pid]/attr/" > "exec>, below). Since Linux 2.6.11, SELinux lifted this restriction and " > "began supporting \"set\" operations via writes to this node if authorized by " > "policy, although use of this operation is only suitable for applications " > What is "b)" about? Thanks, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/
