From: Michael Rothwell <rothwell@holly-springs.nc.us>
To: Mo McKinlay <mmckinlay@gnu.org>
Cc: Peter Samuelson <peter@cadcamlab.org>, linux-kernel@vger.kernel.org
Subject: Re: named streams, extended attributes, and posix
Date: Mon, 29 Jan 2001 10:20:55 -0500 [thread overview]
Message-ID: <3A758A57.CB019330@holly-springs.nc.us> (raw)
In-Reply-To: <Pine.LNX.4.30.0101191633200.2331-100000@nvws005.nv.london>
Mo McKinlay wrote:
> I would too, but POSIX won't let us unless we start enforcing side-effect
> rules for all filesystems. Hence why I came up with openstream() :)
So, openstream() is probably the most painless way to get named streams
support into Linux in the immediate future. Openstream() will have to
fail on filesystems that do not support streams, ideally without
changing those filesystems. And as long as we're adding a system call to
deal with streams, we should consider adding the functions for extended
attributes at the same time.
>From http://www.flyingbuttmonkeys.com/streams-on-posix.txt ...
Minimum VFS Support
vop_eattr_get - read an EA
vop_eattr_set - set an EA
vop_eattr_remove - remove an EA
vop_eattr_list - list the EAs like vop_readdir would a directory.
Optional Support
vop_eattr_create - Create an EA or error if it exists.
vop_eattr_multi - perform a sequence of EA vops atomically.
vop_eattr_rename - change the name of an EA
vop_eattr_serialize - export all the EAs as a stream of entries.
Thoughts? You mught want to refer back to the paper to get the whole EAs
proposal...
-M
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2001-01-29 15:22 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 20:00 named streams, extended attributes, and posix Michael Rothwell
2001-01-11 22:22 ` Michael Rothwell
2001-01-12 6:27 ` James H. Cloos Jr.
2001-01-16 15:20 ` Michael Rothwell
2001-01-17 0:28 ` Peter Samuelson
2001-01-17 0:37 ` Mo McKinlay
2001-01-18 1:03 ` Peter Samuelson
2001-01-18 21:30 ` Mo McKinlay
2001-01-19 8:14 ` Michael Rothwell
2001-01-19 14:19 ` Mo McKinlay
2001-01-19 14:39 ` Michael Rothwell
2001-01-19 14:59 ` Mo McKinlay
2001-01-19 15:11 ` Michael Rothwell
2001-01-19 15:20 ` Mo McKinlay
2001-01-19 15:44 ` Michael Rothwell
2001-01-19 15:49 ` Mo McKinlay
2001-01-19 16:04 ` Michael Rothwell
2001-01-19 16:07 ` Mo McKinlay
2001-01-19 16:13 ` Michael Rothwell
2001-01-19 16:33 ` Mo McKinlay
2001-01-29 15:20 ` Michael Rothwell [this message]
2001-01-29 15:46 ` Mo McKinlay
2001-01-21 7:27 ` Albert D. Cahalan
2001-01-22 9:19 ` Michael Rothwell
2001-01-25 20:41 ` Daniel Phillips
2001-01-25 21:07 ` Thunder from the hill
2001-01-25 23:03 ` alex
2001-01-17 4:40 ` Michael Rothwell
2001-01-17 2:05 ` Peter Samuelson
-- strict thread matches above, loose matches on Subject: below --
2001-01-25 23:15 Leif Sawyer
2001-01-26 2:41 ` Steven N. Hirsch
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=3A758A57.CB019330@holly-springs.nc.us \
--to=rothwell@holly-springs.nc.us \
--cc=linux-kernel@vger.kernel.org \
--cc=mmckinlay@gnu.org \
--cc=peter@cadcamlab.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox