web-hurd
[Top][All Lists]
Advanced

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

RE: address@hidden: Re: address@hidden: hurd-paper again]]


From: Jim Franklin
Subject: RE: address@hidden: Re: address@hidden: hurd-paper again]]
Date: Fri, 11 May 2001 18:48:23 -0700

-----Original Message-----
From: Jim Franklin [mailto:address@hidden
Sent: Friday, May 11, 2001 6:41 PM
To: Jim Franklin
Cc: address@hidden
Subject: RE: address@hidden: Re: address@hidden: hurd-paper again]]


Please confer with the authors of the document(s) in question if you feel it
is necessary to implement these changes.

-----Original Message-----
From: Vincent Legoll [mailto:address@hidden
Sent: Monday, May 14, 2001 3:40 AM
To: Jim Franklin
Subject: Re: address@hidden: Re: address@hidden: hurd-paper again]]


Yes thanks, that's what I had in mind, but this should be cleared in the
FAQ,
if you need it to be done, I can take the time to clarify this point and
make
an addition to the FAQ, or dou you intend to do it yourself (because of my
broken english) ?

Is there a document somewhere which explain what to do to submit such
modifications ?

> This is a nice explanation from Gordon.
>
> >>>>>  Hurd Paper:
>
>  HP> However, the Hurd is constructed so that the worst possible
>  HP> consequence is an interruptible hang.
>
> >>>>>  Vincent Legoll writes:
>
>  VL> I can't clearly understand what "hangs" (and what is required to
>  VL> interrupt that hang).  You meant the wrong process used as a
>  VL> translator hangs and the system can recover from that situation
>  VL> by interrupting (a CTRL-C / SIGINT equivalent) this process ?
>
> No, when a client process tries to access the filesystem, it will
> expect the translator to implement the filesystem protocol, and so
> will wait for the translator to reply.
>
> If the translator returns a bad reply, then the client will propagate
> an error, so there is no problem.  On the other hand, if the
> translator doesn't reply at all, the client will hang waiting for it.
>
> On the Hurd, you can just interrupt the client (C-c, or some other
> signal), and it will stop waiting.  On many other kernels, the client
> cannot be interrupted, and will essentially prevent the client's
> terminal from being used until the system is rebooted, or the
> translator returns some kind of a reply.
>
> Is that clearer?
>
> --
>  Gordon Matzigkeit <address@hidden>  //\ I'm a FIG (http://fig.org/)
> Committed to freedom and diversity \// Be Pliant (http://fig.org/pliant/)
>
> ----- End forwarded message -----
>
> _______________________________________________
> Web-hurd mailing list
> address@hidden
> http://mail.gnu.org/mailman/listinfo/web-hurd





reply via email to

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