____/ The Ghost In The Machine on Tuesday 02 October 2007 15:59 : \____
> In comp.os.linux.advocacy, Roy Schestowitz
> <newsgroups@xxxxxxxxxxxxxxx>
> wrote
> on Tue, 02 Oct 2007 06:49:57 +0100
> <2669443.S8oSdvrrQ3@xxxxxxxxxxxxxxx>:
>> ____/ The Ghost In The Machine on Tuesday 02 October 2007 02:46 : \____
>>
>>> It already has; VmWare, QEMU, and Bochs come to mind.
>>> Of course the desktop was highly virtual to begin with
>>> anyway; an X window is an abstract token handled by the
>>> X server, for example.
>>
>> Yes, it's already there, but rarely does one share load
>> across different workstation. It would be nice to
>> 'borrow' some cycles from a colleagues PC if s/he only
>> read some document off the screen. Moving the load to
>> the server or making all programs Web/server-based is
>> one possibility, but there are other interesting options.
>>
>
> I'd have to research the matter, but a quick Google
> coughed up
>
> http://lcic.org/
>
> ("Linux Clustering Information Center")
>
> and
>
>
http://www.ibiblio.org/pub/Linux/docs/HOWTO/other-formats/pdf/Cluster-HOWTO.pdf
>
> ("Linux Cluster HOWTO" -- PDF required)
Along the lines of a network mesh (/a la/ OLPC), maybe you could pool RAM and
CPU cycles. The only problem with that is the low throughput (wireless) and
the possibility of losing connectivity. You can't recover from lost
threads/memory buffer like you can recover from lost packets by
retransmitting.
--
~~ Best of wishes
Roy S. Schestowitz | INQredible Hacktivism
http://Schestowitz.com | Open Prospects | PGP-Key: 0x74572E8E
Tasks: 156 total, 1 running, 154 sleeping, 0 stopped, 1 zombie
http://iuron.com - knowledge engine, not a search engine
|
|
