This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
Home Products Support Community News


[Xen-devel] Questions about Xen qemu-dm so I can finish my Debian packag

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Questions about Xen qemu-dm so I can finish my Debian packaging
From: Thomas Goirand <thomas@xxxxxxxxxx>
Date: Tue, 29 Dec 2009 04:55:53 +0800
Cc: Samuel Thibault <sthibault@xxxxxxxxxx>, Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx>, Christian Motschke <christian@xxxxxxxxxxx>, Stefano Stabellini <stefano.stabellini@xxxxxxxxxxxxx>
Delivery-date: Mon, 28 Dec 2009 12:56:18 -0800
Dkim-signature: v=1; a=rsa-sha1; c=relaxed; d=goirand.fr; h=message-id :date:from:mime-version:to:cc:subject:content-type: content-transfer-encoding; s=postfix; bh=amaS7sD3czLVF/xC3bdPx5l Dulc=; b=pc6sp1+G8yV6TpasCelWjnkl9gTbCZwuzlDTT8wVRZJRmvhUTHukUzQ tcYtIvFI1TIItkbRikpJd3i4J0IyqCIqR6gjzm///LB3DNfv86taSWSCTkkihnjc jpfk/B7Teterke+9q/HZPXR8xxUaggh+YhKwheOystcHTs4RpKjQ=
Domainkey-signature: a=rsa-sha1; c=nofws; d=goirand.fr; h=message-id:date :from:mime-version:to:cc:subject:content-type: content-transfer-encoding; q=dns; s=postfix; b=TDcmK8vHUwfjMbjb8 xsn/E/Gtr47SxjoElTmKe6oO2DDjGyWQ5iZVNsGgxS/24F2qNQnMIizG7w7qZj/5 AD/9Ki8n8V0YYAtLdOgnRaExxGefR8VaRNhwMl+ABUudUgdNyuOtC6vBAAYQEDfM uSg57XDcD2xm3CMHrn9T9w+r9w=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Openpgp: id=98EF9A49
Organization: GPLHost
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla-Thunderbird (X11/20090707)

By default in xen-config-host.h, there is:

#define DEFAULT_NETWORK_SCRIPT "/etc/xen/qemu-ifup"

why isn't it:

#define DEFAULT_NETWORK_SCRIPT "/etc/xen/scripts/qemu-ifup"

and can it be changed in the Git to be like this by default? Or should I
patch it in my package?

Also, I asked the following, and still got no answer about it:

1- What is qemu-nbd-xen for, and do I need to package it (together with
its manpage)? Should it go in /usr/bin?

2- Is there anything else than qemu-dm, or qemu-img-xen, that needs to
be present in this package?

3- By default, the xen-setup script does:

./configure --disable-gfx-check --disable-curses \
   --disable-slirp "$@" --prefix=/usr

but I saw in the help of ./configure that there is:

that can have the value oss alsa sdl esd pa fmod. I really believe that
OSS support only is not a good idea, and that ALSA, Pulse Audio, SDL and
ESD support would be good. Are they activated by default?

4- Is this normal, and could it be avoided:

dpkg-shlibdeps: warning: dependency on libm.so.6 could be avoided if
"debian/xen-qemu-dm-3.4/usr/lib/xen-3.4/boot/qemu-dm" were not uselessly
linked against it (they use none of its symbols).
dpkg-shlibdeps: warning: dependency on libXext.so.6 could be avoided if
"debian/xen-qemu-dm-3.4/usr/lib/xen-3.4/boot/qemu-dm" were not uselessly
linked against it (they use none of its symbols).

I really need these answers before the upload of my Debian package, that
by the way, works already.


Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>