From: Carlo Marcelo Arenas Belon <carenas-kLeDWSohozoJb6fo7hG9ng@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: using the kvm python wrapper (was Re: [PATCH] Fallback to use /sbin/ifconfig if /sbin/ip is not available)
Date: Sun, 16 Sep 2007 05:37:33 -0500 [thread overview]
Message-ID: <20070916103733.GA27461@tapir> (raw)
In-Reply-To: <46ECFF59.3040702-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Sun, Sep 16, 2007 at 12:03:05PM +0200, Avi Kivity wrote:
<SNIP>
> but why is anyone using this wrapper? I thought I was the
> only one, and that from tradition rather than any real need.
at least in my case, out of confusion, as it gets installed and is not
prepared to work in an installed tree but in the root of a compiled one, hence
generating errors when executed.
FWIW, it is also being used by debian in their kvm package installed in
/etc/kvm/utils/kvm as you can see from :
http://packages.debian.org/sid/kvm
I agree though that it isn't really that useful, and in that case it should
be probably removed (or at least not part of make install)
Carlo
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
next prev parent reply other threads:[~2007-09-16 10:37 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-09-16 9:42 [PATCH] Fallback to use /sbin/ifconfig if /sbin/ip is not available Carlo Marcelo Arenas Belon
2007-09-16 10:03 ` Avi Kivity
[not found] ` <46ECFF59.3040702-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2007-09-16 10:37 ` Carlo Marcelo Arenas Belon [this message]
2007-09-18 14:03 ` using the kvm python wrapper (was Re: [PATCH] Fallback to use /sbin/ifconfig if /sbin/ip is not available) Avi Kivity
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=20070916103733.GA27461@tapir \
--to=carenas-kledwsohozojb6fo7hg9ng@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org \
--cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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