aboutsummaryrefslogtreecommitdiff
path: root/handbook/eresources.sgml
blob: aa8260f8617acda9e0c0f39df114e6ea020f22f4 (plain) (blame)
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
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
<!-- $Id: eresources.sgml,v 1.2.4.3 1995-11-07 18:24:44 jfieber Exp $ -->
<!-- The FreeBSD Documentation Project -->

<chapt>
  <heading>Resources on the Internet<label id="eresources"></heading>

  <p>The rapid pace of FreeBSD progress makes print media
    impractical as a means for following the latest
    developments.  Electronic resources are the best, if not the
    only way stay informed of the latest advances.  Also, since
    FreeBSD is a volunteer effort, the user community also serves
    as the technical support department and invariably,
    electronic mail and Usenet news are the most effective way of
    getting technical problems resolved.

    Below, the most important points of contact with the FreeBSD
    user community are outlined.  If you are aware of other
    resources not included, please send them to
    <tt>doc@freebsd.org</tt> so they may be included.

      <sect>
        <heading>Mailing lists<label id="eresources:mail"></heading>

<p>Though many of the FreeBSD development members read USENET, we cannot
always guarantee that we'll get to your questions in a timely fashion
(or at all) if you post them only to one of the comp.unix.bsd.*
groups.  By addressing your questions to the appropriate mailing list
you will reach both us and a concentrated FreeBSD audience, invariably
assuring a better (or at least faster) response.

There are list charters at the bottom of this document.  Please read
the list charter before joining a list.  We must strive to
keep the signal to noise ratio of the lists high, especially in
the technical lists.

Archives are kept for all of the mailing lists and can be searched
using the the <url url="http://www.freebsd.org/"
name="FreeBSD World Wide Web server">.  The keyword searchable archive
offers an excellent way to find answers to frequently asked questions
and should be consulted before posting a question.

<sect1><heading>List summary</heading>

<p><bf>General lists:</bf> The following are general lists that
anyone is free to join:
<verb>
List                     Purpose
----------------------------------------------------------------------
freebsd-announce         Important events / milestones
freebsd-bugs             Bug reports
freebsd-chat             Non technical items related to the community
freebsd-current          Discussions about the use of FreeBSD-current
freebsd-isp              Issues for ISP's using FreeBSD
freebsd-policy           Policy issues and suggestions
freebsd-questions        User questions
</verb>

<bf>Technical lists:</bf> The following are the technical lists. You should
read the charter carefully before joining them, and you should keep
your e-mail within the scope of the guidelines.
<verb>
List                     Purpose
----------------------------------------------------------------------
freebsd-doc              Documentation project
freebsd-fs               Filesystems
freebsd-hackers          General Technical discussions
freebsd-hardware         General discussion of FreeBSD hardware
freebsd-multimedia       Multimedia discussions
freebsd-platforms        Porting to Non-Intel platforms
freebsd-ports            Discussion of "ports"
freebsd-security         Security issues
freebsd-scsi             SCSI subsystem
</verb>

<bf>Limited lists:</bf> The following are limited lists that you will need
approval to join.  Even though access to these lists is controled,
anyone is free to send suggestions and comments to them.  It is a
good idea establish a presence in the technical lists before asking
to join one of these limited lists.
<verb>
List                     Purpose
----------------------------------------------------------------------
freebsd-admin            Administrative issues
freebsd-arch             Architecture and design discussions
freebsd-core             FreeBSD core team
freebsd-install          Installation development
freebsd-user-groups      User group coordination
</verb>

<bf>CVS lists:</bf> The following lists are for people seeing the log messages
for source changes in specific areas:
<verb>
List name       Source area          Area Description (source for)
----------------------------------------------------------------------
cvs-CVSROOT     /usr/src/[A-Z]*      Top level /usr/src file changes
cvs-all         /usr/src             All changes to the tree (superset)
cvs-bin         /usr/src/bin         System binaries
cvs-etc         /usr/src/etc         System files
cvs-games       /usr/src/games       Games
cvs-gnu         /usr/src/gnu         GPL'd utilities
cvs-include     /usr/src/include     Include files
cvs-kerberosIV  /usr/src/kerberosIV  Kerberos encryption code
cvs-lib         /usr/src/lib         System libraries
cvs-libexec     /usr/src/libexec     System binaries
cvs-ports       /usr/ports           Ported software
cvs-sbin        /usr/src/sbin        System binaries
cvs-share       /usr/src/share       System shared files
cvs-sys         /usr/src/sys         Kernel
cvs-usrbin      /usr/src/usr.bin     Use binaries
cvs-usrsbin     /usr/src/usr.sbin    System binaries
</verb>

<sect1><heading>How to subscribe</heading>

