On Thu, 11 Aug 2005, Herbert Poetzl wrote:
I probably wasn't clear on this.
> given you do not disable legacy support, you can still use
> the legacy tools for your shiny new vs2.0 kernel ...
There is a vServer 2.6.10-vs1.94 kernel running but nothing important
guest-wise in on the system.
> if you compile and install the 0.30.208 (+fix) tools, they
> should also work fine with your existing kernel, so ...
Will they then work with the new vs2.0 kernel, ie. the build doesn't look
at running kernel and make decisions about what/hoe to build the utils.
> whatever you do, it is supposed to just work :)
Famous last words. Yes I am hoping this is so.
Follow up question.
I went ahead and started building the utils as RPMs and ran into a couple
of dependency issues. This is probably more an Enrico question.
Why tetex-latex? Is it Redhat ( RPM ) build-documentation requirement?
Why xalan-j ( Java? ) Is this also a Redhat-ism?
I like RPMs but I'd prefer a really clean Vserver host. ( I'll try a
straight tarball build next. )
Rod
--
"Open Source Software - You usually get more than you pay for..."
"Build A Brighter Lamp :: Linux Apache {middleware} PostgreSQL"
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
