From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Subject: Re: editable udf metadata
Date: 21 Oct 2003 15:54:26 -0600 [thread overview]
Message-ID: <1066773266.2888.83.camel@patehci2> (raw)
In-Reply-To: <1065635511.7602.38.camel@patehci2>
[ BC linux_udf@hpesjro.fc.hp.com ]
> The web trail I know to the udfct_1_0r2 tool is:
>
> http://www.google.com/search?q=philips+udf+verifier
> http://www.google.com/search?q=philips+udf+verifier&btnI=1
> http://www.extra.research.philips.com/udf/
> http://www.extra.research.philips.com/udf/download.html
>
> I see udfct_1_0r2 describes itself as designed to work in Win 9X/ME.
>
> I see compiling a wnaspi32.dll (e.g. via the wnaspi32.cpp for mingw gcc
> attached) makes udfct_1_0r2 work in Win 2K/XP too.
>
> I'm told Linux udfct_1_0r2 as yet works only on disk images ...
I saw this claim kindly challenged here, I'm now beginning to believe
the challenge. I have now found:
http://www.extra.research.philips.com/udf/download/udfct_1_0r2.tar.gz
FAQ.TXT
Binaries with SCSI/Atapi support are only present for Windows and Linux
Possibly I was just remembering udfct as yet another example of a lab
tool that chokes because Mac OS X has no root-privileged SCSI pass thru.
Pat LaVarre
next prev parent reply other threads:[~2003-10-21 21:54 UTC|newest]
Thread overview: 36+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-07 19:02 zeroes read back more often than appended Pat LaVarre
2003-10-07 20:54 ` Pat LaVarre
2003-10-08 3:49 ` Ben Fennema
2003-10-08 16:41 ` Pat LaVarre
2003-10-08 16:47 ` editable udf metadata Pat LaVarre
2003-10-08 17:51 ` Pat LaVarre
2003-10-08 18:09 ` big-endian udfct_1_0r2 Pat LaVarre
2003-10-08 18:30 ` Matthew Wilcox
[not found] ` <3F8472FE.9040403@lougher.demon.co.uk>
2003-10-08 19:49 ` Matthew Wilcox
2003-10-08 20:43 ` Phillip Lougher
2003-10-21 21:54 ` Pat LaVarre [this message]
2003-10-21 23:17 ` editable udf metadata Pat LaVarre
2003-10-23 16:06 ` Pat LaVarre
2003-10-24 21:40 ` Pat LaVarre
2003-10-22 8:15 ` same page access Mark B
2003-10-22 11:21 ` Matthew Wilcox
2003-10-22 17:09 ` Mark B
2003-10-22 17:10 ` Matthew Wilcox
2003-10-08 17:02 ` zeroes read back more often than appended Pat LaVarre
2003-10-08 17:06 ` toggling smp clears x86_mce_p4thermal of make xconfig Pat LaVarre
2003-10-08 17:21 ` zeroes read back more often than appended Pat LaVarre
2003-10-08 16:46 ` soft trace of read/write of drivers/block/loop.c Pat LaVarre
2003-10-08 20:32 ` zeroes read back more often than appended Pat LaVarre
2003-10-09 20:54 ` Pat LaVarre
2003-10-10 0:52 ` Pat LaVarre
2003-10-10 16:39 ` Pat LaVarre
2003-10-10 18:15 ` Pat LaVarre
2003-10-14 0:38 ` Pat LaVarre
2003-10-14 1:48 ` Pat LaVarre
2003-10-20 23:20 ` Pat LaVarre
2003-10-21 14:47 ` Pat LaVarre
2003-10-21 16:46 ` Pat LaVarre
2003-10-21 18:44 ` Pat LaVarre
2003-10-23 18:52 ` Pat LaVarre
2003-10-27 21:55 ` Pat LaVarre
-- strict thread matches above, loose matches on Subject: below --
2003-11-26 15:58 editable udf metadata Pat LaVarre
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=1066773266.2888.83.camel@patehci2 \
--to=p.lavarre@ieee.org \
--cc=linux-fsdevel@vger.kernel.org \
/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.