From: "Lorenzo Hernández García-Hierro" <lorenzo@gnu.org>
To: familiar-dev@handhelds.org, selinux@tycho.nsa.gov,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Cc: familiar@handhelds.org, handhelds@handhelds.org,
kernel-discuss@handhelds.org, oe@handhelds.org, agruen@suse.de,
Russell Coker <rcoker@redhat.com>
Subject: JFFS2 Extended attributes support & SELinux in handhelds
Date: Tue, 22 Feb 2005 17:17:19 +0100 [thread overview]
Message-ID: <1109089039.4100.114.camel@localhost.localdomain> (raw)
[-- Attachment #1: Type: text/plain, Size: 1454 bytes --]
Hi,
I've been working in implementing extended attributes support in the
JFFS2 filesystem.
During the (short) time I worked on it, I just decided to try to bring
back the thread on SELinux in hand-held and embedded devices and see if
there's someone interested in contributing to it and collaborating to
make something out of it.
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.
Then Russell Coker commented to me that I should use the handhelds.org
kernel, so, I have the doubt on which one use, even if porting the
changes made to JFFS2 code base to vanilla sources wouldn't be
difficult, at least I suppose.
I've opened a few wiki pages for discussion and documenting until it
gets further developed:
http://wiki.tuxedo-es.org/tuxedo/JFFS2xattr
http://wiki.tuxedo-es.org/tuxedo/SELinuxEmbedded
In addition, having someone experienced with xattr API could be great,
as development documentation seems inexistent, among James Morris'
merged xattr consolidation code.
Thanks in advance,
Cheers.
--
Lorenzo Hernández García-Hierro <lorenzo@gnu.org>
[1024D/6F2B2DEC] & [2048g/9AE91A22][http://tuxedo-es.org]
[-- Attachment #2: Esta parte del mensaje está firmada digitalmente --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next reply other threads:[~2005-02-22 16:17 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 [this message]
2005-02-22 18:21 ` Josh Boyer
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=1109089039.4100.114.camel@localhost.localdomain \
--to=lorenzo@gnu.org \
--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=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®