Quoting David Michael (2013-09-17 18:43:24)
Hi,
On Tue, Jul 30, 2013 at 5:59 AM, Justus Winter
4win...@informatik.uni-hamburg.de wrote:
* hurd/fsys.defs: Add fsys_get_children.
* hurd/fsys_reply.defs: Add fsys_get_children.
While trying to build the latest changes, this seems to result
Hi,
On Tue, Jul 30, 2013 at 5:59 AM, Justus Winter
4win...@informatik.uni-hamburg.de wrote:
* hurd/fsys.defs: Add fsys_get_children.
* hurd/fsys_reply.defs: Add fsys_get_children.
While trying to build the latest changes, this seems to result in a
new compile failure. The file
fsys_get_children returns any active translators bound to nodes of the
receiving filesystem as an argz vector containing file names relative
to the root of the receiving translator.
* hurd/fsys.defs: Add fsys_get_children.
* hurd/fsys_reply.defs: Add fsys_get_children.
---
hurd/fsys.defs |
At Tue, 30 Jul 2013 11:59:18 +0200,
Justus Winter wrote:
fsys_get_children returns any active translators bound to nodes of the
receiving filesystem as an argz vector containing file names relative
to the root of the receiving translator.
What if the caller is chrooted? The filenames should
On Tue, Jul 30, 2013 at 12:20:32PM +0200, Neal H. Walfield wrote:
fsys_get_children returns any active translators bound to nodes of the
receiving filesystem as an argz vector containing file names relative
to the root of the receiving translator.
What if the caller is chrooted? The
At Tue, 30 Jul 2013 22:44:22 +0200,
Richard Braun wrote:
On Tue, Jul 30, 2013 at 12:20:32PM +0200, Neal H. Walfield wrote:
fsys_get_children returns any active translators bound to nodes of the
receiving filesystem as an argz vector containing file names relative
to the root of the
On Tue, Jul 30, 2013 at 10:50:51PM +0200, Neal H. Walfield wrote:
I'm not concerned about the mtab implementation. I'm concerned about
the RPC's interface.
I'm not sure why you think chroot is only for compatibility and why we
therefore shouldn't correctly support it.
First, it's not
