From: Herbert Poetzl (herbert_at_13thfloor.at)
Date: Tue 09 Aug 2005 - 00:19:23 BST
On Tue, Aug 09, 2005 at 12:24:34AM +0200, Enrico Scholz wrote:
> jcpetit_at_syspark.com (Jean-Christophe Petit) writes:
> > 18.104.22.168-vs2.0-rc9 with util-vserver-0.30.208 under CentOS 4
> > followed the http://linux-vserver.org/CentOS_HowTo
> > when in the vserver, "rpm -qa" gives nothing.
> Expected; external packagemangement is used by default which holds rpm
> database outside of the vserver. When you *really* need it, 'vserver
> ... pkgmgmt internalize' should copy it into the vserver so that 'rpm
> -q' works there. But for most vserver types, the external management
> should suffice.
well, probably depends on the application ...
I guess the 'typical' vps provider, which wants to
give a guest to the customer is not too happy about
an external package management (and probably the
customer will not be too happy either), but as you
said, it's configurable which should suffice ...
> > I have the /.rpmdb/ in place with files inside:
> > bash-3.00# ls -la /.rpmdb/
> > total 504
> > drwxr-xr-x 2 root root 4096 Aug 3 05:12 .
> > drwxr-xr-x 22 root root 4096 Aug 3 05:04 ..
> > -rw-r--r-- 1 root root 16384 Aug 3 05:08 __db.001
> > -rw-r--r-- 1 root root 1318912 Aug 3 05:08 __db.002
> > -rw-r--r-- 1 root root 450560 Aug 3 05:08 __db.003
> > -rw-r--r-- 1 root root 12288 Aug 3 05:12 Group
> These files were created by your 'rpm -q' operation which initializes
> the rpm database.
an option at vserver creation time would be nice
to have though ... maybe it's already there but not
documented yet? (like the ulimits on 2.6)
> Vserver mailing list
Vserver mailing list