Xref: utzoo comp.sys.att:7243 unix-pc.general:3534
Path: utzoo!attcan!utgpu!watmath!uunet!tut.cis.ohio-state.edu!rutgers!dptg!mtunb!jcm
From: jcm@mtunb.ATT.COM (was-John McMillan)
Newsgroups: comp.sys.att,unix-pc.general
Subject: Re: sockets & ptys
Keywords: PD socket & PD pty
Message-ID: <1604@mtunb.ATT.COM>
Date: 9 Aug 89 12:42:22 GMT
References: <637@holin.ATT.COM> <2229@umbc3.UMBC.EDU> <589@uncle.UUCP>
Reply-To: jcm@mtunb.UUCP (John McMillan)
Organization: AT&T ISL Middletown NJ USA
Lines: 16

>>In article <637@holin.ATT.COM> bes@holin.ATT.COM (Bradley Smith) writes:
>>				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.					  ^^^^^^^^^^^^^^^
  ^^^^^^^^^^^^^^^
	If we're going to enumerate the circumstances wherein the 
	above view appears a bit "restricted":
		+ A new wind.o is installed
		+ A new kernel is installed (for some, a regular experience)
		+ 'ktune' changes the kernel's size by at least a page
		+ The system's RAM is switched from <=.5MB to >= 1MB,
			(or vice-versa -- Mega-YETCH !-)

	In other words, it's not a "reasonably good way of doing it"
	from some perspectives.