Path: utzoo!mnetor!tmsoft!torsqnt!news-server.csri.toronto.edu!bonnie.concordia.ca!uunet!indetech!daver!bungi.com!news Newsgroups: comp.sys.nsc.32k Subject: Returned mail: Cannot send message for 3 days Message-ID: <9102180720.AA08565@uunet.UU.NET> Date: 14 Feb 91 23:35:12 GMT Sender: news@daver.bungi.com Lines: 62 Approved: news@daver.bungi.com ----- Transcript of session follows ----- 421 bnrgate.tcp... Deferred ----- Unsent message follows ----- Received: by bnr-vpa; Fri, 15 Feb 91 02:02:14 est Return-Path: Received: from utzoo with uucp; Thu, 14 Feb 00 18:35:12 Received: by neat.cs.toronto.edu with UUCP id <20569>; Thu, 14 Feb 1991 23:47:54 -0500 Received: from daver.UUCP by uunet.UU.NET (5.61/1.14) with UUCP id AA03717; Thu, 14 Feb 91 23:28:02 -0500 Received: by daver.bungi.com (/\=-/\ Smail3.1.18.1 #18.16) id ; Thu, 14 Feb 91 16:21 PST X-Path: lev.Seri.GOV!sverre From: sverre@lev.Seri.GOV (Sverre Froyen) To: pc532@bungi.com Subject: Re: MINIX 1.5 / 1.3 hybrid DISTRIBUTION Date: Thu, 14 Feb 1991 18:35:12 -0500 Message-Id: <9102142335.AA05906@lev.seri.gov> Illegal-Object: Syntax error in References: value found on neat.cs.toronto.edu: References: <<9102141939.AA08494@strawberry.cs.wwu.edu>> ^ ^-illegal reference separator \-expected word, illegal end of message identification Reply-To: pc532@bungi.com Precedence: bulk > > WARNING: This distribution does not contain full source or executable >due to the copyright on Minix. This will take some effort on your part >to get it working. Several people have successfully created working >versions of the 1.5 hybrid ... (Would you who have working 1.5 hybrid >systems please tell of your experiences with it?) I have been using a prerelease if this hybrid for about 3 weeks. My recommendation: The effort it takes to upgrade is well worth it. The new version is WONDERFUL! Most of the problems porting code in 1.3, like shell scripts failing, makes not working properly, etc., are GONE. There are still bugs no doubt. I sent a description of some to Bruce and I will post the ones that were not fixed to the mailing list once I take a look at new distribution. This brings up the question, once again, of software maintenance. Should we try to find a way to coordinate Minix bug fixes, porting of utilities, etc. One way to do this would be to assign a moderator for each task. A task could be the kernel, another the libraries (or a subset of the libraries), yet anothre gcc, etc. We would send our changes, improvements, or fixes to the moderator, with an optional posting to the mailing list so that others might get immediate benefit. The moderator would incorporate the changes and send out an ``approved'' patch/version and maybe also a new binary. This scheme might avoid some of the duplication of effort that seemed to take place with Minix 1.3. Irrespective of the above, from now on, please indicate for which version your changes, fixes, ports, etc. are meant. Sverre -- Sverre Froyen sverre@seri.gov, sunpeaks!seri!sverre