:: www.undernet.org - welcome to the undernet IRC network
Welcome to the undernet IRC 
network
HomeDocumentsNewsletterUserguidePromotionsClassWebmastersTranslatorsUUSNewsNews
:: Welcome to Undernet User Committee - #class

:: #Class
User-com Home

Class
Members
Guidelines
Contact Us

Beginner Class
English
French
Spanish
Romanian
Italian
Macedonian

Advanced Class
English
French
Spanish
German
Romanian

Undernet Home
Coder-Com Home
Routing-Com Home


Beginner Class (English)


<Class> "Good Evening. This instructional script is brought to you by the Undernet User Committee. Please send comments, suggestions or ideas to class@undernet.org. Our Webpage is http://www.user-com.undernet.org/class/ -- We'd like to welcome you all to the Undernet New User School. (INT1)"
<Class> "This class will not cover how to connect to a server or how to work your IRC client. Since you are online now, you should have no problem with it. If you have questions, please refer to your client's help files, or ask your tutor. (INT2)"
<Class> "If after the class you find you need additional help with IRC, feel free to ask in #userguide. To join this channel type /join #userguide. (INT3)"
<Class> "As a continuation of this class, we suggest you attend the advanced class. This will be held next Friday at 7:30PM EDT (Sat 00:30 GMT) (http://tycho.usno.navy.mil/zones.html for your time zone) in #class. (INT4)"


<Class> "Now for the rules of the class. These are to your benefit to prevent disruption. (R1)"
<Class> "The teaching staff is divided up alphabetically. Each tutor will answer questions for the nickname group they are assigned to: For example, A-G_Tutor handles nicks starting with A through G, and so on. If your nickname starts with anything else, don't sweat it. Just use the tutor with -A- included in their nickname group. (R2)"
<Class> "Please ask any questions you have about IRC or this class to your tutor. To do this, type /msg < tutor > < question >. Please do not /notice me, your tutor, or the channel. (R3)"
<Class> "The channel is also set to +m. This means only the teacher and tutors will be able to talk. This is set to prevent disruptions of the class. (R4)"
<Class> "To get rid of interruptions of people joining the channel, we also set it to +i. This means you need to be invited by your tutor to join back if you experience an accidental server disconnection. (R5)"
<Class> "If you leave or disconnect, you can /msg your tutor to request an invite to get back in the channel. Please do not leave or ask for invites if it is not necessary. Make a note of your tutor's nickname now. (R6)"
<Class> "Nickname changes are prohibited during class. While class is in session, you will not be permitted to change your nickname. That's why we put a ban on *!*@*, to turn off nick change ability. (R7)"
<Class> "I'd ask that you please do not message me. I have the job of keeping the lesson flowing. Ask all questions to your tutor. (R8)"
<Class> "If you plan to stay for the class, you may wish to log the session - please turn on your logging now ( /log on ). If you need help with this, please /msg your tutor. (R9)"
<Class> "To get rid of disruptions of people leaving or quitting, you may wish to put these messages in your status window. In mIRC, go to Options (press Alt + O), IRC section, Events - and uncheck Joins/Parts in channel, and Quits in channel. (R10)"
<Class> "The numbers and letters you see at the end of these lines are reference marks. They help me and the tutors to find where they are during the class. You do not need to pay attention to these. (R11)"


<Class> "SESSION A - INTRODUCTION TO CLASS: A short session on the class and basic vocabulary. (A1)"
<Class> "This class was set up for beginner IRC users to come and learn about IRC and the Undernet. We offer this course every other week so the users can better understand what IRC has to offer. Check the topic in this channel for class times. (A2)"
<Class> "Here are some important basic definitions to know when you are on IRC: (A3)"
<Class> "User - This is a person who is using IRC. You are a user right now. (A4)"
<Class> "Channel - A channel is a virtual place on IRC where people can meet and talk with each other. A channel is simply a virtual chat room. (A5)"
<Class> "Client - The software program you use to connect to an IRC server. Some popular clients are mIRC, Ircle, pIRCh, and ircII. (A6)"
<Class> "Server - The machine you are connected to in order to join chat channels. We'll explain more about servers later on. (A7)"
<Class> "Network - Servers are linked together to create a network. Some networks include Undernet, which you are on now, EFNet, and DALnet. (A8)"
<Class> "Think of networks, servers, and channels as television. Television itself is IRC. Networks on TV are networks on IRC. Each TV network has different channels. Think of these channels as IRC servers, they all have the same information, they are just in different areas of the world. And the TV programs are IRC channels, each diverse with information and fun. (A9)"
<Class> "We'll now pause briefly in case you have any questions that you need to ask your tutor. We will do this during and after every session to allow you to ask questions. Remember, /MSG the tutor with your nickname group. (AP)"


