Path: utzoo!attcan!uunet!mcvax!unido!ztivax!tumuc!lan!ocker From: ocker@lan.informatik.tu-muenchen.dbp.de (Wolfgang Ocker) Newsgroups: comp.os.os9 Subject: Re: Porting UNIX code to OS/9-68K Message-ID: <1103@infovax.lan.informatik.tu-muenchen.dbp.de> Date: 27 Jun 89 14:25:44 GMT References: <1625@brwa.inmos.co.uk> Reply-To: ocker@lan.informatik.tu-muenchen.dbp.de (Wolfgang Ocker) Organization: Inst. fuer Informatik, TU Muenchen, W. Germany Lines: 74 In article <1625@brwa.inmos.co.uk> davidb@inmos.co.uk () writes: >What is involved in porting UNIX programs to OS/9-69000 ?? >2) Yes the library supports many UNIX calls (more now than it used > to). However, the main omissions are fork() and isatty(). > Both of these cause major problems. fork() is a real problem, isatty() not: #include /* * i s w h a t */ static int iswhat(p) int p; { struct _sgs opt; if (_gs_opt(p, &opt) < 0) return(-1); return(opt._sgs_class); } /* * i s a t t y */ int isatty(f) int f; { int t; if ((t = iswhat(f)) < 0) return(0); return(t == 0); } /* * i s a p i p e */ int isapipe(f) int f; { int t; if ((t = iswhat(f)) < 0) return(0); return(t == 1); } >3) You don't have timers. But they are near. In 2.2 alarms are implemented, but don't work correctly in all cases. >There are masses of things which are different but these are >the ones which have caused me grief. However, you certainly >can get pretty far porting UNIX code to OS9/68000. For instance, >I've had "yacc", "lex", "kermit" and many other things going >without much trouble. (I don't think X11 will work :) X11.R3 runs on OSK (I have seen it with my own eyes.) A company in Germany has ported it. Regards, /// Wolfgang -- | Wolfgang Ocker | ocker@lan.informatik.tu-muenchen.dbp.de | | Lochhauserstr. 35a | pyramid!tmpmbx!recco!weo (home) | | D-8039 Puchheim | Technische Universitaet Muenchen | | Voice: +49 89 80 77 02 | Huh, What? Where am I? |