>> Why not just *install* gcc and all the rest ?
>> All it'll cost you is HD space - about 300 megs all told.
> There is not much disk/memory space and I do not even have physical access
> to the machine. All I got is a dial-up connection with telnet/ftp and that's
If you are using telnet or ftp the machine has been cracked - the password
goes in the clear across the net! Surely you mean ssh. But anyway, ssh
is all you need.
Quote:> The machine is quite heavily used, so installing 300 MB with the risk it
> runs out of disk space is the way of bringing it down to it's knees.
If it's heavily used then it has disk space (or what are they using?).
300MB is a tiny amount - less than 1% of the smallest disk you can buy
nowadays. But to compile stuff you should be able to get away with less
than 100MB easily!
Quote:> Captain Dondo has a very good point with his remark about accepting a binary
> from an unknown source. This is certainly not the way to go either. That
> leaves me nothing else than building a duplicate system.
Why? You can use nfs to mount a development environmnent on your
server (in /usr/local) and compile there - compilation takes no
noticable resources, especially if done with nice.