• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Klinux (or equiv.) for SETI@Home? Does it exist?

SETIdude

Member
I was wondering if there is a SETI@home Klinux version or something similar. I have an older computer I would like to use without a harddisk for some more S@H computing power.

I loaded Klinux and then tried to mount a DOS-formatted floppy with S@H program files for linux and got an error that the kernel does not have MSDOS mounting type available (I assume it was taken out to decrease the size of the kernel so it will fit on the 1.44 floppy).

Since I don't currently have access to a linux machine that can write the program files to a floppy, I guess i'm out of luck. Of course, this all depends on there being enough ramdisk space for S@H to operate properly in Klinux.

Any insight would be appreciated 😀
Thanks

-SETIdude
 
>>>>Of course, this all depends on there being enough ramdisk space for S@H to operate properly in Klinux<<<<

Well ,I don't know how much it would apply to Linux ,but the SETI CLI or GUI for Windows uses 14Mb of RAM when running.
 
With as much as the SETI clients access the hard drive, I belive that would be very slow (trying to access the floppy), though it might be possible to setup a RAM disk. You'd also need to have the computer on a LAN so it could get the WU's.
 
Sukhoi - actually the disk writes to floppy are minimal for seti - basically updating the state.sah file. I have tested running SETI on a floppy-based linux - Pocket Linux and it does work pretty good - even with my test on a P120 notebook w/40MB RAM! In fact, just today, I and a co-worder were discussing which distro might be best for floppy-based crunching and I mentioned KLinux (suitably modified). He mentioned his intention to give it a shot with Trinux.

Getting a good single-floppy setup would allow for some decent crunch racks... heh. Especially since this new client looks like it'll put our averages to shame and we'll need to double the assimilations to make up for lost time... 😉

[EDIT: Danzigrules - I noticed that we thought alike regarding Pocket! Seti does with with it! 🙂]
 
It would be a very good idea for you guys to keep hacking away at this. The longer term payoff will be when the RC5 team comes to pay its &quot;dues&quot; to TA SETI for the help they've given us.

If you can &quot;package&quot; something for a crackrack it will be to the TeAm advantage.

You'll need to offer a personal proxy (SETI Q?)for a web connected machine and a single floppy boot distro for the nodes. A stats generator for the pproxy would be an advantage. All this needs to be bundled with simple instructions and then posted where it can be readily accessed.

You never know, somebody could find that missing key tomorrow - think of all those cpu cycles you will harness....if you're ready! 😀😀
 
From what I know, SETIQ needs to be run in Windows. But, aren't there some Windows emulators for Linux? Maybe that would work?
 
Sukhoi - I'm currently running WINE (which stands for &quot;WINE Is Not an Emulator&quot; 😉) on the system in my sig. I run the 3.x CLI in a window in Linux. From my testing, I've found that not only is the CLI more optimized than the seti linux client, but WINE runs the CLI faster than native winblows does! :Q

I have heard of people using WINE to run Setiqueue but I haven't tried that yet... I've only been putzing around with WINE for about a month... I did try it to install and run folding@home, and it seemed to work except when it was time to upload the WU (it sortof sat there - but then that was around the time when they were having connection problems).
 
Does WINE come in a box? Wait, wrong subject matter. 😉 Does WINE support TCP/IP? That'd be the main problem with getting SETIQ to connect.
 
Back
Top