[1077] in arla-drinkers
Re: thoughts?
daemon@ATHENA.MIT.EDU (Michele A. Trovero)
Tue Aug 17 10:30:17 1999
From owner-arla-drinkers@stacken.kth.se Tue Aug 17 14:30:16 1999
Return-Path: <owner-arla-drinkers@stacken.kth.se>
Delivered-To: arla-drinkers-mtg@bloom-picayune.mit.edu
Received: (qmail 24253 invoked from network); 17 Aug 1999 14:30:14 -0000
Received: from unknown (HELO sundance.stacken.kth.se) (130.237.234.41)
by bloom-picayune.mit.edu with SMTP; 17 Aug 1999 14:30:14 -0000
Received: (from majordom@localhost)
by sundance.stacken.kth.se (8.8.8/8.8.8) id QAA07665
for arla-drinkers-list; Tue, 17 Aug 1999 16:20:21 +0200 (MET DST)
Received: from smtpsrv1.isis.unc.edu (smtpsrv1.isis.unc.edu [152.2.1.138])
by sundance.stacken.kth.se (8.8.8/8.8.8) with ESMTP id QAA07661
for <arla-drinkers@stacken.kth.se>; Tue, 17 Aug 1999 16:20:15 +0200 (MET DST)
Received: from trovero.stat.unc.edu (trovero.stat.unc.edu [152.2.69.14])
by smtpsrv1.isis.unc.edu (8.9.1/8.9.1) with ESMTP id KAA28871;
Tue, 17 Aug 1999 10:20:05 -0400 (EDT)
Date: Tue, 17 Aug 1999 10:20:06 -0400
From: "Michele A. Trovero" <trovero@email.unc.edu>
To: "Todd T. Fries" <toddf@acm.org>, arla-drinkers@stacken.kth.se
Subject: Re: thoughts?
Message-ID: <2877303308.934885206@trovero.stat.unc.edu>
In-Reply-To: <19990817063339.H25561@LightHouse.fries.net>
Originator-Info: login-id=trovero; server=imap.unc.edu
X-Mailer: Mulberry (Win32) [1.4.3, s/n S-397020]
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Sender: owner-arla-drinkers@stacken.kth.se
Precedence: bulk
It seems to me that coda (http://www.coda.cs.cmu.edu/) would more
appropriate for your needs: it is an evolution of AFS designed to support
disconnected operation for mobile computing. I know it runs on Linux, I
guess it will run on BSD as well, although I never used it, so I don't know
how well it works.
Michele
--On Tuesday, August 17, 1999, 6:33 AM -0500 "Todd T. Fries"
<toddf@acm.org> wrote:
> I have a couple of machine that almost could use arla but not quite. I
> have been told this is a place to seek brainstorm activity, to boldly
> create new ideas never thought of before, or seek out ones I have not
> known, etc...
>
> So.. the situation as best I can describe it...
>
> I have a network of machines at my apartment, different archs, a few large
> disks. I have OpenBSD on all machines (but two hppa machines, nfsroot
> works, so soon they will be OpenBSD as well) .. I mention the os because
> it has arla integrated and thus is available as a client .. several nfs
> fileservers, two machines 'borg' and 'wearable'. 'Borg' is a black
> thinkpad, and wearable explains itself. Although the wearable needs some
> more hardware before it is truly portable, it will be soon enough.
>
> I have lots of data I find myself manually duplicating across borg,
> wearable, and 'the rest of the net'. As logistics would have it, borg
> and wearable will naturally be separated from the home net and each other
> for periods of time.
>
> What I think I need is a cachefs of sorts, one that allows me to place in
> some sort of persistent writable cache in disconnect mode any files I will
> be dealing with while away (for borg, mp3's and src, car casette adaptors
> and laptops with audio work nicely!) ..
>
> My thoughts on an appropriate solution:
>
> - arla server.
> a) I hear this is in the pipeline, but I would not yet want
> to plan on converting my nfs servers to arla servers.
> b) I hear there exists a 'server' that serves local filesystems instead
> of arla volumes. Seems perfect for a temporary solution.
> - cachefs like filesystem that adds the behaviors:
> - persistent cache across disconnection
> - persistent cache across reboot
> - disconnected writing to the cache
> - arla-drinkers@ original/already thought of idea??
>
> Thoughts?
>
> I'm not on this mailing list, please cc: appropriately.
> --
> Todd Fries .. toddf@acm.org
>
