XP or Linux for old parts crunching machine?

[karl_eller]

Ah, the joys of moving house: The packing, the heavy lifting, the dust, the heavy lifting, the mess, the finding random boxes of old computer parts.

So yeah, dug up a box of old computer parts, and I think there's enough to build a complete (abet rather old) computer. Looks like it'll be a 1.6 Ghz P4, 256-512mb DDR1 RAM, some crappy Compaq mATX motherboard (probable OCing ability: none), and whatever HDD I can find lying around.

I read here (and other places) that Windows tends to generate higher points than Linux does, but my question is, on a system as old as this one, would a Linux OS such as Kubuntu be a better choice since it'll use less system resources (and thus leave more for crunching)?

Eller

[don_xvi]

I'd suggest since you're going to be short on RAM that Linux would be good. I've found kubuntu to give me various problems (lockups, installation problems) so I use ubuntu although I prefer KDE. I read somewhere that gnome is more stable than KDE but only believe it because it fits my personal experiences !

[brot]

I read somewhere that gnome is more stable than KDE but only believe it because it fits my personal experiences !

In the release right now, ubuntu is more fine tuned than kubuntu. i like kde more than gnome, too, but when using *buntu i would take ubuntu. btw, if you are short on ram, try xubuntu.

http://www.xubuntu.org
"Once installed, Xubuntu can run with 64 MB RAM, but it is strongly recommended to have at least 128 MB RAM"

"Xubuntu uses the Xfce desktop environment, meaning that it will run fast while still delivering a user-friendly interface. Older computers feel lively again, while newer ones will run faster than ever before!"

My ibook 500Mhz runs xfce and it really runs great.

[Blauhung]

Plus its free and far less of a headache if you are just going to be crunching. The point difference is tiny, and will be even less of a factor on an old computer.

[Underwater Mike]

What about Mepis?

[rcofell]

You could also just run command line, if it'll only be crunching there isn't much need for X-windows. CLI installation is easy, download the sh file, have it extract all the files, and then go to the new directory and run boinc. To attach to the project you'd either need to learn to use boinc_cmd to send the commands to the core client, which isn't very hard, or else set up RPC so you can manage it from a different machine. Having it run at bootup isn't very hard either, I just add it to the rc.local startup script(well, actually you need to add "<directory>/run_client -daemon").

[sierra_bound]

Just an FYI. BOINC is included with Ubuntu. You just have to install the client and BOINC Manager using the Synaptic Package Manager. Takes less than a minute.:) No need for command line. You could also run the 64-bit version, but you would likely have to install the 32-bit libraries. That's easy to do too.

[karl_eller]

Alrighty, I'll give kubuntu a try, or if I can steal another 256mb RAM stick off someone, ubuntu, and see how that goes.

And there wouldn't be much point in installing the 64-bit version of Boinc if I'm using a 32-bit CPU and 32-bit OS, no? :p:

Eller

[sierra_bound]

You could run Ubuntu 64-bit with a 64-bit client. Would likely generate more points. If you're not using an EM64T processor, you can install the 32-bit libraries and still be able to run both a 64-bit OS and client.

Most people assume that because WCG apps are 32-bit, a 64-bit OS or client will not make a difference. The reality though is that it does, as many of us have found out.

[don_xvi]

Alrighty, I'll give kubuntu a try, or if I can steal another 256mb RAM stick off someone, ubuntu, and see how that goes.

You may have missed a letter above, the suggestion for low memory footprint is Xubuntu which uses a "lighter" GUI than ubuntu or Kubuntu.

[sierra_bound]

I don't think there's that big a difference in minimum system requirements between Ubuntu and Xubuntu. Once installed, Ubuntu can run with 64MB of memory.

https://help.ubuntu.com/community/Installation/SystemRequirements

The recommended minimum requirement is 192MB of RAM. Since the thread starter has 256-512MB of memory, he should be fine. 8GB of disk space is also recommended. Unless he has a really old low-capacity drive, he should be fine there as well.

Xubuntu is recommended for low-spec machines. But the system requirements for Ubuntu are not that demanding either.

[[XC] moddolicous]

