l4-hurd
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Hurdish applications for persistence


From: Marcus Brinkmann
Subject: Re: Hurdish applications for persistence
Date: Thu, 13 Oct 2005 16:17:41 +0200
User-agent: Wanderlust/2.14.0 (Africa) SEMI/1.14.6 (Maruoka) FLIM/1.14.7 (Sanjō) APEL/10.6 Emacs/21.4 (i386-pc-linux-gnu) MULE/5.0 (SAKAKI)

At Thu, 13 Oct 2005 16:04:43 +0200,
Alfred M Szmidt wrote:
> 
>    These two positions are logically inconsistent.  The "little
>    firewall thingy" requires (to share files) a file_reparent
>    operation that _effectively works_ in the context of the whole
>    system.  You can not ask for the one thing and reject the other.
> 
> Ah, but now it is you who are confused.  I'm talking about a firewall
> thingy for a sub-hurd, not chroot.

I understood that quite well.

> And I don't recall file_reparent
> getting used for sub-hurds.  Baiscly letting boot pass things to the
> underlying system, but things that are specifed by the user, so you
> could for example only get access to /servers/socket/2, and no other
> node.

Right.  I want to pass my music directory to the subhurd, but _only_
that.  How do I prevent it from looking up ".."?  The easiest way to
do this is to use file_reparent on the music directory port and pass
that to the subhurd.

See also my other mail to Jonathan were I explain this connection in
more detail.

Marcus
 





reply via email to

[Prev in Thread] Current Thread [Next in Thread]