Date: Tue, 11 Jan 2000 09:13:52 -0700 (MST) From: "Ronald G. Minnich" <rminnich@lanl.gov> To: freebsd-hackers@FreeBSD.ORG Subject: Re: rfork() [was: Concept check] Message-ID: <Pine.LNX.4.20.0001110911320.1512-100000@mini.acl.lanl.gov> In-Reply-To: <Pine.BSF.4.05.10001110055470.26127-100000@bsd1.nyct.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 11 Jan 2000, Michael Bacarella wrote: > I'm sorry I missed the discussion on rfork()... but I say this only > because I want to understand. > > What were you thinking? rfork()? Why is it a system call? > > Almost all of the flags it accepts seem like functionality that can easily > be implemented in userspace around fork() (and maybe vfork()). nope. This whole issue is about (let me check :-) ) 4.5 years old. I did the first rfork for freebsd ca. 9/1994, and I can tell you that you can't easily get what it does with userland wrappers. Well, actually, in the general case it's impossible. Just think about that fact that with shared file descriptors, a child can open a socket and the parent can use it, right down to using the same FD #. (And yes, I use this). I don't want to try to emulate that behaviour in userland. Fork and vfork, however, are a subset of rfork. ron To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.LNX.4.20.0001110911320.1512-100000>