From: Pat LaVarre <p.lavarre@ieee.org>
To: linux-fsdevel@vger.kernel.org
Subject: Re: Fwd: udf folders pointing to self and above
Date: 23 Oct 2003 12:35:02 -0600 [thread overview]
Message-ID: <1066934102.2276.180.camel@patehci2> (raw)
In-Reply-To: <1066876910.9105.145.camel@patehci2>
Solved! Indeed, solved by "use cvs udftools", precisely as hinted.
Thank you all.
Pat LaVarre
P.S. A tty log of the contrast follows ...
> > $ sudo udf_test /dev/loop0 | grep -i -B 1 -A 7 'error:'
> > EFE file type DIR name: "lost+found"
> > EFE 28 icbtag error: parentICBLocation: (3,0),
> > - recommended: (0,0) for strategy type 4.
> > - Icbtag Parent ICB Location shall not point to itself
> > - or to a higher parent in the directory hierarchy.
> > - ECMA 3rd edition 4/8.10.1, 4/14.6.7, UDF 2.3.5.3.
> > - icbtag: ECMA 4/14.6.*, 4/A.5, UDF 2.3.5.*, 6.6
> > - name: "lost+found"
> > EFE 216 Embedded data, 40 bytes
>
> Versus the 2002 Feb 9 1.0.0b2 udftools of
> sourceforge, I yield 2643 lines of diff -ur
> if I try:
>
> % setenv CVSROOT :pserver:anonymous@cvs.sourceforge.net:/cvsroot/linux-udf
$ find `which mkudffs` -printf '%l\n'
.../udftools-cvs/mkudffs/mkudffs
$
$ sudo losetup /dev/loop0 dd.bin
$
$ sudo mkudffs --udfrev=0x0102 /dev/loop0
$
$ sudo udf_test /dev/loop0 -udf 1.02 | egrep -i '(error|warning|note):'
$
$ sudo udf_test /dev/loop0 -udf 1.02 | egrep -i 'final udf rev'
Final UDF Revision range: 1.02 only
$
next prev parent reply other threads:[~2003-10-23 18:35 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-21 23:37 Fwd: udf folders pointing to self and above Pat LaVarre
2003-10-22 13:25 ` Pat LaVarre
2003-10-23 1:04 ` Pat LaVarre
2003-10-23 2:41 ` Pat LaVarre
2003-10-23 18:35 ` Pat LaVarre [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-10-23 4:31 Steve Jobs
2003-09-29 21:53 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=1066934102.2276.180.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox