[Pkg-xen-devel] NetworkManager problems with xen bridging

[Sally-Anne Edwards]

> I think you did not get what I meant:
> You want n-m to not touch some of your network configuration.
> And I say: if you do not want n-m to do bad stuff:
> just not install it.
>
It installs by default if you choose a `Desktop'  install and it will
confuse people who haven't encountered it before

> In real world, Xen runs on servers. And servers does not use n-m.
> They use static configuration in /e/n/i. Final point.

See these slides by Ian Pratt, page 4:

Xen Project Mission
- Support multiple CPU types; big and small
systems
 – From server to client to mobile phone

>
> I guess that n-m got installed because you installed an entire graphical
> environment, which is just *bad* *bad* *bad* on a server.
>
It is a dependency of `apt-get install gnome'

I agree it is bad for a server

Virtualization is not just for servers, nor is Debian just for servers

VMware has a workstation and `Player' product, both are well known -
people will expect the same from Xen

This probably can't be made perfect for Lenny, but at least it can go
in the README.Debian, and a more elegant solution can be requested
from the Xen community in the long term