[Pkg-xen-devel] xendomains and hypervisor splitting

Ralph Passgang ralph at debianbase.de
Fri Feb 17 11:40:20 UTC 2006


Am Freitag, 17. Februar 2006 12:07 schrieb Julien Danjou:
> On Fri, Feb 17, 2006 at 12:03:29PM +0100, Guido Trotter wrote:
> > One of the first changes we might want to do is move away
> > /etc/sysconfig/xendomains... We should put it either in
> > /etc/default/xendomains (since it's an init script configuration) or
> > /etc/xen/xendomains (since it's xen related)... Which one do you prefer?
>
> /etc/default

I also think /etc/default would be the best.

> > As for the way to do it I propose a dpatch file that changes the two
> > files in the upstream tarball that actually nominate the path... It's
> > easy and it works, but sure can be done in other ways, anything you would
> > prefer?
>
> No.
>
> > Then we can go ahead splitting hypervisor and userspace... Preferences
> > for the naming? Shall we keep the hypervisor as "xen" and call the rest
> > "xen-userspace"? or "xen-hypervisor" and "xen-userspace" and have xen be
> > a metapackage depending on both, for the sake of compatibility with the
> > past?
>
> xen-userspace is a bad name I think.
> xen-manager or something like that (xen-tools is even better.. grrr).
>
> xen or xen-hypervizo+metapackage, I don't really care.

I think we should make "xen" the metapackage that installs userspace + 
hypervisor. This would help, because xen2 users are used to just install 
"xen" for all their needs.

xen-hypervisor is a good name for the hypervisor package, but what about the 
userspace stuff? I agree that xen-tools would be the best name, but as 
already noticed, this name is not free anymore. so maybe: xen-utils ?

and what about development headers and so on? xen-utils-dev or still 
libxen-dev?

--Ralph



More information about the Pkg-xen-devel mailing list