From: Peter Samuelson <peter@cadcamlab.org>
To: Michael Rothwell <rothwell@holly-springs.nc.us>
Cc: "James H. Cloos Jr." <cloos@jhcloos.com>, linux-kernel@vger.kernel.org
Subject: Re: named streams, extended attributes, and posix
Date: Tue, 16 Jan 2001 18:28:06 -0600 [thread overview]
Message-ID: <20010116182806.B6364@cadcamlab.org> (raw)
In-Reply-To: <3A5E10F5.716F83B7@holly-springs.nc.us> <m3snmpgu8t.fsf@austin.jhcloos.com> <3A6466D0.6587C11A@holly-springs.nc.us>
In-Reply-To: <3A6466D0.6587C11A@holly-springs.nc.us>; from rothwell@holly-springs.nc.us on Tue, Jan 16, 2001 at 10:20:48AM -0500
[Michael Rothwell]
> It seems that if you move a file with a colon -- "file:colon" -- in
> the name from Ext2 to "StreamFS," you would end up with a file named
> "file" with a stream named "colon". When copying back, you would get
> "file:colon" back.
What if you copy both 'filename' and 'filename:ext' onto the same fs?
Do they get combined into one file? That to me violates principle of
least surprise. The fs should just mangle filenames it doesn't agree
with, like the existing legacy filesystems already do.
Any semantics by which 'filename:stream' and 'filename' refer to the
same file would be b0rken. If instead you use 'filename/stream'
syntax, at least that is an illegal filename on *all* Linux
filesystems, so this particular point of confusion does not come up.
Peter
-
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-17 0:28 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 [this message]
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
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=20010116182806.B6364@cadcamlab.org \
--to=peter@cadcamlab.org \
--cc=cloos@jhcloos.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rothwell@holly-springs.nc.us \
/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