🚀 go-pugleaf

>>I.e., It Would Probably Be A Good Idea if ICL did this the way Sun did,
>>and if ICL just picked it up from USL, It Would Probably Be A Good Idea
>>if USL did this the way Sun did....
>
>ICL's SVR4 is the SPARC reference SVR4.  Solaris 2.x is not a real SVR4
>USL release; it is a USL-Sun development tree which was branched at some
>arbitrary intra-version point and dragged off by Sun to make it as
>divergent as they felt like.

Nevertheless, it would *STILL* probably be a good idea if ICL did this
the way Sun did, given that the way Sun did it matches what the standard
AT&T/USL SVR4 documentation I have says, and the way ICL did it doesn't
- i.e., if you include <sys/fault.h> in SunOS 5.x, you get the fault
codes defined, just as the damn "proc(4)" man page says you do, but, it
appears, you *don't* get them defined if you include <sys/fault.h> in
the ICL system.

Not to mention the fact that putting all the fault codes in a
"sys/sparc/XXX.h" file is Just Too Fucking Stupid For Words, given that
they are intended to represent faults that just about *any* machine will
have; only an idiot would arrange that, say, the fault code for
"recoverable page fault" would have different values on the x86 SVR4,
MIPS SVR4, SPARC SVR4, etc..