Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!bu.edu!m2c!viewlog.viewlogic.com!greg
From: greg@suntan.viewlogic.com (Gregory Larkin)
Newsgroups: comp.os.minix
Subject: Need help with readclock(1)
Message-ID: <1991May28.173321.20589@viewlogic.com>
Date: 28 May 91 17:33:21 GMT
Sender: news@viewlogic.com
Organization: Viewlogic Systems, Inc., Marlboro, MA
Lines: 42
Originator: greg@mobius
Nntp-Posting-Host: mobius


Hi there,

I posted a question about readclock(1) not working yesterday, and I 
think I've gotten a little closer to the solution, but I just hit a
really big problem!!

My system did not have a /dev/port device, so readclock(1) could not
get the system time.  "OK", I thought, "I'll just create the device".

I did: (from the makedev.sh script)

mknod /dev/port b 1 4 0
chmod 600 /dev/port
chown bin /dev/port
chgrp sys /dev/port

Is this OK?

I then typed: "readclock", hoping it would give me a system time. Well,
it hung the machine!!  Not even CTRL-ALT-DEL would reboot it, either!

I powered down and rebooted, but since readclock(1) is in my /etc/rc
file, the boot gets to certain point and dies.

The only thing I can think of is that the battery backup for the clock
could be dead.  I do seem to remember that when the PC is booted to DOS,
the time is all screwed up every time.  Could this cause the hang?

Any ideas, folks?

If you have any ideas, I'd love to hear them..  I'm going to be out of
luck until I solve this!  Back to DOS, I guess... :-(((((

Thanks,


-- 
Greg Larkin (ASIC Engineer)|"This is a fragile ball we are living on; 
Viewlogic Systems, Inc.    |it's a miracle and we are destroying it.."
293 Boston Post Road West  |Peter Garrett, Midnight Oil               
Marlboro, MA 01752  (greg@Viewlogic.COM)