Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!purdue!ames!ll-xn!mit-eddie!uw-beaver!ubc-cs!alberta!calgary!enme3!deraadt From: deraadt@enme3.ucalgary.ca (Theo Deraadt) Newsgroups: comp.os.minix Subject: Re: Minix for the Amiga...vaporware Message-ID: <1635@cs-spool.calgary.UUCP> Date: 21 Jul 89 06:32:29 GMT References: <1610@uw-entropy.ms.washington.edu> <12212@s.ms.uky.edu> <175@cerc.wvu.wvnet.edu.edu> <116494@sun.Eng.Sun.COM> <267@nlgvax.UUCP> Sender: news@calgary.UUCP Reply-To: deraadt@enme3.UUCP (Theo Deraadt) Organization: U. of Calgary, Calgary, Alberta, Canada Lines: 27 In article shadow@pawl.rpi.edu (Deven T. Corzine) writes: >cncmanis> their entry points rather than back doors in the ROM. > >And then a different set of people wrote AmigaDOS, taking the opposite >approach. (i.e. encourage braindamage) True. That's being worked on now. The end sum will win with AmigaDOS ahead, for device support at least. I am the other guy that ported Minix to the Amiga alone, but I got nowhere with writing device drivers. Also, Minix will not run on a 68020 Amiga. In fact, without some changes to the kernel, it will not run on the 68010 either. Pretty braindamaged. But then, perhaps we are trying to teach students not to think far ahead. Exec on the Amiga is quite full featured. In my version of Minix, I at least let AmigaDOS boot, then I ran a program. That program preserves the Boardlist that Autoconfig has allready built up. In this way, it's possible to write device drivers inside Minix that could check for boards. The "real" Amiga Minix is written in Europe. Any North Americans want to place bets that it boots straight from a floppy only? And to think that I was gonna write a HD driver before I was going to write a Floppy driver.. [but have a floppy driver almost working.. FAST]