AABENSON@MTUS5.BITNET (12/12/90)
Somebody mentioned that if you didn't have irc access, but had telnet access
that there was a BBS place you could telnet to. This is true, but I've found
it easier just to telnet directly to somebody's IRC server. It works just
as well (not that good).
If anybody wants #'s, let me know (email aabenson@balance.cs.mtu.edu).
- Andrew.maye_ltd@uhura.cc.rochester.edu (Robert Mayer) (12/13/90)
Ok, bedtime for bonzo.... I've been loosing my mind and you've gotta help me out. I went mucking about my Unix site a couple of days ago, hoping against hope that I could find a servicable xmodem driver...well I lucked out. I managed to find a server that works with X/Y/Zmodem protocals in the /usr/cif/bin directory.... now the catch is that I can't just use the commands normally from the shell, ie type "xs" because they are not in the normal place /usr/bin/ I can't change it because I'm a _ltd user (read 3rd class citizen) and don't have write permission to /usr/bin/ THIS IS NOT THE PROBLEM. What is the problem is that also in the /usr/cif/bin directory is a nifty little progam called IRC... I have tinkered (rather unsucessfully) with it. With all the noise about a gathering over IRC, I thought it would be worth my while to figure it out. THIS IS THE PROBLEM. There is absolutely NO documentation for IRC anywhere in the system. I did a man irc, man -k irc, and finally in utter frustration ran a a global find [iI][rR][cC] which took hours and produced no results. I searched through all of my users manuals, most notably UNIX system V release 4 the complete reference" by Stephen Coffin. Not a damn thing same story with my other unix books. I don't know about you but when I find a neat toy that comes with no info I get curious, then I tinker, if tinkering doesn't work I get upset....then when I calm down I ask. So I'm asking.. (forgive me for taking a page to get to the point but I thought a slow burn would be sortof suspensful, that and it's somewhat thereputic) Can someone: 1. Send me documentation for IRC 2. Tell me where to FTP information on IRC 3. Explain in clear and explicit terms what I should be doing after I get into IRC and "/join +(insert group here)" I managed to join a group and nothing got printed to the screen. It just sat idle while I swore at the cpu.... after a minute I got a message that read "** Signoff Goofball" I have to admit that I really lost control, and don't remember much after that point... So any help would be infinitely appreciated. Rob Mayer maye_ltd@uhura.cc.rochester.edu MAYELTD@UORVM.BITNET If all else fails, read the directions.
greg@hoss.unl.edu (Hammer T. H.) (12/13/90)
In <90345.160809AABENSON@MTUS5.BITNET> <AABENSON@MTUS5.BITNET> writes: >Somebody mentioned that if you didn't have irc access, but had telnet access >that there was a BBS place you could telnet to. This is true, but I've found >it easier just to telnet directly to somebody's IRC server. It works just >as well (not that good). Heh, I remember one site that got kinda mad at Quartz BBS (quartz.rutgers.edu) for using IRC in "raw mode" without a client. Seems that their main argument was that it was possible to crash their server doing this, and so they locked them out, until they got a client that didn't pose a security risk to the BBS. Actually, I'm not sure if they got a safe client or not... comments Opus? > - Andrew. -- __ _____________ __ \ \_\ \__ __/ /_/ / How many Sirius Cybernetics Corporation robots \greg@hoss.unl.edu/ does it take to change a lightbulb? \_\ \_\|_|/_/ /_/ "Lights... don't talk to me about lights."
AABENSON@MTUS5.BITNET (12/14/90)
Robert Mayer, Well, I can't really help with the IRC thing, because I don't have any instructions either. But, I can tell you how to get those commands accessible from your command line... I think! I don't know what shell you're using, but I use csh as my login shell. Anyway, in my ".login" file, there's one line that says something like "set path = /usr /usr/bin /etc /usr/local/bin / and a bunch more..." You can add other directories to that string.. Just make sure that if you are going to make it go to a new line, put a backslash right before you press return -- that will stop it from taking that as the end of the line. Then, when you login, you should be able to access commands that are in the new directory (/usr/cif/bin, right?). Also, you might need to type rehash. I'm not sure when exactly that is necessary.
marekp@pnet91.cts.com (Marek Pawlowski) (12/16/90)
Wrong.
--
If your default shell is "sh" (aka the Bourne shell), the file called .profile
in your directory, will be the first one to be executed.
If your default shell is "csh" (ake the C-shell), the file called .login in
your directory, will be the first one executed.
The "path" or "PATH" shell variables, contains various directory names, which,
when a command is entered, will be searched through (in order of appearance)
for the specified binary.
Under sh, you would set it up like so:
PATH=/bin:/usr/bin:$HOME/bin:. # set command search path
What this means, is that if the user types "ls", for example. The system will
look in /bin first. If "ls" is in there, it gets executed. If not, it goes
on to /usr/bin, if not again, then it looks in the $HOME/bin directory. And
if not, it will look in the current directory (=".") for this file. If "ls"
wasn't found anywhere, you will be told so.
To add another path to this list (under the Bourne shell!) just add another
"field", separated from the rest with a colon.
Put that line in a file in your directory called .profile
For csh, it is a similar story:
set path = (/bin /usr/bin $home/bin .) # execution search path
(BTW, anything following the number-sign, is a comment, and ignored).
Just two different ways of doing it.
I hope that helps!
/* Marek Pawlowski, marekp@{generic|pnet91|contact|bkj386|torag|aunix}.uucp */
/* President, Intelligent Twist Software, 250 Harding Blvd, PO BOX 32017 */
/* Richmond Hill, Ontario, L4C 9M7, CANADA. An ideal route is as follows: */
/* { Ph: (416) 884-4501 4-8pm EDT } generic!pnet91!marekp@zoo.toronto.edu */