Hey folks,
I had an earlier post where I thought this was a k3b problem, and I thought I fixed it.
I THOUGHT the new k3b was working...but after that first test, things soured. I kept getting this message:
Read error on old image
So I'm posting this in a new thread, as it seems to be an mkisofs problem.
I went back to the CLI and installed the most recent cdrtools, 2.01.01a26. And again, I THOUGHT I got mkisofs so I could burn multiple sessions. But now I'm finding that after one, maybe two sessions, I get that error again. Why can't it read the old image?
Here are the mkisofs commands I use:
For the first session:
Code:
mkisofs -vv -f -r -l -posix-L -J -o ~/backup.iso ./burndir
For subsequent sessions:
Code:
mkisofs -dev /dev/hdc -C 46939,71005 -prev-session /dev/hdc -vv -f -r -l -posix-L -J -o ~/backup.iso ./burndir
Where 46939,71005 is the output frome
Code:
cdrecord dev=/dev/hdc -msinfo
The only other difference is that I use a full path for backup.iso an
burndir.
So do these commands look faulty?
I'm using Slack 11, with a 2.6 kernel. Every time, cdrecord complains
about the 2.6 and suggests a 2.4; anyone else had trouble with Slack
11 and 2.6?
Oh, and here's ~/.mkisofsrc:
PUBL=Bill Powell, billpowellisalive.com
SYSI=Slackware Linux
I don't think it's the hardware; on previous iterations of Slack, I'd
burn multisession CDs all the time. I didn't pass those exact
parametrs to mkisofs, but they were quite similar.
Thanks for any advice!
