From: Filip Navara <xnavara@volny.cz>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] Win98: how to exchange data with Linux
Date: Wed, 14 Jul 2004 05:15:39 +0200 [thread overview]
Message-ID: <40F4A55B.2000203@volny.cz> (raw)
In-Reply-To: <20040714022611.GB6436@jbrown.mylinuxbox.org>
Jim C. Brown wrote:
>Technically speaking, one could write a file system driver that talks to qemu
>instead of going through a storage driver. (I didn't say it would be easy, just
>barely possible.) Qemu could then translate attempts (to write a file on Windows
>using this driver would cause qemu to write the file on linux's fs natively for
>example). It is more work than its worth, but it is possible.
>
>
Strictly technically you would need to fake a storage device (~ 1000
lines code) since Windows can't mount filesystem without a device and
then you can write a file system driver that will recoginze the fake
device and act as you described. I agree, yes, doing this is possible,
but it would be pretty complex to implement for no real gain. It's less
flexible than any solution based on networking (since you would have to
write a guest driver for every OS that you want to use the feature in)
and the speed increase would be marginal if any.
>A modified user-net which emulated SMB protocol to the guest but did the i/o
>natively on the host would do the same thing and be easier to implement.
>
>
Again, I agree, that's the way to go.
Regards,
Filip
next prev parent reply other threads:[~2004-07-14 16:30 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-12 21:56 [Qemu-devel] Win98: how to exchange data with Linux Mario Cazorzi
2004-07-12 22:12 ` Joe Menola
2004-07-13 1:23 ` Jim C. Brown
2004-07-13 2:03 ` Joe Menola
2004-07-13 2:51 ` /dev/tun Was: " Jim C. Brown
2004-07-13 3:15 ` Joe Menola
2004-07-15 2:10 ` Joe Menola
2004-07-15 2:49 ` Jim C. Brown
2004-07-16 1:01 ` Joe Menola
2004-07-16 1:39 ` Jim C. Brown
2004-07-18 23:12 ` Joe Menola
2004-07-12 22:25 ` John R. Hogerhuis
2004-07-13 7:24 ` vaise
2004-07-13 14:08 ` Sebastien Bechet
2004-07-13 14:18 ` Adrian Smarzewski
2004-07-13 14:46 ` Adrian Smarzewski
2004-07-13 17:22 ` Filip Navara
2004-07-13 17:45 ` John R. Hogerhuis
2004-07-13 17:58 ` Adrian Smarzewski
2004-07-13 18:11 ` John R. Hogerhuis
2004-07-13 18:31 ` Adrian Smarzewski
2004-07-14 2:42 ` Jim C. Brown
2004-07-14 9:50 ` Adrian Smarzewski
2004-07-14 10:04 ` Antony T Curtis
2004-07-14 11:11 ` Fabrice Bellard
2004-07-14 11:58 ` Adrian Smarzewski
2004-07-14 14:01 ` Adrian Smarzewski
2004-07-14 12:28 ` Brad Watson
2004-07-14 12:46 ` Adrian Smarzewski
2004-07-14 16:44 ` John R. Hogerhuis
2004-07-15 0:38 ` Leigh Dyer
2004-07-15 5:25 ` John R. Hogerhuis
2004-07-15 5:38 ` Leigh Dyer
2004-07-14 2:34 ` Jim C. Brown
2004-07-14 6:02 ` Jim C. Brown
2004-07-14 6:15 ` Johannes Martin
2004-07-13 17:50 ` Adrian Smarzewski
2004-07-13 22:31 ` Sebastien Bechet
2004-07-14 2:26 ` Jim C. Brown
2004-07-14 3:15 ` Filip Navara [this message]
2004-07-14 9:54 ` Adrian Smarzewski
2004-07-14 9:55 ` Adrian Smarzewski
2004-07-14 10:14 ` J. Mayer
2004-07-14 2:21 ` Jim C. Brown
2004-07-12 22:50 ` [Qemu-devel] " Robert Wittams
-- strict thread matches above, loose matches on Subject: below --
2004-07-13 16:07 [Qemu-devel] " Mario Cazorzi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=40F4A55B.2000203@volny.cz \
--to=xnavara@volny.cz \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).