From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BkZe3-0000JW-9V for qemu-devel@nongnu.org; Tue, 13 Jul 2004 22:37:19 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BkZe2-0000JK-Or for qemu-devel@nongnu.org; Tue, 13 Jul 2004 22:37:19 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BkZe2-0000JH-L4 for qemu-devel@nongnu.org; Tue, 13 Jul 2004 22:37:18 -0400 Received: from [38.113.3.61] (helo=babyruth.hotpop.com) by monty-python.gnu.org with esmtp (Exim 4.34) id 1BkZbM-0005UM-5n for qemu-devel@nongnu.org; Tue, 13 Jul 2004 22:34:32 -0400 Received: from phreaker.net (kubrick.hotpop.com [38.113.3.103]) by babyruth.hotpop.com (Postfix) with SMTP id 631956D9CDC for ; Wed, 14 Jul 2004 01:48:41 +0000 (UTC) Received: from jbrown.mylinuxbox.org (pcp03144805pcs.midval01.tn.comcast.net [68.59.228.236]) by smtp-2.hotpop.com (Postfix) with ESMTP id 826AC6D9CC0 for ; Wed, 14 Jul 2004 01:48:39 +0000 (UTC) Date: Tue, 13 Jul 2004 22:34:25 -0400 From: "Jim C. Brown" Subject: Re: [Qemu-devel] Win98: how to exchange data with Linux Message-ID: <20040714023425.GC6436@jbrown.mylinuxbox.org> References: <200407122356.02502.eschmit@tin.it> <1089671145.12301.10.camel@aragorn> <200407130924.58879.vaise@votreservice.com> <1089727701.7843.58.camel@espiron.av7.local> <40F3EF20.2020802@kadu.net> <40F3F5B1.2040908@kadu.net> <40F41A65.8050807@volny.cz> <1089740739.17526.3.camel@aragorn> <40F422BB.8020908@kadu.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <40F422BB.8020908@kadu.net> Reply-To: qemu-devel@nongnu.org List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: qemu-devel@nongnu.org On Tue, Jul 13, 2004 at 07:58:19PM +0200, Adrian Smarzewski wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > John R. Hogerhuis wrote: > | Yes, it is a non-workable idea to try to share a filesystem between two > | running OSes. > > I don't agree because samba for example is the application that does it. > > - - change samba serwer to little server builded-in into qemu > - - change smb windows client to filesystem driver communicating with our > server > - - change tcp protocol to hidden ioports communication between windows > driver and qemu little-server (like vmware-tools communication protocol) > > and it will be the thing that I'm talking about. > > - -- > Pozdrowienia > Adrian Smarzewski You don't need the second step, > - - change smb windows client to filesystem driver communicating with our > server but the rest is workable. VMware actually does this, iirc. It would be easier to support NFS as the special protocol and use an open-source NFS client for Windows tho. Then again, do we really need full filesystem access? It would be simpler for qemu to emulate an ftp server on the guest side (use "-ftp" option to turn the server on, and "-ftpdir " to tell qemu where it should serve from). > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v1.2.4 (GNU/Linux) > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > iD8DBQFA9CK7gnuWEmthbpURAgSNAJ4g31sbNV4BLAQWNtABTvD1+tPOdwCdFsYQ > oEu0hgylEraYe7U5M7GO9dk= > =GDW5 > -----END PGP SIGNATURE----- > > > _______________________________________________ > Qemu-devel mailing list > Qemu-devel@nongnu.org > http://lists.nongnu.org/mailman/listinfo/qemu-devel -- Infinite complexity begets infinite beauty. Infinite precision begets infinite perfection.