-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, Michael Rothwell ([EMAIL PROTECTED]) wrote:
> 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 strea
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() wil
On Thu, 25 Jan 2001, Leif Sawyer wrote:
> [EMAIL PROTECTED] [[EMAIL PROTECTED]] wrote:
> > Here's an idea: streams/etc are reached by appending
> > "/.../xxx" or some such to paths, thus:
> > for streamname on /dir/file, we have "/dir/file/.../streamname"
> > for a directory /dir/dir, we get
[EMAIL PROTECTED] [[EMAIL PROTECTED]] wrote:
> Here's an idea: streams/etc are reached by appending
> "/.../xxx" or some such to paths, thus:
> for streamname on /dir/file, we have "/dir/file/.../streamname"
> for a directory /dir/dir, we get /dir/dir/.../streamname"
>-- "..." is a speci
On Thu, Jan 25, 2001 at 02:07:11PM -0700, Thunder from the hill wrote:
> Daniel Phillips wrote:
> > For some reason totally beyond my comprehension // inside a file name is
> > taken to be the same as /, but if it wasn't it could be the stream
> > separator. *sigh*
> It seems that you mix up forw
Daniel Phillips wrote:
>
> Michael Rothwell wrote:
> > 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.
>
> For some reason totally beyond my comprehension // inside
Michael Rothwell wrote:
> 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.
For some reason totally beyond my comprehension // inside a file name is
taken to be the same as
quot;
<[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Saturday, January 20, 2001 11:27 PM
Subject: Re: named streams, extended attributes, and posix
> Michael Rothwell writes:
> > ...
> >> Today, Michael Rothwell ([EMAIL PROTECTED]) wrote:
>
> >>> The fil
Michael Rothwell writes:
> ...
>> Today, Michael Rothwell ([EMAIL PROTECTED]) 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
>>>
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, Michael Rothwell ([EMAIL PROTECTED]) wrote:
> Mo McKinlay wrote:
>
> > Nono, that's not what I mean - each of the filesystems fails if it
> > doesn't support what you're trying to do, that's given - but having a
> > different delimet
Mo McKinlay wrote:
> Nono, that's not what I mean - each of the filesystems fails if it
> doesn't support what you're trying to do, that's given - but having a
> different delimeter registered by the filesystem (and hence the
> possibility of every single filesystem using a different delimeter) b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, Michael Rothwell ([EMAIL PROTECTED]) wrote:
> Oh, undoubtedly. But NTFS already disallows several characters in valid
> filenames. This also violates the "consistent abstract interface." But
> it's reality.
Nono, that's not what I mean
Mo McKinlay wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Today, Michael Rothwell ([EMAIL PROTECTED]) wrote:
>
> > The filesystem, when registering that it supports the "named streams"
> > namespace, could specify its preferred delimiter to the VFS as well.
> > Ext4 could
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, Michael Rothwell ([EMAIL PROTECTED]) 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
Mo McKinlay wrote:
> (Take symbolic linking, for example - if you ln -s on VFAT, you get
> 'operation not permitted' - named stream/EA operations on a filesystem
> that doesn't support them should return the same, IMHO).
And they would, if the chosen namespace was not supported.
> Also, I don't
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, Michael Rothwell ([EMAIL PROTECTED]) wrote:
> 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 na
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Well, EAs are accessed via a special API. The paper also covers that.
> Streams, however, are by nature accessed as files; this is what makes
> them not EAs. EAs are set and retrieved atomically. Streams can be used
> with open(), seek(), r
Mo McKinlay wrote:
>
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Today, Michael Rothwell ([EMAIL PROTECTED]) wrote:
>
> > Unfortunately, unix allows everything but "/" in filenames. This was
> > probably a mistake, as it makes it nearly impossible to augment the
> > namespace, b
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, Michael Rothwell ([EMAIL PROTECTED]) wrote:
> 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 rea
y" <[EMAIL PROTECTED]>
To: "Peter Samuelson" <[EMAIL PROTECTED]>
Cc: "Mo McKinlay" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Thursday, January 18, 2001 1:30 PM
Subject: Re: named streams, extended attributes, and posix
> -BEGIN PGP SIGN
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yesterday, Peter Samuelson ([EMAIL PROTECTED]) 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 (':'
[Mo McKinlay]
> We went through this last time around. What happens to directories
> with streams?
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 t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Yesterday, Peter Samuelson ([EMAIL PROTECTED]) wrote:
>
> [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
[Peter Samuelson]
> > What if you copy both 'filename' and 'filename:ext' onto the same
> > fs? Do they get combined into one file?
[Michael Rothwell]
> ON Ext2, you get two files. On NTFS, you get one file, and a stream
> on that file.
Yeah. I think that's broken. It gets worse when you s
> What if you copy both 'filename' and 'filename:ext' onto the same fs?
> Do they get combined into one file?
ON Ext2, you get two files. On NTFS, you get one file, and a stream on that
file.
> Any semantics by which 'filename:stream' and 'filename' refer to the
> same file would be b0rken. If
[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 'filena
"James H. Cloos Jr." wrote:
>
> Michael> Please read and comment! :)
>
> There should be some discussion on what to do about filenames which
> contain colons in such a setup. Moving a file w/ a colon from a fs
> which does not support named streams to one which does should DTRT;
> exactly what
Michael> Please read and comment! :)
There should be some discussion on what to do about filenames which
contain colons in such a setup. Moving a file w/ a colon from a fs
which does not support named streams to one which does should DTRT;
exactly what TRT is should be discussed.
-JimC
--
Jame
CORRECTION:
> existing, widely-deployed filesystems (e.g., NFS, XFS, BeFS, HFS, etc.),
NTFS---^
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
Please read the FAQ at http://www.tux.org
30 matches
Mail list logo
