From owner-freebsd-hackers Tue Oct 24 21:01:46 1995 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.6.12/8.6.6) id VAA25206 for hackers-outgoing; Tue, 24 Oct 1995 21:01:46 -0700 Received: from kaiwan.kaiwan.com (4@kaiwan.kaiwan.com [198.178.203.2]) by freefall.freebsd.org (8.6.12/8.6.6) with ESMTP id VAA25201 for ; Tue, 24 Oct 1995 21:01:42 -0700 Received: from exit.com (uucp@localhost) by kaiwan.kaiwan.com (8.6.12/8.6.12) with UUCP id VAA04875 for hackers@freebsd.org; Tue, 24 Oct 1995 21:01:12 -0700 *** KAIWAN Internet Access *** Received: (from frank@localhost) by exit.com (8.6.12/8.6.12) id UAA26267 for hackers@freebsd.org; Tue, 24 Oct 1995 20:55:46 -0700 From: Frank Mayhar Message-Id: <199510250355.UAA26267@exit.com> Subject: Re: process migration To: hackers@freebsd.org Date: Tue, 24 Oct 1995 20:55:46 -0700 (PDT) In-Reply-To: <199510250325.XAA00130@ns1.win.net> from "Mark Hittinger" at Oct 24, 95 11:25:14 pm X-Mailer: ELM [version 2.4 PL24 ME5a] Content-Type: text Content-Length: 583 Sender: owner-hackers@freebsd.org Precedence: bulk Regarding process migration, Locus "Transparent Network Computing" (TNC) does this using a virtual-process layer analogous to the vnode layer in file systems. TNC does it dynamically using an RPC mechanism. It _is_ a complex problem, particularly when you have to handle things like shared semaphores, locked files, etc., ad nauseum. There were a couple of white papers written on the subject a few years ago. If there's sufficient interest I'll see if I can dig them up. There may also be references on the Locus Web page, http://www.locus.com/. -- Frank Mayhar frank@exit.com