OK, I get it. Obvious... the VM is running on the same machine, and the
TCP/IP is between Linux and the VM.
Sorry for the stupid question. :-/
Fabio
> > On Wed, 9 Oct 2002, Andrew Clausen wrote:
> > > The only method I can think of is TCP/IP communication saying
> > > things like: "move onto the next test now" and "verify that has
> > > no errors now", etc. I guess it's not too hard, but a bit messy.
> >
> > Looks more efficent :)
> >
> > favouritevm winbox
> > while (prepare next test)
> > ssh winbox mount drive
> > ssh winbox execute test
> > wait for result or timeout/crash
> > if (timeout/crashed)
> > restart favouritevm winbox
> > else
> > ssh winbox umount drive
> >
> > Szaka
>
> Humm... but how can we do tests on a remote machine? The tests must
> be done by linux code and windoze code on the HD of the same
> machine. Therefore, there is no remote testing via TCP possible.
> You need to reboot/re-VM the machine back and forth between linux
> and windoze.
>
> Fabio
>
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Linux-NTFS-Dev mailing list
> Lin...@li...
> https://lists.sourceforge.net/lists/listinfo/linux-ntfs-dev
|