Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!uwm.edu!zaphod.mps.ohio-state.edu!usc!orion.oac.uci.edu!balboa.eng.uci.edu!dlawyer
From: dlawyer@balboa.eng.uci.edu (David Lawyer)
Newsgroups: comp.os.minix
Subject: Re: 1.5.0 readclock and /dev/port problem
Message-ID: <4111@orion.cf.uci.edu>
Date: 10 Jan 90 16:33:35 GMT
References: <4073@orion.cf.uci.edu>
Sender: news@orion.oac.uci.edu
Reply-To: dlawyer@balboa.eng.uci.edu (David Lawyer)
Organization: University of California at Irvine.
Lines: 13

In article <4073@orion.cf.uci.edu> dlawyer@balboa.eng.uci.edu (David Lawyer) writes:
>......							  But after I
>installed a /dev/port 1 4 (major/minor #'s) as a block (b) device, an
>attempt to readclock will crash the system hard (cntrl-alt-del will not
>reboot). ..... 
>				Dave Lawyer

I've just changed /dev/port to a character (c) device and this fixed my
readclock problem.  A few days ago I changed the mode for opening
/dev/mem and /dev/port to O_RDWR in the two library functions:
peekpoke.s and portio.s as suggested by Tim Bunnell.

				Dave Lawyer