Samuel Thibault skribis:
> Ludovic Courtès, le Wed 05 Feb 2014 14:52:27 +0100, a écrit :
>> Justus Winter <4win...@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 w
Justus Winter <4win...@informatik.uni-hamburg.de> skribis:
> 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 <4win...@informatik.uni-hamburg.de> skribis:
>> >
>> > > * exec/main.c (S_exec_init): Get the device maste
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 <4win...@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.
> >
Ludovic Courtès, le Wed 05 Feb 2014 14:52:27 +0100, a écrit :
> Justus Winter <4win...@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
Justus Winter <4win...@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? (