<p>All mailing lists live on <tt>FreeBSD.ORG</tt>, so to post to a
list you simply mail to <em>listname</em><tt>@FreeBSD.ORG</tt>.  It
will then be redistributed to mailing list members throughout the
world.

To subscribe to a list, send mail to:
<tscreen><verb>
majordomo@FreeBSD.ORG
</verb></tscreen>
And include the keyword
<tscreen><verb>
subscribe <listname> [<optional address>]
</verb></tscreen>
In the body of your message.  For example, to subscribe yourself to
freebsd-announce, you'd do:
<tscreen><verb>
% mail majordomo@FreeBSD.ORG
subscribe freebsd-announce
^D
</verb></tscreen>
If you want to subscribe yourself under a different name, or submit a
subscription request for a local mailing list (note: this is more efficient
if you have several interested parties at one site, and highly appreciated by
us!), you would do something like:
<tscreen><verb>
% mail majordomo@FreeBSD.ORG
subscribe freebsd-announce local-announce@somesite.com
^D
</verb></tscreen>
Finally, it is also possible to unsubscribe yourself from a list, get a
list of other list members or see the list of mailing lists again by
sending other types of control messages to majordomo.  For a complete
list of available commands, do this:
<tscreen><verb>
% mail majordomo@FreeBSD.ORG
help
^D
</verb></tscreen>
Finally, we again request that you keep the technical mailing lists on
a technical track.  If you're only interested in the "high points",
then it's suggested that you join freebsd-announce, which will contain
only infrequent traffic.

<sect1><heading>List charters</heading>

<p>
<descrip>
<tag/FREEBSD-ADMIN/ <em>Administrative issues</em><newline>
<!-- XXX -->

<tag/FREEBSD-ANNOUNCE/ <em>Important events / milestones</em><newline>
This is the mailing list for people interested only in occasional
announcements of significant freebsd events.  This includes
announcements about snapshots and other releases.  It contains
announcements of new FreeBSD capabilities.  It may contain calls
for volunteers etc.  This is a low volume list.

<tag/FREEBSD-ARCH/ <em>Architecture and design discussions</em><newline>
This is the mailing list for people discussing FreeBSD architectural
issues.  It is a closed list, and not for general subscription.

<tag/FREEBSD-BUGS/ <em>Bug reports</em><newline>
This is the mailing list for reporting bugs in FreeBSD
Whenever possible, bugs should be
submitted using "send-pr".

<tag/FREEBSD-CHAT/ <em>Non technical items related to the
                              community</em><newline>
This list contains the overflow from the other lists about
non-technical, social information.  It includes discussion about
whether Jordan looks like a tune ferret or not, whether or not to
type in capitals, who is drinking too much coffee, where the best
beer is brewed, who is brewing beer in their basement, and so on.
Occasional announcements of important events (such as upcoming
parties, weddings, births, new jobs, etc) can be made to the
technical lists, but the follow ups should be directed to this
-chat list.

<tag/FREEBSD-CORE/ <em>FreeBSD core team</em><newline>
This is an internal mailing list for use by the core members.

<tag/FREEBSD-CURRENT/ <em>Discussions about the use of
FreeBSD-current</em><newline> This is the mailing list for users
of freebsd-current.  It includes warnings about new features
coming out in -current that will affect the users, and
instructions on steps that must be taken to remain -current.
Anyone running "current" must subscribe to this list.

<tag/FREEBSD-CURRENT-DIGEST/ <em>Discussions about the use of
FreeBSD-current</em><newline> This is the digest version of the
freebsd-current mailing list.  The digest consists of all
messages sent to freebsd-current bundled together and mailed out
as a single message.  The average digest size is about 40kB.

<tag/FREEBSD-DOC/ <em>Documentation project</em><newline> 
This mailing list belongs to the FreeBSD Doc Project and is for
the discussion of documentation related issues and projects.

<tag/FREEBSD-FS/ <em>Filesystems</em><newline> 
Discussions concerning FreeBSD filesystems.

<tag/FREEBSD-HACKERS/ <em>Technical discussions</em><newline> 
This is a forum for technical discussions related to FreeBSD.  This
is the primary technical mailing list.  It
is for individuals actively working on FreeBSD, to bring up problems
or discuss alternative solutions.  Individuals interested in
following the technical discussion are also welcome.

<tag/FREEBSD-HACKERS-DIGEST/ <em>Technical
discussions</em><newline> This is the digest version of the
freebsd-hackers mailing list.  The digest consists of all
messages sent to freebsd-hackers bundled together and mailed out
as a single message.  The average digest size is about 40kB.

<tag/FREEBSD-HARDWARE/ <em>General discussion of FreeBSD
hardware</em><newline> General discussion about the types of
hardware that FreeBSD runs on, various problems and suggestions
concerning what to buy or avoid.

