From owner-freebsd-hackers  Mon Apr 28 23:44:30 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id XAA29538
          for hackers-outgoing; Mon, 28 Apr 1997 23:44:30 -0700 (PDT)
Received: from rah.star-gate.com (rah.star-gate.com [204.188.121.18])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id XAA29533
          for <freebsd-hackers@freebsd.org>; Mon, 28 Apr 1997 23:44:28 -0700 (PDT)
Received: from rah.star-gate.com (localhost.star-gate.com [127.0.0.1]) by rah.star-gate.com (8.8.5/8.7.3) with ESMTP id XAA02193; Mon, 28 Apr 1997 23:44:27 -0700 (PDT)
Message-Id: <199704290644.XAA02193@rah.star-gate.com>
X-Mailer: exmh version 1.6.9 8/22/96
To: Simon Shapiro <Shimon@i-Connect.Net>
cc: freebsd-hackers@freebsd.org
Subject: Re: New Features - invitation to comment 
In-reply-to: Your message of "Mon, 28 Apr 1997 21:21:55 PDT."
             <XFMail.970428222317.Shimon@i-Connect.Net> 
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Mon, 28 Apr 1997 23:44:27 -0700
From: Amancio Hasty <hasty@rah.star-gate.com>
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


Well, 


This sort of thing reminds me of  VMS clusters merged with NFS.

At first glance , I see the need for redundancy / mirroring . Also,
the access time or weight for a given host block. Ability to migrate
work load to different system on demand.

Does the system implements caching : write behind or read ahead?

Also I  would like to hear a little bit more on the distributed
lock manager and how does it handle failure cases or what happens
if the host where the application is running dies.

Perhaps, is best if the system address "virtual hosts/block" so if
a system goes down requests can continue on a mirroring system.

I better stop rambling . It does sound like a "cool" project 8)

	Regards,
	Amancio