|
Does loop mounting a partition use less RAM than loop mounting an image file? Multiple people including myself and dasmoover (as I recall) have had issues with a K5 locking up while trying to do anything useful in a loop mounted ext3 (or ext2) image file, such as building packages. Even apt-get can lock up...
Is the method suggested here significantly better? Has anybody tried compiling something significant in a loop mounted debian on a K5?
In the past, I successfully built X11 on a K3 in a loop mounted debian. I had yet to learn the details of eink updates, but at least the build was successful. It took about 12 hours on my K3. It would be interesting to see how long it takes on a K5 (or even if it completes).
Perhaps loop mounting a raw partition would be faster and use less RAM when NOT going through layers of loop mounting an image file on a fuse filesystem, and the vfat support and all that...
|