linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steve Kenton <skenton@ou.edu>
To: Ken Moffat <zarniwhoop@ntlworld.com>,
	Randy Dunlap <rdunlap@infradead.org>
Cc: linux-kernel@vger.kernel.org, Robert Howard <bob@bcdusa.com>,
	Jan Kara <jack@suse.com>
Subject: Re: fs/udf and udftools
Date: Wed, 10 Feb 2016 21:45:05 -0600	[thread overview]
Message-ID: <56BC03C1.2010802@ou.edu> (raw)
In-Reply-To: <20160211021906.GB32580@milliways>

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.

>>
>> 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.

>>
> A bit of googling for udftools suggests that gentoo are maintaining
> their build, debian have patches for gcc-4 and gcc-5 among others,
> Fedora have their own patches, and Arch have some patches (which
> might be the same as some of hte others, I did not look).
> 
> Looks like the normal "possibly abandonned, but still useful to some
> people" software, where distros keep it building.

Yep, that's where my ~works came from.
Ah, thanks for the links. I'll pull them all together and see what's there.

smk

> 
> There may also be others.
> 
> Links -
> 
> https://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo-x86/sys-fs/udftools/ChangeLog?view=markup
> 
> https://launchpad.net/debian/+source/udftools/+changelog
> 
> http://pkgs.fedoraproject.org/cgit/rpms/udftools.git/tree/
> 
> https://aur.archlinux.org/packages/udftools/
> 
>>
>>> I'm having to dig into fs/udf and udftools/mkudffs as part of a project I'm working on.
>>> It looks like both have been lacking in personal TLC for quite a while. The changes to
>>> fs/udf seem to be tree wide VFS work but not updates to things like write support and
>>> udftools seems to have been frozen for >10  years. Both ~work but I'd like to fix an
>>> oops I'm getting in udftools and work on adding fallocate() support to fs/udf and then
>>> feed it back to the community rather than let the changes bit rot locally.
>>>
>>> Where to go from here? I've been reading LKML on marc: for years, mainly to see what Linus,
>>> Al and a variable group of other people say/do but I've never done more than tinker with
>>> the kernel locally. I'm using git for the project mentioned above but again am not an
>>> expert but willing to learn. I'm not currently subscribed so please cc me if you could.
>>>
>>> smk
>>>
>>
>>
>> -- 
>> ~Randy
> 

  reply	other threads:[~2016-02-11  3:45 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 [this message]
2016-02-11 10:03       ` Jan Kara
2016-02-11 15:30         ` Steve Kenton

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=56BC03C1.2010802@ou.edu \
    --to=skenton@ou.edu \
    --cc=bob@bcdusa.com \
    --cc=jack@suse.com \
    --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 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).