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
|
---|
6 | accessible 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,
|
---|
38 | requests for help with packages not (yet) in
|
---|
39 | either the LFS Book or the BLFS Book,
|
---|
40 | and other requests and discussion concerning software
|
---|
41 | that might be installed on an LFS system.</para>
|
---|
42 |
|
---|
43 | <para>It does not include topics such as
|
---|
44 | the price of beer, what hardware to buy,
|
---|
45 | or GNU versus BSD or Microsoft versus Linux flamewars.
|
---|
46 | These belong on lfs-chat,
|
---|
47 | and since blfs-support is high traffic,
|
---|
48 | please 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
|
---|
63 | the BLFS Book's maintenance.
|
---|
64 | Traffic on it is mostly Bugzilla and CVS commit messages.
|
---|
65 | It is important that all development discussion
|
---|
66 | of 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.
|
---|
74 | It's a place where anything goes, nothing is off-topic.
|
---|
75 | You can discuss the price of beer or what hardware to buy.
|
---|
76 | Even GNU versus BSD and Microsoft versus Linux flamewars
|
---|
77 | are 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
|
---|
85 | following 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
|
---|
102 | notification of new stable releases
|
---|
103 | without 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.
|
---|
111 | Traffic on it is mostly Bugzilla and CVS commit messages.
|
---|
112 | It is important that all development discussion
|
---|
113 | of 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.
|
---|
121 | Vulnerability alerts, configuration questions,
|
---|
122 | security related packages, and other things to do with secure systems
|
---|
123 | are 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
|
---|
139 | from <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 mailinglists can be subscribed to by
|
---|
147 | sending an email to <ulink
|
---|
148 | url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org</ulink>
|
---|
149 | and writing <emphasis>subscribe listname</emphasis> as the subject
|
---|
150 | header of the message.</para>
|
---|
151 |
|
---|
152 | <para>Multiple lists at the same time can be subscribed to by using
|
---|
153 | one email. This is done by leaving the subject blank and putting all the
|
---|
154 | commands in the body of the email. The email will look like:</para>
|
---|
155 |
|
---|
156 | <blockquote><literallayout>To: listar@linuxfromscratch.org
|
---|
157 | Subject:
|
---|
158 |
|
---|
159 | subscribe lfs-dev
|
---|
160 | subscribe blfs-support
|
---|
161 | subscribe alfs-discuss</literallayout></blockquote>
|
---|
162 |
|
---|
163 | <para>After the email is sent, the Listar program will reply with an
|
---|
164 | email requesting a confirmation of the subscription request. After
|
---|
165 | this confirmation email is sent back, Listar will send an
|
---|
166 | email again with the message that the user has been subscribed to the
|
---|
167 | list(s) along with an introduction message for that particular
|
---|
168 | list.</para>
|
---|
169 |
|
---|
170 | </sect2>
|
---|
171 |
|
---|
172 | <sect2>
|
---|
173 | <title>How to unsubscribe?</title>
|
---|
174 |
|
---|
175 | <para>To unsubscribe from a list, send an email
|
---|
176 | to <ulink url="mailto:listar@linuxfromscratch.org"/> and
|
---|
177 | write <emphasis>unsubscribe listname</emphasis> as the subject header of
|
---|
178 | the message.</para>
|
---|
179 |
|
---|
180 | <para>Multiple lists can be unsubscribed at the same time
|
---|
181 | using one email. This is done by leaving the subject header blank and
|
---|
182 | putting all the commands in the body of the email. The email will look
|
---|
183 | like: </para>
|
---|
184 |
|
---|
185 | <blockquote><literallayout>To: listar@linuxfromscratch.org
|
---|
186 | Subject:
|
---|
187 |
|
---|
188 | unsubscribe lfs-dev
|
---|
189 | unsubscribe blfs-support
|
---|
190 | unsubscribe alfs-discuss</literallayout></blockquote>
|
---|
191 |
|
---|
192 | <para>After the email is sent, the Listar program will reply with an
|
---|
193 | email requesting a confirmation of the unsubscription
|
---|
194 | request. After this confirmation email is sent back, Listar will
|
---|
195 | send an email again with the message that the user has been unsubscribed
|
---|
196 | from 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
|
---|
205 | url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org</ulink>.
|
---|
206 | The modes themselves are set by writing
|
---|
207 | the appropriate commands in the subject header of the message.</para>
|
---|
208 |
|
---|
209 | <para>As the name implies, the <emphasis>Set command</emphasis> tells
|
---|
210 | what
|
---|
211 | to write to set a mode. The <emphasis>Unset command</emphasis> tells
|
---|
212 | what to write to unset a mode.</para>
|
---|
213 |
|
---|
214 | <para>The listname in the example subject headers should be replaced
|
---|
215 | with the
|
---|
216 | listname to which
|
---|
217 | the mode is going to be applied to. If more than one mode is to be set
|
---|
218 | (to
|
---|
219 | the same list or multiple lists) with one email, this can be done by
|
---|
220 | leaving the subject header blank and writing all the commands in the
|
---|
221 | body of
|
---|
222 | the message instead.</para>
|
---|
223 |
|
---|
224 | </sect2>
|
---|
225 |
|
---|
226 | <sect2>
|
---|
227 | <title>Digests</title>
|
---|
228 |
|
---|
229 | <literallayout>
|
---|
230 | Set command: <emphasis>set listname digest</emphasis>
|
---|
231 | Unset command: <emphasis>unset listname digest</emphasis>
|
---|
232 | </literallayout>
|
---|
233 |
|
---|
234 | <para>All lists have the digest mode available which can be set after a
|
---|
235 | user
|
---|
236 | has subscribed to a list. Being in digest mode will
|
---|
237 | cause you to stop receiving individual messages as they are posted to
|
---|
238 | the list and instead receive one email a day containing all
|
---|
239 | the 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
|
---|
242 | to this
|
---|
243 | mode he will receive the daily digests but will also continue to
|
---|
244 | receive the individual messages to the lists as they are posted. To
|
---|
245 | set 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>
|
---|
254 | Set command: <emphasis>set listname vacation</emphasis>
|
---|
255 | Unset 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
|
---|
259 | receiving
|
---|
260 | messages from the lists but doesn't want to unsubscribe, he can change
|
---|
261 | to vacation mode. This has the same effect as unsubscribing,
|
---|
262 | but without having to go through the unsubscribe process and
|
---|
263 | then later through the subscribe process again.</para>
|
---|
264 |
|
---|
265 | </sect2>
|
---|
266 |
|
---|
267 | </sect1>
|
---|
268 |
|
---|