On Mon, Jun 06, 2005 at 08:11:08PM +0200, [EMAIL PROTECTED] wrote: > The advantages are: > - no ide-channel is blocked (unlike vvFat)
I don't believe this is a major issue. Alias, vvFat is readonly and anyways not suitable for the purposes of every OS (e.g. copy from Linux guest to Linux host, preserving ownership). > - ftp IS a very common protocol (is there SMB for exotic OS?) > - as the server is only virtual, you don't have to care about security-issues > - the server only runs, when it is needed > - implementaion should be easy (get some open-source FTP, strip it down > and change its binding to an interface like it was done with the internal > dhcp) > - the data-transfer resides inside the guest, which would be more > intuitive to the non-technical user when working in the VM. > Like I said, modifying TFTP for R/W would be a good option. It's already there, the "miminalists" can't complain about having it removed (e.g. it may one day be used to support "virtual" netboots), and one can use ftp clients for the tftp server (I think). > > btw: The SMB server (Samba) provides read/write access if you insist on > > it. All you in theory need to do is to set up the password file on the > > host. > > The Samba-wrapper does not work on Win-on-Win situations > But windows host has native SMB support. Surely the wrapper could be altered to support using SMB via win32 ? > > Have a nice day, > Jan > > > > _______________________________________________ > 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. _______________________________________________ Qemu-devel mailing list Qemu-devel@nongnu.org http://lists.nongnu.org/mailman/listinfo/qemu-devel
