Asbjørn Sannes

We currently migrate to MediaWiki from our old installation, but not all content has been migrated yet. Take a look at the Wiki Team page for instructions how to help or browse through our new wiki at wiki.linux-vserver.org to find the information already migrated.

I'm a student of the University of Oslo (Norway), and works/runs a small internet webhotel called Interhost ANS. We use vserver to increase security and seperate our services as much as possible. Spend most of my time studying. :)

Things that I want, need and use in vserver for linux 2.6:

• Process seperation of course! No vserver root taking over!
• IPv4 and IPv6 support to control which vserver can use which ips, this is top priority for me.
• Memory Limitation per context.
• Scheduling in a way that makes all vservers "equal" in terms of CPU.
• Support quota on filesystems mounted within the vservers root without givin raw access.
• Shouldn't meddle too much with filesystem code, I will be using ReiserFS4 when it gets a bit more stable and it supports filesystem plugins easily, meaning it shouldn't be needed to rewrite code in it to make stuff you want available.
• It should work on SMP systems.
• Documentation! (I'll help with this, even clean up developers notes and bad English)
• As little overhead as possible!

Yes, you may say that this stuff is already supported, but I'm just pointing it out.

I'd like if things were kept simple (KISS - Keep It Simple Stupid) and not make this a project that changes "everything" in the kernel because this will keep it out of the main tree forever. I actually believe that it is already too late to make it into 2.6. Also, I'm terrified of the thought of having a virtualnetwork solution (with own devices and such) as some people are thinking about, I havn't researched it properly, but I believe that it would add too much overhead for my own taste. And for the mergemem part, keep it as a seperate kludge for those who want it.