From: "Michael Rothwell" <rothwell@holly-springs.nc.us>
To: "Mo McKinlay" <mmckinlay@gnu.org>,
"Peter Samuelson" <peter@cadcamlab.org>
Cc: <linux-kernel@vger.kernel.org>
Subject: Re: named streams, extended attributes, and posix
Date: Fri, 19 Jan 2001 00:14:12 -0800 [thread overview]
Message-ID: <004701c081ef$e32dcb90$8501a8c0@gromit> (raw)
In-Reply-To: <Pine.LNX.4.30.0101182129050.1089-100000@nvws005.nv.london>
Unfortunately, unix allows everything but "/" in filenames. This was
probably a mistake, as it makes it nearly impossible to augment the
namespace, but it is the reality.
Did you read the "new namespace" section of the paper?
It also talked a bit about supporting Extended Attributes, which are access
via an API and not with a filename separator. We could, perhaps, begin by
supporting EAs. That would take care of HFS, HPFS, XFS, and BeFS, and half
of NTFS. Then we could go on to tackle the Named Streams problem.
-M
----- Original Message -----
From: "Mo McKinlay" <mmckinlay@gnu.org>
To: "Peter Samuelson" <peter@cadcamlab.org>
Cc: "Mo McKinlay" <mmckinlay@gnu.org>; <linux-kernel@vger.kernel.org>
Sent: Thursday, January 18, 2001 1:30 PM
Subject: Re: named streams, extended attributes, and posix
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Yesterday, Peter Samuelson (peter@cadcamlab.org) wrote:
>
> > Yeah, I agree, 'file/stream' is lousy syntax as well. If it weren't
> > for the possibility of having streams on directories, it would almost
> > be acceptible. I still don't know which (':' or '/') is the worse
> > hack.
>
> Me neither :/
>
> > As I've said elsewhere in this thread, I can't think of *any* clean
way
> > to shoehorn forks into nice, transparent posix calls. It really wants
> > a new API.
>
> Likewise. This was my standpoint the last time around - a clear concise
> portable API for accessing streams (even if it *started out*
> Linux-specific) - without imposing silly semantics on existing
> applications which currently ignore streams anyway.
>
> Mo.
>
> - --
> Mo McKinlay
> mmckinlay@gnu.org
> - ------------------------------------------------------------------------
-
> GnuPG/PGP Key: pub 1024D/76A275F9 2000-07-22
>
>
>
>
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.0.4 (GNU/Linux)
> Comment: For info see http://www.gnupg.org
>
> iEYEARECAAYFAjpnYGQACgkQRcGgB3aidfmWBQCfXgNq/vqltt76mApoDiNI9HnH
> ws8AoJZ2vvlH1iCAeUu7yktWWN0Bncc3
> =gEmD
> -----END PGP SIGNATURE-----
>
> -
> 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/
>
-
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-19 5:16 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 [this message]
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
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='004701c081ef$e32dcb90$8501a8c0@gromit' \
--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