source: introduction/welcome/maillists.xml@ 71e06e23

10.0 10.1 11.0 6.0 6.1 6.2 6.2.0 6.2.0-rc1 6.2.0-rc2 6.3 6.3-rc1 6.3-rc2 6.3-rc3 7.10 7.4 7.5 7.6 7.6-blfs 7.6-systemd 7.7 7.8 7.9 8.0 8.1 8.2 8.3 8.4 9.0 9.1 basic bdubbs/svn elogind gnome kde5-13430 kde5-14269 kde5-14686 ken/refactor-virt krejzi/svn lazarus nosym perl-modules qt5new systemd-11177 systemd-13485 trunk v5_1 v5_1-pre1 xry111/git-date xry111/git-date-for-trunk xry111/git-date-test
Last change on this file since 71e06e23 was 71e06e23, checked in by Larry Lawrence <larry@…>, 17 years ago

fix chunk xsl error in Preface and Introduction

git-svn-id: svn://svn.linuxfromscratch.org/BLFS/trunk/BOOK@2104 af4574ff-66df-0310-9fd7-8a98e5e911e0

  • Property mode set to 100644
File size: 7.9 KB
Line 
1<sect1 id="intro-welcome-maillists" xreflabel="Mailing lists">
2<?dbhtml filename="maillists.html"?>
3<title>Mailing lists</title>
4
5<para>The linuxfromscratch.org server is hosting a number of mailing
6lists that are used for the development of the <acronym>BLFS</acronym>.
7These lists include, among others, the main development and support
8lists.</para>
9
10<!-- <itemizedlist>
11
12<listitem><para>blfs-support</para></listitem>
13
14<listitem><para>blfs-dev</para></listitem>
15
16<listitem><para>blfs-book</para></listitem>
17
18<listitem><para>lfs-chat</para></listitem>
19
20<listitem><para>lfs-support</para></listitem>
21
22<listitem><para>lfs-dev</para></listitem>
23
24<listitem><para>lfs-announce</para></listitem>
25
26<listitem><para>lfs-book</para></listitem>
27
28<listitem><para>lfs-security</para></listitem>
29
30<listitem><para>alfs-discuss</para></listitem>
31
32</itemizedlist>
33
34<sect2>
35<title>blfs-support</title>
36
37<para>The blfs-support list is for the BLFS Book and beyond.</para>
38
39<para>It includes requests for help following the BLFS Book,
40requests for help with packages not (yet) in
41either the LFS Book or the BLFS Book,
42and other requests and discussion concerning software
43that might be installed on an LFS system.</para>
44
45<para>It does not include topics such as
46the price of beer, what hardware to buy,
47or GNU versus BSD or Microsoft versus Linux flame wars.
48These belong on lfs-chat,
49and since blfs-support is high traffic,
50please follow this rule strictly.</para>
51
52</sect2>
53
54<sect2>
55<title>blfs-dev</title>
56
57<para>The blfs-dev list is for discussion of BLFS Book development.</para>
58
59</sect2>
60
61<sect2>
62<title>blfs-book</title>
63
64<para>The blfs-book list is used for coordinating
65the BLFS Book's maintenance.
66Traffic on it is mostly Bugzilla and CVS commit messages.
67It is important that all development discussion
68of interest to the Book's users take place on blfs-dev, not here.</para>
69
70</sect2>
71
72<sect2>
73<title>lfs-chat</title>
74
75<para>The lfs-chat list is the place for community chatter.
76It's a place where anything goes, nothing is off-topic.
77You can discuss the price of beer or what hardware to buy.
78Even GNU versus BSD and Microsoft versus Linux flame wars
79are okay in lfs-chat.</para>
80
81</sect2>
82
83<sect2>
84<title>lfs-support</title>
85
86<para>The lfs-support list is the place to get help
87following the instructions in the LFS Book itself.</para>
88
89<para>If you're finished with the LFS Book, use blfs-support instead.</para>
90
91</sect2>
92
93<sect2>
94<title>lfs-dev</title>
95
96<para>The lfs-dev list is for discussion of LFS Book development.</para>
97
98</sect2>
99
100<sect2>
101<title>lfs-announce</title>
102
103<para>The lfs-announce list is a moderated list for those who want
104notification of new stable releases
105without the higher traffic of lfs-dev.</para>
106
107</sect2>
108
109<sect2>
110<title>lfs-book</title>
111
112<para>The lfs-book list is used for coordinating the LFS Book's maintenance.
113Traffic on it is mostly Bugzilla and CVS commit messages.
114It is important that all development discussion
115of interest to the Book's users take place on lfs-dev, not here.</para>
116
117</sect2>
118
119<sect2>
120<title>lfs-security</title>
121
122<para>The lfs-security list discusses security issues.
123Vulnerability alerts, configuration questions,
124security related packages, and other things to do with secure systems
125are appropriate on this list.</para>
126
127</sect2>
128
129<sect2>
130<title>alfs-discuss</title>
131
132<para>The alfs-discuss list is for discussion of ALFS development.</para>
133
134</sect2>
135
136<sect2>
137<title>Mail archives</title>
138
139<para>All these lists are archived and can be viewed online at
140<ulink url="http://archive.linuxfromscratch.org/mail-archives"/> or downloaded
141from <ulink url="&ftp-root;/mail-archives"/>.</para>
142
143</sect2>
144
145<sect2>
146<title>How to subscribe?</title>
147
148<para>Any of the above-mentioned mailing lists can be subscribed to by
149sending an email to <ulink
150url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org</ulink>
151and writing <emphasis>subscribe listname</emphasis> as the subject
152header of the message.</para>
153
154<para>Multiple lists at the same time can be subscribed to by using
155one email. This is done by leaving the subject blank and putting all the
156commands in the body of the email. The email will look like:</para>
157
158<blockquote><literallayout>To: listar@linuxfromscratch.org
159Subject:
160
161subscribe lfs-dev
162subscribe blfs-support
163subscribe alfs-discuss</literallayout></blockquote>
164
165<para>After the email is sent, the Listar program will reply with an
166email requesting a confirmation of the subscription request. After
167this confirmation email is sent back, Listar will send an
168email again with the message that the user has been subscribed to the
169list(s) along with an introduction message for that particular
170list.</para>
171
172</sect2>
173
174<sect2>
175<title>How to unsubscribe?</title>
176
177<para>To unsubscribe from a list, send an email
178to <ulink url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org
179</ulink> and write <emphasis>unsubscribe listname</emphasis> as the subject
180header of the message.</para>
181
182<para>Multiple lists can be unsubscribed at the same time
183using one email. This is done by leaving the subject header blank and
184putting all the commands in the body of the email. The email will look
185like: </para>
186
187<blockquote><literallayout>To: listar@linuxfromscratch.org
188Subject:
189
190unsubscribe lfs-dev
191unsubscribe blfs-support
192unsubscribe alfs-discuss</literallayout></blockquote>
193
194<para>After the email is sent, the Listar program will reply with an
195email requesting a confirmation of the unsubscription
196request. After this confirmation email is sent back, Listar will
197send an email again with the message that the user has been unsubscribed
198from the list(s).</para>
199
200</sect2>
201
202<sect2>
203<title>Other list modes</title>
204
205<para>The modes that can be set by a user require sending an email to
206<ulink
207url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org</ulink>.
208The modes themselves are set by writing
209the appropriate commands in the subject header of the message.</para>
210
211<para>As the name implies, the <emphasis>Set command</emphasis> tells
212what
213to write to set a mode. The <emphasis>Unset command</emphasis> tells
214what to write to unset a mode.</para>
215
216<para>The listname in the example subject headers should be replaced
217with the
218listname to which
219the mode is going to be applied to. If more than one mode is to be set
220(to
221the same list or multiple lists) with one email, this can be done by
222leaving the subject header blank and writing all the commands in the
223body of
224the message instead.</para>
225
226</sect2>
227
228<sect2>
229<title>Digests</title>
230
231<literallayout>
232Set command: <emphasis>set listname digest</emphasis>
233Unset command: <emphasis>unset listname digest</emphasis>
234</literallayout>
235
236<para>All lists have the digest mode available which can be set after a
237user
238has subscribed to a list. Being in digest mode will
239cause you to stop receiving individual messages as they are posted to
240the list and instead receive one email a day containing all
241the messages posted to the list during that day.</para>
242
243<para>There is a second digest mode called digest2. When a user is set
244to this
245mode he will receive the daily digests but will also continue to
246receive the individual messages to the lists as they are posted. To
247set this mode, substitute <emphasis>digest</emphasis> for
248<emphasis>digest2</emphasis> in the command.</para>
249
250</sect2>
251
252<sect2>
253<title>Vacation</title>
254
255<literallayout>
256Set command: <emphasis>set listname vacation</emphasis>
257Unset command: <emphasis>unset listname vacation</emphasis>
258</literallayout>
259
260<para>If a user is going to be away for a while or wishes to stop
261receiving
262messages from the lists but doesn't want to unsubscribe, he can change
263to vacation mode. This has the same effect as unsubscribing,
264but without having to go through the unsubscribe process and
265then later through the subscribe process again.</para>
266
267</sect2> -->
268
269<para>For more information regarding which lists are available, how to
270subscribe to them, archive locations, etc. visit <ulink
271url="http://www.linuxfromscratch.org/mail.html"/>.</para>
272
273</sect1>
Note: See TracBrowser for help on using the repository browser.