Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!foxhound.dsto.gov.au!fang.dsto.gov.au!myall.awadi.com.au!blymn From: blymn@awadi.com.au (Brett Lymn) Newsgroups: comp.os.386bsd.development Subject: Re: Newbie question. Date: 06 Jul 1993 20:15:31 GMT Organization: AWA Defence Industries Lines: 20 Message-ID: <BLYMN.93Jul6141537@mallee.awadi.com.au> References: <20v4bu$dfu@stimpy.css.itd.umich.edu> <1993Jul1.220406.935@fcom.cc.utah.edu> NNTP-Posting-Host: mallee.awadi.com.au In-reply-to: terry@cs.weber.edu's message of Thu, 1 Jul 93 22:04:06 GMT >>>>> On Thu, 1 Jul 93 22:04:06 GMT, terry@cs.weber.edu (A Wizard of Earth C) said: A> 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. A> It's part of the changes necessary for a kernel threads implementation. A> Use "curproc" instead, and get the u information out of the struct as A> dereferenced off of "curproc". If the book is the same one that I am thinking of then it is describing writing device drivers for System V UNIX systems so you will need to be careful about some of the structures in the examples. -- Brett Lymn