From owner-freebsd-current Wed Jun 5 18:07:41 1996 Return-Path: owner-current Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id SAA21616 for current-outgoing; Wed, 5 Jun 1996 18:07:41 -0700 (PDT) Received: from time.cdrom.com (time.cdrom.com [204.216.27.226]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id SAA21609; Wed, 5 Jun 1996 18:07:39 -0700 (PDT) Received: from localhost (localhost [127.0.0.1]) by time.cdrom.com (8.7.5/8.6.9) with SMTP id SAA28805; Wed, 5 Jun 1996 18:00:11 -0700 (PDT) To: Terry Lambert cc: jehamby@lightside.com, jfieber@indiana.edu, bostic@bsdi.com, current@freebsd.org, jhs@freebsd.org Subject: Re: editors In-reply-to: Your message of "Wed, 05 Jun 1996 17:46:53 PDT." <199606060046.RAA00195@phaeton.artisoft.com> Date: Wed, 05 Jun 1996 18:00:11 -0700 Message-ID: <28803.834022811@time.cdrom.com> From: "Jordan K. Hubbard" Sender: owner-current@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > with transactioning" using the soft updates work. This toenails > nicely into the idea of a generic addressable block store in a flat > block name space, on top of which you implement attribution services > for attributes like, oh, say, names and directory hierarchies. 8-). Sounds like you could also implement logical volumes under this and get generic addressable block stores that span volumes or shrink on demand - no more fixed filesystem sizes. :) > I think this is the direction we eventually want to pursue to get > the most flexible framework for doing the sort of UI things you > are talking about here (icon binding, etc.). There's also the Absolutely. The visual representation of a file is just one more property. > FS event model, which lends itself to soft update representation > as well... you need something like that to be able to say "I'm Hmmmm. The details of a filesystem event model sounds like a somewhat different kettle of fish. :-) I'd be interested in the details of what you had in mind. Jordan