I think the problem with his solution is - it is neither here or there! The Windows camp probably wanted "click this button and all is done" solution and those in the Linux camp would not dream of having Windows as the server. To appeal to the windows users you need everything packaged in a simple i...

Hmmm..... These must be really interesting proteins as I am folding 12 of them now!

Results from completed WUs:

09.33 DUAL P3 1.4G(1 client)
07.18 P4 2.2G (400FSB) (farm client)
07.17 P4 2.2G (400FSB) (win2k)
07.29 MP 2200 (1 client)
06.32 P4 2.4G

Nice to see linux folding just as well as win2k.

mas92264 wrote:History is in stats\proteindata.csv in your emiii directory. Excel.

M

Thanks.

Does anyone where EMIII stores its configuration files? I want to move EMIII to another computer but do not want to lose all the stats that has been collected.

Thanks.

efcoins wrote:neoprene (as used to make wetsuits) is a good substitute, comes in 3
and 5mm thicknesses
or
http://www.gelmec.co.uk/ make"Soft silicone free gel sheet" does the same thing

This looks very interesting. Has anyone tried it?

Ouch... 115EUR.

I brought a Qtechnology 400W for 79EUR from pcsilent. This PSU has a 120mm ADDA fan which needs to be fitted with rubber mounts otherwise it can get quite noisy heavy underload.

Personally, I like the sound of rain, the sound of wind in the trees, or the sound of the ocean striking a rocky beach. Why can't my computer make sounds like that? When my children were babies we brought a device which is attached next to the cot. It emits all the sounds you have mention and help ...

I think the results depend more on which CPU used. I have two p850 WU on my folding farm - here are the results from FAH LogStats,

PPW
308 - Duron 1.3G
412 - P3 Tualatin 1.4G

brynach wrote:

CharlieChan wrote:As the kernel needs the lan driver at boot shouldn't the driver be compiled into the kernel rather than as a module. Loadable modules normally get loaded when the kernel is up and running.

The standard LTSP kernel uses modules for ALL NIC drivers. None of them are compiled in.

David,

As the kernel needs the lan driver at boot shouldn't the driver be compiled into the kernel rather than as a module. Loadable modules normally get loaded when the kernel is up and running.

Charlie.

David,

You may find the instructions here easier to understand.

Charlie.

Yep, you have two versions of the linux kernel there I have three so calm down. You default pxe kernel is v19 as specified in pxelinux.cfg/default, you can tell each client on the farm to use a different kernel by creating a file which bears the name of the hex IP address of the client. For example,...

The heatsink here is about 40 pounds ($100AUD) so it does seem pretty expensive there. As for running only one PSU fan, with my system it works ok but only because I have undervolted from 1.5 to 1.1 volts (bios won't let me go any lower). Without undervolting another fan would probably be needed. I...

I make'd modules modules_install bzImage Is there anything else I need to 'make'? I think thats about right. [*]I tried doing 'make install' but got an error: make: *** No rule to make target `/root/ltsp/linux-2.4.24/include/asm/param.h', needed by `/root/ltsp/linux-2.4.24/include/linux/sched.h'. S...

Up to this point I have simply configured and built a kernel. I don't understand what LTSP is and how it fits into the picture. The last thing I have done is to 'make bzImage'. Do I 'make install'? David David, It has been six months since I build the LTSP kernel so I may be missing something. If y...

Compile the kernel and modules: # make dep && make clean && make zImage && make modules System is 734 kB System is too big. Try using bzImage or modules. make[1]: *** [zImage] Error 1 make[1]: Leaving directory `/root/ltsp/linux-2.4.24/arch/i386/boot' make: *** [zImage] Error 2 Now what? Too big fo...

If I came across as arrogant I did not mean to CharlieChan. And the heatsink does have limitations, mainly due to the relatively old design of PC cases which were developed originally for much cooler devices. If you look at the tsheatronics web site at http://www.tsheatronics.co.jp they have some i...

Look Charlie...I don't think FrankT said anything "harsh", whatever that means in the UK. Like me he's just surprised so few people on this forum are using this heatsink. I only remember maybe two people who posted about their Zens around here. Ok, I chose the wrong word but I was trying to be poli...

I have to agree with you Bluefront, I thought there would be more interest in these heatsinks as well. I think I'm the first one to post my experiences with it and I would have thought more people would be interested in an actual user perspective rather than just a review (especially on SPCR). Good...

I feel like I have been thrown into the deep end of the pool! :lol: Hope you can swim :lol: . I am looking at three files, trying to understand the role they play in all of this: /etc/sysconfig/iptables # Firewall configuration # Manual customization of this file is not recommended. etc/rc.d/init.d...

OK, I can now ping the farm clients from the farm server by changing the gateway in ifcfg-eth0 from, GATEWAY=192.168.0.1 to GATEWAY=192.168.2.200 farm server eth0 = 192.168.2.200 (farm subnet) farm server eth1 = 192.168.0.200 (main network) Linksys router = 192.168.0.1 I connected a keyboard and mon...

Hmmm, I had a look at the iptables start script on my farm server. It appears it defaults to ip masq by default, here is a snipe, /etc/rc.d/init/iptables echo -n $"Resetting built-in chains to the default ACCEPT policy:" iftable filter -P INPUT ACCEPT && \ iftable filter -P OUTPUT ACCEPT && \ iftabl...

OMG, after reading this thread I realised I don't know what I have done :!: Lockheed may beable to clarify a few things. Does iptables do ip masq by default as if I run "iptables --list" on my farm server I get, Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACC...

David, You farmer server is the gateway to the blades. This need to be added, option routers 192.168.1.100 # gateway for blades to the dhcpd.conf on the farm server and restart network. Also you need to made sure the line GATEWAY=192.168.0.1 is added to ifcfg-eth1, this sends packets on the subnet t...

haysdb wrote:Is this in addition to, or in lieu of, the bridge?

No bridge neccessary.

I've read where this value goes away following a reboot, so needs to be placed in a startup script. Where should it go?

I do not record that happening to me. Try it and see .

Charlie.

David,

Type the following as root on the farm server,

echo "1" > /proc/sys/net/ipv4/ip_forward

To test you need to connect a PC to the subnet and ping the dlink router.

Charlie.

David, I have not read the complete thread so may missed something. You could be having a software problem so I suggest installing linux on each of the unstable blades first. If the blades folds without crashing then you should consider using redhat 8 on the server. I get the feeling it is another o...

David,

You could always put the farm on a subnet

Charlie.

Nice to see someone else exploring Linux! I have not read all the thread so it I repeated someone else reply, my apologizes. Guncash: This is basically a GNOME program and links to all the gnome libraries dynamically hence installing this program requires most of gnome. SUSE uses KDE by default henc...

Charlie, Toward the end of script /opt/ltsp/i386/etc/rc.local is this code: pr_set 94 "Starting ypbind" echo "Starting ypbind" if [ -z "${NIS_SERVER}" ]; then ypbind -broadcast else ypbind fi # # Need to give ypbind a chance to bind to the server, hopefully # this is long enough # sleep 1 Do you ha...