i am installing on an opteron system using gentoo and portage.
when emerging util-vserver it errored with the following
cc1: error: unrecognized command line option -fno-stack-protector-all
make: *** [bin-x86_64/start.o] Error 1
make: *** Waiting for unfinished jobs
cc1: error: unrecognized
On Sat September 23 2006 05:16, Chuck wrote:
i am installing on an opteron system using gentoo and portage.
when emerging util-vserver it errored with the following
cc1: error: unrecognized command line option -fno-stack-protector-all
make: *** [bin-x86_64/start.o] Error 1
make: ***
On Fri, Sep 22, 2006 at 11:06:49AM -0400, John Cianfarani wrote:
Hello,
I'm new to using Vserver and have just been testing it the past few
weeks. Using CentOS 4.3 and the development sources Kernel 2.6.17.11
patches 2.1.1-rc31 and utils 0.30.210.
I've been trying to find information about
got it to compile by using ~amd64 installing the r18 version
--
Chuck
___
Vserver mailing list
Vserver@list.linux-vserver.org
http://list.linux-vserver.org/mailman/listinfo/vserver
On Fri, Sep 22, 2006 at 09:09:19PM +0100, Konstantinos Pachopoulos wrote:
Hi,
while searching i saw that by editing the following
files one can set the capabilities in Debian
/etc/vservers/vserver-name/bcapabilities
/etc/vservers/vserver-name/ccapabilities.
However, trying with CAP_SYS_ADMIN
the gentoo vserver how-to says to set up the kernel this way:
[ ] Enable Legacy Kernel API
[*] Disable Legacy Networking Kernel API
however, and i don't know why this is unless i was told to set it this way
last year, the year old machine we have running has the kernel set this way:
[*]
On 2006.09.23 17:24:39 -0400, Chuck wrote:
the gentoo vserver how-to says to set up the kernel this way:
[ ] Enable Legacy Kernel API
[*] Disable Legacy Networking Kernel API
Using util-vserver 0.30.210 or later, these setting are fine, earlier
tools need the legacy networking, ancient
Hi,
as I am running debian in my vservers I got the well known problems with
dpkg on some package updates. (It failed updating files with setuid or
setgid bit set, because it cannot change the mode to 0600 before deletion).
Google quickly found the hack in modifying dpkg. I did and it worked.