-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 I decided to run the buildbot in a chroot (bind-mounting required directories like /bin, /usr, and so on) to give my system (now Ubuntu "Dapper Drake" on my old G3 powerpc) a bit of protection, and that seems to be working. Soon after getting the buildbot working, though, and with GHC plugging away at Yhc's code, my machine decided to lock up. Gkrellm is great, I can see green cpu usage for "nice" processes (such as I made the buildbot slave), and I saw that I had about 200 megabytes of swap usage at that point. Well I'm not giving up, just warning that my computer seems a bit unreliable! :) (plus, can't wait till Yhc can compile itself for doubled testing and lower resource usage (hmm, proper testing shouldn't start with an old alpha version, but self-compilation and using the self-compiled version to get the exact same results[1] should be a good test in general) ... or could a standard way to use hugs be set up perhaps, rather than necessarily doing the testing using the resource-hungry ghc?) Isaac [1] Unfortunately compilation isn't always necessarily referentially transparent, particularly when date-of-compilation preprocessor symbols are used. -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.2.2 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFE3K1WHgcxvIWYTTURAkLyAJ9Hu9LJgQdUyqXG/4YHnV9mlKtjBgCgkOFs kSUGGJOnfpE9mOMaFwpWzOE= =NBu9 -----END PGP SIGNATURE-----