paul@moore.com (Paul Maclauchlan) (11/03/90)
I'm posting this for a friend, please respond by email to his address.
He will summarize the solution and post back to the newsgroup.
Question:
Has anyone got 'talk' to work on an RS6000 M320 that doesn't have a network
card installed. I'm told it is dependent on tcpip ( which I have added,
although it obviously semi-fails since ifconfig barfs ), and I have the inetd
and portmapper demons running. What else needs to be done?
I'm trying to pull the wool over the RS's eyes (hey who turned out the lights?)
Thanks!
**********************************************************************
Kevin Kimsa vmail: 416-366-6363
The Braegen Group Inc. fax : 416-366-4428
email: uunet!moore!bragrt!kck
**********************************************************************
--
.../Paul Maclauchlan
Moore Corporation Limited, Toronto, Ontario (416) 364-2600
paul@moore.com -or- {...!uunet,...!telly}!moore!paul
"Living is easy with eyes closed, misunderstanding all you see"/JL'67ici@crl.melco.co.jp (Mr. Toshinao Ishii) (03/07/91)
Hi.
I have been trying to use 'talk' of AIX3.1. and found a problem.
If someone else tries to 'talk' to me working on AIX Window,
there is no way to know I am 'talk'ed to. Because the information
appears on /dev/hft. Using of 'swcons' doesn't help. IBM Japan
said this is not bug.
I hope this will improved in the next version of OS.
-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-
Toshinao Ishii
MITSUBISHI Electric Corp. Central Research Lab.
Email: ici@adm.crl.melco.co.jp
Tel: 06-497-7050 (JAPAN)
Fax: 06-497-7288 (JAPAN)scott@prism.gatech.EDU (Scott Holt) (03/08/91)
In article <ICI.91Mar6164614@loame03.crl.melco.co.jp> ici@adm.crl.melco.co.jp writes: > >If someone else tries to 'talk' to me working on AIX Window, >there is no way to know I am 'talk'ed to. Because the information >appears on /dev/hft. Using of 'swcons' doesn't help. IBM Japan >said this is not bug. Well, it may not be a bug - at least in talk. When you try to talk to someone who is logged in mulitple times, the talk daemon selects ONE of their sessions to broadcast the invitation to. The same is true when working in a multi-window environment. I have not seen any documentation that says which "terminal" is selected to recieve the invitation, but I bet its determined by a simple linear search through utmp - which would yield /dev/hft. This is the normal behaviour of talk on just about every system - I don't think IBM's implementation is broke. In actuality, its up to YOU to determine which terminal to send the invitation to - at least accoring to the man pages for vanilla 4.2 and 4.3 BSD talk. What is broke is the fact that you can't get output which is sent to /dev/hft - not just talk invitations. -Scott -- This is my signature. There are many like it, but this one is mine. Scott Holt Internet: scott@prism.gatech.edu Georgia Tech UUCP: ..!gatech!prism!scott Office of Information Technology, Technical Services
ici@crl.melco.co.jp (Mr. Toshinao Ishii) (03/16/91)
In article <23835@hydra.gatech.EDU> scott@prism.gatech.EDU (Scott Holt) writes: > What is broke is the fact that you can't get output which is > sent to /dev/hft - not just talk invitations. I agree. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Toshinao Ishii Mitsubishi Electric Corp. Central Research Lab. Email ici@adm.crl.melco.co.jp Tel 06-497-7050 (Japan) Fax 06-497-7288 (Japan)