Path: utzoo!mnetor!uunet!nuchat!peter From: peter@nuchat.UUCP (Peter da Silva) Newsgroups: comp.sys.amiga Subject: Re: UNIX on the Amiga Message-ID: <719@nuchat.UUCP> Date: 3 Mar 88 02:31:40 GMT References: <6836@agate.BERKELEY.EDU> <1869@leo.UUCP> <2836@bloom-beacon.MIT.EDU> <197@wsccs.UUCP> Organization: Public Access - Houston, Tx Lines: 49 In article <197@wsccs.UUCP>, terry@wsccs.UUCP (terry) writes: > If by UNIX, you mean Berkley $.3 or SystemV.3, not a snowballs chance. > Commodore, in it's infinite wisdom, use the 68000 chip, not a 68010, so the > Amiga can't run a vmunix... it can't support an MMU. The 68000 supports an MMU just fine. It doesn't support demand paged virtual memory, but it supports an MMU just fine. I've done a lot of work with 68000 based UNIX. In fact I'm using a 68000 based UNIX box from Arete at work right now. And, of course, there's no reason you couldn't require a 68020 with the UNIX if you're a demand-paging bigot. Myself, I'd rather just add more real memory. Virtual memory means virtual performance. Real time systems like Amy don't like VM at all... > Tandy was able to get > a Xenix up on their model 16 and the model 6000 (both 68000 boxes), but it > was an OEM from Microsoft, and they don't usually part with code, let alone > something BB (Big Blue? ...Big Brother?) might consider back-stabbing. Don't judge the 68000 but the Tandy 6000. They deliberately crippled the MMU in the box. > Besides, everyone knows Xenix is fixed SystemIII with > nifty things AT&T is only now coming out with. Xenix is Version 7 (not System III) with a couple of minor improvements and a bunch of business-oriented features of dubious value, tricked out to look like it's System III. > It might be possible to run > protected *IF* you replaced your 68000 with a 68010. You need a seperate MMU to run protected mode whether you get a 68000, a 68010, or a 68020. > If by "well-behaved", you mean compatable with the idea of not doing > the nasty-no-no (MPSW), workbench fails that test. Try replacing your 68000 > with a 68010 and adding something using the desk calculator. The calculator is not part of the Workbench. It's a separate program. By "well behaved", I mean not allocating message buffers on the stack; always using MEMF_PUBLIC with AllocMem; not using processor-specific instructions; not diddling around in private data structures, and so on. -- -- a clone of Peter (have you hugged your wolf today) da Silva `-_-' -- normally ...!hoptoad!academ!uhnix1!sugar!peter U -- Disclaimer: These aren't mere opinions... these are *values*.