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
WRITE(1) BSD General Commands Manual WRITE(1)
NAME
write -- send a message to another user
SYNOPSIS
write user [ttyname]
DESCRIPTION
write allows you to communicate with other users, by copying lines from your terminal to theirs.
When you run the write command, the user you are writing to gets a message of the form:
Message from yourname@yourhost on yourtty at hh:mm ...
Any further lines you enter will be copied to the specified user's terminal. If the other user wants to reply, they must run write as well.
When you are done, type an end-of-file or interrupt character. The other user will see the message 'EOF' indicating that the conversation is
over.
You can prevent people (other than the super-user) from writing to you with the mesg(1) command. Some commands, for example nroff(1) and
pr(1), disallow writing automatically, so that your output isn't overwritten.
If the user you want to write to is logged in on more than one terminal, you can specify which terminal to write to by specifying the termi-
nal name as the second operand to the write command. Alternatively, you can let write select one of the terminals - it will pick the one
with the shortest idle time. This is so that if the user is logged in at work and also dialed up from home, the message will go to the right
place.
The traditional protocol for writing to someone is that the string '-o', either at the end of a line or on a line by itself, means that it's
the other person's turn to talk. The string 'oo' means that the person believes the conversation to be over.
SEE ALSO
mesg(1), talk(1), who(1)
HISTORY
A write command appeared in Version 6 AT&T UNIX.
BSD
June 6, 1993 BSD