OSDev.org

Posted: **Wed Mar 28, 2007 8:42 am**

This is only "slightly OT" as the issue in question is definitely related to OS development, but...

The following is found in the manual page for vfork(2) on my system:

Code: Select all

CONFORMING TO
       The vfork call may be a bit similar to calls with the same name  in  other
       operating  systems.  The  requirements  put  on vfork by the standards are
       weaker than those put on fork, so an implementation where the two are syn-
       onymous  is  compliant.  In  particular, the programmer cannot rely on the
       parent remaining blocked until a call of execve() or  _exit()  and  cannot
       rely on any specific behaviour w.r.t. shared memory.

Especially the "may be a bit similar to" made me laugh.

Posted: **Thu Mar 29, 2007 6:40 am**

On the subject of funny manpages:

Code: Select all

BUGS
       This manpage is confusing.

-- getopt_long manual page

Posted: **Fri Mar 30, 2007 12:44 am**

a classic for FORTRAN

Code: Select all

"The primary purpose of the DATA statement is to give names to constants; instead of referring to pi as 3.141592653589793 at every appearance, the variable PI can be given that value with a DATA statement and used instead of the longer form of the constant. This also simplifies modifying the program, should the value of pi change." —Early FORTRAN manual for Xerox Computers[8]

Posted: **Fri Mar 30, 2007 8:52 am**

http://cm.bell-labs.com/magic/man2html/1/emacs

OSDev.org

[slightly OT] In series of funny manual pages: linux vfork

[slightly OT] In series of funny manual pages: linux vfork