Re: Remastering of 64-bits version: Trouble with isofs? Huge .rr_mved
On Sun, Jul 17, 2011 at 09:53:37PM +0000, Capri Corny wrote:
> Thanks for the reply!
>
> I'll copy them and use much the� same parameters as you do, but I prefer
> not to use a pipe - it seems to me that remastering of large images goes
> better without. The parameters are not relevant for the problem at hand,
> though.
>
> I have worked more on it, and now I think it is a 64/32 problem, maybe
> with aufs or cloop.� No isofs problems are apparent, and I haven't done
> anything exceeding the capabilities of isofs, either.
But both aufs and cloop work fine with 64-bit. You can boot Knoppix with
linux64, can't you? ;-)
> I have checked my method on large and small images, also created the
> images from 32-bits system, same error every time.� To see if this was a
> problem with the method or remastering from HD install, I tried the method
> on a HD install from CD - everything worked fine, so it is not the method,
> or starting from HD install.
>
> To clarify, I have no need for creating DVD iso of my remasterings until
> they are, eventually, "finished" - they reside on hard disk partitions and
> USB media, and I will do the splitting exercise only when I am more sure
> about the content.� I don't have to cater for FAT32 needs either, if I
> don't want to.� So file size isn't very important.
>
> Can it be that the 64-bits kernel is set up with 32-bits aufs module, and
A 32bit aufs or cloop module would not even load with a 64-bit kernel.
If you used the Knoppix kernel configuration, aufs and cloop are built
into the static kernel part, so they will match the kernel version and
bit-ness automatically.
> this doesn't work with 64-bits images?� It's not the cloop image in itself
> - as I wrote, I can run the programs in it in 64-bits.
Maybe it is a problem with the busybox-internal "losetup" command, if
mounting the image fails in the initrd already? Did you also recompile
the statically linked programs inside minirt.gz?
Regards
-Klaus
Reply to: