Hi David!
On Thu, 18 Sep 2014 17:14:17 -0400, David Michael wrote:
> On Wed, Sep 3, 2014 at 8:33 AM, Justus Winter
> <4win...@informatik.uni-hamburg.de> wrote:
> > Bind the startup server to /servers/startup instead. Use this to
> > contact the startup server.
>
> I'm trying to test this patch,
On Tue, Jan 27, 2015 at 6:35 PM, Samuel Thibault
wrote:
> Justus Winter, le Fri 16 Jan 2015 11:15:37 +0100, a écrit :
>> Quoting David Michael (2014-09-18 23:14:17)
>> > On Wed, Sep 3, 2014 at 8:33 AM, Justus Winter
>> > <4win...@informatik.uni-hamburg.de> wrote:
>> > > Bind the startup server to
Justus Winter, le Fri 16 Jan 2015 11:15:37 +0100, a écrit :
> Quoting David Michael (2014-09-18 23:14:17)
> > On Wed, Sep 3, 2014 at 8:33 AM, Justus Winter
> > <4win...@informatik.uni-hamburg.de> wrote:
> > > Bind the startup server to /servers/startup instead. Use this to
> > > contact the startu
Hello Samuel,
Quoting David Michael (2014-09-18 23:14:17)
> On Wed, Sep 3, 2014 at 8:33 AM, Justus Winter
> <4win...@informatik.uni-hamburg.de> wrote:
> > Bind the startup server to /servers/startup instead. Use this to
> > contact the startup server.
>
> I'm trying to test this patch, and glibc
Hi Roland :)
Quoting David Michael (2014-09-18 23:14:17)
> On Wed, Sep 3, 2014 at 8:33 AM, Justus Winter
> <4win...@informatik.uni-hamburg.de> wrote:
> > Bind the startup server to /servers/startup instead. Use this to
> > contact the startup server.
>
> I'm trying to test this patch, and glibc
Hi David :)
Quoting David Michael (2014-09-18 23:14:17)
> Hi,
>
> On Wed, Sep 3, 2014 at 8:33 AM, Justus Winter
> <4win...@informatik.uni-hamburg.de> wrote:
> > Bind the startup server to /servers/startup instead. Use this to
> > contact the startup server.
>
> I'm trying to test this patch, an
Hi,
On Wed, Sep 3, 2014 at 8:33 AM, Justus Winter
<4win...@informatik.uni-hamburg.de> wrote:
> Bind the startup server to /servers/startup instead. Use this to
> contact the startup server.
I'm trying to test this patch, and glibc appears to need an update as
well. Does this look okay?
Thanks.
Previously, the Hurd (ab)used the fact that the startup server speaks
all protocols on its message port. Any server that wished to register
for shutdown notifications would use proc_getmsgport to get a port to
the startup server.
This hardcodes the PID of /hurd/startup, and does not allow one to