[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH 1/2] exec: connect std{in,out,err} to the mach console
From: |
Justus Winter |
Subject: |
Re: [PATCH 1/2] exec: connect std{in,out,err} to the mach console |
Date: |
Wed, 05 Feb 2014 19:10:51 +0100 |
User-agent: |
alot/0.3.4 |
Quoting Samuel Thibault (2014-02-05 18:21:48)
> Ludovic Courtès, le Wed 05 Feb 2014 14:52:27 +0100, a écrit :
> > Justus Winter <4winter@informatik.uni-hamburg.de> skribis:
> >
> > > * exec/main.c (S_exec_init): Get the device master port and connect
> > > std{in,out,err} to the mach console.
> >
> > That’s a good idea when bootstrapping (I remember doing that to debug
> > the Nix-built GNU/Hurd), but not so much afterwards, no?
>
> Why not? It's better if exec can tell us if it has issues later on,
> isn't it?
I put it in the S_exec_init function, so it is only done for the
initial exec server as far as I can tell.
Justus
- [PATCH 1/2] exec: connect std{in,out,err} to the mach console, Justus Winter, 2014/02/04
- [PATCH 2/2] daemons/getty: always print a newline before the banner, Justus Winter, 2014/02/04
- Re: [PATCH 1/2] exec: connect std{in,out,err} to the mach console, Samuel Thibault, 2014/02/04
- Re: [PATCH 1/2] exec: connect std{in,out,err} to the mach console, Ludovic Courtès, 2014/02/05