Return to BSD News archive
Newsgroups: comp.os.386bsd.development Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!elroy.jpl.nasa.gov!usc!howland.reston.ans.net!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!math.ohio-state.edu!sol.ctr.columbia.edu!hamblin.math.byu.edu!news.byu.edu!ns.novell.com!gateway.univel.com!fcom.cc.utah.edu!cs.weber.edu!terry From: terry@cs.weber.edu (A Wizard of Earth C) Subject: Re: Newbie question. Message-ID: <1993Jul1.220406.935@fcom.cc.utah.edu> Sender: news@fcom.cc.utah.edu Organization: Weber State University, Ogden, UT References: <20v4bu$dfu@stimpy.css.itd.umich.edu> Date: Thu, 1 Jul 93 22:04:06 GMT Lines: 19 In article <20v4bu$dfu@stimpy.css.itd.umich.edu> altitude@css.itd.umich.edu (Alex Tang) writes: >Hi. I'm just starting to move into system type coding. I've picked up a book >on writing device drivers called "writing Unix Device Drivers". I'm wondering >where the u. structure is defined (if at all). When I tried writing one of >the sample programs, it said that u wasn't defined. I thought that it was a >base structure. One of my colleagues is a systems programmer and did not >understand why u. wasn't defined. I'm confused. Sorry if this is a dumb >question. It's part of the changes necessary for a kernel threads implementation. Use "curproc" instead, and get the u information out of the struct as dereferenced off of "curproc". Terry Lambert terry@icarus.weber.edu --- Any opinions in this posting are my own and not those of my present or previous employers.