[Pkg-xen-devel] missing xen-utils binaries

Henning Sprang henning_sprang at gmx.de
Mon Jun 18 10:49:25 UTC 2007


Goswin von Brederlow wrote:
>>> look at
>>> # for i in `ls /usr/lib/xen-3.1.0-1/bin`; do ls /usr/sbin/$i; done
>>> (with the correct version string, I suppose)
> 
> They should not be linked nor should they be used with the full path
> by anything outside that path. Instead there should be a wraper script
> in xen-utils-common that detects the right version and then calls the
> full path. Look at /usr/sbin/xend.

O.K. I forgot the wrapper. But, there are also links, just the links go 
to the wrapper, and the wrapper goes to /usr/lib/xen*/bin/* (as you 
explain).

And then, there are links for some of the binaries (linking to the 
wrapper, which then calls the right binary), for some stuff delivered by 
upstream, and some binaries are not available via the wrapper, but they 
are there in lib. And that's the point.

The question is: why?
My opinion (as a user) is: there should be all binaries available that 
are in upstream, unless there is a good reason to.
This good reason exists for xenmon.py, as Guido explained to me 
yesterday, but there are some more binaries not available - again, see

for i in `ls /usr/lib/xen-3.0.3-1/bin`; do ls /usr/sbin/$i; done

(now for the original etch Xen packages)

Henning



More information about the Pkg-xen-devel mailing list