summaryrefslogtreecommitdiffstats
path: root/slackbook/html/basic-network-commands-talk.html
diff options
context:
space:
mode:
author Patrick J Volkerding <volkerdi@slackware.com>2009-08-26 10:00:38 -0500
committer Eric Hameleers <alien@slackware.com>2018-05-31 22:41:17 +0200
commit5a12e7c134274dba706667107d10d231517d3e05 (patch)
tree55718d5acb710fde798d9f38d0bbaf594ed4b296 /slackbook/html/basic-network-commands-talk.html
downloadcurrent-5a12e7c134274dba706667107d10d231517d3e05.tar.gz
current-5a12e7c134274dba706667107d10d231517d3e05.tar.xz
Slackware 13.0slackware-13.0
Wed Aug 26 10:00:38 CDT 2009 Slackware 13.0 x86_64 is released as stable! Thanks to everyone who helped make this release possible -- see the RELEASE_NOTES for the credits. The ISOs are off to the replicator. This time it will be a 6 CD-ROM 32-bit set and a dual-sided 32-bit/64-bit x86/x86_64 DVD. We're taking pre-orders now at store.slackware.com. Please consider picking up a copy to help support the project. Once again, thanks to the entire Slackware community for all the help testing and fixing things and offering suggestions during this development cycle. As always, have fun and enjoy! -P.
Diffstat (limited to 'slackbook/html/basic-network-commands-talk.html')
-rw-r--r--slackbook/html/basic-network-commands-talk.html184
1 files changed, 184 insertions, 0 deletions
diff --git a/slackbook/html/basic-network-commands-talk.html b/slackbook/html/basic-network-commands-talk.html
new file mode 100644
index 000000000..5c61119e3
--- /dev/null
+++ b/slackbook/html/basic-network-commands-talk.html
@@ -0,0 +1,184 @@
+<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
+ "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
+<html xmlns="http://www.w3.org/1999/xhtml">
+<head>
+<meta name="generator" content="HTML Tidy, see www.w3.org" />
+<title>Talking to Other People</title>
+<meta name="GENERATOR" content="Modular DocBook HTML Stylesheet Version 1.7" />
+<link rel="HOME" title="Slackware Linux Essentials" href="index.html" />
+<link rel="UP" title="Basic Network Commands" href="basic-network-commands.html" />
+<link rel="PREVIOUS" title="FTP Clients" href="basic-network-commands-ftp.html" />
+<link rel="NEXT" title="Security" href="security.html" />
+<link rel="STYLESHEET" type="text/css" href="docbook.css" />
+<meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1" />
+</head>
+<body class="SECT1" bgcolor="#FFFFFF" text="#000000" link="#0000FF" vlink="#840084"
+alink="#0000FF">
+<div class="NAVHEADER">
+<table summary="Header navigation table" width="100%" border="0" cellpadding="0"
+cellspacing="0">
+<tr>
+<th colspan="3" align="center">Slackware Linux Essentials</th>
+</tr>
+
+<tr>
+<td width="10%" align="left" valign="bottom"><a href="basic-network-commands-ftp.html"
+accesskey="P">Prev</a></td>
+<td width="80%" align="center" valign="bottom">Chapter 13 Basic Network Commands</td>
+<td width="10%" align="right" valign="bottom"><a href="security.html"
+accesskey="N">Next</a></td>
+</tr>
+</table>
+
+<hr align="LEFT" width="100%" />
+</div>
+
+<div class="SECT1">
+<h1 class="SECT1"><a id="BASIC-NETWORK-COMMANDS-TALK"
+name="BASIC-NETWORK-COMMANDS-TALK">13.10 Talking to Other People</a></h1>
+
+<div class="SECT2">
+<h2 class="SECT2"><a id="AEN4989" name="AEN4989">13.10.1 <tt
+class="COMMAND">wall</tt></a></h2>
+
+<p><tt class="COMMAND">wall</tt>(1) is a quick way to write a message to the users on a
+system. The basic syntax is:</p>
+
+<table border="0" bgcolor="#E0E0E0" width="100%">
+<tr>
+<td>
+<pre class="SCREEN">
+<samp class="PROMPT">%</samp> <kbd class="USERINPUT">wall [file]</kbd>
+</pre>
+</td>
+</tr>
+</table>
+
+<p>This will result in the contents of [file] being displayed on the terminals of all
+currently logged in users. If you don't specify a file, wall will read from standard
+input, so you can just type your message, and end with <b class="KEYCAP">Ctrl</b>+<b
+class="KEYCAP">d</b>.</p>
+
+<p><tt class="COMMAND">wall</tt> doesn't have many features, and apart from letting your
+users know that you're about to do some serious maintenance to the system, or even reboot
+it, so they have time to save their work and log off :)</p>
+</div>
+
+<div class="SECT2">
+<h2 class="SECT2"><a id="AEN5006" name="AEN5006">13.10.2 <tt
+class="COMMAND">talk</tt></a></h2>
+
+<p><tt class="COMMAND">talk</tt>(1) allows two users to chat. It splits the screen in
+half, horizontally. To request a chat with another user, use this command:</p>
+
+<table border="0" bgcolor="#E0E0E0" width="100%">
+<tr>
+<td>
+<pre class="SCREEN">
+<samp class="PROMPT">%</samp> <kbd class="USERINPUT">talk &lt;person&gt; [ttyname]</kbd>
+</pre>
+</td>
+</tr>
+</table>
+
+<div class="FIGURE"><a id="FIG-BASIC-NETWORK-COMMANDS-TALK-TALK"
+name="FIG-BASIC-NETWORK-COMMANDS-TALK-TALK"></a>
+<p><b>Figure 13-7. Two users in a <tt class="COMMAND">talk</tt> session</b></p>
+
+<p><img src="basic-network-commands/talk.png" /></p>
+</div>
+
+<p>If you specify just a username, the chat request is assumed to be local, so only local
+users are queried. The ttyname is required if you want to ring a user on a specific
+terminal (if the user is logged in more than once). The required information for <tt
+class="COMMAND">talk</tt> can be obtained from the <tt class="COMMAND">w</tt>(1)
+command.</p>
+
+<p><tt class="COMMAND">talk</tt> can also ring users on remote hosts. For the username
+you simply specify an email address. <tt class="COMMAND">talk</tt> will try to contact
+that remote user on that host.</p>
+
+<p><tt class="COMMAND">talk</tt> is somewhat limited. It only supports two users and is
+half-duplex.</p>
+</div>
+
+<div class="SECT2">
+<h2 class="SECT2"><a id="AEN5033" name="AEN5033">13.10.3 <tt
+class="COMMAND">ytalk</tt></a></h2>
+
+<p><tt class="COMMAND">ytalk</tt>(1) is a backwards compatible replacement for <tt
+class="COMMAND">talk</tt>. It comes with Slackware as the <tt class="COMMAND">ytalk</tt>
+command. The syntax is similar, but has a few differences:</p>
+
+<table border="0" bgcolor="#E0E0E0" width="100%">
+<tr>
+<td>
+<pre class="SCREEN">
+<samp class="PROMPT">%</samp> <kbd
+class="USERINPUT">ytalk &lt;username&gt;[#ttyname]</kbd>
+</pre>
+</td>
+</tr>
+</table>
+
+<div class="FIGURE"><a id="FIG-BASIC-NETWORK-COMMANDS-TALK-YTALK"
+name="FIG-BASIC-NETWORK-COMMANDS-TALK-YTALK"></a>
+<p><b>Figure 13-8. Two users in a <tt class="COMMAND">ytalk</tt> session</b></p>
+
+<p><img src="basic-network-commands/ytalk.png" /></p>
+</div>
+
+<p>The username and terminal are specified the same as under talk, except you must put
+them together with the hash mark (#).</p>
+
+<p>ytalk offers several advantages:</p>
+
+<ul>
+<li>
+<p>It supports more than two users.</p>
+</li>
+
+<li>
+<p>A menu of options that can be brought up anytime with <kbd
+class="USERINPUT">Esc</kbd>.</p>
+</li>
+
+<li>
+<p>You can shell out while still in the talk session.</p>
+</li>
+
+<li>
+<p>Plus more...</p>
+</li>
+</ul>
+
+<p>If you're a server administrator, you'll want to make sure that the <tt
+class="COMMAND">ntalk</tt> port is enabled in <tt class="FILENAME">/etc/inetd.conf</tt>.
+<tt class="COMMAND">ytalk</tt> needs that to work properly.</p>
+</div>
+</div>
+
+<div class="NAVFOOTER">
+<hr align="LEFT" width="100%" />
+<table summary="Footer navigation table" width="100%" border="0" cellpadding="0"
+cellspacing="0">
+<tr>
+<td width="33%" align="left" valign="top"><a href="basic-network-commands-ftp.html"
+accesskey="P">Prev</a></td>
+<td width="34%" align="center" valign="top"><a href="index.html"
+accesskey="H">Home</a></td>
+<td width="33%" align="right" valign="top"><a href="security.html"
+accesskey="N">Next</a></td>
+</tr>
+
+<tr>
+<td width="33%" align="left" valign="top">FTP Clients</td>
+<td width="34%" align="center" valign="top"><a href="basic-network-commands.html"
+accesskey="U">Up</a></td>
+<td width="33%" align="right" valign="top">Security</td>
+</tr>
+</table>
+</div>
+</body>
+</html>
+