You could also just run command line, if it'll only be crunching there isn't much need for X-windows. CLI installation is easy, download the sh file, have it extract all the files, and then go to the new directory and run boinc. To attach to the project you'd either need to learn to use boinc_cmd to send the commands to the core client, which isn't very hard, or else set up RPC so you can manage it from a different machine. Having it run at bootup isn't very hard either, I just add it to the rc.local startup script(well, actually you need to add "<directory>/run_client -daemon").
I think you should give this a try. Sounds like a really cool and efficient way to get a cruncher up.

[alucasa]

Just giving you another option.
It is also possible to nlite windows xp to bare minimum.
I've done this to my EeePC and it only uses 514mb (HDD) and runs fine with 512mb ram.

[[XC] moddolicous]

Just giving you another option.
It is also possible to nlite windows xp to bare minimum.
I've done this to my EeePC and it only uses 514mb (HDD) and runs fine with 512mb ram.
Well, he could do that, but having a command prompt only linux definitely would be soo much cooler.

[karl_eller]

You may have missed a letter above, the suggestion for low memory footprint is Xubuntu which uses a "lighter" GUI than ubuntu or Kubuntu.
Haha yeah, whoops. I meant Xubuntu, not kubuntu. Since I'll only be using 256mb RAM (can't find anyone with a spare 256mb DDR1 133 Mhz RAM stick), it'll probably be a better choice. Plus it's something I haven't used before ^.^

You could also just run command line, if it'll only be crunching there isn't much need for X-windows. CLI installation is easy, download the sh file, have it extract all the files, and then go to the new directory and run boinc. To attach to the project you'd either need to learn to use boinc_cmd to send the commands to the core client, which isn't very hard, or else set up RPC so you can manage it from a different machine. Having it run at bootup isn't very hard either, I just add it to the rc.local startup script(well, actually you need to add "<directory>/run_client -daemon").
So does that mean I'll be able to set it up so that the computer won't need a monitor, and then just give it commands and what-not remotely from another computer? I haven't really looked into running a machine remotely, so it's all fairly new to me, and my knowledge of Linux command lines is average at best. That said, I'm willing to learn the commands used if it'd be worthwhile. Also, would that work if the cruncher is running Linux while the PC I'm issuing commands from is running Windows (Vista)?

Eller

[rcofell]

So does that mean I'll be able to set it up so that the computer won't need a monitor, and then just give it commands and what-not remotely from another computer? I haven't really looked into running a machine remotely, so it's all fairly new to me, and my knowledge of Linux command lines is average at best. That said, I'm willing to learn the commands used if it'd be worthwhile. Also, would that work if the cruncher is running Linux while the PC I'm issuing comsmands from is running Windows (Vista)?
Yup, OpenSSH (http://www.openssh.com/) would allow you to do exactly that. If you haven't already heard of SSH, it's a protocol that allows you to remotely log onto a system and have a shell session that's secure, as opposed to something like telnet that's easy to eavesdrop on. As for accessing it from other operating systems, there are SSH clients for every major OS(I'd recommend Putty (http://www.chiark.greenend.org.uk/~sgtatham/putty/) for Windows) and it'll work as long as you have OpenSSH set up properly and running on the target system. I guess depending on what distribution you use it'll affect what you have to do to get it installed and running, but generally all you'll need to do is change a couple lines in a config file, nothing too hard if you follow a tutorial. I think I also had to set up an RSA key and certificate or something, nothing too terribly complicated, but again it helps having a tutorial if you haven't done it before :)

Yeah, I'm at least feel comfortable with running command line, but at least realize my knowledge pales in comparison to that of some people out there; I mostly run it because I find it interesting and use Linux more as a server, instead of as a desktop replacement. All you need is little bit of time and a will to learn, Google helps a lot too :)

As for controlling Boinc itself remotely(like with Boincview, or you can actually use the regular client manager to do so), I know on numerous occasions its been explained how to do so, but there doesn't appear to be a sticky. I can explain it if need be, maybe get it written out write so it can be stickied. But sadly the developer of Boincview(great tool for managing multiple Boinc installations) has disappeared for more than half a year and it's closed source... perhaps someone in Germany wants to track him down? :) As a result it hasn't been updated, but still works fine, just there's a lack of excitement over any new features being added :(