1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
|
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en" lang="en">
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8" />
<meta http-equiv="expires" content="0" />
<meta name="language" content="en-us" />
<meta name="keywords" content="slackware freenode irc" />
<meta name="abstract" content="##slackware on freenode" />
<meta name="author" content="Robby Workman" />
<meta name="contact" content="rworkman AT slackware.com" />
<meta name="generator" content="vi" />
<link rel="stylesheet" type="text/css" href="css/swfn.css" />
<title>##slackware info</title>
</head>
<body>
<h2 align="center">##slackware (freenode) informational website</h2>
<div class="body">
<p>Welcome to the offical information page for Freenode's <tt>##slackware</tt>.
This page contains a bit of (hopefully) helpful information along
with the channel rules/guidelines.
</p>
</div>
<h3 align="center">General Channel Information</h3>
<div class="body">
<ul>
<li>Need a channel operator/moderator? Type <tt>!ops</tt> in your IRC
client. Note that there's no guarantee that an op will currently
be available; all of them are volunteers.
<br /> <br />
</li>
<li>You must be registered and authenticated with <tt>NickServ</tt>
to talk in <tt>##slackware</tt>.
<br /> <br />
</li>
<li>Get Slackware here: <a href="http://slackware.com/getslack/">
http://slackware.com/getslack/</a>
<br /> <br />
</li>
<li>Keep up with security and bugfix patches for your Slackware
version: <a href="https://mirrors.slackware.com/feeds/">
Slackware RSS Feeds</a>
<br /> <br />
</li>
<li>If you're a new Slackware user, you should have a look at the
<a href="http://docs.slackware.com/slackware:beginners_guide">
Slackware Beginner's Guide</a>.
<br />
</li>
</ul>
</div>
<h3 align="center">##slackware channel rules/guidelines</h3>
<div class="body">
<ul>
<li>Generally speaking, treat other users in the manner you'd like
to be treated. No "flames" or trolling or nonsense behavior is
welcome.
<br /> <br />
<ul>
<li>No, "flames" and "trolling" and "nonsense behavior"
will not be quantified or formally defined.
<br />
</li>
</ul>
<br />
</li>
<li>Don't post information that is deliberately detrimental to someone,
and especially not in a sneaky fashion (i.e. don't try to obfuscate
it).
<br /> <br />
</li>
<li>Don't flood the channel. Use <tt>#overflow</tt> or some such. If you need to
show a configuration file or long error message, make use of public
paste servers such as:
<br /> <br />
<ul>
<li><a href="http://pastebin.com">http://pastebin.com<br /></a></li>
<li><a href="http://pastebin.ca">http://pastebin.ca<br /></a></li>
<li><a href="http://dpaste.net">http://dpaste.net</a><br /></li>
</ul>
<br />
</li>
<li><tt>##slackware</tt> exists as a Slackware discussion channel and as a help
resource for users. Newcomers and "Old Hats" alike will be more
likely to receive quality assistance if they heed the following
suggestions:
<br /> <br />
<ul>
<li>When asking a question, be prepared to show evidence that
you've researched it on your own. We like to help, but we
don't want to do it for you.
<br /> <br />
</li>
<li>If you're asked for additional information, please provide
it. If you're unsure as to why some one wants to see a
config file or a routing statement or anything similar,
just ask them. In this way, you and others might learn
something about how the different parts of your Slackware
Linux system interact in addition to solving your problem.
<br /> <br />
</li>
<li>Be sure to specify what version of Slackware you're running
along with any local customizations you've done. It's also
useful to know if the problem is new, i.e. did this work
before? If so, what's changed since then?
<br /> <br />
<ul>
<li>Slackware -current is <strong>NOT</strong> the
same thing as the latest stable release, e.g.
14.2. Along the same lines, there is no such
thing as "Slackware 14.2 -current" or "Slackware
## -current"; either you're running a stable
release plus patches or you're running -current,
unless of course you're running some FrankenSlack,
in which case you're on your own.
<br /> <br />
</li>
<li><tt>slackpkg</tt> and <tt>slackpkg+</tt> are
<strong>NOT</strong> the same thing. Make sure
you mention which one you're using if you're
having problems with "slackpkg" and you're
actually using <tt>slackpkg+</tt>.
<br /> <br />
</li>
</ul>
</li>
</ul>
</li>
<li><tt>##slackware</tt> exists for Slackers to share their knowledge about
Slackware Linux and topics related to Slackware (e.g. system
administration and security concerns, networking Slackware with
other operating systems, etcetera). With that said, we do not mind
off-topic (OT) discussions or questions, but we ask that you
refrain from such discussions if someone wishes to discuss
something that *is* on-topic. Think of the channel in the same way
that you would think of a radio channel. When everyone talks at
once, the result is a jumble of confusion. By "vacating" the
channel of off-topic discussion when some one has an on-topic
discussion, we all benefit.
<br /> <br />
</li>
<li>In recent years, it has become popular to "break" a few of the old
IRC netiquette conventions. Generally speaking, we can't stop all
of this, but repeat offenders will be dealt with. Specifically, as
simple courtesies to everyone, we request that you not do the
following things:
<br /> <br />
<ul>
<li>Don't private message (<tt>/msg</tt>) people without first asking
and obtaining permission from them
<br /> <br />
</li>
<li>Don't use IRC stat scripts. Nobody wants to see your nick
change when you walk away from the keyboard, and nobody
wants to see your current music selection announced.
However, some channel regulars IRC from work and suffix
"-work" or some such to their nickname when doing so.
<br /> <br />
</li>
<li>Name calling and particularly vulgar language is frowned
upon. With that said, we are not nannies and aren't going
to wash your mouth out with soap for petty offenses.
Racist, sexist, and similar language will not be tolerated
under any circumstances. Hackers know that someone's skin
color, gender, and/or sexual orientation has nothing to do
with ability to contribute to the group. Along similar
lines, your latest "bedroom conquests" aren't at all related
to Slackware and won't be tolerated (unless some how they
<strong>are</strong> related to Slackware, in which case we'd like to hear
about them. ;^)
<br /> <br />
</li>
<li>
Repeated/persistent personal attacks are not tolerated.
<br /> <br />
</li>
<li>If you have been banned or de-voiced from a channel, don't
try to avoid the punishment by changing nicks or similar
methods. We will ban your entire netblock if need be. If
you feel that you have been unfairly blocked, speak to one
of the channel ops politely. If you are indeed innocent or
have "learned your lesson", we will likely be happy to
remove the block.
<br /> <br />
</li>
<li>If you have questions about how to do something in some
other distribution, you should check in that distribution's
support forums and/or channels: <tt>##slackware</tt> is for
Slackware support.
<br /> <br />
</li>
<li>Third party package management tools, such as <tt>slapt-get</tt>
and <tt>swaret</tt>, are not supported in <tt>##slackware</tt>.
This does not necessarily mean that discussion is off-limits,
nor does it necessarily mean that you will not receive help
if you encounter problems from using them, but the best place
for support with those tools is in their respective channels
and/or support forums. The same principle applies to the
third-party gnome builds for Slackware.
<br />
Third party packages vary widely in quality; some repos
are good and some are not so good. That being the case,
the best place to get support for third party packages is
from the person(s) who packaged them.
<br />
The following links should not be construed as endorsements
or recommendations from <tt>##slackware</tt>, but they might be
better sources of help with the respective projects:
<br /> <br />
<ul>
<li><a href="https://slackbuilds.org">SlackBuilds.org</a> or <tt>#slackbuilds</tt> on freenode<br /></li>
<li><a href="http://sbopkg.org">sbopkg</a> or <tt>#sbopkg</tt> on freenode</li>
</ul>
</li>
</ul>
<br />
</li>
<li>Most importantly, have fun and Happy Slacking!
</li>
</ul>
</div>
<br />
<div align="center">
<p>
<a href="https://validator.w3.org/check?uri=referer">
<img src="https://www.w3.org/Icons/valid-xhtml10"
alt="Valid XHTML 1.0 Transitional"
height="31" width="88" /></a>
<a href="https://jigsaw.w3.org/css-validator/check/referer">
<img style="border:0;width:88px;height:31px;"
src="https://jigsaw.w3.org/css-validator/images/vcss"
alt="Valid CSS!" /> </a>
</p>
</div>
<br />
</body>
</html>
|
