From: Shahbaz Youssefi <shabbyx@gmail.com>
To: willy@infradead.org
Cc: linux-fsdevel@vger.kernel.org, ebiggers@kernel.org,
viro@zeniv.linux.org.uk
Subject: Re: Streams support in Linux
Date: Wed, 19 Sep 2018 22:06:06 -0400 [thread overview]
Message-ID: <CALeOzZ-5TejL3K6Mui+FtHAsKyn=rrUTaF4MGcTDswZx34mpTw@mail.gmail.com> (raw)
> Let's go over the properties of a file stream:
>
> - It has no life independent of the file it's attached to; you can't move
> it from one file to another
> - If the file is deleted, it is also deleted
> - If the file is renamed, it travels with the file
> - If the file is copied, the copying program decides whether any named
> streams are copied along with it.
> - Can be created, deleted. Can be renamed?
> - Openable, seekable, cachable
> - Does not have sub-streams of its own
> - Directories may also have streams which are distinct from the files
> in the directory
> - Can pipes / sockets / device nodes / symlinks / ... have streams? Unclear.
> Probably not useful.
This certainly sounds useful! And it's called tar.
With fs-verity as well, I don't see why they have to put the tree and
the data in the same file, when they can just bundle them in a
tarball.
next reply other threads:[~2018-09-20 7:47 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-09-20 2:06 Shahbaz Youssefi [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-08-25 13:51 Streams support in Linux Matthew Wilcox
2018-08-25 14:47 ` Al Viro
2018-08-25 15:51 ` Matthew Wilcox
2018-08-25 18:00 ` Al Viro
2018-08-25 20:57 ` Matthew Wilcox
2018-08-25 22:36 ` Al Viro
2018-08-26 1:03 ` Steve French
2018-08-27 17:05 ` Jeremy Allison
2018-08-27 17:41 ` Jeremy Allison
2018-08-27 18:21 ` Matthew Wilcox
2018-08-27 18:45 ` Al Viro
2018-08-27 19:06 ` Jeremy Allison
2018-08-28 0:45 ` Theodore Y. Ts'o
2018-08-28 1:07 ` Steve French
2018-08-28 18:12 ` Jeremy Allison
2018-08-28 18:32 ` Steve French
2018-08-28 18:40 ` Jeremy Allison
2018-08-28 19:43 ` Steve French
2018-08-28 19:47 ` Jeremy Allison
2018-08-28 20:43 ` Steve French
2018-08-28 20:47 ` Jeremy Allison
2018-08-28 20:51 ` Steve French
2018-08-28 21:19 ` Stefan Metzmacher
2018-08-28 21:22 ` Jeremy Allison
2018-08-28 21:23 ` Steve French
2018-08-29 5:13 ` Ralph Böhme
2018-08-29 13:46 ` Tom Talpey
2018-08-29 13:54 ` Aurélien Aptel
2018-08-29 15:02 ` Tom Talpey
2018-08-29 16:00 ` Jeremy Allison
2018-08-29 15:59 ` Jeremy Allison
2018-08-29 18:52 ` Andreas Dilger
2018-08-26 20:30 ` Matthew Wilcox
2018-08-25 16:25 ` Theodore Y. Ts'o
2018-08-27 16:33 ` Jeremy Allison
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='CALeOzZ-5TejL3K6Mui+FtHAsKyn=rrUTaF4MGcTDswZx34mpTw@mail.gmail.com' \
--to=shabbyx@gmail.com \
--cc=ebiggers@kernel.org \
--cc=linux-fsdevel@vger.kernel.org \
--cc=viro@zeniv.linux.org.uk \
--cc=willy@infradead.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;
as well as URLs for NNTP newsgroup(s).