qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Anthony Liguori <anthony@codemonkey.ws>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [PATCH] Capture network traffic to a tcpdump file - updated
Date: Mon, 10 Dec 2007 16:36:27 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0712101633460.27959@racer.site> (raw)
In-Reply-To: <475D6965.5010500@codemonkey.ws>

Hi,

On Mon, 10 Dec 2007, Anthony Liguori wrote:

> Johannes Schindelin wrote:
> > 
> > On Mon, 10 Dec 2007, Anthony Liguori wrote:
> > 
> >   
> > > Balazs Attila-Mihaly (Cd-MaN) wrote:
> > >     
> > > > Here goes v0.2 for my patch :-)
> > > > Changes
> > > > - now the option is a separate command line switch:
> > > >   -net capture,vlan=2,file=test.pcap
> > > >         
> > > Is it really necessary/useful to specify this on the command line 
> > > since it can be controlled from the monitor?
> > >     
> > 
> > As was said in another mail, if you want to guarantee that _every_ 
> > packet is logged, the command line is the most convenient.
> > 
> > Besides, if you get your monitor support, why do you care about 
> > command line support?
> >   
> 
> It's just an issue of usability.  If you don't have to expose something 
> two ways, then it's better not to.

Okay, since you so nicely ask for it: I _want_ the command line option.  I 
do not like having to type the same thing into the monitor every time I 
start QEmu.

But I expressly do _not_ ask to scrap the monitor interface, even if I 
have no use for it.

However, I have no problem maintaining my own fork.  Much like I will do 
with VNC again, since I recently had to use QEmu via VNC and the artefacts 
are just horrible.

Ciao,
Dscho

  reply	other threads:[~2007-12-10 16:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-12-10 10:45 [Qemu-devel] [PATCH] Capture network traffic to a tcpdump file - updated Balazs Attila-Mihaly (Cd-MaN)
2007-12-10 15:36 ` Anthony Liguori
2007-12-10 15:40   ` Johannes Schindelin
2007-12-10 16:29     ` Anthony Liguori
2007-12-10 16:36       ` Johannes Schindelin [this message]
2007-12-10 17:53         ` Anthony Liguori
2007-12-10 19:28           ` Johannes Schindelin
2007-12-10 21:56             ` Anthony Liguori
2007-12-10 16:05   ` Paul Brook
2007-12-10 16:15     ` Anthony Liguori
2007-12-11  1:25   ` Thiemo Seufer
2007-12-11 22:28 ` andrzej zaborowski
2007-12-11 22:40   ` Paul Brook
  -- strict thread matches above, loose matches on Subject: below --
2007-12-10 16:20 Balazs Attila-Mihaly (Cd-MaN)

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=Pine.LNX.4.64.0712101633460.27959@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=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).