Mirc Linux

[Егор Ульянов]

You are expected to familiarize yourself with our Code of conduct and General guidelines#IRC before joining any of the official channels. For a list of commonly used abbreviations, see Arch terminology.

This section is about #archlinux, the main Arch Linux support IRC channel, and #archlinux-offtopic, the main Arch Linux social channel, both available on the Libera Chat network. See -of-official-irc-channels-to-liberachat/

Group contacts mediate matters between the Libera Chat network staff, Arch Linux staff and Arch Linux users. That includes the management of channels in the #archlinux-* namespace on the Libera Chat network and the assignment of archlinux/* hostmasks. Please note that only Arch Linux staff is eligible for hostmasks.

When requesting help from an IRC help channel (like #archlinux), it is inappropriate to paste logs into the channel and this may even get you kicked. Use a pastebin instead, you can use phriks factoid !paste to see which pastebins are acceptable.Acceptable pastebins usually work without enabling JavaScript. Some require enabling JavaScript for posting from a web browser, which is still acceptable because it does not affect the viewer. They should not display advertising or other disrupting content and should also not require a login. Excellent pastebins usually provide a way to paste output via piping.

When first entering the channel, there is no need to say hello. State the problem you are experiencing and make sure to be verbose and to provide logfiles. It also helps to search for any error messages you are getting first to not waste anybodys time. It is also worth it to search for issues on any of the bugtrackers of the relevant software.The more helpful and verbose you are, the quicker you are going to receive help.

The size of our community led to the creation of multiple IRC channels. To get a list of all channels on irc.libera.chat that contain archlinux in their name, use the command /query alis LIST *archlinux*. For further information on how to search channels, see

FreeNode recently started requiring logging into their IRC network to access the #puppylinux chatting channel. For new users and people that don't want to create a FreeNode account, there is now an alternative IRC network...Libera Chat. It also hosts a #puppylinux channel, but it does not require logging in.

I have confidence in Libera Chat and that they will be online for quite a while. Their administrators had previously left FreeNode after new management was apparently doing shady things. The administrators then created Libera Chat.

Today freenode decided to mass take ownership of every channel with Libera.Chat in their topic and clear all set modes and flags removing all moderators entirely. This move shows how little respect they have for projects and that the network is no longer a safe home for any FOSS project.

I installed a Hybrid-IRC Server on my linux Vserver.If i try to connect to my IRC Server with Xchat i get this: "Closing Link (Install identd)", but if i use a online IRC client like kiwiirc.com or i connect to localhost (on the Vserver) it works. I alerady used other IRC client like mIRC, but i got the same error. I think it`s a problem with the server.

GCC is just a compiler (and a linker). There is no direct connection between GCC and IRC.
To connect to the server and communicate with it, you just need sys/socket.h; I won't go in details, there's a lot of examples and tutorials about server-client linux C/C++ programs.

USER is a command that tells the server your username, host name and real name. Like, when you whois someone, you see [email protected] and his "Real Name". That data the client sends just after establishing the connection.

I guess that's enough to get into IRC. The whole lot of other stuff you can try yourself just by reading about IRC protocol itself, trying things with telnet or nc and then getting into coding a program using the basic sockets.

To be accurate, the term Linux properly only refers to the Operating System kernel developed by Linus Torvalds. Linux distributions are then built on that kernel. Not all distrbutions are built the same way. There are two main families: those that use the RPM package system (Redhat, Fedora, CentOS, Scientific Linux, Suse, etc) and those that use the .Deb package systems (Debian, Ubuntu, Kubuntu, etc).

Those families further differ in how they manage system services. The .Deb family largely follows BSD style init scripts. The RPM family follows AT&T System V init scripts. To control CTP as a service (start, stop, get status) on your Linux distribution you must choose the proper tool from the two options below.

The CTP/linux folder of the CTP installation now includes a new file called ctpService-red.sh. This file is internally documented, but in brief you must confirm that the variable settings in it match your environment settings. The simplest way to to this is the following. From the command line verify that the following will start CTP:

If the above works, then we need only assure that the JAVA_HOME, JAVA_BIN, CLASSPATH and CTP_HOME settings in the script match the output of the "env" command. Once that is confirmed, do the following steps (where CTP_HOME is the true location of the CTP root folder):

I'm an IRC kind of guy. I appreciate the simplicity of pure text chat,emoticons instead of emojis, and the vast array of IRC clients and servers tochoose from, including the option to host your own. All of my interactivecommunication happens over IRC either through native IRC channels (like#linuxjournal on Freenode) or using a local instance of Bitlbee to act as anIRC gateway to other chat protocols. Because my IRC client supportsconnecting to multiple networks at the same time, I've been able to manageall of my personal chat, group chat and work chat from a single window thatI can connect to from any of my computers.

Before I upgraded to IRC, my very first chat experience was in the late 1990son a web-based Java chat applet, and although I hold some nostalgia for web-basedchat because I met my wife on that network, chatting via a web browser justseems like a slow and painful way to send text across the internet. Also,shortly after we met, the maintainers of that network decided to shut down thewhole thing, and since it was a proprietary network with proprietaryservers and clients, when they shut it down, all those chat rooms and groupswere lost.

What's old is new again. Instead of Java, we have JavaScript, and kids thesedays like to treat their web browsers like Emacs, and so every application hasto run as a web app. This leads to the latest trend in chat: Slack. I say thelatest trend, because it wasn't very long ago that Hipchat was hip, and beforethat, even Yammer had a brief day in the sun. In the past, a software projectmight set up a channel on one of the many public or private IRC servers, butnowadays, everyone seems to want to consolidate their projects under Slack'sinfrastructure. This means if you joined a company or a softwareproject that started during the past few years, more likely than not, you'llneed to use Slack.

I'm part of a few Slack networks, and up until recently, I honestly didn'tthink all that much about Slack, because unlike some other proprietary chatnetworks, Slack had the sense to offer IRC and XMPP gateways. This meant thatyou weren't required to use its heavy web app, but instead, you could usewhatever client you preferred yet still connect to Slack networks. Sure, mytext-based IRC client didn't show animated Giphy images or the 20party-parrot gifs in a row, but to me, that was a feature. Unfortunately, Slack couldno longer justify the engineering effort to backport web chat features to IRCand XMPP, so the company announced it was shutting down its IRC and XMPPgateways.

When Slack first announced it was shutting down the IRC gateway, I wasn'tsure what I would do. I knew that I wouldn't use the web app, so I figured ifan alternative didn't come around, I'd just forget about the Slack networks Iwas a part of, just like when that old Java chat shut down. Fortunately, theFLOSS community saved the day, and someone wrote a plugin that uses thelibpurple library (a kind of Rosetta stone plugin framework for chat used byprograms like Pidgin and Bitlbee to allow access to ICQ, MSN, Yahoo andother dead proprietary chat networks). Although using the direct IRC gateway waseasier, setting this up on Bitlbee wasn't so bad. So, in this article, Idescribe how to do exactly that.

I know that many console-based chat fans have switched to Weechat as theirIRC client, and it has a native Slack plugin. That's great, but I've beenusing Irssi for something like 15 years, so I'm not about to switchclients just for Slack's sake. Anyway, with the Bitlbee program, you canconnect to Slack using your preferred IRC client whether that's Irssi, Xchator even MIRC (no judgment).

Since the Slack Bitlbee plugin uses libpurple, the first step is to make sureyou install a Bitlbee package that has libpurple built in. OnDebian-based distributions, this means replacing the basic bitlbee packagewith bitlbee-libpurple if you don't already have it installed. This packageshould set up a local network service listening on the IRCport automatically. I cover how to use Bitlbee in detail in my past article"WhatReally IRCs Me: Instant Messaging", so I recommend you refer to thatarticle for moredetails.

Note that Slack isn't yet on this list. The next step is to build and installthe Slack libpurple plugin on your machine. To do this, make sure you havegeneral build tools installed on your system (for Debian-based systems, thebuild-essential package takes care of this). Then install the libpurple-develor libpurple-dev package, depending on your distro. Finally, pull down thelatest version of the plugin from GitHub and build it:

Once you have the Slack module set up, the next step is to configure it likeany other Bitlbee network. First, create a new Bitlbee account thatcorresponds to your Slack account from the Bitlbee console:

c80f0f1006