Andy Polyakov <[EMAIL PROTECTED]> wrote:
> > I cannot speak for the sofware you used to look at the image.
>
> In other words you're implying that under no circumstances results
> obtained with software of my choice could be possibly right.
I cannot confirm your claims as I cannot see any hi
You used mkisofs incorrectly
Command line sequence was *tailored* to allow to produce usable input
for *hex editor* in less than minute.
Why did you use -C16,xxx?
This is definitely wrong.
The reason is in the beginning of merge_isofs() in multi.c. In
particular for (i=0;i<100;i++) loop. As ar
Joerg Schilling wrote:
Andy Polyakov <[EMAIL PROTECTED]> wrote:
You used mkisofs incorrectly
Command line sequence was *tailored* to allow to produce usable input
for *hex editor* in less than minute.
Why did you use -C16,xxx?
This is definitely wrong.
Andy Polyakov <[EMAIL PROTECTED]> wrote:
> > You used mkisofs incorrectly
> Command line sequence was *tailored* to allow to produce usable input
> for *hex editor* in less than minute.
> >>> Why did you use -C16,xxx?
> >>>
> >>> This is definitely wrong.
>
> The reason is in the be
You used mkisofs incorrectly
Command line sequence was *tailored* to allow to produce usable input
for *hex editor* in less than minute.
Why did you use -C16,xxx?
This is definitely wrong.
The reason is in the beginning of merge_isofs() in multi.c. In
particular for (i=0;i<100;i++) loop. As
Andy Polyakov <[EMAIL PROTECTED]> wrote:
> Exhibit #7. 'isoinfo -l -T -i /dev/dvd' output for same recording:
>
> Directory listing of /
> d- 000 2048 May 20 2008 [2621639 02] .
> d- 000 2048 May 20 2008 [2621639 02] ..
> -- 00
Bill Davidsen <[EMAIL PROTECTED]> wrote:
> > The second step will be to make retained multi-extent files correclty in
> > the
> > next session.
> >
> > If there is a remaining problem, lets see.
> >
> >
> I have no problem with following correct steps in order. I think there's
> a proble
Joerg Schilling wrote:
Bill Davidsen <[EMAIL PROTECTED]> wrote:
Only a setting up correct multi-extent file directory entry will work correctly.
I'm curious how you handle the case where the file shrinks and no longer
needs multi-extent. I hope that's clear, I don't have a better
Bill Davidsen <[EMAIL PROTECTED]> wrote:
> > Only a setting up correct multi-extent file directory entry will work
> > correctly.
> >
>
> I'm curious how you handle the case where the file shrinks and no longer
> needs multi-extent. I hope that's clear, I don't have a better
> description at
Joerg Schilling wrote:
Andy Polyakov <[EMAIL PROTECTED]> wrote:
You used mkisofs incorrectly
Command line sequence was *tailored* to allow to produce usable input
for *hex editor* in less than minute.
Why did you use -C16,xxx?
This is definitely wrong.
Why I ev
Andy Polyakov <[EMAIL PROTECTED]> wrote:
> >>> You used mkisofs incorrectly
> >> Command line sequence was *tailored* to allow to produce usable input
> >> for *hex editor* in less than minute.
> >
> > Why did you use -C16,xxx?
> >
> > This is definitely wrong.
>
> Why I even bothered to report
>>> You used mkisofs incorrectly
>> Command line sequence was *tailored* to allow to produce usable input
>> for *hex editor* in less than minute.
>
> Why did you use -C16,xxx?
>
> This is definitely wrong.
Why I even bothered to report this? To be told that I can't use
multi-sessioning options
Andy Polyakov <[EMAIL PROTECTED]> wrote:
> > You used mkisofs incorrectly
>
> Command line sequence was *tailored* to allow to produce usable input
> for *hex editor* in less than minute.
Why did you use -C16,xxx?
This is definitely wrong.
BTW: isoinfo gives you all information you need in ord
addresses for old files.
No. What apparently happens is following. As mkisofs -M reads 1st.iso it
runs across two directory records describing two extents of 5G.0. As it
pays no attention to ISO_MULTIEXTENT flag, it treats these two extents
as two files with same name. Then it discovers name confl
"Thomas Schmitt" <[EMAIL PROTECTED]> wrote:
> Hi,
>
> > 5G.0;1 0x804GB-2KB X
> > 5G.0;1 0x005GB-(4GB-2KB) X+0x20-1
>
> as an interested bystander i wonder how
> it is about general mountability of this
> image. Is this supported in contemporary
> Linux ?
A
Andy Polyakov <[EMAIL PROTECTED]> wrote:
> $ ./mkisofs -v
> mkisofs 2.01.01a39 ...
>
> Consider creating say 5GiB file and mastering an image:
>
> $ touch 5G.0
> $ perl -e 'truncate("5G.0",5*1024*1024*1024)'
> $ ./mkisofs -iso-level 3 5G.0 > 1st.iso
>
> One does not have to wait till mkisofs compl
>> 5G.0;1 0x804GB-2KB X
>> 5G.0;1 0x005GB-(4GB-2KB) X+0x20-1
>
> as an interested bystander i wonder how
> it is about general mountability of this
> image. Is this supported in contemporary
> Linux ?
Define "supported." Multi-extent files are recognized by
Hi,
> 5G.0;1 0x804GB-2KB X
> 5G.0;1 0x005GB-(4GB-2KB) X+0x20-1
as an interested bystander i wonder how
it is about general mountability of this
image. Is this supported in contemporary
Linux ?
Have a nice day :)
Thomas
--
To UNSUBSCRIBE, email to [EMA
$ ./mkisofs -v
mkisofs 2.01.01a39 ...
Consider creating say 5GiB file and mastering an image:
$ touch 5G.0
$ perl -e 'truncate("5G.0",5*1024*1024*1024)'
$ ./mkisofs -iso-level 3 5G.0 > 1st.iso
One does not have to wait till mkisofs completes, just press ctrl-c as
soon as progress indicator goe
JP> the -path-list option was added to version 1.12 and is in the v1.12 man page ...
http://www.fokus.gmd.de/research/cc/glone/employees/joerg.schilling/private/man/mkisofs-1.12.html
-path-list does not appear anywhere on *that* page - maybe it exists on *another* 1.12
page???
--
To UNSUBS
>From: Brian Perkins <[EMAIL PROTECTED]>
>JP> you can use the -path-list option.
>The only link I had for the mkisofs man page was to 1.12 and the
>"-path-list" option isn't there. When I tried to find it and couldn't, I
>became suspicious. I just found the 1.13 page and am very happy I sen
>The only link I had for the mkisofs man page was to 1.12 and the
>"-path-list" option isn't there. When I tried to find it and couldn't, I
>became suspicious. I just found the 1.13 page and am very happy I sent my
>post to this list.
Hmm, strange, although it's not that important - the -pat
My apologies!
JP> you can use the -path-list option.
The only link I had for the mkisofs man page was to 1.12 and the
"-path-list" option isn't there. When I tried to find it and couldn't, I
became suspicious. I just found the 1.13 page and am very happy I sent my
post to this list.
Much o
>At this point, I just want to create a single session image file. But, not
>all the files will exist in the same directory and they will be small and
>numerous.
Can't see the problem - mkisofs will allow you to have multiple source
directories on the command line. If you have lots of source dir
Hi James,
Thanks for the quick reply! (And... YES, it does help!)
However, it raises a new question...
Just how *DO* I append files to an existing ISO image session?
JP>mkisofs does not write anything to a CD.
Thanks, but I don't recall saying anything about writing to a CD... yet.
;~)
At
>Can someone clarify the use of the "-M" switch please?
>
>Does the "-M" option append files/directories to the existing session in the sp
>ecified ISO image?
>Or, does it append a new session for the output image?
>
>The man page appears to be saying the first, but isn't entirely clear.
The last
Hello,
Can someone clarify the use of the "-M" switch please?
Does the "-M" option append files/directories to the existing session in the specified
ISO image?
Or, does it append a new session for the output image?
The man page appears to be saying the first, but isn't entirely clear.
Thx,
Br
27 matches
Mail list logo
