Path: utzoo!utgpu!jarvis.csri.toronto.edu!daemon Newsgroups: comp.unix.ultrix From: cks@white.toronto.edu (Chris Siebenmann) Subject: Re: frustration with tip and cu and /etc/remotes under Ultrix 2.2 Message-ID: <89Aug29.232824edt.30790@snow.white.toronto.edu> Sender: Organization: Ziebmef home away from home References: <89Aug28.232709edt.30790@snow.white.toronto.edu> Date: 30 Aug 89 03:29:26 GMT Well, thanks to some people and some carefull reading of manpages and kernel rebuilding, I managed to both get a direct connection working with tip and get the printer to print. My problems with tip were caused by port permissions; the port tip will run on has to be owned by uucp, even if you're tip-ing out as root. If it isn't, tip fails with the ever-so-helpful "all ports busy" error message. The printer finally started working after I looked at the diskless client kernel config file and rebuilt it with a "flags 0x0f" entry on the ss device line. I'm surprised this isn't standard, given that DEC says you have to do it that way in the ss(4) manpage. Send email if you want either the /etc/printcap entry I ended up with or my direct-connect /etc/remote entry. -- "I shall clasp my hands together and bow to the corners of the world." Number Ten Ox, "Bridge of Birds" Chris Siebenmann ...!utgpu!{ncrcan,ontmoh!moore}!ziebmef!cks cks@white.toronto.edu or ...!utgpu!{,csri!}cks