From: Steve Kenton <skenton@ou.edu>
To: Jan Kara <jack@suse.cz>
Cc: Ken Moffat <zarniwhoop@ntlworld.com>,
Randy Dunlap <rdunlap@infradead.org>,
linux-kernel@vger.kernel.org, Robert Howard <bob@bcdusa.com>,
Jan Kara <jack@suse.com>
Subject: Re: fs/udf and udftools
Date: Thu, 11 Feb 2016 09:30:36 -0600 [thread overview]
Message-ID: <56BCA91C.1090401@ou.edu> (raw)
In-Reply-To: <20160211100352.GB21760@quack.suse.cz>
On 02/11/2016 04:03 AM, Jan Kara wrote:
> On Wed 10-02-16 21:45:05, Steve Kenton wrote:
>> On 02/10/2016 08:19 PM, Ken Moffat wrote:
>>> On Wed, Feb 10, 2016 at 05:56:16PM -0800, Randy Dunlap wrote:
>>>> [add Jan Kara]
>>>>
>>>> On 02/10/16 13:29, Steve Kenton wrote:
>>>>> Is anyone maintaining these or am I about to volunteer for another job?
>>
>> I guess I should have said "developing" rather than "maintaining" for
>> fs/udf since it's clear that someone has been keeping it running in-tree.
>> I started with udftools from source forge and then discovered that the
>> kernel udf driver does not support fallocate() which I was hoping to use.
>>
>> Thanks for the pointer to Jan Kara. I'll see how he feels about patches
>> from the wilderness.
>
> So I don't have too much time for UDF. That's why I mostly fix bugs someone
> reports, occasionally improve stuff or review patches others send but I
> don't have time for development of new features for UDF.
OK, I'll see what I can do and try not to bother you until stuff is working well.
>
>>>> CUrrent MAINTAINERS file says:
>>>>
>>>> UDF FILESYSTEM
>>>> M: Jan Kara <jack@suse.com>
>>>> S: Maintained
>>>> F: Documentation/filesystems/udf.txt
>>>> F: fs/udf/
>>>>
>>>> and that Doc. file says:
>>>>
>>>> For the latest version and toolset see:
>>>> http://linux-udf.sourceforge.net/
>>
>> Yes, that's where I started. The last release was 1.0.0b3 in 2004.
>> Which is what the Ubuntu 14.04LTS package reports as it's version too.
>
> Pali Rohar has recently startted a repo on github for udftools. It is at
> https://github.com/pali/udftools
>
> So userspace patches go to him.
Perfect! All of my googling pointed to source forge but this is what I was hoping for.
smk
>
> Honza
>
prev parent reply other threads:[~2016-02-11 15:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-10 21:29 fs/udf and udftools Steve Kenton
2016-02-11 1:56 ` Randy Dunlap
2016-02-11 2:19 ` Ken Moffat
2016-02-11 3:45 ` Steve Kenton
2016-02-11 10:03 ` Jan Kara
2016-02-11 15:30 ` Steve Kenton [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=56BCA91C.1090401@ou.edu \
--to=skenton@ou.edu \
--cc=bob@bcdusa.com \
--cc=jack@suse.com \
--cc=jack@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@infradead.org \
--cc=zarniwhoop@ntlworld.com \
/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.