Neil Schneider wrote:
I don't really see this as an issue. We don't really need much in the
way of development tools, and from a security point of view, there
shouldn't be any on a web server/mail server.
That should be the case, but then you have to recompile some package
because it has a bug/version/feature problem. And then dependency hell
breaks loose.
If Ubuntu had a "dev-tools" package that you could install, compile, and
uninstall that would be fine. However, their dev-tools-like packages
always seem to miss something. Then configure goes "WAAAAH!" and wets
itself because it isn't running in a DeadRat environment.
How much does dom0 need? I've no set up Xen myself yet, but it seems
that a minimal install would be required for dom0.
Maybe, but you might have to be able to do kernel recompiles. The dom0
also generally defines the limits of your I/O, so you might have to tune
that like you would have to tune any Linux install for I/O throughput.
For #2, I think it would make best sense to continue running Debian
Stable, just as we do now.
I'm not a big fan of Debian, however I'm not that sensitive about it
either. Since the consensus seems to run against me, I agree.
Well, the big thing is that we can probably port the existing sparky to
a virtualized instance in a pretty straightforward way if we use Debian
in the domU.
However, if we want to use a different OS, someone can put in the time
to configure a different domU.
-a
--
KPLUG-Steer@kernel-panic.org
http://www.kernel-panic.org/cgi-bin/mailman/listinfo/kplug-steer