<Class> "SESSION B - WELCOME TO IRC: Internet Relay Chatting information. (B1)"
<Class> "IRC was created in 1988 by Jarkko Oikarinen. It started in Finland and is now used in over 70 countries around the world. (B2)"
<Class> "It has grown as a popular and exciting place for people to meet from around the world. It was widely used during the Gulf War, Oklahoma City Bombing, the O.J. Simpson trial and Princess Diana's death for news updates and reaction. (B3)"
<Class> "IRC is simple when it comes to how it works. When you type a line of text, that line goes to the server you are using. Then, your server is sending it to the server the receiver is using to connect to IRC and finally from there the line arrives the final destination - the user or the channel you sent the line to. (B4)"
<Class> "Of course this always can't happen quickly, especially with the growing population of the Undernet. Sometimes there is lag (time between when you type the message and other users see it). (B5)"
<Class> "Lag is caused because servers are either too full, not synched, or a netsplit is ready to occur. We will discuss a netsplit later in the class. (B6)"
<Class> "To get on the Undernet to chat, you need to connect to a server. The server holds information about channels and users in them. It also routes your messages to other servers which it is connected to, forming a network as explained earlier. (B7)"
<Class> "Selecting a server geographically close to you can be beneficial and recommended, but it is not generally required. If you get a message that you cannot connect to a specific server, simply try another one. Most Undernet servers follow the same format: city.state.country.undernet.org or city.country.eu.undernet.org. (B8)"
<Class> "Many large cities have servers. Need a list of servers? Check out http://www.undernet.org/servers.php . (B9)"
<Class> "You need to set up your client so that it works best for you. This way you can feel more comfortable while on IRC. (B10)"
<Class> "Most clients ask for a real name. Don't bother entering your real name here, but if you want to, go ahead. Most people stick something cute in there. Entering your real e-mail address is not necessary either. (B11)"
<Class> "You need to select a nickname. A nickname is the name people will recognize as you on IRC. Try not to pick one which is too general,because others might use that, and then your friends will get confused. Your nickname is limited to nine characters on the Undernet. (B12)"
<Class> "When you connect to a server, you may experience server errors. Don't worry, you didn't mess the server up. Try connecting to another server, or try connecting later. (B13)"
<Class> "Error messages will be discussed later in Session F. (B14)"
<Class> "As an IRC user, you need to get used to a netsplit. A netsplit is when the network splits into two networks when a server link is closed. This can happen because of bad routing or server popularity. (B15)"
<Class> "Sometimes during a netsplit, the two sides don't receive the correct information, resulting in a desynch. You will notice this when, forexample, a server deops a user whom a channel operator has already opped. This occurs because the server on the other side of the netsplit doesn't know that the op exists, so it will automatically deop the user that was previously opped. (B16)"
<Class> "We'll pause briefly in case you have any questions that you would like to ask your tutor. (BP)"


