From owner-freebsd-mobile Thu Feb 10 21:51:47 2000 Delivered-To: freebsd-mobile@freebsd.org Received: from grey.cloud.rain.com (c1029014-a.bvrtn1.or.home.com [24.12.160.67]) by builder.freebsd.org (Postfix) with ESMTP id AE68F4688 for ; Thu, 10 Feb 2000 21:51:44 -0800 (PST) Received: (qmail 8735 invoked from network); 11 Feb 2000 05:46:31 -0000 Received: from localhost.cloud.rain.com (HELO cloud.rain.com) (@127.0.0.1) by localhost.cloud.rain.com with SMTP; 11 Feb 2000 05:46:31 -0000 To: Nik Clayton Cc: mobile@freebsd.org Subject: Re: Mobile FreeBSD References: <20000210213824.A45875@kilt.nothing-going-on.org> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <8731.950247991.1@cloud.rain.com> Date: Thu, 10 Feb 2000 21:46:31 -0800 Message-ID: <8732.950247991@cloud.rain.com> From: Bill Trost Sender: owner-freebsd-mobile@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org Nik Clayton writes: For preference, I'd like to be able to pull the laptop off this network for periods of time, and have things just work... The tricky bit, as far as I can see, is going to be the file sharing. In particular, when the laptop is plugged back in to the network, any changes made to shared files while the laptop was away (regardless of whether those changes were made on the laptop or on the network) should be integrated. That sounds like the coda filesystem, which is included as part of the distribution (there is also a reference at www.freebsd.org/projects). As I understand it, it requires a machine dedicated to being the coda server, and it has this itsy 100 MB cache on the clients, but it might meet your needs. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-mobile" in the body of the message