| 1 |
On 08/14/2010 12:32 PM, Jarry wrote: |
| 2 |
> On 13. 8. 2010 21:05, Enrico Weigelt wrote: |
| 3 |
>> * Bill Longman<bill.longman@×××××.com> wrote: |
| 4 |
>> |
| 5 |
>>> Basically just run VMWare/Virtualbox etc and put the services in there. |
| 6 |
>> |
| 7 |
>> well, these solutions are way "bigger" (iow: more resource |
| 8 |
>> intensive), since they run a complete operation system instance |
| 9 |
>> within the virtual machine. |
| 10 |
> |
| 11 |
> That is why I picked up Linux-VServer (actually, first I tried |
| 12 |
> OpenVZ but could not make it run). It is a kind of compromise, |
| 13 |
> where all guests share the same kernel. This brings certain |
| 14 |
> security implications, but on the other side, I can run dozens |
| 15 |
> of guest on a moderate machine, with 4-cores and 8GB memory |
| 16 |
> (i.e. a guest running bind takes just about 20MB of memory)... |
| 17 |
|
| 18 |
This looks rather interesting, Jarry. Is it simply a matter of compiling |
| 19 |
the vserver-sources and util-vserver? Did it take much time to set up |
| 20 |
the kernel for your box? Or is it pretty much a typical kernel setup? |
| 21 |
Any good tools in the util-vserver package? |
| 22 |
|
| 23 |
> The only service running on my "host" (main system) is sshd, |
| 24 |
> which I secured as much as I could. Everything else (web, mail, |
| 25 |
> dns, ftp, syslog, X, and plenty of users' services) runs on its |
| 26 |
> own guest-system, chrooted in addition (where it was possible). |
| 27 |
|
| 28 |
Sounds very efficient. |
| 29 |
|
| 30 |
TIA, |
| 31 |
|
| 32 |
Bill |
Archives