bug-hurd
[Top][All Lists]
Advanced

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

Re: Hurd development (was: Release process & rolling new releases)


From: Justus Winter
Subject: Re: Hurd development (was: Release process & rolling new releases)
Date: Fri, 16 Jan 2015 13:26:52 +0100
User-agent: alot/0.3.5

Quoting Samuel Thibault (2015-01-16 12:08:07)
> Justus Winter, le Fri 16 Jan 2015 12:01:26 +0100, a écrit :
> > No it is not.
> 
> You mean in Debian?

Yes.

> > I have a new server that implements the startup protocol, and it
> > neither has a fixed PID nor does it speak the startup protocol over
> > its message port.
> 
> You mean your recent rewrite of startup in scheme, for which the
> brownpaper patch in the Debian tree is not enough, but the proper patch
> in our glibc tree is?

Correct.  The proper thing to do is to look up `/servers/startup',
which Davids patch does.

> I'm sorry it must be looking like obvious questions for anybody who have
> been really following the matters lately, but I have not for personal
> reasons (which are fortunately mostly over), and I hate not having done
> so, but that's unfortunately what has happened.

Well, I haven't really talked too much about that.  The short version
is, that I split up `startup' into two components.  One of those
components, `startup-standalone' (for the lack of a better name),
supervises the core servers and handles the system shutdown.  I bind
it to `/servers/startup' for my new bootstrap procedure.

> Also, don't you have commit access to the debian packaging?  I guess
> that's one of the things we must fix.

No I don't have access.

Justus



reply via email to

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