HDTenEightyP/NetNews huggingface dataset:
X-Mailer: ELM [version 2.3 PL0 (LUT)]
Newsgroups: bit.listserv.medlib-l
Date:         Mon, 25 Jan 1993 10:41:48 GMT
From:         HJ Dyer <H.J.Dyer@LUT.AC.UK>
Subject: Re: 3M Security System
              93 8:13 pm

If you'd thought of problems relating to OPACs, I'll bet this wasn't one of
them!

Hilary
>
> New opac terminals located about 10 feet from our 3M gate caused
> the security system to malfunction.  3M representatives were very
> helpful in helping to identify the specific problem and provided
> guidance on a solution (the design of a thick aluminum shield box
> around the terminals).  A local contractor made the shield box
> and we paid for materials and labor.
>
> Don Lanier, Site Librarian             U17113@UICVM (BITNET)
> University of Illinois at Chicago      U17113@UICVM.UIC.EDU (INTERNET)
> College of Medicine at Rockford
> 1601 Parkview Ave.                     (815) 395-5658 (VOICE)
> Rockford, IL  61107                    (815) 395-5655 (FAX)
>


--
==============================================================
|  Mrs Hilary Dyer                                           |
|  Senior Lecturer,  Department of Information and Library   |
|  Studies, Loughborough University, Loughborough,           |
|  Leicestershire, LE11 3TU                                  |
|                                                            |
|  JANET: H.J.Dyer@uk.ac.Loughborough                        |
|  Phone: (0509) 223068 (direct line)                        |
|  Fax: (0509) 223053                                        |
==============================================================
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.medlib-l
Date:         Fri, 22 Jan 1993 09:11:55 U
From:         Evelyn Wrinn <Evelyn_Wrinn@QUICKMAIL.YALE.EDU>
Subject:      ADVERTISEMENT

                       Subject:                               Time:8:41 AM
  OFFICE MEMO          ADVERTISEMENT                          Date:1/22/93
TECHNICAL SERVICES LIBRARIAN, Harvey Cushing/John Hay Whitney Medical Library,
Yale University, Minimum rank: Librarian II. RESPONSIBILITIES:  Manages the
monograph and serials acquisitions operations in the Medical Library and
coordinates cataloging activities and work flow with Head of Medical
Cataloging.  Supervises staff.  Assists in identifying, selecting and
establishing business relationships with publishers and vendors.  Monitors
expenditures.  May perform original cataloging.  QUALIFICATIONS; MLS from an
ALA-accredited library school.  At least two years of successful professional
library experience in technical services; effective oral and written
communication skills; organizational ability; strong interpersonal skills and
ability to work with others; supervisory experience; ability to analyze and
evaluate operations and services and to effectively plan and manage appropriate
changes; reading knowledge of at least one European language; experience with
PC based library applications and at least one automated library system.
SALARY; from a minimum of $32,700 dependent upon qualifications and experience.
 Full benefits package including 22 vacation days, 17 holiday, resess and
personal days; comprehensive health care, retirement.  To be assured of
consideration, please submit a letter of application, resume, and the names of
three references by March 15, 1993 to Diane Y. Turner, Director, Library
Personnel Services, Yale University Library, P.O. Box 1603A Yale Station, New
Haven, CT 06520.  Yale University is an equal opportunity affirmative
 action#011#
employer.#011#
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.medlib-l
Date:         Thu, 28 Jan 1993 09:44:16 -0500
From:         "SHANAHAN, Mary" <mshanaha@LIFE.DNET.NASA.GOV>
Subject:      RE: CD Plus statistics

     ACKNOWLDEDGE RECEIPT AT:  28-JAN-1993 08:42
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer: ELM [version 2.3 PL11]
Newsgroups: bit.listserv.medlib-l
Date:         Thu, 28 Jan 1993 13:40:06 EST
From:         Eric H Schnell <ehschnel@MAGNUS.ACS.OHIO-STATE.EDU>
Subject: Re: CAI for Physician Assistants
              Lukas" at Jan 28, 93 12:07 pm

     I have personally found OCLC/EPIC more rewarding than AVLINE when
searching for CAI's. AVLINE seems to be filled with too many Apple II programs.
Ther Bowell book is excellent. It also has been included in the CDROM version
of CINAHL (Cumulative Index to Nursing and Allied Health Literature)