<tag/FREEBSD-INSTALL/ <em>Installation discussion</em><newline> 
This mailing list is for discussing FreeBSD installation
development for the future releases.

<tag/FREEBSD-ISP/ <em>Issues for Internet Service Providers</em><newline>
This mailing list is for discussing topics relevant to Internet
Serivce Providers (ISPs) using FreeBSD.

<tag/FREEBSD-MULTIMEDIA/ <em>Multimedia discussions</em><newline>
This is a forum about multimedia applications using FreeBSD.
Discussion center around multimedia applications, their installation, their
development and their support within FreeBSD

<tag/FREEBSD-PLATFORMS/ <em>Porting to Non-Intel
platforms</em><newline> Cross-platform freebsd issues, general
discussion and proposals for non-Intel FreeBSD ports.

<tag/FREEBSD-POLICY/ <em>Policy issues and
suggestions</em><newline> This is a forum for policy discussions
related to FreeBSD.  This includes where FreeBSD is going, how to
set up a consortium, whether or not and how to make FreeBSD pay
for itself, how to attract more users, and so on.  When a topic
relates directly to FreeBSD but has little or no technical
content then it should be sent to this list.

<tag/FREEBSD-PORTS/ <em>Discussion of "ports"</em><newline> 
Discussions concerning FreeBSD's "ports collection" (/usr/ports), proposed
ports, modifications to ports collection infrastructure and general
coordination efforts.

<tag/FREEBSD-QUESTIONS/ <em>User questions</em><newline> 
This is the mailing list for questions about FreeBSD.  You should not
send "how to" questions to the technical lists unless you consider the
question to be pretty technical.

<tag/FREEBSD-QUESTIONS-DIGEST/ <em>User questions</em><newline>
This is the digest version of the freebsd-questions mailing list.
The digest consists of all messages sent to freebsd-questions
bundled together and mailed out as a single message.  The average
digest size is about 40kB.

<tag/FREEBSD-SCSI/ <em>SCSI subsystem</em><newline> 
This is the mailing list for people working on the scsi subsystem
for FreeBSD.

<tag/FREEBSD-SECURITY/ <em>Security issues</em><newline> 
FreeBSD computer security issues (DES, Kerberos, known security holes and
fixes, etc).

<tag/FREEBSD-USER-GROUPS/ <em>User Group Coordination List</em><newline>
This is the mailing list for the coordinators from each of the 
local area Users Groups to discuss matters with each other and a 
designated individual from the Core Team.  This mail list should
be limited to meeting synopsis and coordination of projects that span
User Groups.

</descrip>

      <sect>
        <heading>Usenet newsgroups<label id="eresources:news"></heading>

        <p>In addition to two FreeBSD specific newsgroups, there
          are many others in which FreeBSD is discussed or are
          otherwise relevant to FreeBSD users. <url
          url="http://minnie.cs.adfa.oz.au/BSD-info/bsdnews&lowbar;search.html"
          name="Keyword searchable archives"> are available for
          some of these newsgroups from courtesy of Warren Toomey
          <tt>&lt;wkt@cs.adfa.oz.au&gt;</tt>.

        <sect1>
          <heading>BSD specific newsgroups</heading>

          <p><itemize>
              <item>comp.unix.bsd.freebsd.announce
              <item>comp.unix.bsd.freebsd.misc
            </itemize>

        <sect1>
          <heading>Other Unix newsgroups of interest</heading>

          <p><itemize>
              <item>comp.unix 
              <item>comp.unix.questions 
              <item>comp.unix.admin 
              <item>comp.unix.programmer 
              <item>comp.unix.shell 
              <item>comp.unix.user-friendly 
              <item>comp.security.unix 
              <item>comp.sources.unix 
              <item>comp.unix.advocacy 
              <item>comp.unix.misc 
              <item>comp.os.386bsd.announce
              <item>comp.os.386bsd.apps
              <item>comp.os.386bsd.bugs 
              <item>comp.os.386bsd.development 
              <item>comp.os.386bsd.misc 
              <item>comp.os.386bsd.questions 
              <item>comp.bugs.4bsd 
              <item>comp.bugs.4bsd.ucb-fixes 
              <item>comp.unix.bsd 
            </itemize>

        <sect1>
          <heading>X-Window system</heading>

          <p><itemize>
              <item>comp.windows.x.i386unix 
              <item>comp.windows.x 
              <item>comp.windows.x.apps 
              <item>comp.windows.x.announce 
              <item>comp.windows.x.intrinsics 
              <item>comp.windows.x.motif 
              <item>comp.windows.x.pex 
              <item>comp.emulators.ms-windows.wine 
            </itemize>

      <sect>
        <heading>World Wide Web servers<label id="eresources:web"></heading>

        <p><itemize> 
            <item><url url="http://www.freebsd.org/"></item>
          </itemize>
    </sect>