All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jan Kiszka <jan.kiszka@siemens.com>
To: Rob Landley <rob@landley.net>
Cc: blauwirbel@gmail.com, Vincent Palatin <vpalatin@chromium.org>,
	qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] -net interface association behavior change in current -git.
Date: Fri, 13 May 2011 12:57:06 +0200	[thread overview]
Message-ID: <4DCD0E82.6000103@siemens.com> (raw)
In-Reply-To: <4DCD0878.2050408@landley.net>

On 2011-05-13 12:31, Rob Landley wrote:
> On 05/13/2011 01:39 AM, Jan Kiszka wrote:
>>>  Actually, reading qemu
>>> --help it looks like I should be using hostfwd= but the documentation on
>>> that is REALLY WEIRD:
>>>
>>>   This option can not be given multiple times, but multiple rules may
>>>   be combined.
>>
>> Where did you find this? A quick grep did not reveal the location to me.
>> qemu-options.hx states it clearly:
> 
> I did a "man qemu" and searched for hostfwd, it was at the end of the
> first paragraph:
> 
>    hostfwd=[tcp|udp]:[hostaddr]:hostport-[guestaddr]:guestport
>        Redirect incoming TCP or UDP connections to the host port
>        hostport to the guest IP address guestaddr on guest port
>        guestport. If guestaddr is not specified, its value is x.x.x.15
>        (default first address given by the built-in DHCP server). By
>        specifying hostaddr, the rule can be bound to a specific host
>        interface. If no connection type is set, TCP is used. This
>        option can not be given multiple times, but multiple rules may
>        be combined.
> 
> Looks like it grabbed the xubuntu 10.04 (current LTS) man page, which is
> wrong.  The one in the qemu source is correct, but wasn't built by
> "make" or installed by "make install".  (It built when I explicitlly
> said make qemu.1 though.  Go figure.)
> 
> *shrug*  Never underestimate ubuntu's ability to subtly break qemu, this
> is the... fourth different way I've noticed them doing that?  (I dunno
> why they keep fiddling with it.  Thought installing qemu from source
> also installed the man page, which would be in the search path before
> the distro version.  My bad...)

Did they also "improve" the code accordingly? Indeed very strange.

Jan

-- 
Siemens AG, Corporate Technology, CT T DE IT 1
Corporate Competence Center Embedded Linux

  reply	other threads:[~2011-05-13 10:57 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-12  2:39 [Qemu-devel] -net interface association behavior change in current -git Rob Landley
2011-05-12 13:20 ` Vincent Palatin
2011-05-13  1:10   ` Rob Landley
2011-05-13  1:19     ` Vincent Palatin
2011-05-13  1:49       ` Rob Landley
2011-05-13  6:39         ` Jan Kiszka
2011-05-13 10:31           ` Rob Landley
2011-05-13 10:57             ` Jan Kiszka [this message]
2011-05-13  6:15       ` Brad Hards
2011-05-12 14:10 ` Markus Armbruster
2011-05-13  1:48   ` Rob Landley
2011-05-13  6:54     ` Markus Armbruster
2011-05-13 10:34       ` Rob Landley
2011-05-13 12:19         ` Markus Armbruster
2011-05-13 21:45           ` Rob Landley
2011-05-16 14:12             ` Markus Armbruster

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=4DCD0E82.6000103@siemens.com \
    --to=jan.kiszka@siemens.com \
    --cc=blauwirbel@gmail.com \
    --cc=qemu-devel@nongnu.org \
    --cc=rob@landley.net \
    --cc=vpalatin@chromium.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.