home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.unix.sys5.r4
- Path: sparky!uunet!munnari.oz.au!sgiblab!spool.mu.edu!yale.edu!ira.uka.de!math.fu-berlin.de!mailgzrz.TU-Berlin.DE!news.netmbx.de!Germany.EU.net!mcsun!sunic!seunet!news.icl.se!nsemani
- From: nsemani@nose.sth.icl.se (Markku Niku ICL/Swe)
- Subject: Re: defines of FAULTS in solaris
- Message-ID: <1993Jan25.170035.16928@icl.se>
- Sender: nsemani@nose (Markku Niku ICL/Swe)
- Nntp-Posting-Host: maniipx
- Organization: ICL DATA AB, Sweden
- References: <1993Jan22.090028.25843@cse.iitb.ernet.in> <16586@auspex-gw.auspex.com> <C1DGL7.FLu@queernet.org> <16609@auspex-gw.auspex.com>
- Date: Mon, 25 Jan 1993 17:00:35 GMT
- Lines: 32
-
- In article <16609@auspex-gw.auspex.com>, guy@Auspex.COM (Guy Harris) writes:
- |> >>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..
-
- I've forwarded your "flames" to the developing department at ICL, lets see
- what comes out. Anyhow, in the other SVR4 port ICL has (Intel machines),
- <sys/fault.h> looks out to be more reasonable.
-
-
- /// Markku Niku, ICL Sweden, mniku@icl.se
- PLS OBSERVE, all I write is my opinnion, it may differ from ICL policy.
-