Path: utzoo!attcan!uunet!cbmvax!bpa!rutgers!netsys!lamc!well!aleks From: aleks@well.UUCP (Brian J. Witt) Newsgroups: comp.sys.amiga.tech Subject: Re: Unix V7 functionality under (or along with) AmigaDOS? Summary: multiple schedulers are bad Keywords: scheduler, surrogate OS Message-ID: <11017@well.UUCP> Date: 19 Mar 89 17:35:41 GMT References: <6157@cbmvax.UUCP> <6185@cbmvax.UUCP> <473@laic.UUCP> Reply-To: aleks@well.UUCP (Brian J. Witt) Distribution: comp Organization: ex-Wendin, Inc contract programmer Lines: 19 In article <473@laic.UUCP> darin@nova.UUCP (Darin Johnson) writes: >However, the purpose of MINIX is to provide a instructional base to OS >design, not just to be an alternate OS for micro users. This means >that if MINIX is implemented on top of Exec, then it is impossible to >expirement with different scheduling algorithms, etc. >Darin Johnson (leadsv!laic!darin@pyramid.pyramid.com) Yes, running one scheduler on top of Exec it not a casual concept to implement! I tried putting a VAX/VMS like scheduler on top of Exec's scheduling and had nothing but trouble. The system was the Wendin Operating System Toolbox. <--REFERENCE Although I did get it to work, the evil I was performing would make Carl lose sleep and pace the floor. One thing missing from the Exec process state is "SUSPENDED": don't even try to launch me. I faked it by just placing the task on the WaitList. I believe if you blew off DOS, that creating the task would be much easier, though. --- busy waiting for the next level 7 interrupt --- brian