Date: Thu 10 Oct 2002 - 16:40:27 BST
One list will do fine :-)
> I'm a little worried by your comment that I'm "throwing rocks." If you
> mean I was criticizing, that wasn't my intent. Anyone who'd like one
> is welcome to a list of what I've got on my vservers.
> Cathy Sarisky
> On Thursday, October 10, 2002 4:55 AM, Roderick A. Anderson
> [SMTP:raanders_at_acm.org] wrote:
>> On Wed, 9 Oct 2002, Cathy Sarisky wrote:
>> > 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.
>> > 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.
>> This is great, but ...
>> > 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.
>> you know what would be greater? Yup, your idea (rpm list) of a
>> trimmed down vserver install. :-)
>> It is so much easier to throw rocks than to build. Mind you, I
>> wouldn't throw rocks.
>> "Open Source Software - Sometimes you get more than you paid for..."