From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([140.186.70.92]:39142) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKGe7-0001F8-BQ for qemu-devel@nongnu.org; Wed, 11 May 2011 17:08:40 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QKGe5-0002Ro-Kl for qemu-devel@nongnu.org; Wed, 11 May 2011 17:08:39 -0400 Received: from isrv.corpit.ru ([86.62.121.231]:35341) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QKGe5-0002Pv-EB for qemu-devel@nongnu.org; Wed, 11 May 2011 17:08:37 -0400 Message-ID: <4DCAFACA.1040104@msgid.tls.msk.ru> Date: Thu, 12 May 2011 01:08:26 +0400 From: Michael Tokarev MIME-Version: 1.0 References: <4DCAF63E.9060905@web.de> In-Reply-To: <4DCAF63E.9060905@web.de> Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Subject: Re: [Qemu-devel] adding search to dhcp List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Jan Kiszka Cc: Stefan Hajnoczi , Markus Armbruster , Carl Karsten , qemu-devel 12.05.2011 00:49, Jan Kiszka =D0=BF=D0=B8=D1=88=D0=B5=D1=82: > On 2011-05-11 18:08, Stefan Hajnoczi wrote: >> On Wed, May 11, 2011 at 4:22 PM, Carl Karsten = wrote: >>> On Wed, May 11, 2011 at 6:01 AM, Markus Armbruster wrote: >>>> Stefan Hajnoczi writes: >>>> >>>>> On Tue, May 10, 2011 at 6:40 PM, Carl Karsten wrote: >>>>>> I would expect the syntax to look like this: >>>>>> >>>>>> qemu -hda 1.qcow2 -net nick -net >>>>>> user,hostname=3Dqemu,search=3Dexample.com,sales.example.com >>>>> >>>>> Comma escaping is needed but it seems like a reasonable feature to = me. >>>> >>>> Comma escaping is ugly: >>>> -net user,hostname=3Dqemu,search=3Dexample.com,,sales.example.com >>>> >>>> Could we have multiple search options instead? Like this: >>>> -net user,hostname=3Dqemu,search=3Dexample.com,search=3Dsales.exampl= e.com >>>> >>> >>> How about: >>> >>> -net user,hostname=3Dqemu,search=3D"example.com,sales.example.com" >> >> That does not work the way you'd expect: >> $ echo asdf=3Dasdf,ok=3D"this,is,a,test" >> asdf=3Dasdf,ok=3Dthis,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. >=20 > -net user,hostfwd=3D...,hostfwd=3D... >=20 > Let's got for multiple specification, ',,' is just ugly IMHO. I second this, just repeat the specification, please no double ,,. Or alternatively, search1=3Dfoo,search2=3Dbar, 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