public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 20:05:05 -0600 (CST)	[thread overview]
Message-ID: <14948.64977.712237.357229@wire.cadcamlab.org> (raw)
In-Reply-To: <3A5E10F5.716F83B7@holly-springs.nc.us> <m3snmpgu8t.fsf@austin.jhcloos.com> <3A6466D0.6587C11A@holly-springs.nc.us> <20010116182806.B6364@cadcamlab.org> <012901c0803f$b5e62df0$8501a8c0@gromit>


  [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 start doing other
posixy things.  Say you do 'mv foo bar:baz' on an ntfs partition.
Those strong in the force will recall that rename() is supposed to
atomically unlink 'bar:baz'.  Instead you seem to be asking it to add
an extra stream to 'bar'.  So should we still unlink the old 'bar'?
And then what if 'foo' is a multi-stream file?  Where do the extra
streams go?  Or do you just get a big fat -EINVAL for every special
case?

I think ultimately there is no posixy (or least-surprise) way to deal
with such things.  If we truly need forks, we need a new api to
manipulate them.  Cleverness with ':' or '/' only takes you so far.

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/

  reply	other threads:[~2001-01-17  2:05 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
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 [this message]
  -- 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=14948.64977.712237.357229@wire.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