09-07-2012
I don't know of one in this day and age... The ability to just randomly talk to user x in machine y isn't too useful anymore, and the scope of the modern internet means listening to the network at large isn't terribly smart.
It's a really old utility. Many systems no longer have the ability to write to someone else's terminal in that manner. When I traced my version of talk, it wasn't even trying to use TCP, but some weird kind of BSD network socket I'd never heard of, that naturally didn't work.
9 More Discussions You Might Find Interesting
1. UNIX for Dummies Questions & Answers
Hi,
I am trying talk but it isn't working.
I tried
talk ip terminal
talk ip:terminal
First it says:
Then after 2 seconds
I have checked the mesg status: Its y
I am not getting any invitation on the other machine.
Thanks in Advance (1 Reply)
Discussion started by: vibhor_agarwali
1 Replies
2. Solaris
Hi ,
I am trying to configure a private LAN and corporate LAN on the same machien on Solaris 10.
How can I achieve this?
Thanks (1 Reply)
Discussion started by: deedee
1 Replies
3. Infrastructure Monitoring
Hi
i have installed Nagios 3.0.6 on Centos 5.2 also to configure it i have installed Centreon, my problem is the following , i have created a user for Nagios on google talk and using an script from the web trying to send notification for host status and services.
i have tested the script using... (0 Replies)
Discussion started by: pokker67
0 Replies
4. IP Networking
Hi,
We have a website running on a local centos 5.4 surfer, static IP.
The domain.com uses no-ip.com to take care of the DNS, it forwards all to my server.
My router receives the port 80 call, routes it to my server and the world can see domain.com perfectly fine.
However, we cannot see... (3 Replies)
Discussion started by: lawstudent
3 Replies
5. Red Hat
I am facing strange problem regarding hostname on my Linux(2.6.18-164.el5xen x86_64 GNU/Linux), the hostname changes if reboot with lan cable and with NO lan cable
Reboot with lan cable:
The hostname is ubunut
Unable to connect Oracle database using sqlplus some times database is not... (2 Replies)
Discussion started by: LinuxLearner
2 Replies
6. Ubuntu
Well this is weird. I restarted my dual boot Win7/Ubuntu 10.10 from ubuntu to windows. Everything was working fine and windows is always connecting properly to my lan. After restarting back into Ubuntu, all of a sudden I can't connect to my network. It looks as if its trying to connect through... (15 Replies)
Discussion started by: zixzix01
15 Replies
7. Hardware
Hi Everyone,
First time here on Unix.com forums. I've been trying to install Nexenta on a new server machine that I built. The MotherBoard is a Gigabit GA-G41MT-S2P and the LAN chip is an AR8151.
I understand that the AR8151 isn't natively supported by the Solaris kernel, but I'm wondering if... (1 Reply)
Discussion started by: cbstryker
1 Replies
8. UNIX for Dummies Questions & Answers
DELETE (0 Replies)
Discussion started by: morrison71
0 Replies
9. What is on Your Mind?
Retro Games has announced that the C64 is back, this time full-sized with a working keyboard for the dedicated retro home-computer fan, available December 2019.
See also:
CNN:
Iconic 80s computer The Commodore 64 to return with fully-functional keyboard
YouTube:
The C64 | Trailer
... (2 Replies)
Discussion started by: Neo
2 Replies
TALK(1) BSD General Commands Manual TALK(1)
NAME
talk -- talk to another user
SYNOPSIS
talk person [ttyname]
DESCRIPTION
The talk utility is a visual communication program which copies lines from your terminal to that of another user.
Options available:
person If you wish to talk to someone on your own machine, then person is just the person's login name. If you wish to talk to a user on
another host, then person is of the form 'user@host' or 'host!user' or 'host:user'.
ttyname If you wish to talk to a user who is logged in more than once, the ttyname argument may be used to indicate the appropriate terminal
name, where ttyname is of the form 'ttyXX'.
When first called, talk sends the message
Message from TalkDaemon@his_machine...
talk: connection requested by your_name@your_machine.
talk: respond with: talk your_name@your_machine
to the user you wish to talk to. At this point, the recipient of the message should reply by typing
talk your_name@your_machine
It does not matter from which machine the recipient replies, as long as his login-name is the same. Once communication is established, the
two parties may type simultaneously, with their output appearing in separate windows. Typing control-L '^L' will cause the screen to be
reprinted. Typing control-D '^D' will clear both parts of your screen to be cleared, while the control-D character will be sent to the
remote side (and just displayed by this talk client). Your erase, kill, and word kill characters will behave normally. To exit, just type
your interrupt character; talk then moves the cursor to the bottom of the screen and restores the terminal to its previous state.
Permission to talk may be denied or granted by use of the mesg(1) command. At the outset talking is allowed.
CONFIGURATION
The talk utility relies on the talkd system daemon. See talkd(8) for information about enabling talkd.
FILES
/etc/hosts to find the recipient's machine
/var/run/utmpx to find the recipient's tty
SEE ALSO
mail(1), mesg(1), wall(1), who(1), write(1), talkd(8)
HISTORY
The talk command appeared in 4.2BSD.
In FreeBSD 5.3, the default behaviour of talk was changed to treat local-to-local talk requests as originating and terminating at localhost.
Before this change, it was required that the hostname (as per gethostname(3)) resolved to a valid IPv4 address (via gethostbyname(3)), making
talk unsuitable for use in configurations where talkd(8) was bound to the loopback interface (normally for security reasons).
BUGS
The version of talk released with 4.3BSD uses a protocol that is incompatible with the protocol used in the version released with 4.2BSD.
Multibyte characters are not recognized.
BSD
August 21, 2008 BSD