From owner-freebsd-fs Fri May 26 7:49:24 2000 Delivered-To: freebsd-fs@freebsd.org Received: from bingnet2.cc.binghamton.edu (bingnet2.cc.binghamton.edu [128.226.1.18]) by hub.freebsd.org (Postfix) with ESMTP id 14BB537BBF0; Fri, 26 May 2000 07:49:20 -0700 (PDT) (envelope-from zzhang@cs.binghamton.edu) Received: from sol.cs.binghamton.edu (sol.cs.binghamton.edu [128.226.123.100]) by bingnet2.cc.binghamton.edu (8.9.3/8.9.3) with ESMTP id KAA23285; Fri, 26 May 2000 10:49:18 -0400 (EDT) Date: Fri, 26 May 2000 10:48:16 -0400 (EDT) From: Zhihui Zhang To: Robert Watson Cc: Chuck McCrobie , freebsd-fs@FreeBSD.ORG Subject: Re: Opinion on File System Implementation 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 Fri, 26 May 2000, Robert Watson wrote: > > Chuck, > > Responding briefly as I'm currently on travel at a DARPA PI meeting and > checking out shortly -- in 4.0-RELEASE/STABLE and 5.0-CURRENT, there is an > interface for "extended attributes" on file system objects. Take a look > at extattr(9), VOP_GETEXTATTR(9) and VOP_SETEXTATTR(9). There are exposed > syscalls to userland also, but in 4.x they don't have man pages as there > are no tools using them. > > In 5.0-CURRENT, I introduced rudimentary support for extended attributes > in UFS/FFS to support security extensions I have been working on, so we > also pushed in simple command line tools to allow userland to > read/set/control extended attributes (setextattr(8), getextattr(8), > extattrctl(8)). It may be that this interface is the appropriate > interface to read, if not write, this meta-data. > I am interested in where you are going to put those extended attributes, in the extended inode, in the file data, or in a separate associated file? -Zhihui To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-fs" in the body of the message