[cap-talk] Moving running applications

[Valerio Bellizzomi]

On 27/11/2007, at 6.36, Jonathan Smith wrote:

>An historical perspective:
>
>"A Survey of Process Migration Mechanisms", by J. M. SMith, in ACM OS  
>Review,
>pp. 28-40, July 1988.
>
>																-JMS

Thanks JMS,
On December I will do an update of CapBib
(www.selnet.org/pubs/capbib.html).
The novelty is that I am using a parser to extract URLs from a text
archive of cap-talk. The parser understands the usual "http://" prefix. So
for the purpose of publishing links in CapBib the prefix must be present.

val


>
>
>On Nov 26, 2007, at 8:04 PM, Valerio Bellizzomi wrote:
>
>> On 27/11/2007, at 0.24, David Hopwood wrote:
>>
>>> Jed Donnelley wrote:
>>>> On 11/21/2007 5:18 PM, Norman Hardy wrote:
>>
>>>
>>> It isn't strictly necessary for a system to use a pure message
>>> passing architecture, for it to provide sufficient abstraction from
>>> underlying devices to support migration. The design will probably be
>>> cleaner if it does use pure message passing, because otherwise  
>>> special
>>> case treatment of particular kinds of device may be required -- but
>>> many VMM implementations seem to have managed to implement this  
>>> anyway.
>>
>> It isn't necessary either to use a VMM to do migration. Look at  
>> openMosix,
>> which can migrate processes from one node to another, and it isn't  
>> a VMM,
>> it is a Linux kernel extension.
>>
>> val
>>
>>
>> _______________________________________________
>> cap-talk mailing list
>> cap-talk at mail.eros-os.org
>> http://www.eros-os.org/mailman/listinfo/cap-talk
>
>Jonathan M. Smith,  Olga and Alberico
>Pompa Professor, University of Pennsylvania,
>T: 215.898.9509, E: jms at cis.upenn.edu
>
>
>
>_______________________________________________
>cap-talk mailing list
>cap-talk at mail.eros-os.org
>http://www.eros-os.org/mailman/listinfo/cap-talk