just_survive wrote:I wanted to use the Pi as some extra power (1gb ram) for my laptop.
This isn't as insane as people imagine. But you have to realise that you can't stick the pi to the laptop and everything gets a speed bump, what you can do is use the pi *and* the laptop at the same time doing operations that you can divide between the two.
For example, let's say you want to run more than one copy of firefox but your laptop doesn't have enough speed or ram for that. Maybe your pi can run firefox and then you can view the output on the laptop. This was one of my original plans for the first generation pi but it wasn't really fast enough and didn't really have enough ram. But the new one is quad core and has a gig of ram, it might be fine. From your laptop, you could type ssh -X [email protected]
firefox and you should end up with firefox running on the pi but the output on the laptop. Because of the rather relaxed demands on the laptop in this scenario, you can use it for other things.
My current configuration takes this one step further. I have a main machine that has X2go installed on it. You can have several such machines if you get adventuresome. From that machine, I can run ssh -X to various programs on various desktops on that main machine. From any machine I want to *view* these applications, I simply access via X2go.
A while ago, I stupidly turned off the machine I was using to view the X2go session by hitting the power bar's switch. I was about to get mad because I had a bunch of stuff open and then I realised that it was still open, this machine couldn't matter less for what is going on with the main one. So I just started it up again and logged back in via X2go and everything was fine.This, of course, also works using vnc and other desktop sharing software, the reason I was using X2go is because it was working better.
In any case, the desktop I was viewing, was separating the firefox sessions and other programs into chunks that could then be run on various machines via ssh -X [email protected]
program . So, for example, if I want to run intelliJ *and* want to loop sbt, the simple build tool for scala, I might divide these operations between two systems. (sbt is command line character based so doesn't need to even use X) This gives the full power of one machine to the building of the program while retaining the full power (and memory) of another for IntelliJ. You'll probably find that the pi lacks enough memory to do this very effectively in this case but the idea can be used with two or more systems that do have the needed resources.
Depending on your available systems, you may have to move around which systems are being used ssh -X and which one or more are being used via a desktop sharing program and which you are using to view into that. But you *can* do things with the pi that augment your laptop's capabilities, assuming you don't just want to play some silly video game faster.