Path: utzoo!attcan!uunet!lll-winken!ncis.llnl.gov!helios.ee.lbl.gov!pasteur!agate!bionet!csd4.milw.wisc.edu!mailrus!wasatch!hoosier.utah.edu!mjb
From: mjb%hoosier.utah.edu@wasatch.UUCP (Mark J. Bradakis)
Newsgroups: comp.sys.hp
Subject: Re: 4.3 on Series 300s
Summary: HIL under bsd question
Keywords: HIL addressing
Message-ID: <941@wasatch.UUCP>
Date: 20 Jan 89 17:35:37 GMT
References: <10890@umn-cs.CS.UMN.EDU> <5963@boulder.Colorado.EDU>
Sender: news@wasatch.UUCP
Reply-To: mjb%hoosier.utah.edu.UUCP@wasatch.UUCP (Mark J. Bradakis)
Organization: University of Utah Computer Science
Lines: 23

In article <5963@boulder.Colorado.EDU> kevinj@boulder.Colorado.EDU (Kevin Jackson) writes:
 
>They've actually done a fairly nice job.  Some of the things that are 
>'hardwired' into the setup can be a problem (e.g. the keyboard must be the
>first device in the hil chain on the console), but for the most part 
>things work just as you'd expect a 4.3bsd machine to work.  Also, code seems 
>to port very easily to these machines.  

Is there a specific problem you've had with the keyboard being hil1?  Under
HP-UX we always had them set up that way, so we made it that way in bsd.
Not having complete docs about the hardware and software we can't do
EVERYTHING right, but we try.  Incidently, the Utah port does NOT support
the 310 mahines, only 68020 and 68030 based processors.

mjb.
ps: we usually have
hil1 => keyboard
hil2 => ID
hil3 => mouse

mjb@hoosier.utah.edu

"I put you behind the wheel of a duece and a quarter, yes I did!"