Re: [PATCH 4/5] exec: Remove #ifdef 0-out code for user specified exec servers.

2013-08-29 Thread Roland McGrath
There was some reason for the EXECSERVERS environment variable and I think it might not have been just because we didn't yet have the various translators (unionfs, etc.) that would make it straightforward to populate a private root directory for such purposes. But I really can't recall any more.

Re: [PATCH 4/5] exec: Remove #ifdef 0-out code for user specified exec servers.

2013-08-28 Thread Samuel Thibault
Justus Winter, le Thu 15 Aug 2013 18:41:53 +0200, a écrit : > This code was meant to allow the user to specify alternative exec > servers using an environment variable. The Hurd uses the file system > as namespace for server lookups, so the proper way to use one's own > exec server seems to be the

[PATCH 4/5] exec: Remove #ifdef 0-out code for user specified exec servers.

2013-08-15 Thread Justus Winter
This code was meant to allow the user to specify alternative exec servers using an environment variable. The Hurd uses the file system as namespace for server lookups, so the proper way to use one's own exec server seems to be the remap translator. * exec/exec.c (S_exec_exec): Remove unused code.