The "legacy" method did, in fact, ignore /lib64 and failed to copy it.
After manually copying that directory,
I got no error messages, but I still couldn't start the vserver.
I finally managed to get the "yum" method to work, and the vserver
starts!!!! YEAH!
Jacques Gelinas wrote:
On Thu, 17 Feb 2005 14:33:05 -0500, Paul S. Gumerman wrote
I'm at the point where I need some help.
The machine is a dual Opteron, with Fedora Core 3 installed. I've
downloaded a vanilla 2.6.11rc-3 kernel, and patched it with the latest
vs1.94-rc4 patch set, which applied and built cleanly. Then I built the
util-vserver packages from source, and installed them with rpm.
Since I want to try things first with a FC3 x86_64 virtual server, I
ended up using the "legacy" option to build vserver "vts64". I then
edited rc.sysinit to remove most everything. I also created a "test"
server with the "skeleton" build option, and used that info and info
from Google to create the newer config files for "vts64". I'm fairly
certain that all the config stuff is good.
But ...... when I try to start the vserver, I get this error message:
vcontext: execvp("/etc/rc.d/rc"): No such file or directory
Do you have /lib64 installed in the vserver ?
Maybe the build strategy ignore this directory (which only exists on x64).
---------------------------------------------------------
Jacques Gelinas <[EMAIL PROTECTED]>
dav_ufs: Access your home directory using WebDav
http://www.solucorp.qc.ca/miscprj/dav_ufs.hc
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
|
_______________________________________________
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
