From: Stelian P. <st...@po...> - 2004-12-20 15:02:48
|
On Mon, Dec 20, 2004 at 09:01:53AM -0500, David Gesswein wrote: > > Personnaly I don't directy use a fifo but dump into a temp > > file which I burn afterwards, and this always worked for me. I don't > > see how this could change something for you but still, you may want > > to try it. > > > Do you then burn it as an ISO file system so the file you are duming > shows up as a file on the CD? If so thats the difference. No, I burn as the dump as an ISO image, which will get automatically padded by cdrecord to the multiple of the cd block size (I guess). >> The cdrecord > method I used is writing raw data so you can't mount it. The -pad adds > extra 0's to the end of the track so dump will read extra data. If you > are writing it as a file it will be read as the correct length. > > Can dumps data structure deal with finding extra junk at the end of a volume? > If not I don't see how the method I used based on the example could work. That's what the restore -V option is there for. Correction: looking at the source I see that -V is used only when reading multi-volume *compressed* dumps (and indeed, this is what I use myself). I wonder whether uncompressed dumps need a special treatement or not... > > I will also look at the shunt program suggested. > > > Anther thing you could try is extracting with 'restore -rf' instead > > of the interactive mode. The code is a bit different, maybe there > > is something there. > > > Does this really need a clean partition? No, a clean directory only, it will extract all the dump into the current directory. Stelian. -- Stelian Pop <st...@po...> |