Uh, is there a reason why I can't talk or ntalk
back to the initiator?

Message from Talk_Daemon@grex at 17:44 ...
ntalk: connection requested by bob@is.really.normal
ntalk respond with: ntalk bob@is.really.normal

[Unable to connect with initiator : Permission denied (13)]










-------------------------------------------------------------











?

24 responses total.

If the initiator is on a remote system, I guess you can't reply
because you'd be using outgoing telnet and you're not a member.

(that would be strange, as last I checked, we didn't have a remote
talk-daemon that answered incoming talk requests. Has something changed in
the last month?)

I've gotten off system talk requests before, and the first was a lot more
than a month ago.  As far as vishnu's problem goes, it was probably
related to not being a member, but is is.really.normal a real address?

/u/rcurl nsquery is.really.normal
nsquery: is.really.normal: Unknown host

When responding to local talk requests, does one really have to type out
ntalk username@grex.cyberspace.org in its entirety?  And if a talk request 
comes in while one is doing something like posting a response, is there a
time limit for getting to some prompt that one can reply from?  (I think
what I did last time was to post the reply in the response I was working on,
then email the person to tell them where to look for it.) 

The WELL has a command call huh that retrieves the last message sent to you,
so you can in effect let sends accumulate and reply at leisure.  And if the
other person has since logged off, the reply is automatically mailed. 

You just have to type "talk username"; ntalk and talk are the same thing
on Grex, and if both you and the other person are on the same machine,
you don't have to include the machine name.

There's also no time limit to reply, but the other person can abort
the talk connection at any time.  If you reply after they've bailed
out, you may have to wait a few moments while *they* get a talk request,
finish what they're doing at the moment, and reply.

(now that I've thought about it, I've gotten a talk request from jasmine
on M-Net, but whenever I try to use my local talk program to connect to
someone from Grex, I get a "The remote talk daemon is not responding"
message. I'm using LAN Workplace for Windows' talk program.)

I just said bill@is.really.normal as an example.  It's
not real.

er, bob.  Anyway, it's not just
on remote systems, it is also
on local talk things.

This response has been erased.

If I'm trying to talk to somebody on Grex, I always leave out the
"@cyberspace.org"  Sometimes it works and sometimes it doesn't, but
generally if it works locally it works remotely.  It seems to have a lot
to do with what the system load is.

Folks, remember:  There's something screwy with the actual
program "talk".  Use "ntalk" or "ytalk" instead.

Don't ask me what the problem is.

This response has been erased.

I have the same problems with talk locally.  I usually give up and
use "chat".

I can't use talk, ntalk, or ytalk, with
or without the @cyberspace.org

This response has been erased.

I'd like to ask, whenever commands in Picospan are being explained,
whether or not a bang (!) is needed. It has gotten confusing because
more unix commands used in Picospan are being set up to not require
the bang (!). For example, I thought write, chat and talk did - but
do they still?

I'd imagine a 'safe' rule of thumb would be:
When in doubt, bang!!

Or: if you try what someone suggests and it doesn't work, try sticking !
at the beginning & see if that's the problem.

Rane, we try to remember to keep this straight in explaining things, but
it's easy to forget.  This is the kind of thing we sometimes forget ourselves,
without even noticing because we see immediately what's wrong & retype the
command.

This response has been erased.

This response has been erased.

Are there any unix commands that *couldn't* be debanged in Picospan?

This response has been erased.

That could be dangerous ... but I've often wished for it myself.

Response not possible - You must register and login before posting.

- Backtalk version 1.3.30 - Copyright 1996-2006, Jan Wolter and Steve Weiss