• 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.

ECCp-109 linux floppy

Postman

Senior member
At first I thought it would be easy to use klinux as base, but since the eccp client works differently than dnetc, I'm a bit at loss.
Mainly about it automatically creating dplist.log, and the reboot issues.

Any help?
 


<< Oh, this is linux client I'm using now, performs better than the official or the statsaholic enchanced linux client: client >>



I know, I compiled it! 🙂

I've never used a diskless node in any DC project, so I can't help you there. Other people have done ECCp this way, so hopefully they will give you the details. IIRC, the linux distribution trinux was involved.
 
Oh 🙂 No-one mentioned your compilation in any recent previous threads (i'n known to be blind tho..), so I just happened to google it and give a try, it rocks 🙂

Hopefully someone with a clue comes around with the floppy issue.
 
I've been thinking about setting up ECCP on KLinux like I did on SETI. The main problem is, I don't know how to compile it for gnulibc1, which is the version KLinux uses. I could possibly copy over some gnulibc2 files, but they would probably be too big to fit on a floppy.

Oh, and I'm not sure the computer I'd compile on has the gnulibc1 files!

So, anyone know how to set the gnulibc version?
 
Unfortunately, my skills with gcc limit just limit to 'make' and 'gcc -o helloworld.c', not to even speak about the libc issues. 🙁.

But the fundamental problem with eccp floppy I see is with stock clients is atleast, that it needs to save eccinfo and dplist.log on disk. So pure ramdisk solution is out of the question I guess?
 
I've been running a diskless ECCp rack for a while now using Trinux. It is not very convenient, though. With Trinux, it is possible to mount the floppy and run files there, but disk life is real low. I let it run for a week and the floppy was detroyed forever at that point. It just accesses it too much. So I normally run it out of a ramdisk and back up the files to a floppy once a day. Another problem is it takes to disks -- the Trinux booter and another disk for the ECCp client.

I originally tried using Freesco, because it mounts the floppy as read/write. But there are two problems -- not enough room left on the floppy, and the kernel version is wrong or something because the ECCp client isn't even executable in Freesco! Again, beyond my abilities.

I'd sure like to see someone put together a good ECCp floppy. Until then, I guess we might have to tolerate the little old hard drives! I've kind of defaulted to a minimum install of Win95 on 540MB hard drives for my racks. The optimized Windows clients are marginally faster than the Linux clients anyway.
 
So, the obvious solution seems to be master node with nfs shares for clients.

Which brings me back to the issue in my other thread, netbooting 🙁
 
I've been using Trinux disks myself except RC set them up. Each system only needs one disk. It creates a ramdisk and decompresses everything into that. The only problem though is that the statsaholic 1.27 client seems to be the only one that works properly. None of the 1.3 clients are able to upload.
 


<< So, the obvious solution seems to be master node with nfs shares for clients.

Which brings me back to the issue in my other thread, netbooting 🙁
>>



You shouldnt need to do netbooting. Boot from a floppy and as long as it has nfs support you should be good. You could also pick up ~1GB disks pretty cheaply.

EDIT: Boot off of cdrom. You will have more space to include goodies like NFS.
 


<<

<< Oh, this is linux client I'm using now, performs better than the official or the statsaholic enchanced linux client: client >>



I know, I compiled it! 🙂

I've never used a diskless node in any DC project, so I can't help you there. Other people have done ECCp this way, so hopefully they will give you the details. IIRC, the linux distribution trinux was involved.
>>



Damn that client is fast! Im getting another 100k with it. Ill have to monitor stability for a while though, and switch up other clients when I get the chance. Thanks for the link!
 


<< You shouldnt need to do netbooting. Boot from a floppy and as long as it has nfs support you should be good. You could also pick up ~1GB disks pretty cheaply.

EDIT: Boot off of cdrom. You will have more space to include goodies like NFS.
>>



I don't want want hard disks except one in the rack, obvious reasons. As discussed, the floppy solution in general seems problematic and for the price of cdroms, I could get pretty easily bootable nics. Not to mention that netbooting seems the most elegant solution.
 
Back
Top