anthony@pitt.UUCP (M. Anthony Kapolka 3) (04/04/89)
In my continued quest to get my system working under 3.51, I've noticed
users on /dev/ph1 can't open /dev/tty. This is most obvious under rn...
which doesn't work properly.
I'm told that this is due to a bug in the ph1 driver.
Can someone give me some more info about this? I'm not eager to modify
rn, since the same executable worked under 3.0 (and it should work now!)
Thanks in advance!
M. Anthony Kapolka III School:anthony@vax.cs.pittsburgh.edu
"Don't look for answers where anthony@PITTVMS.bitnet
no answers can be found" Home: ...pitt!idis!eklektik!anthonykevin@kosman.UUCP (Kevin O'Gorman) (04/09/89)
In article <4801@pitt.UUCP> anthony@pitt.UUCP (M. Anthony Kapolka 3) writes: > >In my continued quest to get my system working under 3.51, I've noticed >users on /dev/ph1 can't open /dev/tty. This is most obvious under rn... >which doesn't work properly. > >I'm told that this is due to a bug in the ph1 driver. > >Can someone give me some more info about this? I'm not eager to modify >rn, since the same executable worked under 3.0 (and it should work now!) Nope. There's a one-line fix to rn that makes this behavior go away. I don't have the line in front of me, but what you're looking for is an open(2) call, and what has to change is an O_NDELAY (I think it has to be added). Anyway, I use rn all the time, and have been doing it for so long I forget when I got it. If no-one else supplies the exact information, I can do the research to resurrect the patch. Send me mail.