<Class> "SESSION C - IRC COMMANDS AND EXPLANATIONS: Since you know basically what IRC is, we can start to understand how to use it. (C1)"
<Class> "Now it's time to learn the basic commands of IRC. To type a command remember to put the / before the actual command. (C2)"
<Class> "/NICK < nick > - This command changes your nickname to a new one. Do not do this while in this class. You can only change your nick about two times in a 30 second period. Remember, a nickname is limited to nine characters. (C3)"
<Class> "/WHOIS < nickname > - This allows you to find basic information on other users. If I wanted information on HomerJ for example, I would type /WHOIS HomerJ. This will show me what channels he's on and user@host information to ensure this is the right person. (C4)"
<Class> "/AWAY < reason > - This allows you to set your client to be away. This usually helps other users know you are away instead of thinking you are there and trying to chat with you. This usually is only used if you are away for about five minutes. Be sure to make a good away message, dull ones are never any fun ;) (C5)"
<Class> "The /list command can give you information about channels including name, number of users, and topic. The command works with a wildcard (*) as well. /list #channel finds one channel. You can add a * before and/or after the channel name to expand the search: /list #channel* or /list #*channel*. (C6a)"
<Class> "You can also search for channels with a certain number of users. For mIRC, use /raw list >4 (to list channels with more than four users on it), pIRCh uses /verbose list >4, and ircII uses /quote list >4. (C6b)"
<Class> "Besides chatting in a channel, you can also privately chat with other users. You probably have seen this if you have asked a question to your tutor. Here are some commands on user communication: (C7)"
<Class> "/QUERY < nickname > - This opens a private chat window between you and the nickname you specify. Only you two people can see what is typed. This command may not be available to all clients. (C8)"
<Class> "/NOTICE < nickname > < message > - This sends a one line message to a user without opening another window. This is effective if you need to get a message to a user immediately. (C9)"
<Class> "/NOTICE @#< channel > < message > - This command allows channel operators to send notices to all of the other operators in the channel. This is similar to the /onotice command in mIRC, but the server handles sending the message instead of mIRC. This will also help prevent the -Target change too fast- error message, discussed later. (C10)"
<Class> "/IGNORE < nickname > - This ignores a user. For example, if you don't care for a user's attitude, type /ignore < nickname > and you will not see any more messages they type. *Note: For this to take effect in QUERY, close any active query windows with the user concerned. (C11)"
<Class> "/DCC CHAT < nickname > - Very effective if you are lagged. This enables a private chat, just like /QUERY, but it establishes a direct connect between each user, bypassing the server. (C12)"
<Class> "/DCC SEND, GET < nickname > < file > - Directly sends a user a file which you specify. Enter the nickname of the person you are sending it to, and the file you want to send (For example, /dcc send HomerJ c:/powerplant/reactor.txt to give out the boss's important info). (C13)"
<Class> "Do not have your DCC GET set to autoreceive, there are too many trojans being sent by users and you run the risk of being infected if you receive and run them. (C13a)"
<Class> "Remember, with all the commands listed above, do not include the < > marks. This is just an aid to indicate to you of the parameters you need to enter. (C14)"
<Class> "We'll pause briefly in case you have any questions that you would like to ask your tutor. (CP)"


<Class> "SESSION D - CHANNEL INTRODUCTION: A channel is a virtual place where you meet other users. Think of it as a room. (D1)"
<Class> "All IRC channels start with # or &. # is most commonly used because that channel is available globally to all users on the network. For example, #newbies is a channel. Channel names have a maximum length of 89 characters. (D2)"
<Class> "A channel that begins with & is only available to users on the local IRC server. If you open a channel like &Mychannel people on other irc servers will not be able to chat there with you. This kind of channel is used rarely. (D3)"
<Class> "Many commands are available to use when you're on a channel. These commands help you join a channel, leave a channel, invite others to a channel, and many other commands. (D4)"
<Class> "/JOIN < channel > - This command obviously allows you to join the specified channel. (For example, if I wanted to join #BillIsABigCreep, I would type /JOIN #BillIsABigCreep). (D5)"
<Class> "/PART < channel > - This allows you to leave the channel. (If I wanted to leave #UndernetisCool, I would type /PART #UndernetisCool). (D6)"
<Class> "/INVITE < nickname > < channel > - This invites a user to a channel you are in. If you wanted to invite Marge to join #TheSimpsons, you could type: /INVITE Marge #TheSimpsons. If the channel is set to invite-only (explained later in class), people cannot join the channel unless they be invited by an operator. Only a channel operator can invite people into a channel. (D7)"
<Class> "Most channels have a chanop. They are there to participate in the channel and to monitor it using special commands which are available. (D8)"
<Class> "All users in the user list with a @ in front of their nickname are chanops in that channel. If you join a new channel, e.g. #newchannel, and no one is in there, you just create it and you will automatically become a chanop. (D9)"
<Class> "If you are a chanop in a channel, here is a example listing of some commands you can perform: (D10)"
<Class> "/KICK < channel > < nickname > < reason > - This kicks a user out of a channel. They can rejoin after this, but it is used frequently for troublemakers. (D11)"
<Class> "/TOPIC < channel > < topic > - This changes the channel topic. Try it in a channel you create yourself. It makes this topic appear when a user joins a channel, and on top of the channel window in most clients. (D12)"
<Class> "There are more commands, including the ban command, which will be discussed later in this class. (D13)"
<Class> "We'll pause briefly in case you have any questions that you would like to ask your tutor. (DP)"


