From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S261249AbTD1SQq (ORCPT ); Mon, 28 Apr 2003 14:16:46 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S261250AbTD1SQp (ORCPT ); Mon, 28 Apr 2003 14:16:45 -0400 Received: from niwot.scd.ucar.edu ([128.117.8.223]:19635 "EHLO niwot.scd.ucar.edu") by vger.kernel.org with ESMTP id S261249AbTD1SQp (ORCPT ); Mon, 28 Apr 2003 14:16:45 -0400 Date: Mon, 28 Apr 2003 12:28:56 -0600 From: Craig Ruff To: Mark Grosberg Cc: "Richard B. Johnson" , linux-kernel@vger.kernel.org Subject: Re: [RFD] Combined fork-exec syscall. Message-ID: <20030428182856.GA18075@ucar.edu> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.4i Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org > On Mon, 28 Apr 2003, Richard B. Johnson wrote: > > > The Unix API provides execve(), fexecve(), execv(), execle(), > > execl(), execvp(), and execlp() for what you call 'exec'. So > > there is no 'fork and exec' as you state. By the way, the latest ISO/IEC 9945-1:2002 POSIX standard defines the posix_spawn* functions which provide this fork/exec style of operation.