On Mon, Jun 06, 2005 at 04:54:25PM -0700, John R. Hogerhuis wrote: > I can think of some reasons for a non-native file service that is > instead built into QEMU: > <reasons snipped> > > -- John. >
I agree with you there, especially for non-networked OS support. A qemu-specific guest program will take in a file and tell qemu what the filename should be and give it the size/contents of said file. Another such program will give qemu a filename and recieve from qemu the size/contents of that file. qemu will do read/writes on the host to satisfy such requires. This is not an argument against adding file sharing network support in qemu though. The way I see it: OSes such as DOS, which are well known and still semi-popular can use their own qemu guest app to handle this without the difficulty of setting up networking (sidenote: i've never heard of anyone getting networking to work under DOS in qemu). OSes such as Minix, which are not as well known nor as popular but support networking easily can just use the tftp server (tho minix itself seems to lack a tftp client) without the need of having to write a special guest app. -- 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