<Class> "SESSION E - NEW CHANNELS: To create your own channel, simply think of a channel, and join it. If it is already present, then you cannot create this channel until the people in it leave. (E1)"
<Class> "You can register a channel if you want on the Undernet. Go to the Channel Service web site at http://cservice.undernet.org to register a channel. Before you do this, make sure an Undernet channel service bot is not in the channel. Channel service bots are robots with the nickname X. Channel Registration is now ready. (E2)"
<Class> "You can register a username (not nickname) on Undernet for X bot access. Go to the Channel Service web site at http://cservice.undernet.org and click on the web interface link to register a username. (E3)"
<Class> "If you need help or have questions about registration of a channel, join #cservice. They have a lot of knowledgeable people in there to help. (E4)"
<Class> "If you want to see what a channel manager (the user who registered the channel) does, try attending an #opschool. This is similar to this school, except it teaches about X. Visit their website at http://cservice.undernet.org/main/opschool/index.html or check the topic in #opschool to see the class schedule. (E5)"
<Class> "Your behavior on channels is always important on the Undernet, and mostly anywhere else you go. Be sure to follow directions, if any, set by the channel ops. Be sure to look at the topic of the channel for more info. (E6)"
<Class> "Try not to say hello and goodbye to every user. If you want to, send them a private message. It is rude to interrupt conversations by constantly saying hello, even if you are trying to be friendly. While different channels have different rules, it is generally good manners not to send a /query or dcc chat to another user without first asking in channel. (E7)"
<Class> "If you become advanced in IRC and learn how to program a bot so your client performs certain instructions on command, never use autogreets. Autogreets are when a user joins a channel and another user'scomputer automatically greets them. They are not only obvious, but rude. (E8)"
<Class> "Remember, users will not see you, and they judge their opinions about you on what you type. Always think about what you are typing before you say it. Don't flood a channel (continuously entering many lines of messages to a channel). This will almost certainly get you kicked and banned. (E9)"
<Class> "Never harass other users. You might think it is funny, but others may take it the wrong way. It is just another way to be thought of as rude and annoying. (E10)"
<Class> "Try not to use other people's nicknames. This will result in people thinking you are one person while you really are another. Think of a creative nickname that no one will have. Don't use a nickname of -John- for instance. Anyway, a registered username will always identify you whatever nickname you are using. (E11)"
<Class> "Overall, just try to be nice to people. IRC is a privilege, so try to take advantage of it in an entertaining, educational way. Don't abuse it. Remember, ChanOps can kick and ban anyone they want for any reason or no reason. (E12)"
<Class> "We'll pause briefly in case you have any questions that you would like to ask your tutor. (EP)"


<Class> "SESSION F - PROBLEMS: There are things that can go wrong on IRC, and there are also things that can be avoided. (F1)"
<Class> "If there are no ops on a channel, that channel cannot do anything about annoying or flooding people who enter it. You can report this to an IRC operator if necessary. To find an oper with mIRC, type /who 0 o. Other clients use different commands for this, so refer to the program's help files. (F2)"
<Class> "Sometimes other users may use clones, which are multiple connections from the same IP. If at all possible, only use one connection when you are on the Undernet. (F3)"
<Class> "Some channel ops like to kick and ban users for no reason. Since they are in charge of the channel, there is nothing you can do if you are kicked and banned. Just move on and join another channel. (F4)"
<Class> "The Undernet is a community, while you may enter and hold an unregistered channel, getting along with others that want to share it is encouraged. Flooding or attacking other users to gain ops is considered a takeover and action can be taken. (F5)"
<Class> "If you are in doubt, join #Userguide and ask The people in there can always help you on almost any question you have. If they don't have the answer they can probably refer you to another place where you can find it. (F6)"
<Class> "Here are some common error messages users receive when logging onto a server. (F7)"
<Class> "1. -No authorization-, or -Connection refused-. This means your ISP (Internet Services Provider) has no authorization to connect to the server. Simply use another one, preferably a closer server. (F8)
<Class> "2. -Too many connections from your host- or -Your connection class is full -. This means there are more connections from your host (clones) than the server allows or that there are too many people from the same Internet Service Provider already connected to the server. Try to connect to another server, preferably a closer one. (F9)
<Class> "3.- Your host is trying to (re)connect too fast -- throttled -. This means that your irc client retries to connect to the network too fast. Wait for at least 20 seconds before trying to reconnect. (F10)
<Class> "4. -Target change too fast- This message means that you are either sending too many messages to many different people, trying to join too many channels in a short period of time, or using the old /onotice command. Use the /notice @#channel command (discussed earlier in Session C)instead of /onotice. (F11)"
<Class> "5. -Not Enough Parameters- Means you have not set up your client completely. Go back to your setup screen, and fill in the remaining boxes with the correct information. (F12)"
<Class> "We'll pause briefly in case you have any questions that you would like to ask your tutor. (FP)"


