All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Tokarev <mjt@tls.msk.ru>
To: Jan Kiszka <jan.kiszka@web.de>
Cc: Stefan Hajnoczi <stefanha@gmail.com>,
	Markus Armbruster <armbru@redhat.com>,
	Carl Karsten <carl@personnelware.com>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] adding search to dhcp
Date: Thu, 12 May 2011 01:08:26 +0400	[thread overview]
Message-ID: <4DCAFACA.1040104@msgid.tls.msk.ru> (raw)
In-Reply-To: <4DCAF63E.9060905@web.de>

12.05.2011 00:49, Jan Kiszka пишет:
> On 2011-05-11 18:08, Stefan Hajnoczi wrote:
>> On Wed, May 11, 2011 at 4:22 PM, Carl Karsten <carl@personnelware.com> wrote:
>>> On Wed, May 11, 2011 at 6:01 AM, Markus Armbruster <armbru@redhat.com> wrote:
>>>> Stefan Hajnoczi <stefanha@gmail.com> writes:
>>>>
>>>>> On Tue, May 10, 2011 at 6:40 PM, Carl Karsten <carl@personnelware.com> wrote:
>>>>>> I would expect the syntax to look like this:
>>>>>>
>>>>>> qemu -hda 1.qcow2 -net nick -net
>>>>>> user,hostname=qemu,search=example.com,sales.example.com
>>>>>
>>>>> Comma escaping is needed but it seems like a reasonable feature to me.
>>>>
>>>> Comma escaping is ugly:
>>>> -net user,hostname=qemu,search=example.com,,sales.example.com
>>>>
>>>> Could we have multiple search options instead?  Like this:
>>>> -net user,hostname=qemu,search=example.com,search=sales.example.com
>>>>
>>>
>>> How about:
>>>
>>> -net user,hostname=qemu,search="example.com,sales.example.com"
>>
>> That does not work the way you'd expect:
>> $ echo asdf=asdf,ok="this,is,a,test"
>> asdf=asdf,ok=this,is,a,test
>>
>> Also, let's not get into the business of matching quotes and passing
>> them escaped on the shell.  That's just as ugly as escaping commas and
>> more work.
>>
>> I think the two options are using QEMU's typical comma escaping ',,'
>> or specifying the option multiple times.  I'd go with comma escaping
>> for consistency.  I'm not aware of any other option in QEMU that is
>> specified multiple times.
> 
> -net user,hostfwd=...,hostfwd=...
> 
> Let's got for multiple specification, ',,' is just ugly IMHO.

I second this, just repeat the specification, please no double ,,.
Or alternatively, search1=foo,search2=bar, but this is also sort
of ugly.

But I'm not sure why there's no way to use some other character,
like colon (:) for example - it's used for protocol:details
already, and for domain names it works well too...

/mjt

  reply	other threads:[~2011-05-11 21:08 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-10 17:40 [Qemu-devel] adding search to dhcp Carl Karsten
2011-05-11  9:02 ` Stefan Hajnoczi
2011-05-11 11:01   ` Markus Armbruster
2011-05-11 15:22     ` Carl Karsten
2011-05-11 16:08       ` Stefan Hajnoczi
2011-05-11 20:49         ` Jan Kiszka
2011-05-11 21:08           ` Michael Tokarev [this message]
2011-05-12  9:00             ` 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=4DCAFACA.1040104@msgid.tls.msk.ru \
    --to=mjt@tls.msk.ru \
    --cc=armbru@redhat.com \
    --cc=carl@personnelware.com \
    --cc=jan.kiszka@web.de \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@gmail.com \
    /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.