> > > changes: > > > make mmap.2 reference mincore > > > > Done, for 2.33. > > > > > explicitly state that a read-only MAP_PRIVATE is equivalent to > > > MAP_SHARED > > > > *why?* You do not explain what benefit this serves. > Because, upon reflection, it isn't immediately clear from the wording > of the page as it exists now. In particular: > > Create a private copy-on-write mapping
Umm -- we were talking about read-only mappings? > This could be interpretted as meaning "create a new mapping, even if > the file is already mapped", which isn't what people usually want, and > isn't what it does anyway.. > > > > An alternative would be to take the commented-out Linus quote > > > embedded > > > in mmap.2 which says precisely what I want and create a NOTES section > > > out of it. Let me put things another way: why should a programmer care about whether read-only mappings are done the same way internally for both MAP_SHARED and MAP_PRIVATE? Should this information change how programs are written? I can't think of a reason why it should. And therefore there seems no reason to mention it in the man page. Cheers, Michael -- Michael Kerrisk maintainer of Linux man pages Sections 2, 3, 4, 5, and 7 Want to help with man page maintenance? Grab the latest tarball at ftp://ftp.win.tue.nl/pub/linux-local/manpages/, read the HOWTOHELP file and grep the source files for 'FIXME'. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