<Class> "SESSION G - INTRODUCTION TO BOTS: A bot is short for the word -robot-. It is a script run by a user to automatically do things on command. Usually users use bots to protect channels from takeovers by keeping ops. If your channel is well established and the channel regulars support you as manager, then the best policy is to register your channel with Undernet Channel Service. (G1)"
<Class> "Some servers do not want you to run bots. If you do, you are at a possible risk of being detected and dealt with. Make sure always to read the MOTD (message of the day) of the server before you use it. This always appears when you connect to a server, or type /motd. This contains what is allowed and what is not in that server. (G2)"
<Class> "Ultimately, you don't really need a bot. Some are nice for playing games, but it does take up a lot of bandwidth. If you know how to make a bot, make one which is very simple, without backdoors, and run it on a server that allows it. (G3)"
<Class> "As we have talked about before, the Undernet Channel Service maintain a server exclusively for management of a channel. To get a channel service bot in your channel, you need to register it. Go to http://cservice.undernet.org to find out more about Undernet channel registration. (G4)"
<Class> "When you enter channels like #cservice, you will see a channel service bot (currently X). The server works as a tool for a channel manager (user who registers the channel) to use to customize and protect their channel. (G5)"
<Class> "There are help bots on the Undernet which are provided for help. For example, type - /msg UserGuide UserGuide usage - for general Undernet help. (G6)"
<Class> "We'll pause briefly in case you have any questions that you would like to ask your tutor. (GP)"


