There probably should have just been a "run" call, which started a subprocess given the indicated executable. Some UNIX-like operating systems have that. It has the nice property that it scales to clusters; there's no reason a subprocess can't run on another machine. QNX, for example, supports that.
The several different flavors of exec are just convenience functions that lead to an execve syscall (execl* makes the vector out of some of its args; exec*p searches the path first, etc). Maybe you're thinking of vfork (a restricted fork), which seems to have gone away about when copy-on-write came in.
[1] http://linux.die.net/man/2/execve
man pages are your friend ;P
(I think they assume if you are doing this level of debugging, you are familiar with the typical linux sys calls, and/or know where to look-up more information about them)