From: "Albert D. Cahalan" <acahalan@cs.uml.edu>
To: rothwell@holly-springs.nc.us (Michael Rothwell)
Cc: mmckinlay@gnu.org (Mo McKinlay),
peter@cadcamlab.org (Peter Samuelson),
linux-kernel@vger.kernel.org
Subject: Re: named streams, extended attributes, and posix
Date: Sun, 21 Jan 2001 02:27:24 -0500 (EST) [thread overview]
Message-ID: <200101210727.f0L7RO3258994@saturn.cs.uml.edu> (raw)
In-Reply-To: <3A686599.470272D6@holly-springs.nc.us> from "Michael Rothwell" at Jan 19, 2001 11:04:41 AM
Michael Rothwell writes:
> ...
>> Today, Michael Rothwell (rothwell@holly-springs.nc.us) wrote:
>>> The filesystem, when registering that it supports the "named streams"
>>> namespace, could specify its preferred delimiter to the VFS as well.
>>> Ext4 could use /directory/file/stream, and NTFS could use
>>> /directory/file:stream.
...
> Oh, undoubtedly. But NTFS already disallows several characters
> in valid filenames.
NTFS allows all 16-bit characters in filenames, including 0x0000.
Nothing is disallowed. The NT kernel's native API uses counted
Unicode strings. The strings can be huge too, like 128 kB.
So there isn't _any_ safe delimiter.
Win32 will choke on 0x0000 and a few other things, allowing a
clever person to create apparently inaccessible files.
-
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-21 7:28 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-11 20:00 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
2001-01-29 15:46 ` Mo McKinlay
2001-01-21 7:27 ` Albert D. Cahalan [this message]
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
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=200101210727.f0L7RO3258994@saturn.cs.uml.edu \
--to=acahalan@cs.uml.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=mmckinlay@gnu.org \
--cc=peter@cadcamlab.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
all inboxes | Powered by JetHome®