New machine for shitbox

Hi folks,

K, I have finally put a new machine in for ****box. It's still not
super high-end (700Mhz PIII with 384Mb) but it should at least be more
stable and come back up when rebooting.

I also did a dist-upgrade. I hope that wasn't a bad thing. I'm still a
little concerned about the HD but I'm not sure how much trouble it would
be to get it up on a new one. I'm up for suggestions, etc.

I also have a nicer machine P4 (2.4Ghz or so I think) that I was
thinking about replacing flubber with but I am wondering if that makes
the most sense? Since flubber is now the wiki code and such, should it
be taken out of the more "public" role? I'm thinking maybe using the
gnubber hardware for flubber and set up a new gnubber might make more sense.

Thoughts?

Thanks!

Barry deFreese

Hi,

Thu, Jul 03, 2008 at 10:56:17PM -0400, Barry deFreese wrote:

I'm still a little concerned about the HD but I'm not sure how much
trouble it would be to get it up on a new one. I'm up for
suggestions, etc.

Shouldn't be a problem I think Just copy the whole disk :-)

I also have a nicer machine P4 (2.4Ghz or so I think) that I was
thinking about replacing flubber with but I am wondering if that makes
the most sense? Since flubber is now the wiki code and such, should
it be taken out of the more "public" role? I'm thinking maybe using
the gnubber hardware for flubber and set up a new gnubber might make
more sense.

Well, I'm always feeling a bit strange about the fact that a public
machine prone to frequent crashes is also used for the wiki

the other hand, the wiki seems to need a fast machine, so using it
for the wiki exclusively would be a waste

Not sure what the best approach is. Ideally, they should run in two
distinct VMs sharing the hardware :-)

-antrik-

Hello!

Sat, Jul 05, 2008 at 12:57:27PM +0100, Samuel Thibault wrote:
Dani Doni, le Sat 05 Jul 2008 13:52:07 +0200, a :
Maybe I am wrong, but updates on wiki content should trigger little
bursts of activity, not sustained periods of 100% cpu load.

The wiki engine regenerates all the pages, that's what takes time.

As I said before: it regenerates only those that need to be regenerated.


Regards,
Thomas

PGP SIGNATURE
Version: GnuPG v1.4.2.2 (GNU/Linux)


ldEnB6zx8UiJZ5lkDIJ6PsM=
=xXGB
PGP SIGNATURE

Barry deFreese, le Tue 08 Jul 2008 12:28:57 -0400, a :
By "working Debian system" do you mean Debian GNU/Linux or a Debian Hurd
system?

A GNU/Linux system, since gnumach does not support running as dom0.

Samuel