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 witch the vserver-patch(es) and with all the functionality and modules you would need to run your business on this system without vservers. Thomas Am Die, den 24.02.2004 schrieb Roderick A. Anderson um 22:57: > 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 correctly in mind that anything needed in a > vserver -- kernel-wise -- has to be in the main server. But as far as > networking and other very system related stuff this could be limited > during the configure process. > 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 a way to document -- on a running system -- the hardware that needs > drivers/modules and what they are named or where they are located when > doing 'make menuconfig'? > Along with this does 'make dep' resolve any issues that relate to > doing it this way? > > > TIA, > Rod -- Thomas Gelf <[EMAIL PROTECTED]> _______________________________________________ Vserver mailing list [EMAIL PROTECTED] http://list.linux-vserver.org/mailman/listinfo/vserver
