Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!usc!apple!ames!uakari.primate.wisc.edu!relay.nswc.navy.mil!oasys!mimsy!jds From: jds@cs.umd.edu (James da Silva) Newsgroups: comp.os.minix Subject: Re: Relationship of unix, mach, minix, amoeba? Message-ID: <31602@mimsy.umd.edu> Date: 18 Mar 91 04:17:55 GMT References: <9334@star.cs.vu.nl> <9336@star.cs.vu.nl> Sender: news@mimsy.umd.edu Distribution: comp Organization: University of Maryland, Department of Computer Science Lines: 26 In article <9336@star.cs.vu.nl> ast@cs.vu.nl (Andy Tanenbaum) writes: >In article <9334@star.cs.vu.nl> jms@cs.vu.nl (Jan-Mark Wams) writes: >> The MACH sources can only be used with AT&T UNIX source code. >Well, the MACH 3.0 microkernel is free of AT&T, but a freestanding microkernel >without anything else is of limited value, so in practice you need BSD and >AT&T licenses to do anything useful. Only if you don't think writing an operating system is doing something useful. :-) The Mach microkernel provides a solid base for OS work, providing sophisticated IPC and VM, process management, scheduling, multiprocessor support, device driver support including a full suite of device drivers for two platforms (386/AT and DECstation, so far), a kernel debugger, an excellent high-level thread package (Cthreads), and a high-level client/server interface generator package (MIG). That should be good for something, I daresay. Those who have called for industrial-strength "MAXI-MINIX" in this group should be taking a close look at Mach 3.0. I am. Jaime ........................................................................... : domain: jds@cs.umd.edu James da Silva : path: uunet!mimsy!jds Systems Design & Analysis Group