From: Luis de Bethencourt <luisbg@osg.samsung.com>
To: Theodore Ts'o <tytso@mit.edu>,
Greg KH <gregkh@linuxfoundation.org>,
Linux Kernel <linux-kernel@vger.kernel.org>,
Andrew Morton <akpm@linux-foundation.org>,
Al Viro <viro@ZenIV.linux.org.uk>,
Salah Triki <salah.triki@acm.org>,
Javier Martinez Canillas <javier@osg.samsung.com>,
Richard Weinberger <richard@nod.at>,
linux-fsdevel@vger.kernel.org
Subject: Re: Volunteering for BeFS maintainership
Date: Wed, 27 Jul 2016 12:45:36 +0100 [thread overview]
Message-ID: <57989EE0.9070003@osg.samsung.com> (raw)
In-Reply-To: <20160727030551.GD9284@thunk.org>
On 27/07/16 04:05, Theodore Ts'o wrote:
> On Tue, Jul 26, 2016 at 09:30:13PM +0100, Luis de Bethencourt wrote:
>>>
>>> Sounds great! Do you have a git tree set up for your befs development?
>>
>> Yes, I have the following in github (if that is OK):
>> https://github.com/luisbg/linux-befs
>>
>> I have two branches there based on Linus' master:
>> - befs-linus: with patches Andrew Morton has approved
>> - befs-next: with patches I've tested but that remain under review
>
> So it sounds like you plan to send patches through Andrew's tree.
Not sure. Whatever Andrew, Al, Greg and yourself think is better.
> That works fine, although if you end up sending a larger number of
> patches through the linux-mm tree, it might make sense for you to send
> patches to Linus directly. So if you have a chance to get a GPG key
> which is signed by people in the Kernel keyring, that would be a good
> preparation for that eventuality. That will require face-to-face
> verification of your identity by people who are already in the GPG web
> of trust, so it's good to plan for that in advance.
I will be at ELCE in 3 months [0]. It will be a good opportunity to get my
GPG key signed by people in the Kernel keyring. For example Maxime Ripard,
who is one of the speakers and in the GPG web of trust [1].
>
>> It would be amazing to have a framework to run xfstests in a GCE VM.
>
> Please see:
>
> https://thunk.org/gce-xfstests
>
> and
>
> https://github.com/tytso/xfstests-bld/blob/master/README.md
>
> for more information.
Very nice. Looking forward to playing with it soon, and adding it to my
development process. I have learned a lot reading the ext4 code so I am
also interested in running the test suite with that.
>
> I plan to do some work to make it simpler to get started using
> gce-xfstests. (Specifically, so you don't have to build the tree and
> generate your own GCE image, but instead using a premade one.)
I will watch out for updates on this on fstests@vger.
>
> Are there userspace tools available to create and consistency check
> BeFS file systems? If so, I can try to get those included into the
> test appliance image. (Better yet, if you can arrange to have someone
> create a debian package for BeFStools, that would be great.)
>
> - Ted
Support for BeFS in Linux is read-only. So there are no tools to create
BeFS file systems. I have a bunch of BeFS images created from Haiku OS
that cover most things.
There is no reason a consistency check tool can't be written. I think this
could be a fun exercise, I am tempted to add it to my task list :)
However this tool can only inform if the file system is consistent, and not
really fix it. Similar to "e2fsck -n".
Salah told me he is planning to slowly work on adding read support in the
future. But don't want to make any promises/plans on his behalf.
Thanks,
Luis
[0] http://events.linuxfoundation.org/events/embedded-linux-conference-europe/program/schedule
[1] https://www.kernel.org/doc/ksmap/
next prev parent reply other threads:[~2016-07-27 11:45 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-25 17:21 Volunteering for BeFS maintainership Luis de Bethencourt
2016-07-25 21:23 ` Greg KH
2016-07-25 23:16 ` Luis de Bethencourt
2016-07-26 17:56 ` Theodore Ts'o
2016-07-26 20:30 ` Luis de Bethencourt
2016-07-27 3:05 ` Theodore Ts'o
2016-07-27 11:45 ` Luis de Bethencourt [this message]
2016-07-27 13:23 ` Theodore Ts'o
2016-07-27 14:39 ` Luis de Bethencourt
2016-07-27 2:01 ` Salah Triki
2016-07-26 23:54 ` Salah Triki
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=57989EE0.9070003@osg.samsung.com \
--to=luisbg@osg.samsung.com \
--cc=akpm@linux-foundation.org \
--cc=gregkh@linuxfoundation.org \
--cc=javier@osg.samsung.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@nod.at \
--cc=salah.triki@acm.org \
--cc=tytso@mit.edu \
--cc=viro@ZenIV.linux.org.uk \
/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).