From: Jeff Mahoney <jeffm@novell.com>
To: Piotr Neuman <sikkh@wp.pl>
Cc: reiserfs-list@namesys.com
Subject: Re: Participation in developement of Reiser4
Date: Wed, 03 Nov 2004 12:10:30 -0500 [thread overview]
Message-ID: <41891106.3000600@novell.com> (raw)
In-Reply-To: <200411022342.02126.sikkh@wp.pl>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Piotr Neuman wrote:
| Hello
|
| I'm looking for some intresting projects to devote my spare time to.
Reiser v4
| is a very promising one, so I would like to ask wheter there are some
tasks
| that a relative newbie in kernel programming like me could do.
Something like
| kernel-janitor like tasks maybe (code cleanup) or maybe reiser4 tools.
|
| I'm a bit familiar with linux VFS if that can help (I did some work on
User
| Mode Linux filesystem called humfs).
|
| I hope I could help...
|
| Regards
|
| Piotr Neuman
|
| ps. I know I could just start making patches to reiser4 and send them
right to
| namesys.com but I don't know where to start/what to do ;-)
|
Well, this is the same advice that applies to everybody looking to
participate in any project. Find something that bothers you, and try to
fix it. The list will be happy to take a look at your patches and give
you pointers on how to improve them. The best way to learn is through
experience.
All I can really give you as far as more specific advice is things I'd
like to see done with reiser4. The most obvious one, and one that should
be a fairly easy place to start, is to add support for the existing
xattr API to manipulate attributes that reiser4 currently provides under
the ..metas "meta-directory." The ..metas directory is quite
contraversial, and I'd hate to see reiser4 fall by the wayside because
it doesn't support a standard API.
If this feature is already implemented, I apologize, I haven't been
following reiser4 development too closely.
As a note to Hans, who I expect will object strenuously to this email,
the issue of the elegance of the files-as-directories approach that
reiser4 users is a debate that will not likely be concluded any time
soon. I think the best thing for reiser4 to do is to cater to its users.
Many users will disable the files-as-directories support because it does
cause conflicts with existing apps. Whether that makes those apps
"buggy" or not is irrelevant: Users will just use another filesystem
rather than bug their favorite software author to adjust to a situation
that no other filesystem presents. Users that want to use the ..metas
approach are free to do so. To quote something that borders on trite
these days, "Since when does Linux eliminate choice?"
- -Jeff
- --
Jeff Mahoney
SuSE Labs
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFBiRAZLPWxlyuTD7IRAiWiAJ9aQczwp0IafGefLwloral7Q8E2bACfSyjj
ckxTYV0AFS1cQS/z1WsGVaI=
=Se78
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2004-11-03 17:10 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-02 22:42 Participation in developement of Reiser4 Piotr Neuman
2004-11-03 17:10 ` Jeff Mahoney [this message]
2004-11-03 17:19 ` Hans Reiser
2004-11-03 19:58 ` Jeff Mahoney
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=41891106.3000600@novell.com \
--to=jeffm@novell.com \
--cc=reiserfs-list@namesys.com \
--cc=sikkh@wp.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.