From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1N65PF-0000qy-N6 for qemu-devel@nongnu.org; Thu, 05 Nov 2009 11:41:53 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1N65PB-0000li-Qm for qemu-devel@nongnu.org; Thu, 05 Nov 2009 11:41:53 -0500 Received: from [199.232.76.173] (port=40262 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1N65PB-0000lV-Ms for qemu-devel@nongnu.org; Thu, 05 Nov 2009 11:41:49 -0500 Received: from mail2.shareable.org ([80.68.89.115]:57498) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1N65PB-00029z-4s for qemu-devel@nongnu.org; Thu, 05 Nov 2009 11:41:49 -0500 Date: Thu, 5 Nov 2009 16:41:45 +0000 From: Jamie Lokier Subject: Re: [Qemu-devel] [PATCH 0/4] net-bridge: rootless bridge support for qemu Message-ID: <20091105164145.GD21630@shareable.org> References: <1257294485-27015-1-git-send-email-aliguori@us.ibm.com> <4AF2E247.3090409@redhat.com> <4AF2E2E3.1030600@redhat.com> <20091105144608.GB689@redhat.com> <4AF2E6F7.2010201@us.ibm.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <4AF2E6F7.2010201@us.ibm.com> List-Id: qemu-devel.nongnu.org List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Anthony Liguori Cc: Mark McLoughlin , Arnd Bergmann , Dustin Kirkland , Juan Quintela , qemu-devel@nongnu.org, Michael Tsirkin , Avi Kivity Anthony Liguori wrote: > Absolutely. I wanted to not have a hard dependency on PolicyKit to > start out with but that's always been the plan. I'd like to eventually > add an optional PolicyKit dependency and when that's available not even > bother with the qemu acl file. The nice thing about PolicyKit is the > desktop integration. It's a much better user experience to allow a user > to be prompted to allow qemu to access a bridge vs. having to error out > to the user and tell them to muck with a config file. Please do keep it optional. PolicyKit is actively unhelpful when you're configuring a remote server which doesn't have a desktop, or you don't have access to it's desktop. It's also unhelpful when you're trying to script something. The last thing you want a test harness script to do is prompt the user. I much prefer command line errors in both those cases :-) -- Jamie