On Tuesday 08 November 2005 09:56, Blaisorblade wrote: > But hey, it's (now) standard practice to loopback-mount root_fs images to > alter them. I've been using linux since less than 3 years (say RedHat 7.3 > was my first distro), though, so I can't remember about before.
Red Hat 5.something here. (5.1? It _hated_ my video card. And I was already trying to do strange things like loopback mounting a file that lived in another loopback mount...) > Which means that, when just testing the build process in itself, since you > can create a chroot on the loopback-mount, it's perfectly ok to run it in a > chroot on the host, for speed. I've done that (with my build, run the sources/scripts/1.1-* script in the chroot environment after --bind mounting in /tools and /tools/sources). But at the end of the build the packaging step makes a standalone User Mode Linux (with appended squashfs) to test it out, so I'll need it eventually anyway... Of course the gcc build is still quite a memory hog without UML. But the system is more graceful about dealing with it. (Better at random memory pressure than random IO pressure, apparently. It might just be that the anticipatory scheduler on the host system is particularly _bad_ about dealing with saturation level random-seek equal mixes of reads and writes scattered across a couplke hundred megabytes of disk space.) I should be upgrading the host system soon, not worth pursuing this unless the new kernel has the same problem... Rob ------------------------------------------------------- SF.Net email is sponsored by: Tame your development challenges with Apache's Geronimo App Server. Download it for free - -and be entered to win a 42" plasma tv or your very own Sony(tm)PSP. Click here to play: http://sourceforge.net/geronimo.php _______________________________________________ User-mode-linux-devel mailing list User-mode-linux-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/user-mode-linux-devel
