From owner-freebsd-fs Wed Jul 12 7:32: 6 2000 Delivered-To: freebsd-fs@freebsd.org Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by hub.freebsd.org (Postfix) with ESMTP id D762537BE62 for ; Wed, 12 Jul 2000 07:32:03 -0700 (PDT) (envelope-from robert@fledge.watson.org) Received: from fledge.watson.org (robert@fledge.pr.watson.org [192.0.2.3]) by fledge.watson.org (8.9.3/8.9.3) with SMTP id KAA50891; Wed, 12 Jul 2000 10:31:45 -0400 (EDT) (envelope-from robert@fledge.watson.org) Date: Wed, 12 Jul 2000 10:31:45 -0400 (EDT) From: Robert Watson X-Sender: robert@fledge.watson.org To: Kelly Yancey Cc: Marius Bendiksen , Dmitry Brodsky , freebsd-fs@FreeBSD.ORG Subject: Re: Meta-Data & stackable FS In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-fs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org On Wed, 12 Jul 2000, Robert Watson wrote: > In any case, assuming that a working and sufficiently strong stacking > environment exists (FiST satisfies a number of these requirements, I > believe), the chances are you'd add the service (say, ACLs) by layering > EA's on top of FFS, and then a service on top of EA+FFS, in which case > you'd be relying on vnode operations introduced by the EA layer, and > presumably they would strongly resemble the EA VOP's already present, and > probably should even be the same VOPs :-). In which case EA+FFS is > indistinguishable from FFS w/EAs. BTW, I think there's a decent argument that even if you had fully-functional stacking, having the base file store provide EA services is highly desirable, as it allows layers to impose new semantics and meta-data without needing to deal with the namespace and storage issues, and it simplifies the update/consistency problem substantially. Robert N M Watson robert@fledge.watson.org http://www.watson.org/~robert/ PGP key fingerprint: AF B5 5F FF A6 4A 79 37 ED 5F 55 E9 58 04 6A B1 TIS Labs at Network Associates, Safeport Network Services To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message