Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!watmath!clyde!rutgers!sri-spam!ames!ucbcad!ucbvax!VIOLET.BERKELEY.EDU!mwm From: mwm@VIOLET.BERKELEY.EDU.UUCP Newsgroups: mod.computers.68k Subject: Re: Minix to the 68k? Message-ID: <8702070300.AA18784@violet.berkeley.edu> Date: Fri, 6-Feb-87 22:00:19 EST Article-I.D.: violet.8702070300.AA18784 Posted: Fri Feb 6 22:00:19 1987 Date-Received: Sun, 8-Feb-87 04:44:43 EST Sender: mwm@ucbvax.BERKELEY.EDU Organization: The ARPA Internet Lines: 22 Approved: info-68k@ucbvax.berkeley.edu >> Well, given his constraints, he did port it to a decent machine - there >> isnt' a single cheap 68k system on the market that has a mmu in it, yet the >> 8086 family has had one since day one. From what I recall, he didn't use that - he just assumes that things are well-behaved. I think the ST port is doing the same. In any case, getting in contact with those people is probably a good start, as you should be able to use their kernel (context switching code, in this case). >> 2) Hack up Stallman's gnu c compiler so it will generate PIC (but what to >> do when you take the address of a variable on the stack?) What's the problem? References to the stack go through the SP, which will be switched with the rest of the context. I'm sure one of the OS/9 people on the list can enlighten us further. That still leaves you with an unprotected multi-tasking system, but that's an improvement over an unprotected single-tasking system.