Path: utzoo!utgpu!news-server.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!lavaca.uh.edu!uhnix1!sugar!peter From: peter@sugar.hackercorp.com (Peter da Silva) Newsgroups: comp.sys.amiga.tech Subject: Re: MMU + A3000 + AmigaOS2.0 == Non-crashing system? Message-ID: <6322@sugar.hackercorp.com> Date: 9 Aug 90 23:29:03 GMT References: <2489@clinet.FI> <20889@grebyn.com> <6303@sugar.hackercorp.com> <21001@grebyn.com> Reply-To: peter@sugar.hackercorp.com (Peter da Silva) Organization: Sugar Land Unix - Houston Lines: 24 In article <21001@grebyn.com> ckp@grebyn.UUCP (Checkpoint Technologies) writes: > In article <20889@grebyn.com> ckp@grebyn.UUCP (Checkpoint Technologies) writes: > > Therefore, the way to get MMU protection for your applications is to > > abandon application binary compatibility; and if you're going to do > > this anyway, then why not just use Unix? > In article <6303@sugar.hackercorp.com> peter@sugar.hackercorp.com (Peter da Silva) writes: > >Real-time response? > Valid point. You could choose another appropriate real-time protected > kernel. I hear Mach is nice; I wish I knew more about it. CMU will send you pretty full docs if you ask them. I don't recall the address, try postmaster@cmu.edu. One point, though, is that Mach is not yet real-time. Virtual memory and realtime have never been particularly comfortable in bed together... and VM is basic to the Mach design. One intriguing possibility is running virtual Amigas under Mach. I suspect that you could write a custom pager for it that would give pretty close to real-time response. You'd have to make AmigaOS do a suspend operation instead of halting (I *assume* AmigaOS halts when there is no work to do). -- Peter da Silva. `-_-' .