On Wed, 17 Mar 2004, Thomas Guettler wrote:
> - How can I display the capabilities of /proc/self/status
> in a humanreadable form?
reducecap --show
> - Would be nice if you get the missing capability in
> the error message: "Missing Capability CAP_SYS_CHROOT"
> instead of "Operation not pe
On Wed, 17 Mar 2004, Dariush Pietrzak wrote:
> > /proc/mounts is evil too since it discloses the devices where the
> > virtual server and other virtual servers are mounted.
> I don't think proc/mounts counts as 'evil'.
>
> Although it would be nice to have virutalised and configurable
> proc/m
> /proc/mounts is evil too since it discloses the devices where the
> virtual server and other virtual servers are mounted.
I don't think proc/mounts counts as 'evil'.
Although it would be nice to have virutalised and configurable
proc/mounts
--
Key fingerprint = 40D0 9FFB 9939 7320 8294 05E
Herbert Poetzl wrote:
yeah, what proc entries are required on your system?
the thing is, we haven't got too much feedback about
which entries are required on distro XY, so we still
do not know which entries are mandatory, and which are
optional, we know for sure that
/proc/{*info,stat,uptime,lo
Hi again,
If you use "--cap CAP_NET_RAW" with chcontext
chroot is not possible.
Giving at least one --cap option seems to change something.
If I give no --cap option chroot is possible.
Would be nice if this was documented in the man page.
- util-vserver-0.29.3/NEWS:
Version 0.30 --> What is
This is a limited mailing. If you do not wish to receive advertisements from Steelwater Solutions Corporation via e-mail, please contact us at [EMAIL PROTECTED] to be removed from any future mailings and accept our apologies for any inconvenience.
On Wed, Mar 17, 2004 at 10:57:27AM +0100, Thomas Guettler wrote:
> Hi,
Hi Thomas!
> I am new to vserver. I read the very good introduction
> at:
> http://dns.solucorp.qc.ca/miscprj/s_context.hc?dp=0&full=1&prjstate=1&nodoc=0
>
> Versions:
> vserver: 2.4.25-vs1.3.8
> util-vserver-0.29.3
> vproc
Hi,
I am new to vserver. I read the very good introduction
at:
http://dns.solucorp.qc.ca/miscprj/s_context.hc?dp=0&full=1&prjstate=1&nodoc=0
Versions:
vserver: 2.4.25-vs1.3.8
util-vserver-0.29.3
vproc-0.01
~~~
First Problem:
edison:~ # chcontext bash
New security context is