^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
^ Eric Schnell                           EHSCHNEL@magnus.acs.ohio-state.edu  ^
^ Automation Librarian                                                       ^
^ Ohio State University Health Sciences Library                              ^
^                                                                            ^
  GO BILLS !!
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: RELUSR-L@NCSUVM.BITNET
X-VMS-To: IN%"RELUSR-L@NCSUVM.BITNET"
MIME-version: 1.0
Content-transfer-encoding: 7BIT
Newsgroups: bit.listserv.relusr-l
Date:         Thu, 21 Jan 1993 15:15:46 -0700
From:         SAWYER@NAUVAX.BITNET
Subject:      Re: "Super-private" channels

I have a question concerning all of the Classes.
I am curious as to what the class levels are for
Relay and how one would get a certain level on Relay?
Thanks in advance
        Scott aka Knight
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Mailer: Mail User's Shell (7.2.5 10/14/92)
Newsgroups: bit.listserv.relusr-l
Date:         Thu, 21 Jan 1993 12:16:29 -0500
From:         Jay Vassos-Libove <libove@ALF.DEC.COM>
Subject: Re: Changing /signon options ?
              Changing /signon options  ?" (Jan 21, 12:10pm)

Actually, the suggestion of modifying the default behaviour of SIGNON
from its present "put the user on channel 1 if no other channel is
specified" to what IRC does which is "put the user in a limbo where
there is no channel affiliation" probably wouldn't require too big
a modification of the code, though of course Valdis is the one who
really knows how big a change that would be.

If the code is structured the way I guess, then each user has a
structure which defines its (his/her) attributes, including current
channel affiliation.  Presumably, then, in the code for handling where
messages get sent, a check is made of each user's channel affiliation,
and messages are forwarded to those relays which have users signed on
to a given channel (or perhaps the user structures are included in a
list of users on each channel).
In any case, it seems that if a user has no channel affiliation, then
messages just won't get passed from channels to the user, but that
private messages, which bypass channels entirely anyway, would still
work.

Valdis?  Did I get it right?

-Jay
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Acknowledge-To: <ENMORRIS@ECUVM1>
Newsgroups: bit.listserv.relusr-l
Date:         Thu, 21 Jan 1993 11:33:05 EST
From:         V C Morrison <ENMORRIS@ECUVM1.BITNET>
Subject:      Re: "Super-private" channels

I believe by super private channels you mean those below 0 and above 999.
Relayers with Class 3 (I believe) status are able to travel to those channels
for, naturally, super-private reasons.


_________/
________/\
_______/\ \
______/\ \ \
_____/\ \ \ \     "If I cannot bring you comfort,
____/\ \ \ \ \     Then at least I bring you hope."
___/\ \ \ \ \ \
__/\ \ \ \ \ \ \
  \ \ \ \ \ \ \ \
   \_\_\_\_\_\_\_\-={W A L K   T H E   W E B}=_________________________
   / / / / / / / /                           enmorris@ecuvm1.bitnet
  / / / / / / / /      []dreamweaver[]   enmorris@ecuvax.cis.ecu.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.relusr-l
Date:         Thu, 21 Jan 1993 12:28:00 EST
From:         Senthil Ramas Kumar <SRK106@PSUVM.BITNET>
Subject: Re: Changing /signon options ?

>But is it really such a chore to type  /si 543 instead of /si
>
>  / / / / / / / /      []dreamweaver[]   enmorris@ecuvax.cis.ecu.edu

It really isnt a chore at all, but pple like me, _always_ go to the most
crowded ch :) I guess, I really must be bored :)

I think the point is that, the relay can be made more user-friendly, with
just a little bit of an additional effort.

Kumar
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Virginia Polytechnic Institute
Newsgroups: bit.listserv.relusr-l
Date:         Thu, 21 Jan 1993 17:39:15 EST
From:         Valdis Kletnieks <VALDIS@VTVM1.CC.VT.EDU>
Subject:      Channels....

For those who care:

Relay V2.07 will include the following structure:

Channels 0-99 will be public, same as now.

100-999 will be semi-private - you need to know the channel number in order
to get in, but anybody who knows it can get in (see the current usage of
channels 333 and 561 for examples).

1000+ will be private - if the channel is empty, you can go to it and create
it.  However, if it is occupied, you will need a /invite to get in, and
you cannot '/signon' into an occupied private channel.

Channels -999 to -1 will be hidden semi-private channels - they will not
show up on a /list or /who, but you can /signon or /ch to them

Channels -1000 and down will be hidden private channels. They won't show,
and you'll need a /invite to get in.