<Class> "SESSION H - MODES: Channels take on specific characteristics by their modes. Modes force things to happen and help manage a channel. Only chanops can use these modes (remember, the users with the @ in front of their nicknames). (H1)"
<Class> "If you are a chanop, you can use modes by typing /MODE < channel > < mode > < parameter >. The < channel > is the channel you are a chanop in and want to change the mode, the < mode > is the mode key (which will be listed soon),and the < parameters > are the characteristics for the mode. A + or - sign before the mode key determines whether the mode should be added or removed. (H2)"
<Class> "Here is a list of channel modes for channel ops: (H3)"
<Class> "b < ban mode > - This bans a user. If I wanted to ban MLewinsky from #thebigcreep, I would type /mode #thebigcreep +b . The hostmask is available by typing /whois MLewinsky and adding asterisks where dynamic areas are in the user@host. Most clients have mouse driven menus that can assist you with this. (H4)"
<Class> "i - Channel is set to invite-only. Only users who are invited by a channel op can join the channel. Channel ops in the X bot of level 100+ may also invite themselves to a +i channel. (H5)"
<Class> "l < max > - Channel is limited to < max > number of users. If this number is exceeded, they cannot join the channel. (For example, /mode #example +l 25). (H6)"
<Class> "m - Channel is moderated. Only chanops and users with + in front of their nicknames can talk (i.e. send text to the channel). (H7)"
<Class> "n - No external messages are allowed. When you are not in a channel, you can still send msgs to it, by typing /MSG < channel > < text >. This mode prevents this. (H8)"
<Class> "p - Channel is private. When a /WHOIS is performed from outside on anyone in a private channel, the channel will not be displayed in the /WHOIS result. It won't be shown in a channel listing either. (H9)"
<Class> "s - Channel is secret. This is similar to the mode +p: channel won't be shown in a listing and a /WHOIS performed from outside won't reveal the channel. The difference is that, unlike mode +p, you won't be able to see who is in the channel with /who #channel. (H10)"
<Class> "t - Topic is locked. Only chanops can change the topic, not regular users. (H11)"
<Class> "o < nickname > - Gives that user chanop status. (For example, /MODE #example +o LindaTripp) gives LindaTripp chanops in #Example. (H12)"
<Class> "v < nickname > - Gives that user a voice in a moderated channel. This user can chat when the channel is set to +m and when banned. (H13)"
<Class> "k < key > - This sets a key on the channel. Only users typing /JOIN < channel > < key > can join the channel. It acts as a password. (H14)"
<Class> "r - restricted - This useful channel mode allows only users who have previously logged in to their registered username (i.e. to X) to join thechannel. So, to join a +r channel, log in to X and try. This is not restricted to registered channels only but it's available for all the channels. (H15)
<Class> "To see a list of channel modes currently in effect, refer to the title bar of the channel window, or type /MODE < channel >. (H16)"
<Class> "Users can also set modes for themselves. This is different from channel modes. To use these, type /MODE < nickname > < mode >. Here is a listing: (H17)"
<Class> "i - Makes you invisible. When users do a /WHO #example, your nickname will not show up. If they do a /WHOIS < nickname >, it will show which channels you are in. When you are in the channel, users can still see you. This just prevents people from seeing you when they search for people in a channel. (H18)"
<Class> "w - Wallops. Lets you see messages to all IRC operators (another way opers communicate with each other). (H19)"
<Class> "d - Deaf. This prevents you from seeing any channel dialog. Useful for bots. (H20)"
<Class> "x - Host hiding. This useful usermode will hide your real IP/hostname and, instead, show ident@username.users.undernet.org in a /WHOIS info. To enable this mode, log in to X. If you want to turn it off, you'll need to disconnect from the IRC. (H21)"
<Class> "We'll pause briefly in case you have any questions that you would like to ask your tutor. (HP)"


<Class> "SESSION I - IRC OPS: IRC Ops (IRC operators) are users who maintain a server and keep it running, or a specified part of the network. (I1)"
<Class> "Most operators will not deal with channel affairs, unless it's a particular situation, like a channel takeover. (I2)"
<Class> "If you seriously need an IRC Op, find one and report what you need and they should be able to help you. Please do not ask to kill a user because they are using profanity or something similar. IRC Ops are very busy and need to attend to other activities also. (I3)"
<Class> "Try not to /msg an IRC Op numerous times, as they usually cannot respond to every request. They have to maintain over a server, and that is hard work. (I4)"
<Class> "To find an IRC Op online, type /who 0 o. (First 0 is a zero). H means they are Here, G means they are Gone. This only shows opers who are -i or who are in the same channel with you. This works with some clients, but not all. Refer to the help files of your client for information on this feature. (I5)"
<Class> "Remember the IRC Ops are very busy people, so please be considerate if you absolutely need one. (I6)"
<Class> "We'll pause briefly in case you have any questions that you would like to ask your tutor. (IP)"


<Class> "SESSION J - IDENTD: Another important configuration option is called IDENTD. IDENTD is the daemon (process) which runs the IDENT protocol - a system that helps the IRC server identify the person connecting. (J1)"
<Class> "The IDENT is used on IRC to help tell one user apart from the other. (J2)"
<Class> "Clients which have a working IDENT server installed are identifiable because their user@host information is not prefixed with a ~ (tilde). (J3)"
<Class> "For example: ThisIsMe (ident@host.name.country) <-- IDENT is installed and detected. ThisIsMe2 (~email@host.name.country) <-- Ident Not Detected. (J4)"
<Class> "Note that if the server checks for IDENT on your host and fails, it will use the front part of the 'email address' parameter instead. (J5)"
<Class> "When IDENTD is running you have proof you are on a legitimate address. Most connections from hacked hosts or via stolen proxies are not idented, and for this reason people without ident are often banned from channels, or occassionally from entire servers. (J6)"
<Class> "Channel Ops: If you have problems with flooding or abusive users, banning non-idented clients often eliminates most of the hassle - /mode #yourchannel +b *!~*@* bans non-ident clients. This is another reason guests should try to get their IDENTD working correctly. (J7)"
<Class> "The following are instructions for configuring IDENTD: mIRC: Press ALT+O, then click on the plus (+) sign next to Connect. Click on IDENTD under Connect. The following information must be used : (J8)"
<Class> "1) Enable identd must be checked. (J9)"
<Class> "2) User ID should be the same as the first part of your email address found on the main connect page of mIRC. Example: if, on the main connect page, your email is blah@something.com, your user ID should be blah. (This prevents confusion of your identity if ident should fail). (J10)"
<Class> "3) System MUST say UNIX (yes even though you are using Windows, UNIX is what goes in the system box). (J11)"
<Class> "4) Port MUST be 113 (usually set by default). (J12)"
<Class> "For further help with this please read the mIRC help files or /join #mIRC. (J13)"
<Class> "Linux: In Linux If you are not the Administrator of the box, please contact your system administrator for additional help. If you are running a Linux system and are having trouble enabling identd, the package you are looking for is identd-masquerade. (J14)"
<Class> "We'll pause briefly in case you have any questions that you would like to ask your tutor. (JP)"


