Don't be so pessimistic! :-) There are lots of more feasible solutions=20=
involve first gaining control of the windows box with a well known=20
exploit, and then wiping clean the hard-drive (tons of script kiddies=20
every day). The only tricky addition that this guy has to add himself,=20=
is to do a
remote/ftp install of Linux/ with an openMosix kernel after fdisking=20
windows drive. Add a reboot command, and if autodiscovery is working he
should be well on his way :-).
More seriously, if the question was anything more than a crank, it was
probably envisioning some remote launching of programs, not process
migration in anything like the sense you mean it. :-). I know such=20
exist, I just have no idea how to use them.
On Tuesday, May 13, 2003, at 10:31 AM, Moshe Bar wrote:
> It's doable. You first have to obtain the Windows source code. Then,=20=
> obtain the permit to modify it. Then, understand the source code and=20=
> write source migration patches for it. Then, obtain the compilation=20
> environment from Microsoft and pay for it. Then, obtain permission=20
> from Microsoft to distribute, sell, or otherwise make available to=20
> third parties your changes without breaking the customer's support=20
> from Microsoft.
> I guess the shortest task is the third one.
> On Tuesday, May 13, 2003, at 07:02 US/Pacific, jeroen degadt wrote:
>> i'm working on my final project, and i successfully installed an=20
>> openmosix cluster. you probably won't like to hear this, but now=A0have=
>> to do the same with micro$oft windows. has anybody an idea how to=20
>> obtain process migration on a windows machine?
David J. Cutler, Ph. D.
Institute of Genetic Medicine
Johns Hopkins University School of Medicine
600 N. Wolfe Street
Jefferson Street Building, Room 2-120
Baltimore, MD 21287
lab# (410) 502-7534
fax# (410) 502-7544