On Wed, 25 Feb 2004, Sam Vilain wrote:
> Turning off the modules you don't use is a minefield, there is no
> simple answer.
Boy did I discover that. Build a new kernel last Friday, cut way back
module/driver-wise booted it and got no errors and all the vservers were
running or at least appeared
On Wed, 25 Feb 2004, Sam Vilain wrote:
> Turning off the modules you don't use is a minefield, there is no
> simple answer. A good rule of thumb is to use `lspci' and `lsmod' and
> make sure that for each piece of hardware that identified that you
> care about, you have a driver compiled.
Thanks
On Wed, 25 Feb 2004 10:57, Roderick A. Anderson wrote;
> So with a lean .config file all other/specific stuff could be
> added. I'm sure all the serious Linux users on this list already
> do this but for us 'challenged' individuals this ain't the
> case. Where I'm heading is is there
There is only ONE kernel on a vserver system, allowing different
virtual "servers" running in different contexts. This is totally
different from UserMode Linux (UML) where every virtual server
can run a different kernel.
With linux-vserver you have to compile one kernel for your system,
patched w
I'm taking a few minutes (as the compile of a new vserver kernel goes on)
to ask what is probably a very naive question.
Has anyone came up with a very lean .config for vserver? Jacques is OK
but there looks to be a bit of fluff in it. Unneeded modules, features,
etc. I think I have it correct