Hopefully this will provide sufficient flexibility...

/Valdis
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: Virginia Polytechnic Institute
Newsgroups: bit.listserv.relusr-l
Date:         Mon, 25 Jan 1993 17:01:39 EST
From:         Valdis Kletnieks <VALDIS@VTVM1.CC.VT.EDU>
Subject:      Re: Relay Ops and IRC Equivalent

On Mon, 25 Jan 1993 19:15:27 GMT Christopher Davis said:
>If you want a quiet channel for people to converse, and you don't want
>anyone kicking, or whatever, start your channel, invite some people, and
>don't give anyone else channel operator!

Chris:

Does this mean that the IRC folk *finally* plugged that little hole that
allowe basically anybody to seize  channel operator privs whether or not
you wanted to grant them?

A note to all:

Security-wise, IRC leaks like a sieve.  Take note of this anytime you
*think* you know who you're talking to...

                                  Valdis Kletnieks
                                  Computer Systems Engineer
                                  Virginia Polytechnic Institute
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.relusr-l
Date:         Tue, 26 Jan 1993 10:56:52 EST
From:         IP25348@PORTLAND.BITNET
Subject:      The easiest way to become a RELAY OP........

The easiest way to become a RELAY OP is......
to sleep with a MASTER OP (or so I am told)

Nick "Stimpy" Brassard
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Acknowledge-To: <ENMORRIS@ECUVM1>
Newsgroups: bit.listserv.relusr-l
Date:         Thu, 21 Jan 1993 17:20:02 EST
From:         V C Morrison <ENMORRIS@ECUVM1.BITNET>
Subject: Re: Changing /signon options ?

That's a good point.  I know I get annoyed when people sign onto the channel I'
m on.  Actually 543 was just an example.  I normally choose a random super priv
ate channel, i.e. 989283, then change somewhere, basically because I don't want
 to hassle anyone by signing onto a probable occupied channel or get spammed by
 messages when signing onto an occupied channel.  But you're right, I should st
art signing onto public channels <wince>.


_________/
________/\
_______/\ \
______/\ \ \
_____/\ \ \ \     "If I cannot bring you comfort,
____/\ \ \ \ \     Then at least I bring you hope."
___/\ \ \ \ \ \
__/\ \ \ \ \ \ \
  \ \ \ \ \ \ \ \
   \_\_\_\_\_\_\_\-={W A L K   T H E   W E B}=_________________________
   / / / / / / / /                           enmorris@ecuvm1.bitnet
  / / / / / / / /      []dreamweaver[]   enmorris@ecuvax.cis.ecu.edu
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.relusr-l
Date:         Thu, 21 Jan 1993 15:13:41 EST
From:         Pam Hollingsworth <HSHANER@UCS.INDIANA.EDU>
Subject:      Private channel options

Hello,

        Another idea I'd like to see in relay that is currently used on IRC is
the ablity to change modes on a channel.  Such as:
        You can only join the channel if you are invited.
        Only an 'op' may change the topic.

and so on.  Would these ideas be feasible?




    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
    @   Pam Hollingsworth                    HSHANER@ucs.indiana.edu     @
    @                      Have an ordinary day.   :-|                   @
    @   Kokomo, Indiana USA                  Indiana University - Kokomo @
    @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.relusr-l
Date:         Thu, 21 Jan 1993 14:34:02 CST
From:         "Jim Glover (Key), Relay Op" <SPJRG@LATECH.BITNET>
Subject: Re: Changing /signon options ?

>But is it really such a chore to type
>
>/si 543
>
>instead of
>
>/si
>
>?

Actually, one should never /signon to a private channel (any channel
besides 0-99) without checking first to see if the channel is vacant.
Before entering the quoted command, you should wait for a response to
the command:  /who 543   Only if Relay responds by telling you that
there is no one on that channel should you go ahead and /signon to that
channel.  Please note that you should *never* /signon or /ch to a
private channel you haven't been invited to until you have confirmed
that the channel is empty.

Of course, it would be perfectly OK to /signon to a public channel
without checking first, e.g.:

/si 43

               --Jim  (Key)
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Envelope-to: RELUSR-L@NCSUVM.BITNET
X-VMS-To: IN%"RELUSR-L@NCSUVM.BITNET"
Newsgroups: bit.listserv.relusr-l
Date:         Wed, 27 Jan 1993 23:32:00 EST
From:         ALYOSHA@DRYCAS.BITNET
Subject:      Do NOT POST TO THIS LIST!! please.

