From: Fabrice Bellard <fabrice@bellard.org>
To: qemu-devel@nongnu.org
Cc: damm@opensource.se
Subject: Re: [Qemu-devel] Adding a tftpd to slirp
Date: Thu, 15 Jul 2004 22:49:02 +0200 [thread overview]
Message-ID: <40F6EDBE.9020305@bellard.org> (raw)
In-Reply-To: <1089923129.27004.41.camel@kubu.opensource.se>
Magnus Damm wrote:
> Hi all,
>
> I would like to transfer files from my host to the virtual environment
> in a simple and fast way. With as little dependencies as possible. Right
> now I'm using uuencode and uudecode over the serial port, it works but
> it is waaay too slow.
>
> Wouldn't it be a good idea to add a tftpd besides the bootp/dhcp server?
> That would provide a simple way to get files from the host.
> (Yes, and think etherboot, pxe, u-boot...)
>
> If the maintainers think it is a good idea, then I would be happy to
> modify netkit-tftpd to work with slirp.
I would prefer FTP. FTP clients are available for every OSes with good
user interface and the FTP protocol is almost as simple as TFTP.
Fabrice.
next prev parent reply other threads:[~2004-07-15 20:52 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-15 20:25 [Qemu-devel] Adding a tftpd to slirp Magnus Damm
2004-07-15 20:49 ` Fabrice Bellard [this message]
2004-07-16 10:41 ` Pavel Janík
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=40F6EDBE.9020305@bellard.org \
--to=fabrice@bellard.org \
--cc=damm@opensource.se \
--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).