From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1BkmrR-0002ra-PS for qemu-devel@nongnu.org; Wed, 14 Jul 2004 12:44:01 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1BkmrL-0002rO-6s for qemu-devel@nongnu.org; Wed, 14 Jul 2004 12:44:01 -0400 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1BkmrL-0002rL-4S for qemu-devel@nongnu.org; Wed, 14 Jul 2004 12:43:55 -0400 Received: from [216.254.0.204] (helo=mail4.speakeasy.net) by monty-python.gnu.org with esmtp (TLSv1:DES-CBC3-SHA:168) (Exim 4.34) id 1Bkmod-0004xz-Dy for qemu-devel@nongnu.org; Wed, 14 Jul 2004 12:41:07 -0400 Received: from dsl081-088-222.lax1.dsl.speakeasy.net (HELO [192.168.111.2]) ([64.81.88.222]) (envelope-sender ) by mail4.speakeasy.net (qmail-ldap-1.03) with SMTP for ; 14 Jul 2004 16:41:05 -0000 Subject: Re: [Qemu-devel] Win98: how to exchange data with Linux From: "John R. Hogerhuis" In-Reply-To: <40F514D1.1010008@bellard.org> References: <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> <1089742289.13010.20.camel@aragorn> <40F42A9D.5000901@kadu.net> <20040714024203.GD6436@jbrown.mylinuxbox.org> <40F501E8.7030405@kadu.net> <40F514D1.1010008@bellard.org> Content-Type: text/plain Message-Id: <1089823480.1160.124.camel@aragorn> Mime-Version: 1.0 Date: Wed, 14 Jul 2004 09:44:40 -0700 Content-Transfer-Encoding: 7bit Reply-To: jhoger@pobox.com, 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 Wed, 2004-07-14 at 04:11, Fabrice Bellard wrote: > 1) built-in FTP server in the SLIRP layer. HTTP was intended at least in part to replace FTP. It might make more sense as a file transfer protocol. Maybe integrate a simple web server into SLIRP layer instead of FTP? Of course you would need some basic security like default the service to being OFF, and once enabled defaulted to allowing connections from localhost only. Makes you wonder what else would be interesting besides some of the file system one could expose through a default web page by QEMU. Things like: whether in BIOS code, cpu utilization, a recent snapshot of the screen, some basic things about processor mode, amount of RAM in use, perhaps some control buttons like RESET, SUSPEND, PAUSE, partitions and %full, etc. -- John.