Hi,
Jonathan Dowland sent me the URL of a test image which demonstrates
the problem with reading ISO 9660 images not produced on Linux.
Indeed the problem appears when reading the Rock Ridge info of the
root directory. So xorriso-1.4.6 in Debian testing cannot avoid it.
The root directory recor
Hi,
Jonathan Dowland wrote:
> But digging into this a little, it seems to be an argument order issue.
Yes, sequence matters. The arguments are commands like in a shell script,
not options like with program "ls".
There is command -x which lets xorriso sort the arguments in a sequence
that is most
On Wed, Nov 23, 2016 at 03:40:22PM +, Jonathan Dowland wrote:
> But digging into this a little, it seems to be an argument order issue.
...and all of my ISOs now read fine without the RR warnings. I haven't
double-checked
the docs, if you state that the argument order of -read_fs / -indev is
On Fri, Nov 18, 2016 at 05:27:25PM +0100, Thomas Schmitt wrote:
> $ gdb xorriso/xorriso
> (gdb) b fs_image.c:3024
> (gdb) b rockridge_read.c:111
> (gdb) r -read_fs norock -indev /path/to/your.iso
Using the above and one of the UDF images that I am about to email you a URL to,
and the above
On Tue, Nov 22, 2016 at 09:46:16PM +0100, Thomas Schmitt wrote:
> If they demonstrate the Rock Ridge read error despite -read_fs "norock",
> then they might help to solve the riddle.
Yes the do. I'm just about to mail you privately with a URL to one.
signature.asc
Description: Digital signature
Hi,
i wrote about video DVDs:
> > That's probably UDF filesystems. Interesting anayways.
Jonathan Dowland wrote:
> Good catch: you are right, they are. Are they interesting enough for me to
> put them online somewhere?
If they demonstrate the Rock Ridge read error despite -read_fs "norock",
then
On Fri, Nov 18, 2016 at 05:27:25PM +0100, Thomas Schmitt wrote:
> If you got the GNU xorriso tarball, then it is not linked dynamically
> with installed libisofs.so but rather statically with its own copy of
> libisofs.
OK, yup that's what I did.
> In the build directory
>
> $ xorriso/xorriso
Hi,
i wrote:
> > Was that already with -read_fs "norock" ?
Jonathan Dowland wrote:
> Just retried: alas, no difference
> ...
> libisofs: SORRY : Damaged RR/SUSP information.
It should not even get near to that error message.
Grrr ...
> I'm wondering if my hand-built modern xorriso is l
On Fri, Nov 18, 2016 at 03:29:54PM +, Jonathan Dowland wrote:
> I'm wondering if my hand-built modern xorriso is linking against my old
> system libisofs.
> I am doing some investigation.
I can't see any .so files in my xorriso build directory, but ldd does not show
this xorriso
binding agai
On Thu, Nov 10, 2016 at 07:39:22PM +0100, Thomas Schmitt wrote:
> Hi,
>
> > Interestingly 1.4.7 can read one more of these ISOs, leaving 19 bad.
>
> Was that already with -read_fs "norock" ?
Just retried: alas, no difference, same number of unreadable ISOs (19), same
output, here's the full outp
On Thu, Nov 10, 2016 at 07:39:22PM +0100, Thomas Schmitt wrote:
> > Interestingly 1.4.7 can read one more of these ISOs, leaving 19 bad.
>
> Was that already with -read_fs "norock" ?
No, I didn't try that yet; I'll try that when I next take a look (probably
Monday). Thanks for the suggestion!
>
Hi,
> Interestingly 1.4.7 can read one more of these ISOs, leaving 19 bad.
Was that already with -read_fs "norock" ?
If so: Do you still see the error message
"Damaged RR/SUSP information."
?
> With 1.3.2 and this ISO in particular, it said
>libisofs: SORRY : Mandatory Rock Ridge PX entr
On Thu, Nov 10, 2016 at 11:56:36AM +, Jonathan Dowland wrote:
> On Thu, Nov 10, 2016 at 11:35:02AM +, Jonathan Dowland wrote:
> > I'll try the following command with both my current xorriso version and
> > 1.4.6,
> > against all of my currently imported ISOs, and report back what my result
On Thu 10 Nov 2016 at 15:21:42 +0100, Thomas Schmitt wrote:
> Hi,
>
> two hours ago, i sent the mail below as reply to
> https://lists.debian.org/debian-user/2016/11/msg00355.html
> Subject line was:
> LDO_SUBSCRIBER, was Re: xorriso: listing files+offsets in an IS
On Thu, Nov 10, 2016 at 03:21:42PM +0100, Thomas Schmitt wrote:
> My mails (and those of most other regular posters) have it in their
> X-Spam-Status when they arrive in my mailbox something like:
...
> The word "LDOSUBSCRIBER" seems to be the indication for a sunscribed
> sender.
...
> My best the
Hi,
two hours ago, i sent the mail below as reply to
https://lists.debian.org/debian-user/2016/11/msg00355.html
Subject line was:
LDO_SUBSCRIBER, was Re: xorriso: listing files+offsets in an ISO9660 image
w/o RockRidge
Date: Thu, 10 Nov 2016 12:59:10 +0100
But it did not arrive in my
Hi,
i have now uploaded
http://www.gnu.org/software/xorriso/xorriso-1.4.7.tar.gz
for testing of improved xorriso command -read_fs "norock".
Have a nice day :)
Thomas
Hi,
Jonathan Dowland wrote:
> 4 Application:
> 1 Application:
> ...
> The first one is completely empty labels. The second is roughly 64
> whitespace characters.
Looks like an interesting collection.
It would be nice if libisofs could exercise with it.
I am in the process of te
On Thu, Nov 10, 2016 at 11:35:02AM +, Jonathan Dowland wrote:
> I'll try the following command with both my current xorriso version and 1.4.6,
> against all of my currently imported ISOs, and report back what my results
> are:
With 1.3.2, at least, only 20/45 of my ISOs fail; the Application l
On Wed, Nov 09, 2016 at 02:29:25PM +0100, Thomas Schmitt wrote:
> I would be interested to examine such an ISO, if privacy permits.
Thanks for the offer!
Once I've narrowed down which of my ISOs suffer this problem, I'll see
which are not too private, some are basically just "Downloads" folders
f
Hi Thomas, thanks for replying!
On Wed, Nov 09, 2016 at 02:02:48PM +0100, Thomas Schmitt wrote:
> your mail headers do not contain "LDO_SUBSCRIBER", so i Cc: you.
I've never heard of LDO_SUBSCRIBER, but I am subscribed - no need to CC
me. (I put something like that in my signature to make things
Partially answering my own question, "iso-info" from the libcdio-utils
package prints out the Logical Sector Number for files which is probably
what I need, at least it can be translated into the Logical Block Address,
I just need to figure out mapping the numbers from ddrescue's log files
into tha
Hi,
regrettably the ban on reading Rock Ridge gets not into effect before
the attempt to read the SUSP entries of the root directory record.
So if that chain is damaged, then one would have to hack the source code:
-
--- libi
Hi,
it looks like
-read_fs norock
with xorriso >= 1.4.2 gives hope to circumvent the error message.
It will go for the Joliet tree, if present, as would do "isoinfo -J".
If you want the dull ISO names in any case: -read_fs ecma119
-
Hi,
your mail headers do not contain "LDO_SUBSCRIBER", so i Cc: you.
Jonathan Dowland wrote:
> [xorriso] seems to always complain about missing RR records:
> [...]
> xorriso -indev disk.iso -rockridge off -error_behavior image_loading
best_effort -abort_on NEVER -find . -exec report_lba
> libisof
Hi,
I'm trying to map files within ISO9660 images to block offsets within the
image. This is to try and determine which files are impacted by damaged or
missing blocks in the images.
These are all images of home made CD-rs and DVD-Rs from over the last 17 or so
years. I am importing them via ddre
On Tue, Nov 11, 1997 at 03:22:44PM -0600, [EMAIL PROTECTED] wrote:
> Is it possible to somehow mount an iso9660 image file that was
> made with the mkisofs package? I'd like to check out what was
> actually put in the image before doing a CD burn. Even a non-Linux
> solutio
[EMAIL PROTECTED] writes:
> Is it possible to somehow mount an iso9660 image file that was
> made with the mkisofs package? I'd like to check out what was
> actually put in the image before doing a CD burn. Even a non-Linux
> solution might be useful.
I believe that this
On Tue, 11 Nov 1997 [EMAIL PROTECTED] wrote:
> Is it possible to somehow mount an iso9660 image file that was
> made with the mkisofs package? I'd like to check out what was
> actually put in the image before doing a CD burn. Even a non-Linux
> solution might be useful.
Hello!
Is it possible to somehow mount an iso9660 image file that was
made with the mkisofs package? I'd like to check out what was
actually put in the image before doing a CD burn. Even a non-Linux
solution might be useful.
Ri
I will upload 1.3 images created using the debian-cd package on June 2.
I'll probably use Novare as their distribution site - 1.2 GB is a bit
large to propogate to all of the mirrors.
The response to early prototypes at Pixar has been "I love my Debian system".
Bruce
--
Bruce Perens K6BP
-BEGIN PGP SIGNED MESSAGE-
Just curious. Is the "well designed" cdrom image going to be made
available still? I'm going to burn a copy of 1.3 in the next week or
so and I'd much prefer to use a pre-built image simply because it will
be more reliably arranged than anything I could make my
32 matches
Mail list logo
