NCSA Telnet Digest	Wednesday, 4 Nov 1987		Volume 1 : Issue 7

Today's Topics:
			  Blinking session
			  Blinking Session
                How to handle nameserving of nicknames
                  Keyboard remapping and Multi-Finder

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

From: John Matzka <johnm@jacobs.cs.orst.edu>
Date: Fri, 30 Oct 87 12:53:32 pst
Subject: Blinking session

The blinking session doesn't annoy me much but as was pointed out, it isn't
really necessary since the menu bar will flash when sound is turned off.
Perhaps this "feature" could be made an option perhaps this option could be
set in the config.tel file.

John Matzka
johnm@jacobs.cs.orst.edu


------------------------------------------------
From: gaige@ncsa.uiuc.edu (Gaige Paulsen)
Date: Sat, 31 Oct 87 16:05:21 CST
Subject: Blinking Session


The reason that the session blinks when the bell sounds is to identify which
session the bell is coming from.  I am quite aware of the blinking menu bar 
effect, but have been known to have trouble determining which window to look
in when there was a beep caused by external events (especially difficult with
4+ windows).   Perhaps we should look into just blinking the session if it
is not the currently active session.  Therefore, only beeps from a session in
the background would blink at you.


What do you think?


Gaige

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

From: gaige@ncsa.uiuc.edu (Gaige Paulsen)
Date: Sun, 1 Nov 87 13:40:00 CST
Subject: Keyboard remapping and Multi-Finder


  I have been told that people are having problems with the keyboard remapping
screwing up other applications under Multi-Finder.  Although I agree that
it is a problem and am working on finding a nice solution, there is an interim
solution to the problem.  Provided with the new system file is a new keyboard
'cdev'  this should allow you to change the keyboard back and forth as
necessary.

Gaige B. Paulsen
National Center for Supercomputing Applications


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

From: timk@ncsa.uiuc.edu (Tim Krauskopf)
Date: Wed, 4 Nov 87 17:41:52 CST
Subject: How to handle nameserving of nicknames


I would like to get some input on the use of nicknames with NCSA Telnet:

Is the presence of the CNAME field in BIND a nickname facility that we can
use instead of burdening our local config files with all of the nicknames
that each user wants?

Here are the choices that I see:

choice 1:
  add default domain endings to non-qualified names or not.  i.e. we append
  "ncsa.uiuc.edu" to the end of every short name that is typed by the user
  before that name is looked up with domain name lookup.

If you do add them, then people in this building must type fully qualified
names or some other strange scheme when they want to get out of the building.
Or maintain those names in local host files -- same as old problem.

choice 2:
  since we aren't going to add the default domain ending, where shall we
maintain the list of nicknames which includes names from inside our domain
and "nic" or "andrew" which are outside our domain?
  Shall we put them in our individual config files or are we going to maintain
a CNAME cache on our BIND servers?  I know which one is easier.

We are trying to bring up a CNAME server that takes care of our nicknames.
These names would never be exported, but requests at our local servers would
be honored for nicknames.  Another way to do it is support yellow pages, 
but no thank you.

Any other points of view?

Tim Krauskopf
timk@ncsa.uiuc.edu