From: Anthony Liguori <anthony@codemonkey.ws>
To: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] qemu-nbd: inetd support
Date: Wed, 10 Sep 2008 10:24:07 -0500 [thread overview]
Message-ID: <48C7E697.3050805@codemonkey.ws> (raw)
In-Reply-To: <1220866212.4147.15.camel@frecb07144>
Laurent Vivier wrote:
> This patch allows to put qemu-nbd in inetd.conf by using stdin/stdout
> instead of a socket.
>
> This behavior is enabled by specifying "--port=0".
>
That's kind of non-intuitive. Why not just add a --inetd option or a
flag that explicitly means read from stdio?
Regards,
Anthony Liguori
> example:
>
> # add in /etc/services.conf
>
> nbd 1024/tcp
>
> # add in /etc/inetd.conf
>
> nbd stream tcp nowait root /usr/local/bin/qemu-nbd /usr/local/bin/qemu-nbd --nocache --read-only --port 0 /ISO/ubuntu-7.10-desktop-amd64.iso
>
> Signed-off-by: Laurent Vivier <Laurent.Vivier@bull.net>
>
next prev parent reply other threads:[~2008-09-10 15:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-08 9:30 [Qemu-devel] [PATCH] qemu-nbd: inetd support Laurent Vivier
2008-09-10 15:24 ` Anthony Liguori [this message]
2008-09-10 16:10 ` Thiemo Seufer
2008-09-10 16:24 ` Laurent Vivier
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=48C7E697.3050805@codemonkey.ws \
--to=anthony@codemonkey.ws \
--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).