Xref: utzoo comp.sys.att:7216 unix-pc.general:3512
Path: utzoo!utgpu!watmath!uunet!ginosko!aplcen!haven!umbc3!alex
From: alex@umbc3.UMBC.EDU (Alex S. Crain)
Newsgroups: comp.sys.att,unix-pc.general
Subject: Re: sockets & ptys
Keywords: PD socket & PD pty
Message-ID: <2229@umbc3.UMBC.EDU>
Date: 7 Aug 89 19:31:57 GMT
References: <637@holin.ATT.COM>
Reply-To: alex@umbc3.umbc.edu.UMBC.EDU (Alex S. Crain)
Organization: University of Maryland, Baltimore County
Lines: 28

In article <637@holin.ATT.COM> bes@holin.ATT.COM (Bradley Smith) writes:

>Now a question. I want select to work on the /dev/window as well
>(like stdin, stdout) but you can't access data in other loadable
>devices.  I thought of find out what address the struct tty is at
>and looking at it that way.  Does anyone have an idea?

	You can access data in loadable devices, *if you know the address*.
One way of doing this is to link with /etc/lddrv/ifile.wind and assume that
this info will not change. Another way would be to have uipcinit() read
/etc/ldrv/ifile.wind (yuk). Since its reasonable to assume that wind.o
will always be the first driver loaded, then there is no reason that the
addresses should change, ever, so using that ifile is a reasonably good
way of doing it. You could justify it by assuming that the window driver 
will someday be replaced, so this is only temporary :-).

	ld -r -o uipc.o /etc/lddrv/ifile.wind *.o 

should give you what you want.




-- 
#################################		:alex.
#Disclamer: Anyone who agrees   #    University of Maryland Baltimore County
#with me deserves what they get.#	alex@umbc3.umbc.edu
#################################	alex%nerwin.UUCP@umbc3.umbc.edu