From: bert hubert <ahu@ds9a.nl>
To: lartc@vger.kernel.org
Subject: [LARTC] #lartc IRC channel
Date: Sun, 07 Jul 2002 21:06:45 +0000 [thread overview]
Message-ID: <marc-lartc-102607604729681@msgid-missing> (raw)
Hi everybody,
Due to the current situation with openprojects.org (operators begging for
monetary support), we've moved to irc.oftc.net, which is a very fine IRC
network which is managed by rightminded people.
If you are new to IRC - a small introduction. To access IRC you need a
client, I highly recommend irssi (http://www.irssi.org) for Unix users and
mirc for those with Win32.
IRC is a very direct medium. It is well suited for chatting. It is however
no substitute for email. We currently see people joining the channel and
attempting to describe complex problems.
While IRC is very good at 'try this? does it work?' kind of conversations,
it is not good for passing around large amounts of information. So, the
drill is as follows:
0) Search the HOWTO if your question is answered there
1) Post your problem to the mailinglist
2) Mention the problem on #lartc and see if people can/want to help
you
3) If a solution was found on IRC, post it to the list so everybody
can see it.
Do not skip 0 and 1 or risk being ridiculed! Simple small questions are
possible exceptions to these rules.
Very small irc tutorial:
* install irssi
* Start irssi
* type /server irc.oftc.net
* wait a while
* type /join #lartc
* say 'hi'
If you are running an accessfilter (firewall) that drops packets instead of
denying connections, the /server bit may take up to a minute!
Regards,
bert
--
http://www.PowerDNS.com Versatile DNS Software & Services
http://www.tk the dot in .tk
http://lartc.org Linux Advanced Routing & Traffic Control HOWTO
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
reply other threads:[~2002-07-07 21:06 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-102607604729681@msgid-missing \
--to=ahu@ds9a.nl \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.