Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA1372 ; Tue, 23 Feb 93 14:37:21 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!sgiblab!zaphod.mps.ohio-state.edu!saimiri.primate.wisc.edu!usenet.coe.montana.edu!gemini.oscs.montana.edu!osynw From: osynw@gemini.oscs.montana.edu (Nathan Williams) Subject: Re: patchkit 0.2.1 and my serial driver Message-ID: <1993Feb15.021749.7875@coe.montana.edu> Keywords: n Sender: usenet@coe.montana.edu (USENET News System) Organization: Montana State University References: <CGD.93Feb14174123@gaia.CS.Berkeley.EDU> Date: Mon, 15 Feb 1993 02:17:49 GMT Lines: 20 In article <CGD.93Feb14174123@gaia.CS.Berkeley.EDU> cgd@gaia.CS.Berkeley.EDU (Chris G. Demetriou) writes: >because of some changes to various kernel files, my serial driver >won't install into a patchkit-0.2.1'd source tree (or at least, >it shoudln't; i'm trying it right now...). > Though Chris's driver is a great improvement, and I recommend it highly, if you were getting his driver so that you could run X, it is no longer necessary. (Since the stock com driver didn't work with the 0.2 patchkit very well) I forgot to mention in the original announcement that Jordan Hubbard created a patch so that the original driver now works with the new select interface (with code stolen from Chris's driver) Nate -- osynw@terra.oscs.montana.edu | Still trying to find a good reason for nate@cs.montana.edu | these 'computer' things. Personally, home #: (406) 586-0579 | I don't think they'll catch on - Don H.