Newsgroups: comp.os.minix
Subject: Re: Favored Minix Version?
References: <20010620.15495800@geode.is.cshl.org> <slrn9jmccc.hhe.pino+comp_os_minix@mud.stack.nl> <fiqe1vc106dfun846pa4n6ehh7@stereo.pch.home.cs.vu.nl> <slrn9joj7k.op.pino+comp_os_minix@mud.stack.nl>
Organization: Minix
Message-ID: <529deusj44p69f6rcc3c4nmec1@stereo.pch.home.cs.vu.nl>
From: philip@pch.home.cs.vu.nl (Philip Homburg)
Date: Fri, 29 Jun 2001 18:38:34 +0200
Lines: 22
NNTP-Posting-Host: 213.84.34.176
X-Trace: 993832722 newszilla.xs4all.nl 14041 213.84.34.176
Path: news.adfa.edu.au!clarion.carno.net.au!news0.optus.net.au!news1.optus.net.au!optus!news-spur1.maxwell.syr.edu!news.maxwell.syr.edu!colt.net!newspeer.clara.net!news.clara.net!newsfeed.wirehub.nl!transit.news.xs4all.nl!newszilla.xs4all.nl!not-for-mail
Xref: news.adfa.edu.au comp.os.minix:37708

In article <slrn9joj7k.op.pino+comp_os_minix@mud.stack.nl>,
Martijn van Buul <pino+comp_os_minix@dohd.org> wrote:
>Minix >= 2.0.2 has a select call, for instance. VMD's nbio_select comes
>close, but not quite. Signal handling is different.

You mean 2.0.2 as distributed, or 2.0.2 with custom patches? In what way
does the difference in signal handling affect compatiblity?

>I once ported tcsh (Which has a Minix-port) to VMD. I started porting
>the Minix-port, and ended up restarting the whole thing from scratch, doing
>some relatively small modifications to the 'generic BSD' port.

I fetched a Minix port of tcsh from http://barnyard.syr.edu/minix.shtml.
Compiling it required two minor changes (F_SEEK is used by Minix-vmd, and
<ansi.h> no longer exists).

Unfortunately, there seems to be some weird interaction with SIGCHLD.




					Philip Homburg
