Re: vserver path leak?

> On Tue, 2 Jun 2009 00:14:45 -0400
> Micah Anderson <micah@...> wrote:
>
> Thanks for your response, sorry about my delay getting back to you.
>
> > * Karl Goetz <karl@...> [2009-06-01 23:31-0400]:
> > > The suggestion in #vserver was "if you manage to get a host path on
> > > a recent (non broken, i.e. non-debian :) kernel and util-vserver,
> > > then it is considered a bug and will be fixed ASAP ... because that
> > > basically means that the namespace isolation is not working
> > > properly"
> > >
> > > Is this a valid bug? Is there some debianisms involved that could
> > > cause the issues, or is it just another upstream who doesnt like
> > > "unoffical" packages? :)
> >
> > Only one way to find out, build a vanilla upstream, with the patch and
> > find out.
> >
> > However, I cannot reproduce what you have seen, using the same
> > kernel.
>
> Odd. I've just done it again, using the same two vhosts.
> (sorry about the wrapping)
>
> sidvs:~/debomatic/Debomatic#
>
> wesnoth:~#
> mv /home/vservers/sidvs/root/debomatic /home/vservers/autobuilders/root/
>
> sidvs:~/debomatic/Debomatic# cd ..
> sidvs:/home/vservers/sidvs/vservers/autobuilders/root/debomatic#
>
> wesnoth is the host.