From owner-freebsd-hackers Wed Jun 4 10:04:39 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id KAA10749 for hackers-outgoing; Wed, 4 Jun 1997 10:04:39 -0700 (PDT) Received: from wrzx07.rz.uni-wuerzburg.de (wrzx07.rz.uni-wuerzburg.de [132.187.1.7]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id KAA10742 for ; Wed, 4 Jun 1997 10:04:36 -0700 (PDT) Received: from wicx50.informatik.uni-wuerzburg.de (mail@wicx50.informatik.uni-wuerzburg.de [132.187.9.50]) by wrzx07.rz.uni-wuerzburg.de (8.8.5/8.8.5) with SMTP id TAA05738; Wed, 4 Jun 1997 19:04:21 +0200 (MET DST) Received: by wicx50.informatik.uni-wuerzburg.de (8.6.12/uniwue-C-3.1a (CIP Gate)) id TAA21461; Wed, 4 Jun 1997 19:04:20 +0200 Received: from aruba(132.187.9.1) by cipgate via smap (V1.3) id sma021459; Wed Jun 4 19:03:53 1997 Received: by wicx01.informatik.uni-wuerzburg.de (5.65v3.2/uniwue-C-3.1 (C)) id AA09686; Wed, 4 Jun 1997 19:03:53 +0200 From: Matthias Buelow Message-Id: <9706041703.AA09686@wicx01.informatik.uni-wuerzburg.de> Subject: Re: Linux clone() system call To: borjam@we.lc.ehu.es (Borja Marcos) Date: Wed, 4 Jun 1997 19:03:52 +0100 (MET DST) Cc: freebsd-hackers@freebsd.org In-Reply-To: <9706041530.AA02422@sirius.we.lc.ehu.es> from "Borja Marcos" at Jun 4, 97 05:30:55 pm X-Mailer: ELM [version 2.4 PL20] Content-Type: text Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > Anyone knows what is the clone() system call in Lunux? > It seems not to be supported by the Linux emulator. I tried running > the Linux version of Inferno and it died with something like > "clone(): unimplemented system call". > > I did a "man clone" in a Linux box and it gave me > the "undocumented calls" man page. CLONE(2) Linux Programmer's Manual CLONE(2) NAME clone - create a child process SYNOPSIS #include #include pid_t clone(void *sp, unsigned long flags) DESCRIPTION clone is an alternate interface to fork, with more options. fork is equivalent to clone(0, SIGCLD|COPYVM). [...] clone(2) is a Linux-unique system call (they formed it after a Plan9 syscall afaik) and not portable. It looks more or less like a kludgy hack interface to fork/vfork especially when you consider the following :-) : ERRORS ENOSYS clone will always return this error, unless your kernel was compiled with CLONE_ACTUALLY_WORKS_OK defined.