
the root thing is/was to keep it simple.

I've been more concerned with getting the thing to work, crack blocks and act as a pproxy than act with propriety. I guess I'll try to be better in future.
I've managed to get the buff-in topped up again anyway. I take it then, whenever you give a console command from root, the ./ has to be there?
<<
I bet it solves one of your problems anyway. >>
:Q
I do have another question (of course). Whenever I shut down the client and restart it, there seems to be a risk of losing the blocks already cracked. (Those 300 randoms just disappeared). I need to make sure that stops right now! It doesn't happen every time though. This machine has cost me about 5000 blocks in the last fortnight. The two drones sitting beside it are also not producing a thing. I've got to get these three going smoothly before I can build the rest of the cluster.
I'm now putting this one aside and I'll try to get the drones cracking on Klinux using a W98 machine as a pproxy. I've downloaded the pproxy and hooked into Heavyiron's pproxy to check on fetch and flush. It works!
I've pointed another W98 machine at it and now have it successfully fetching and flushing to the pproxy which then flushes to Heavyiron pp.
I am about to try and get one drone up on Klinux and have it start fetching and flushing from the Dantoo pproxy. Let you know! (any advice welcome of course).
Node 1 is Up!!

I had to go the netconfig route as the DHCP was timing out, but it wasn't too scary. You really have done an amazing job with Klinux - Take a huge bow!
I'd bring in Node 2 now, but I'm plumb out of cat 5 cables, miscounted somehow, but I'll rig something before bedtime.