From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Wed 12 Mar 2003 - 10:02:51 GMT
On Wed, Mar 12, 2003 at 08:33:27AM +0100, debby_at_aachenconsulting.de wrote:
> I wonder how you manage to trim down Woody-vservers so that there remain
> only some 20MB that cannot be shared (I suppose those are config files).
from 12 to 25 MB are usually unshareable
between different vservers of the same distribution,
regardless of the distribution size ...
> Is there a script to automate this? '?vunify' does not work with Debian
search the archives, there was a thread about
a generalized vserver unify script somewhere
(I don't know its state, because I use an RPM based
distribution, so vunify works for me)
> and how do you set the 'Immutable Linkage Invert' bit? I cannot
> 'chattr +I' - Do I need to patch the ctx16-kernel ...?
no, the tools to read/modify the ILI flag are in the
vserver package ...
showattr file ...
Presents extended file attribute.
setattr --immutable --immulink file ...
Sets the extended file attributes.
These utilities exist as an interim until lsattr and
chattr are updated.
> Re: [vserver] Trimming the fat?
> Date: Wed, 12 Mar 2003 17:06:55 +1300
> From: Sam Vilain <sam_at_vilain.net>
> To: vserver_at_solucorp.qc.ca
> Reply to: vserver_at_solucorp.qc.ca
> Try starting with something like the debian potato base install if you want
> something really trim. It's only 30MB.
> Debian Woody seems to be more, about 80MB. About 10MB of that is dpkg
> cache, and all but 20MB can be shared between vservers using Immutable
> Linkage Invert.
> On Wed, 12 Mar 2003 13:11, you wrote:
> > Ever since I compiled my very-own kernel (and it works) I'm feeling kind
> > of smug. The system has been up for 5 days plus some hours without
> > getting hit by the infamous ctx16 bug(?).
> > So I'm once again in search of the minimal vserver. This time I taken a
> > different approach. Since many of us seem to to be having a problem
> > with creating a new vserver from RHL CDs I took the cheap route and made
> > my base one from the main server. I'm now in the process of clearing
> > out all the inapropriate and unnecessary stuff. A final clean up on a
> > vserver by vserver basis will be performed as they are created.
> > So to the nuts and bolts of the issue. Has anyone trimed /etc/init.d
> > down to those things that can and need to run in a vserver. ntpd sure
> > is a candidate along with rawdevices. What else can I deleted? I am
> > not concerned about breaking RPM packages, such as deleting a file
> > inserted / created by a package.
> > Any thoughts?
> > TIA,
> > Rod
> Sam Vilain, sam_at_vilain.net
> Real Programmers don't like the Team Programming concept. Unless of
> course, they are the Chief Programmer.