Received: from PACIFIC-CARRIER-ANNEX.MIT.EDU by po7.MIT.EDU (5.61/4.7) id AA08114; Sat, 24 Feb 96 17:16:31 EST
Received: from pain.lcs.mit.edu by MIT.EDU with SMTP
	id AA14611; Sat, 24 Feb 96 17:16:11 EST
Received: (from daemon@localhost) by pain.lcs.mit.edu (8.6.12/8.6.12) id QAA08835; Sat, 24 Feb 1996 16:43:04 -0500
Received: (from mycroft@localhost) by pain.lcs.mit.edu (8.6.12/8.6.12) id QAA08828; Sat, 24 Feb 1996 16:43:01 -0500
Date: Sat, 24 Feb 1996 16:43:01 -0500
From: "Charles M. Hannum" <mycroft@NetBSD.ORG>
Message-Id: <199602242143.QAA08828@pain.lcs.mit.edu>
To: ragge@NetBSD.ORG
Subject: Re: NetBSD master CVS tree commits
Cc: netbsd-developers@NetBSD.ORG
Sender: owner-netbsd-developers@NetBSD.ORG
Precedence: first-class
X-Loop: netbsd-developers@NetBSD.ORG


   Remove __FORK_BRAINDAMAGE, and the reason to why it was there.

You did *not* fix it.  __FORK_BRAINDAMAGE refers to copying the kernel
stack on fork.  Most of the ports don't do this any more; they create
a new kernel stack for the forked process, and arrange for it to exit
directly to user mode, without rewinding through all the fork()
machinery.  This is also why the return type is void; there's no longer
a need to distinguish in sys_fork() whether or not we're returning to
the parent or the child.

[CCed to -developers for the benefit of Jonathon and Paul...]

