From: Pat LaVarre <p.lavarre@ieee.org>
To: linux_udf@hpesjro.fc.hp.com
Cc: linux-kernel@vger.kernel.org
Subject: UDF status
Date: 12 Aug 2004 13:28:31 -0600 [thread overview]
Message-ID: <1092338911.4207.25.camel@patlinux.iomegacorp.com> (raw)
UDF "Development Status" remains "5 - Production/Stable" but includes
the following new issues, now recorded at:
http://sourceforge.net/projects/linux-udf
http://sourceforge.net/tracker/?group_id=295&atid=100295
To fix these we need volunteers able to write patches, of course.
People with less expertise can work to make any of these more plainly
reproducible, e.g. by writing a demo test script.
--- hi priority
1008156 multi-session starts where
1008134 holes above 1 GiB
--- medium priority
1008140 files above 2 GiB
--- low priority
1008188 big-endian mkudffs goes boom
1008152 fsck fails after mkfs
1008186 fsck fails after shrink
1008131 lookup vs. wide chars
1008176 mkudffs does not read and compare
1008174 mkudffs option= help not given
1008172 mkudffs not interoperable by default
1008162 -o lastblock= needed to mount bootable ISO/UDF
1008184 phgfsck chokes over /dev/scd$n
---
Pat LaVarre
http://udfko.blog-city.com/read/585696.htm
reply other threads:[~2004-08-12 19:29 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1092338911.4207.25.camel@patlinux.iomegacorp.com \
--to=p.lavarre@ieee.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_udf@hpesjro.fc.hp.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
all inboxes | Powered by JetHome®