From: Josh Boyer <jdub@us.ibm.com>
To: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
Cc: familiar-dev@handhelds.org, selinux@tycho.nsa.gov,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
familiar@handhelds.org, handhelds@handhelds.org,
kernel-discuss@handhelds.org, oe@handhelds.org, agruen@suse.de,
Russell Coker <rcoker@redhat.com>
Subject: Re: JFFS2 Extended attributes support & SELinux in handhelds
Date: Tue, 22 Feb 2005 12:21:42 -0600 [thread overview]
Message-ID: <1109096502.7813.5.camel@windu.rchland.ibm.com> (raw)
In-Reply-To: <1109089039.4100.114.camel@localhost.localdomain>
On Tue, 2005-02-22 at 17:17 +0100, Lorenzo Hernández García-Hierro
wrote:
> Hi,
>
> I've been working in implementing extended attributes support in the
> JFFS2 filesystem.
You should send this to the JFFS2 development list. The xattr support
is probably a JFFS3 candidate.
>
> The current work is just a draft, I've started with the standard Vanilla
> kernel sources plus mtd JFFS2 sources, used to patch the vanilla ones
> for latest code (I'm confused on which one has the most updated tree or
> if there are special differences between mtd's trees and vanilla's), and
> implemented the skeleton using the reiserfs xattr code base.
The mtd tree is the most current. Any development would probably get
the most benefit from being done there. Especially since JFFS3 doesn't
exist anywhere else :).
> In addition, having someone experienced with xattr API could be great,
> as development documentation seems inexistent, among James Morris'
> merged xattr consolidation code.
There have been some xattr proposals discussed on the MTD and JFFS2
mailing lists. They might be a starting place for you.
josh
next prev parent reply other threads:[~2005-02-22 18:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 16:17 Lorenzo Hernández García-Hierro
2005-02-22 18:21 ` Josh Boyer [this message]
2005-02-22 23:13 ` Lorenzo Hernández García-Hierro
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=1109096502.7813.5.camel@windu.rchland.ibm.com \
--to=jdub@us.ibm.com \
--cc=agruen@suse.de \
--cc=familiar-dev@handhelds.org \
--cc=familiar@handhelds.org \
--cc=handhelds@handhelds.org \
--cc=kernel-discuss@handhelds.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorenzo@gnu.org \
--cc=oe@handhelds.org \
--cc=rcoker@redhat.com \
--cc=selinux@tycho.nsa.gov \
/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®