From: Bill Longman <bill.longman@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Increasing security [WAS: Rooted/compromised Gentoo, seeking advice [Solved?]
Date: Mon, 16 Aug 2010 09:24:31 -0700 [thread overview]
Message-ID: <4C69663F.1060708@gmail.com> (raw)
In-Reply-To: <4C696255.20505@gmail.com>
On 08/16/2010 09:07 AM, Jarry wrote:
> On 16. 8. 2010 17:29, Mark Knecht wrote:
>> On Mon, Aug 16, 2010 at 7:16 AM, Bill Longman<bill.longman@gmail.com>:
>>>>
>>>> That is why I picked up Linux-VServer (actually, first I tried
>>>> OpenVZ but could not make it run). It is a kind of compromise,
>>>> where all guests share the same kernel. This brings certain
>>>> security implications, but on the other side, I can run dozens
>>>> of guest on a moderate machine, with 4-cores and 8GB memory
>>>> (i.e. a guest running bind takes just about 20MB of memory)...
>>>
>>> This looks rather interesting, Jarry. Is it simply a matter of compiling
>>> the vserver-sources and util-vserver? Did it take much time to set up
>>> the kernel for your box? Or is it pretty much a typical kernel setup?
>>> Any good tools in the util-vserver package?
>
> vserver-sources and util-vserver was all I needed. Kernel is
> pretty much like common, with ~10 additional options. util-vserver
> contains handy tools, like "v*" (* being emerge, esync, kill,
> limit, mount, ps, sched, etc.). Updating all gentoo-guests can be
> done with one command executed in host...
>
>>> Sounds very efficient.
>
> Really is. Now I'm running 27 guests, mostly gentoo but also
> some ubuntu and opensuse. Actually, it is possible to run any
> linux-based system (as I said all systems share the same kernel).
> There is also pretty good control over resources allocated
> to individual guests (disk, memory, cpu).
>
> Administration is very comfortable. Tasks like clonning,
> backup/restore, moving, migration, etc, are very easy to...
>
>> I guess the baselayout-vserver packages is somehow for setting up each
>> of the guests?
>
> Guests are installed using customised stage3 (baselayout2-based).
> After that, you work with them as with normal gentoo-system.
The Gentoo version of Solaris Zones! w00t!
next prev parent reply other threads:[~2010-08-16 16:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-10 6:10 [gentoo-user] Re: Rooted/compromised Gentoo, seeking advice [Solved?] Paul Hartman
2010-08-10 8:47 ` Neil Bothwick
2010-08-13 15:25 ` [gentoo-user] Increasing security [WAS: " Enrico Weigelt
2010-08-13 16:25 ` Mark Knecht
2010-08-13 17:07 ` Bill Longman
2010-08-13 19:05 ` Enrico Weigelt
2010-08-14 19:32 ` Jarry
2010-08-16 14:16 ` Bill Longman
2010-08-16 15:29 ` Mark Knecht
2010-08-16 16:07 ` Jarry
2010-08-16 16:24 ` Bill Longman [this message]
2010-09-10 1:06 ` Enrico Weigelt
2010-08-13 18:58 ` Enrico Weigelt
2010-08-13 19:24 ` Mark Knecht
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4C69663F.1060708@gmail.com \
--to=bill.longman@gmail.com \
--cc=gentoo-user@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox