All of lore.kernel.org
 help / color / mirror / Atom feed
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: Fri, 19 Jan 2001 10:11:23 -0500	[thread overview]
Message-ID: <3A68591B.417EC21E@holly-springs.nc.us> (raw)
In-Reply-To: <Pine.LNX.4.30.0101191455570.2331-100000@nvws005.nv.london>

Mo McKinlay wrote:

> openstream(file, stream, flags)
> 
> Where 'file' should be an fd (although i'm sure the VFS gods will think of
> plenty of reasons why this is a bad idea, at which point I'll
> conventiently change my mind ;). Stream is simply the name of the stream,
> flags are as with open() (O_RDONLY, et al). openstream() then returns an
> fd which can be read/written/sendfiled/closed as the programmer wishes.

I'm not opposed to that, and think it is even a useful idea. Sort of
like fdopen().

> Apart from the additional of a new open()-type call, your paper seems to
> be fairly solid.

Thanks. I think having the option of the namespace augmentation would be
useful, in terms of supporting existing filesystems. On NTFS, ":" is not
a legal filename character anyway. The namespace augmentation suggested
in the paper would allow filesystems like NTFS to work as they should,
and all other filesystems to ignore it.

-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/

  reply	other threads:[~2001-01-19 15:11 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 [this message]
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
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=3A68591B.417EC21E@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.