From: Florian Weimer <fw@deneb.enyo.de>
To: Andreas Dilger <adilger@sun.com>
Cc: Charles Manning <manningc2@actrix.gen.nz>, linux-fsdevel@vger.kernel.org
Subject: Re: What's a realistic size for xattr?
Date: Sat, 15 Mar 2008 12:09:28 +0100 [thread overview]
Message-ID: <87iqzow8ev.fsf@mid.deneb.enyo.de> (raw)
In-Reply-To: <20080313034506.GD5851@webber.adilger.int> (Andreas Dilger's message of "Wed, 12 Mar 2008 21:45:06 -0600")
* Andreas Dilger:
> On NTFS the word is that resource forks are mostly used by root kits.
They are also used to mark programs you've downloaded from the Internet,
so that a warning can be displayed when you open them.
prev parent reply other threads:[~2008-03-15 11:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-12 22:06 What's a realistic size for xattr? Charles Manning
2008-03-12 23:03 ` Nathan Scott
2008-03-12 23:23 ` Dave Quigley
2008-03-12 23:32 ` Dave Quigley
2008-03-13 0:03 ` Charles Manning
2008-03-13 17:10 ` Dave Quigley
2008-03-13 0:07 ` Jamie Lokier
2008-03-13 0:27 ` Brad Boyer
2008-03-13 8:56 ` Nicholas Miell
2008-03-13 3:45 ` Andreas Dilger
2008-03-15 11:09 ` Florian Weimer [this message]
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=87iqzow8ev.fsf@mid.deneb.enyo.de \
--to=fw@deneb.enyo.de \
--cc=adilger@sun.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=manningc2@actrix.gen.nz \
/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).