response 234 of 870:

Jan 5 20:54 UTC 2005

I don't know; I've not tried talk.

response 236 of 870:

Jan 5 21:00 UTC 2005

I get the same error message trying to talk to people whether or not they are
logged in - try a talk keesan (I am logged in) or a talk jdeigert.  Something
about sockets.  Presumably a file in the wrong place or some limit set wrong.

response 238 of 870:

Jan 5 21:15 UTC 2005

Sort of.  The program permissions determine who can run it, but what
needs changing is what permissions the program can use to run the other
processes it needs (like those that allow non-members to use talk to
connect to a non-Grex-local machine).

response 240 of 870:

Jan 5 21:28 UTC 2005

http://www.jewsforjoosuz.org/

response 242 of 870:

Jan 5 21:40 UTC 2005

http://www.jewsforjesus.org/

response 244 of 870:

Jan 5 21:53 UTC 2005

Hmm, I wonder what they are.

response 246 of 870:

Jan 5 22:55 UTC 2005

You can see them in ~aruba/.cfonce if you'd like.  My twitfilter also
highlights responses from cetain people by putting them in a different
color.

response 248 of 870:

Jan 5 23:17 UTC 2005

Thanks, mark.

response 250 of 870:

Jan 6 02:06 UTC 2005

I'd noticed that Pine creates debug files on another system I use, so I asked
the sysadmins about it.  They hadn't done anything special.  They also
reported that it behaved similarly on another of their systems.  So the
creation of these files appears to be a decision by the Pine developers.

I added an alias for pine to my list of aliases some time back, because I
want to go directly to the index of messages, not the "main" screen.  I've
now modified that alias to turn off the debug files:

        alias   pine    'pine -d 0 -i'

response 252 of 870:

Jan 6 07:25 UTC 2005

Pine and BBS response still do not work when dialed in direct;
and sz is still missing.

response 254 of 870:

Jan 6 14:35 UTC 2005

<twenex muscles in>

Generally speaking, I would advise against linking new versions of programs
(in the sense that vim is a new version of vi, gnu tar a new version of tar)
to the names of the old ones unless the new version provides functionality as 
near as dammit identical to the old one when called as such.

(On a related note: a lot of "easy to use" Linux systems alias "cp" to "cp -i",
"rm" to "rm -i", and so on. If this applies to any grexer, I would advise them 
to realias them back to their default "values". Not doing so runs the risk of
coming to a system  where they are NOT aliased and accidentally deleting
crucial files because you expected the system to ask you if you /really/ wanted
to do that, but it didn't. At first I used to disdain aliases for this reason,
but then I hit upon the following strategy:

Say I type "ls -F" often enough that it becomes a pain to have to type it all
the time, especially since i never use "ls" on its own. So I create an alias
based on ls which gives a clue as to the extra flags, such as "lsf". That's
a simple example, but with longer commands it could be quite useful.

Unless you know your system well, it's a pain to have to find the file where
the distributors have aliased all the commands, and you run the risk of having
to do it again when you upgrade. So just type, for example:

alias ls="/path/to/ls"

in whatever .profile or .login file your shell uses (the csh syntax might 
actually be a little different). This forces the shell to look for the command
instead of replacing its behaviour with a new one. If you don't want to do 
this for all the systems and/or account you use, then just do it for root on 
those systems you have root access to. 

response 256 of 870:

Jan 6 15:43 UTC 2005

I  was able to telnet in just now but dialin does not work:telnetd:  all
Network ports in use.   ...
Followed a few seconds later by NO CARRIER.    
Twice.
There is considerable telnet lag.   There was no wait when I telnetted.