ktalkd4 Files

This is ktalkd4-0.1 for Linux.

This package is a fork from netkit-ntalk-0.17.

Its purpose is to be backward compatible with the historical talkd and
adding support for Kde or any other environment where terminals running
under X don't notify themselves to the utmp service.

To activate new kde support invoke talkd in your /etc/inetd.conf with two lines
like those:

talk		dgram	udp	wait	root.tty	/usr/local/sbin/talkd in.talkd -k
ntalk		dgram	udp	wait	root.tty	/usr/local/sbin/talkd in.ntalkd -k

Of course you should modify the path of the talkd binary to where it actually
is.

In this way talkd will launch ktalkwake. This will work only if compiled with
ktalkwake support. To enable it do nothing other than installing ktalkwake
before compiling talkd.

Sure, it would be more handy if ktalkwake were included in this package... But
this software is released under an undetermined old BSD Licence while ktalkwake
is GPL and I don't want to do a mess with different terms and conditions.

Since most ytalk users don't need the original talk client, client compilation
is disabled if ytalk binary is found by configure. If you want to compile it
anyway run configure with --enable-client option. The talk client is unmodified
from netkit-ntalk-0.17 for Linux unless for the Makefile* and friends.

This software has never been tested on machines other than 2.6.35-24-generic
#42-Ubuntu SMP Thu Dec 2 02:41:37 UTC 2010 x86_64 GNU/Linux
Please, report both your successfull and unsuccessfull attempts to compile and
run on different systems

What follows is the original README.

Lucio Tomarchio
24 January 2011

------------------------------------
This is netkit-ntalk-0.17 for Linux.

This package updates netkit-ntalk-0.16.

If you're reading this off a CD, go right away and check the net
archives for later versions and security fixes. As of this writing the
home site for NetKit is
	ftp://ftp.uk.linux.org/pub/linux/Networking/netkit

Contents:
	talk		Program for chatting with another user elsewhere.
	talkd		Daemon to help set up talk sessions.

Requires:
	Working compiler, libc, and kernel, and a recent ncurses.

Security:
	This release contains a fix for an almost certainly 
	unexploitable issue in netkit-ntalk-0.16 Just to be safe,
	we recommend not running netkit-ntalk-0.16 or earlier.
	Versions prior to NetKit-0.09 should not be used under any
	circumstances.

Features:
	talk should now works correctly on multihomed machines (those
	with multiple IP addresses).

	talkd now contains code to hopefully detect and handle certain
	kinds of mangled talk packets that you may encounter. It also
	now has an option to log talk packets it doesn't understand;
	see the man page. Hopefully this will be useful if you run into
	interoperability problems.

Other notes:
	Use of the "wordwrap.patch" patch is neither recommended
	nor discouraged. Apply it at your discretion.

Installation:
	Do "./configure --help" and decide what options you want. The
	defaults should be suitable for most Linux systems. Then run
	the configure script.

	Do "make" to compile.
	Then (as root) do "make install".

	Save a backup copy of any mission-critical program in case the
	new one doesn't work, and so forth. We warned you.

	If you get gcc warnings from files in /usr/include, they are
	due to problems in your libc, not netkit. (You may only see
	them when compiling netkit because netkit turns on a lot of
	compiler warnings.)

DEC CC:
	The DEC compiler for the Alpha is now freely available. This
	is a much better compiler with gcc, that is, it generates much
	better code. If you have the DEC compiler, you can explicitly
	use the DEC compiler instead of gcc by configuring like this:

		./configure --with-c-compiler=ccc

	It is known to generate spurious warnings on some files. Also,
	some headers from some versions of glibc confuse it; that may
	prevent	netkit from working. Other problems should be reported
	as bugs.

Bugs:
	Please make sure the header files in /usr/include match the
	libc version installed in /lib and /usr/lib. If you have weird
	problems this is the most likely culprit.

	Also, before reporting a bug, be sure you're working with the
	latest version.

	If something doesn't compile for you, fix it and send diffs.
	If you can't, send the compiler's error output.

	If it compiles but doesn't work, send as complete a bug report as 
	you can. Patches and fixes are welcome, as long as you describe 
	adequately what they're supposed to fix. Please, one patch per
	distinct fix. Please do NOT send the whole archive back or
	reindent the source.

	Be sure to send all correspondence in e-mail to the netkit address.
	Postings to netnews or mailing lists will not be seen due to the 
	enormous volume. Also, anything that doesn't get filed in the bug
	database is quite likely to end up forgotten.

	Please don't report known bugs (see the BUGS file(s)) unless you
	are including fixes. :-)

	Mail should be sent to: netbug@ftp.uk.linux.org


Early in April 2000, a hacker broke into the machine that was hosting
the netkit bug database for me and trashed it. Unfortunately, it seems
backups hadn't gotten done for a while, so three months of mail (since
mid-January) was lost. So, if you sent something and didn't hear back,
or you sent something, heard back, but the changes failed to appear in
this release (unlikely but possible) - please resend.

Please see http://www.hcs.harvard.edu/~dholland/computers/netkit.html
if you are curious why it was so long between the 0.10 and 0.16 releases.

Future plans for netkit maintenance are still up in the air, but in the
meantime new releases will still appear from time to time. I don't have
a whole lot of cycles to spare to work on netkit, so things are likely
to continue to be fairly slow.

David A. Holland
23 July 2000