Please cease all posts to this list effective immediately, as per
request of the list owner.  Every single message posted is generating
a large number of error mail messages to her account, which at present
she is unable to access.

I thought I posted here about it 2 days ago, only to log in today and
find an extrememly large number of posts.  PLEASE let this one be the
last.

Again:  DO NOT POST to RELUSR-L until the list owner gets back and
gives the green light.  Any questions about Relay can be directed to
me or to any Relay Operator you see signed onto Relay.

Thank you.

- Alex Rudd - <Alyosha> - Relay Operator, Va_Tech Relay
  ahrjj@cunyvm  or  alyosha@drycas
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
X-Acknowledge-To: <K189CD@TAMVM1>
Newsgroups: bit.listserv.relusr-l
Date:         Tue, 26 Jan 1993 22:33:19 CST
From:         "Charlotte A. Dick" <K189CD@TAMVM1.BITNET>
Subject:      RelayOp Requirements Info

(This is a generic email answer that I send to users who request
information about becoming an Op at Aggieland Relay.  I would,
of course, edit it appropriately for the circumstances at the
time.  I try to treat it as any other job being filled and
require an email resume, a virtual or in-person interview, and
check references from other users and Ops as appropriate.)
       /Charlotte (aka PrincessOp, Charli, Granni)

     ----------------------------------------------------
Info about becoming a RelayOp.....  Some of the qualifications
for a RelayOp are:  patience (lots of it), maturity, sense of
responsibility, not easily angered, knowledge of Relay operations
and guidelines and knowledge of BITNET/CREN (these can be learned of
course), a liking for people and tolerance of people differences,
ability to be firm but fair and objective, etc.  A good sense of
humor is helpful too sometimes!  :-)

A relayOp is responsible for assisting users with problems,
answering questions, enforcing the rules when needed, monitoring
Relay's operations and keeping it running efficiently, etc.

The best way to become a RelayOp is to get to know the other Ops well
and especially your MasterOp so they can observe what kind of user and
person you are and how well you deal with other people.  You should
also send an informal resume or e-mail to your MasterOp in order
to have it on file.  Some things to include would be:  why you
want to become a RelayOp, why you think you would be a good
RelayOp, your current status (classification, major, student
worker, staff member, etc.), education background, work experience,
and a list of references (Relay users and Ops), etc.

For Aggieland Relay, it must be the primary Relay for the
user's node (or in exceptional cases, the secondary Relay service
area for that node).  If so, then the user can send me the above
information so I can keep it on file for future reference should
a vacancy occur at our Relay.

Charlotte Dick
Aggieland Relay Administrator
K189CD@TAMVM1
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.relusr-l
Date:         Mon, 25 Jan 1993 14:17:42 CST
From:         "Ajay J. Patel." <FREE2019@UIUCVMD.BITNET>
Subject:      Re: Relay Ops and IRC Equivalent

I want to get on IRC, but i don't have any files that would let
me do so from this VM account of mine.
Can someone help me please?  if there are files required, could
you please send them to me? thank you.
You may contact me thru personal e-mail at:  Free2019@uiucvmd.cso.uiuc.edu
Thank you.

--AJ.
Thank you.

--AJ.


