From: Rob Landley <rob@landley.net>
To: Blaisorblade <blaisorblade@yahoo.it>
Cc: user-mode-linux-devel@lists.sourceforge.net
Subject: Re: [uml-devel] Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
Date: Tue, 8 Nov 2005 18:50:26 -0600 [thread overview]
Message-ID: <200511081850.26359.rob@landley.net> (raw)
In-Reply-To: <200511081656.24694.blaisorblade@yahoo.it>
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
next prev parent reply other threads:[~2005-11-09 0:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1130917338.14475.133.camel@localhost>
[not found] ` <20051102172729.9E7C.Y-GOTO@jp.fujitsu.com>
[not found] ` <43687C3D.7060706@yahoo.com.au>
2005-11-02 23:28 ` [uml-devel] Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19 Rob Landley
2005-11-03 5:26 ` Jeff Dike
2005-11-03 5:41 ` Rob Landley
2005-11-04 3:26 ` Blaisorblade
2005-11-04 15:50 ` Rob Landley
2005-11-04 17:18 ` Blaisorblade
2005-11-04 17:44 ` Rob Landley
2005-11-04 19:10 ` Blaisorblade
2005-11-04 20:41 ` Rob Landley
2005-11-04 20:57 ` Rob Landley
2005-11-04 23:42 ` Blaisorblade
2005-11-05 1:45 ` Rob Landley
2005-11-05 5:23 ` Jeff Dike
2005-11-05 5:45 ` Jeff Dike
2005-11-05 11:30 ` Blaisorblade
2005-11-05 23:44 ` Rob Landley
2005-11-06 17:18 ` Blaisorblade
2005-11-08 0:32 ` Rob Landley
2005-11-08 15:56 ` Blaisorblade
2005-11-09 0:50 ` Rob Landley [this message]
2005-11-05 18:57 ` Rob Landley
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200511081850.26359.rob@landley.net \
--to=rob@landley.net \
--cc=blaisorblade@yahoo.it \
--cc=user-mode-linux-devel@lists.sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox