Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!constellation!osuunx.ucc.okstate.edu!moe.ksu.ksu.edu!ux1.cso.uiuc.edu!sdd.hp.com!saimiri.primate.wisc.edu!caen!zip.eecs.umich.edu!quip.eecs.umich.edu!dmuntz From: dmuntz@quip.eecs.umich.edu (Dan Muntz) Newsgroups: comp.os.386bsd.development Subject: Re: Newbie question. Date: 1 Jul 1993 16:59:25 GMT Organization: University of Michigan EECS Dept., Ann Arbor Lines: 16 Message-ID: <20v55d$k3s@zip.eecs.umich.edu> References: <20v4bu$dfu@stimpy.css.itd.umich.edu> NNTP-Posting-Host: quip.eecs.umich.edu 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. The elimination of 'u' is part of the "new and improved" BSD. Take a look at the "open" system call (in /sys/kern/vfs_syscalls.c) as an example of how you get at the information you typically want from 'u'. -Dan dmuntz@eecs.umich.edu