On Thu, 04 Nov 2004 15:00:30 +0100
Enrico Scholz <[EMAIL PROTECTED]> wrote:
> [EMAIL PROTECTED] (Herbert Poetzl) writes:
>
> >> Thoughts/comments
> >
> > what about alternative solutions, like using pivot_root
>
> I think that pivot_root(2) is a poor solution as you will run into the
> following
On Fri, 5 Nov 2004, [ISO-8859-1] Bj?rn Steinbrink wrote:
I've found an easy way to get a clean namespace using lazy mounts. A
I meant "lazy unmounting" of course.
BTW, something I really miss from FreeBSD is a forced umount.
Grisha
___
Vserver mailing lis
>
> I've found an easy way to get a clean namespace using lazy mounts. A
I meant "lazy unmounting" of course.
Bjoern
___
Vserver mailing list
[EMAIL PROTECTED]
http://list.linux-vserver.org/mailman/listinfo/vserver
> why not do it this way:
>
> 1. get a new namespace
> 2. create the vfsmount (for example via --bind)
> 3. pivot_root (or similar, maybe new cmd?) to the vfsmount
> 4. cleanup the namespace (remove host stuff)
> 5. do all required/listed mounts inside that namespace
> 6. create the context
[EMAIL PROTECTED] (Herbert Poetzl) writes:
>> Thoughts/comments
>
> what about alternative solutions, like using pivot_root
I think that pivot_root(2) is a poor solution as you will run into the
following problems:
* who will unmount the old filesystem? You will need something in the
hostile v
[EMAIL PROTECTED] (Sam Vilain) writes:
> >>> (a2) operating from the outside in the vserver
> >>
> >>ACK; (a2) is the real problem and required by tools like vrpm or
> >>vapt-get.
>
> I think this simply isn't always going to be possible in the general
> case. For instance, in my case, my /u
On Thu, Nov 04, 2004 at 11:24:34AM +1300, Sam Vilain wrote:
> OK. Some observations on this thread;
>
> >>>first, I would like to split up (a) into
> >>>
> >>> (a1) 'vserver ... enter' and
> >>> (a2) operating from the outside in the vserver
> >>
> >>ACK; (a2) is the real problem and required b
OK. Some observations on this thread;
>>>first, I would like to split up (a) into
>>>
>>> (a1) 'vserver ... enter' and
>>> (a2) operating from the outside in the vserver
>>
>>ACK; (a2) is the real problem and required by tools
>>like vrpm or vapt-get.
I think this simply isn't always going to be
Herbert Poetzl <[EMAIL PROTECTED]> writes:
>> Currently there are two conflicting requirements:
>>
>> (a) 'vserver ... enter' and operating from the outside in the vserver, and
>> (b) cleaning /proc/mounts
>
> first, I would like to split up (a) into
>
> (a1) 'vserver ... enter' and
> (a2) o
On Tue, Nov 02, 2004 at 12:52:29PM +0100, Enrico Scholz wrote:
> [EMAIL PROTECTED] (Sam Vilain) writes:
>
> > The following patch, to vservers.functions in the util-vserver
> > distribution, will do something of a `namespace cleanup' in lieu of
> > the rework to the vserver startup and mount clean
[EMAIL PROTECTED] (Sam Vilain) writes:
> The following patch, to vservers.functions in the util-vserver
> distribution, will do something of a `namespace cleanup' in lieu of
> the rework to the vserver startup and mount cleanup process that
> Enrico has planned (I'm told).
Currently there are two
Hi all,
The following patch, to vservers.functions in the util-vserver
distribution, will do something of a `namespace cleanup' in lieu of the
rework to the vserver startup and mount cleanup process that Enrico has
planned (I'm told).
That is, with this patch, any filesystems which are NOT within t
12 matches
Mail list logo