This NOTE is a reply to:
------------------------
>Return-Path: <@VMD.CSO.UIUC.EDU:RELUSR-L@NCSUVM.BITNET>
>Received: from UIUCVMD.BITNET (NJE origin LISTSERV@UIUCVMD) by VMD.CSO.UIUC.EDU
>          (LMail V1.1b/1.7e) with BSMTP id 8649; Mon, 25 Jan 1993 14:07:19 -060
>Date:         Mon, 25 Jan 1993 19:15:27 GMT
>Reply-To:     Relay Users Forum <RELUSR-L@NCSUVM.BITNET>
>Sender:       Relay Users Forum <RELUSR-L@NCSUVM.BITNET>
>Comments:     Warning -- original Sender: tag was NETNEWS@AUVM.AMERICAN.EDU
>From:         Christopher Davis <ckd@EFF.ORG>
>Subject:      Re: Relay Ops and IRC Equivalent
>To:           "A. J. Patel" <FREE2019@UIUCVMD.BITNET>
>In-Reply-To:  Rich Jacobs's message of Mon, 25 Jan 1993 11:08:34 EST
>
>RJ> == Rich Jacobs <RJACOBS@CCVM.SUNYSB.EDU>
>
> RJ> This is one of the major reasons why I avoid IRC most of the time.
> RJ> There are *to many* people with higher privalages on IRC and I see
> RJ> this "channel op" privelage as being abused to a very high degree.
>
>So start your own channel.
>
> RJ> I have been on channels where people are booted off for no reason at
> RJ> all.
>
>So start your own channel.
>
> RJ> It is not uncommon to see 5 and 6 people booted off a channel.
>
>So leave that channel and start your own channel.
>
> RJ> When you have so many people that have that type of power, there is a
> RJ> great chance of it being abused.  And I have seen it in action.
>
>So go to a different channel.
>
>The whole point of channel operators on IRC was to allow users to have more
>power over their own destinies--both to get IRC operators out of the
>business of resolving user-user disputes and to take some of the "glamour"
>out of being an IRC operator.
>
>If you want a quiet channel for people to converse, and you don't want
>anyone kicking, or whatever, start your channel, invite some people, and
>don't give anyone else channel operator!
>--
> * Christopher Davis * <ckd@eff.org> * <ckd@kei.com> * [CKD1] * MIME * RIPEM *
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Organization: North Dakota Higher Education Computer Network
Newsgroups: bit.listserv.relusr-l
Date:         Thu, 21 Jan 1993 17:43:24 CST
From:         "J.S. Bach" <SIEGAL@NDSUVM1.BITNET>
Subject: Re: Changing /signon options ?

Everyone....
    This might be just me, but I have the feeling it isn't...
    If you try to /SI to channel 1 and it is full... check the /list and find
another channel... sitting there sending repeated message trying to get on
to channel 1 seems silly, if not stupid.  You can always /msg someone on
channel 1 that you REALLY have to talk to.  Asking Val to change all of the
relay coding seems ludicrous.
    As for signing on to private channels... just do a /na 398 (for example),
if it's occupied, you'll be told so...
    And, adding some of the IRC restricions (such as having an OP the only
person who can change the topic would be unfeasible... unlike IRC, there is
not always an Op on every channel...  and there are only a certain number
of invite only channels on IRC, users can already set up /invite only
channels on relay anyway. Just invite you and all your buds to a channel
between 0-999 :)

    Relay is for relaxation and entertainment.... let's not make this any
harder than it need to be, which is not hard at all.
    Besides, we all want to keep Valdis' life as simmple as possible ;)

Peace,

Susan Siegal
(JD/Titania)
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.relusr-l
Date:         Thu, 21 Jan 1993 13:01:06 -0900
From:         The Palmer House! Art/Jay/Aaron! <FSACP@ALASKA.BITNET>
Subject:      Re: dunno if

thanks for the info!
I appreciate it, it makes me feel a bit easier!
I got to see mary today and she helped to relax me *Grin*
Comments: Gated by NETNEWS@AUVM.AMERICAN.EDU
Newsgroups: bit.listserv.relusr-l
Date:         Fri, 22 Jan 1993 12:41:06 EST
Comments:     Resent-From: Michael Hillwig <MLH4125@SRU>
Comments:     Originally-From: "Jim Glover (Key),
              Relay Op" <SPJRG@LATECH.BITNET>
Comments:     Warning -- original Sender: tag was RELUSR-L@NCSUVM
From:         Michael Hillwig <MLH4125@SRU.BITNET>
Subject: Re: Changing /signon options ?

Jim Glover (Key) wrote:

>Actually, one should never /signon to a private channel (any channel
>besides 0-99) without checking first to see if the channel is vacant.
Before entering the quoted command, you should wait for a response to
I understand the philosophy behind this, but experienced RELAY users
know what channels they usually use, and what ones to stay away from.
For example, I'm usually on one channel, which is a fairly random
number.  I have NEVER seen anyone else on that channel unless they are
a friend or I /invited them.

BTW, what is IRC??
Michael Hillwig aka PhiKap
                aka BoredRA





***********   *        *     ******      Michael Hillwig
    *         *      *      *      *     Sigma Rho 66
   ***        *    *       *        *    209 Rhoads Hall
  * * *       *  *         *  *  *  *    Slippery Rock, PA  16057
  * * *       **           *  ****  *
  * * *       *  *         *  *  *  *    MLH4125@SRU.BITNET
   ***        *     *      *        *    PHIKAP-R@SRU.BITNET
    *         *       *     *      *     "Knowledge is good."
***********   *         *    ******      A. Faber, Animal House