source: introduction/welcome/maillists.xml@ 1d85838

10.0 10.1 11.0 11.1 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 krejzi/svn lazarus nosym perl-modules qt5new systemd-11177 systemd-13485 trunk upgradedb v5_0 v5_0-pre1 v5_1 v5_1-pre1 xry111/intltool xry111/test-20220226
Last change on this file since 1d85838 was 5628618e, checked in by Larry Lawrence <larry@…>, 19 years ago

spellcheck pass

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

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