[EROS-Arch] Missing fault key detail
Jonathan S. Shapiro
shap@eros-os.org
Fri, 21 Sep 2001 10:21:34 -0400
This is a multi-part message in MIME format.
------=_NextPart_000_0217_01C14287.3079A060
Content-Type: text/plain;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
I forgot to mention a relevant detail of fault keys that differs between =
EROS and KeyKOS. In EROS, invoking a fault key can re-assert a =
previously existing fault, but cannot change the fault code. Therefore, =
the ability of a server to invoke a fault key resulting from a proper =
call does not enable the server to trigger the caller's keeper unless =
the keeper itself has diddled the fault code field.
Jonathan
------=_NextPart_000_0217_01C14287.3079A060
Content-Type: text/html;
charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META http-equiv=3DContent-Type content=3D"text/html; =
charset=3Diso-8859-1">
<META content=3D"MSHTML 5.50.4807.2300" name=3DGENERATOR>
<STYLE></STYLE>
</HEAD>
<BODY bgColor=3D#ffffff>
<DIV><FONT face=3DArial size=3D2>I forgot to mention a relevant detail =
of fault keys=20
that differs between EROS and KeyKOS. In EROS, invoking a fault key can=20
re-assert a previously existing fault, but cannot change the fault code. =
Therefore, the ability of a server to invoke a fault key resulting from =
a proper=20
call does not enable the server to trigger the caller's keeper unless =
the keeper=20
itself has diddled the fault code field.</FONT></DIV>
<DIV><FONT face=3DArial size=3D2></FONT> </DIV>
<DIV><FONT face=3DArial size=3D2>Jonathan</FONT></DIV></BODY></HTML>
------=_NextPart_000_0217_01C14287.3079A060--