From: Cathy Sarisky (cathy_at_acornhosting.net)
Date: Wed 09 Oct 2002 - 23:43:13 BST
I'm spawning ~200MB vservers, POST unification. Of course, that includes (ununified) source code and compiled executables for PostgreSQL and AOLserver, in addition to all the usual stuff you might want on a server.
I'd vote for building from the base server the FIRST time, doing a serious weeding job, and then using vbuild to build future servers off that one. Or at least, that's how I do it.
RPMs that can DEFINITELY go:
iptables/chains/etc
anything firewall related (requires iptables/chains/etc)
kudzu <-- evil. May hang during vserver start if the vserver user turns it on with chkconfig.
Anything related to the sound card (duh.)
Anything related to burning CDs (duh. But I got both on my last dedicated server installed by the server provided, so watch for it.)
almost anything involving networking or the kernel.
I prefer to trim down than build up, since there's always something I want that I'll miss if I try to build up.
---------- Original Message ----------------------------------
From: Ivan Faes <ivan.faes_at_winlin.be>
Reply-to: vserver_at_solucorp.qc.ca
Date: 09 Oct 2002 23:55:06 +0200
>Mm mine is now about 600 mb each a bith to big :-)
>
>that one is made with newvserver
>
>
>On Wed, 2002-10-09 at 23:34, Roderick A. Anderson wrote:
>> On 9 Oct 2002, Ivan Faes wrote:
>>
>> > Hi I just started working with vserver.
>> >
>> > I have build some vservers with the vserver xx build and so on
>> >
>> >
>> > Buth what is the best way to make you first vserver and to use that one
>> > as a skel for the other vservers.
>> >
>> > also as small as possible.
>>
>> What is small? This is the question and I have been pondering it for
>> awhile. I just tried using the Linuxconf vserver module to build my base
>> vserver and was not happy with either the minimal or full install. It
>> probably was I wanted some 'optional' packages that I consider necssary
>> and didn't automagically get them. (I still have more experimenting to
>> do.)
>> I'm on a RPM list and have got some suggestions as to how to figure out
>> what packages require what other packages so I cam build a list and then
>> only install those I want and need.
>>
>> For now I've made my base vserver from the main server and I'll start
>> slicing and dicing out the fluff. You might try the same.
>>
>>
>> Rod
>> --
>> "Open Source Software - Sometimes you get more than you paid for..."
>>
>
>
>
________________________________________________________________
Sent via the WebMail system at webmail.pioneernet.net