<Class> "SESSION K - OTHER REFERENCES: There are many help and assistance channels on the Undernet. There are also many knowledgeable people to help you out with problems you may have. Here are some places on The Undernet you can go for help: (K1)"
<Class> "#userguide - Helpful User Committee channel where members are available to answer questions about the many resources that are available on our network as well as provide help or point users in the right direction for both simple and advanced IRC- and computer-related questions. Please visit our webpage for more information, http://www.user-com.undernet.org/userguide .(K2)"
<Class> "#nastrand - Technical help channel, usually for technical help and channel difficulty. (K3)"
<Class> "#vh - Reputable virus removal help channel (vh stands for virus help). (K4)"
<Class> "#cservice - Undernet Channel Service. Help with the X bot and information on how to use it. (K5)"
<Class> "#beginner - Another new users channel to ask questions. (K6)"
<Class> "#help - Help available for more experienced users, along with newbies. (K7)"
<Class> "#opschool - A CService Class similar to this. Follow the directions in the topic for OpSchool classes. (K8)"
<Class> "The Undernet also provides e-mail addresses where you can get help. Here are a few which you should know. (K9)"
<Class> "cservice@undernet.org - Channel Service mailing list. (K10)"
<Class> "opschool@undernet.org - OpSchool mailing list. (K11)"
<Class> "abuse@undernet.org - Abuse or misuse of powers, e.g. IRC operators, NOT channel affairs. (K12)"
<Class> "help@undernet.org - For more experienced users along with newbie help. (K13)"
<Class> "user-com@undernet.org - User Committee mailing list. (K14)"
<Class> "Like explained before, if absolutely necessary, you can get an IRC Op to assist you. Also, Undernet has a homepage with useful resources at http://www.undernet.org. (K15)"
<Class> "We'll pause briefly in case you have any questions that you would like to ask your tutor. (KP)"


<Class> "SESSION L - CLOSING: #class is held every Friday at 7:30 pm EDT (Sat 00:30GMT) (L1)"
<Class> "It has been a pleasure to teach the class today, and we all hope you learned something new. (L2)"
<Class> "IRC is a fun and exciting way to communicate with others. We hope you enjoy it and will spend more of your time here, with us. We look forward to helping you and providing a great network for your enjoyment and education. (L3)"
<Class> "We'd like to thank the people who made this script possible: Many additions and changes have been made and therefore many people have been involved, I can't mention all the names. But to those that helped THANK YOU very much. (L4)"
<Class> "We'd also like to thank all the tutors that take their time to help you every week. (L5)"
<Class> "Additionally we'd like to thank everyone who helps in all of the help channels for their time and effort in making IRC a better place. (L6)"
<Class> "Additionally, please note that there is an advanced class right here in #class. The advanced class is meant as a continuation of this class. (L7)"
<Class> "Every week the New Users Class and the Advanced Class will be alternating on Friday's. Both classes will be in the same place at the same time. Please check the topic for times and changes. (L8)"
<Class> "Thank you all for attending, and have a great evening. (L9)"

Click here to return to the top

Copyright © 1994 - 2012 - Copyright notice and contacts. Please read our Acceptable use policy There are currently 17345 online