I would like to use ytalk and set in /etc/inittab:
I can contact an other (different linux) box on the internal network, but attempts contacting this slackware box fails as "no talk daemon is running". I did not figure out what else is to be set.

Addendum:
I must have missed something, the talk daemon was running. It is still unusable, than the reply now is that the user is "not logged in" (naturally is logged in).

Just did some quick and dirty testing here

ytalk works and uses the talk line in inetd.conf
talk gives the error you describe and uses the second ntalk line

Make sure your using ytalk on both ends

Yes, ytalk was used on both boxes, these have fix IP addresses on the internal network. I can ring the other linux from the Slackware box but can not "call back".

Anyway, thank you for your efforts.

in.talkd runs under inetd, so you should check /etc/hosts.allow too for allowing the boxes to talk each other
just put in the ip/name(s) of the other box(es) ("man 5 hosts_access")

Set, the result is the same. The port 518/udp is open, I can ring the oder box (not Slackware) but can not call back as the user is reported to be "not logged in". If I try to call the router, than ytalk correctly reports that no talk daemon is running at that IP. So the talk daemon is running, the port is open and now allowed in /etc/hosts.allow. I guess I give up and look for something else.

I did like the idea that no server is required by ytalk and don't really intend to use Google Talk which loads a list of my "Contacts" and notifies them all that I am online. I find ytalk would provide me with more freedom

It is regrettable that ytalk seems not to be really supported anymore. (The next question would been: how to get a notification about an incoming call in an X-environment /there was'nt any on the oder box, I had to open a terminal waiting for the ringing

Best regards

you can specify the tty on the talk command line, so you just need to know the tty on which your user has a running shell (let him run the "tty" command to find it, works also under X).

Did not solve the issue. The ringing is received on the other box (not Slack) even without specifying the tty (both were on "0").

Meanwhile I searched the net but did only find "lan messengers" which is not the same as they can not be used over the internet.

sorry if I wasn't clear, that was an answer to this
you have to open a terminal under X, because talk rings on ttys.

If you want something to use through internet maybe you have to move away from talk (I think it's not safe for internet use) and use pidgin (in stock slackware) with some protocol (jabber or whatever) you don't already use (so no bothering for friends there).

Yes, "not safe" as clear text is sent, that is of no concern to me. I would'nt do any serious communication through the internet. If something is that important I tell/bring it personally (not on phone, email etc My concern with Pidgin et al is that they do not respect my privacy as I would like to have it. I register by a provider which keeps track on my contacts, loads them on a list, reports me online etc. You know it all. I instinctively stay away from those services. ytalk would be fine if it would work on Slackware (works on my girlfriends box with a different linux and did not find the difference, I am lost on that system, too

ngircd?
you can refeer here for an easy configuration and to slackbuilds.org for the build script.

1 members found this post helpful.

Yes, I already considered. I am not a big fan of IRC but that might be the way to go.

By the way: the router/server is openwrt and ngircd is already in the repository. (Had a Slackware server for approx 6 years running but the CISCO consumes about only 5W and have an acceptable system - though with compromises - using openwrt)

Many thanks for your advices!

Are you trying it on the terminal only? If not, you might have to have $DISPLAY set in /etc/profile or ~/.bashrc to the one X runs as, .i.e., do 'ps ax|grep X' and right after you should see something like ':0'. Then you have to 'export DISPLAY=:0' (or the number right after 'X') in profile or bashrc. I am not sure I was getting the pop-up messages until I tried this.

You also need to go to a shell and type 'mesg y' for every user you want to be able to receive messages.

1 members found this post helpful.