Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!mcsun!hp4nl!svin02!eba!wjw From: wjw@eba.eb.ele.tue.nl (Willem Jan Withagen) Newsgroups: comp.sys.apollo Subject: Re: I love my Apollo's (ACL-calls) Summary: How do I get to undocumented calls and/or docs :-) Message-ID: <1015@eba.eb.ele.tue.nl> Date: 14 Dec 90 08:44:30 GMT References: <9012071413.AA04525@richter.mit.edu> <4e93f2ff.1a630@apollo.HP.COM> Sender: news@eb.ele.tue.nl (The News system) Organization: Eindhoven University of Technology, The Netherlands Lines: 37 In article <4e93f2ff.1a630@apollo.HP.COM> brady_p@apollo.hp.COM (Pete Brady) writes: >In article <9012071413.AA04525@richter.mit.edu> krowitz@RICHTER.MIT.EDU (David Krowitz) writes: >>....You are correct about the manual having existed. It was > >The manual was called "Programming with Domain Advanced System Calls". >The problem with it is that a lot of the manual is only useful for SR9.X >systems; some of the stuff (like the registry and loader calls) are very >different in SR10. Mind you though, the loader call are documented in the std-manual(some I guess) the registry call are again a nono. Well I talked with my a friend here at HP/Apollo, and he's going to try to get me the SR9 manual. (IF he can still find it) I know that it's of very little use, but it'll give me a clou as to what is going around as typical parameters in those systemcalls. The argument of not having all calls documented because of future changes is very viable too me. But I think that the user should be supplied with a set of calls large enough to get all of his/hers work done. And this would mean that I would be able to set the aegis rights by making *DOCUMENTED* systemcalls. I don't care about the registry(unless my apollo is standalone, I don't want to mess) or the printer-server. The printer-server however is not fully complete and has always required patching.(This is also not a very trivial thing) So my argument here is: Why are some things documented, and hence fixed in their interfaces and are others completely obscured for the sakes of wanting to limit the OS-engineers? Yours, Willem Jan Withagen. Eindhoven University of Technology DomainName: wjw@eb.ele.tue.nl Digital Systems Group, Room EH 10.10 BITNET: ELEBWJ@HEITUE5.BITNET P.O. 513 Tel: +31-40-473401 5600 MB Eindhoven The Netherlands