[xen-tools] name conflicts of xen-tools with xen-tools

[Henning Sprang]

(I resend this because I sent it from the wrong address and don't see
it coming through)

Hi,
To say it first, I like xen-tools very much, and the great
improvements made after my wishlist bugs! I use it very successfully,
integrated with FAI for doing class-based automated
installs of Xen instances. (I'll have to document how I connect
xen-tools with FAI eventually, because I think it's a good combination
to use them together).

But, as I just now realized again, I am having problems with the name
choice of xen-tools. You might know (otherwise I tell you now), the
name xen-tools is also
used for a part of the xen distribution itself, namely these are all
the python tools and libs  cmmmunicating with the xen kernel from
within dom0, which is xm, xend and others,  and a list with the same
name.
So, it's sometimes complicate dto know what people mean when they say
xen-tools, and in my mailbox it's hard to see which of both projects
is named - even both lists add the [xen-tools] banner to the subject!

I'd be interested how you think about this conflict.

I don't know which project got the name first, so it's hard to propose
the perl xen-tools must change their name, with which there is a
running website, Debian package and other stuff associated, but I
wonder if I am the only one who realizes this conflict.

Henning