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-dev</para></listitem>
|
---|
11 |
|
---|
12 | <listitem><para>blfs-book</para></listitem>
|
---|
13 |
|
---|
14 | <listitem><para>blfs-support</para></listitem>
|
---|
15 |
|
---|
16 | <listitem><para>lfs-support</para></listitem>
|
---|
17 |
|
---|
18 | <listitem><para>lfs-dev</para></listitem>
|
---|
19 |
|
---|
20 | <listitem><para>lfs-announce</para></listitem>
|
---|
21 |
|
---|
22 | <listitem><para>lfs-security</para></listitem>
|
---|
23 |
|
---|
24 | <listitem><para>lfs-book</para></listitem>
|
---|
25 |
|
---|
26 | <listitem><para>alfs-discuss</para></listitem>
|
---|
27 |
|
---|
28 | </itemizedlist>
|
---|
29 |
|
---|
30 | <sect2>
|
---|
31 | <title>blfs-book</title>
|
---|
32 |
|
---|
33 | <para>The blfs-book list is used by the BLFS-BOOK editors
|
---|
34 | to co-ordinate blfs-book's maintenance, like XML issues and the like.
|
---|
35 | Actual discussion on what should be added and removed should take place
|
---|
36 | on blfs-dev.</para>
|
---|
37 |
|
---|
38 | </sect2>
|
---|
39 |
|
---|
40 | <sect2>
|
---|
41 | <title>blfs-dev</title>
|
---|
42 |
|
---|
43 | <para>The blfs-dev mailing list discusses matters related to the
|
---|
44 | BLFS-BOOK (Beyond LFS). If problems with the book come up, a bug
|
---|
45 | or two need to be
|
---|
46 | reported, or suggestions to improve the book (such as suggestions as to
|
---|
47 | installation instructions to add) are to be made, this mailing list
|
---|
48 | is the right one.</para>
|
---|
49 |
|
---|
50 | <para>Requests for help with programs beyond the base LFS setup (not
|
---|
51 | just those in BLFS) should go to blfs-support.</para>
|
---|
52 |
|
---|
53 | </sect2>
|
---|
54 |
|
---|
55 | <sect2>
|
---|
56 | <title>blfs-support</title>
|
---|
57 |
|
---|
58 | <para>The blfs-support list deals with support requests for any software
|
---|
59 | not installed in the LFS book. The list is not just for help with
|
---|
60 | software explicitly mentioned in the BLFS book, any software beyond that
|
---|
61 | installed as part of the base LFS system can be discussed here.</para>
|
---|
62 |
|
---|
63 | </sect2>
|
---|
64 |
|
---|
65 | <sect2>
|
---|
66 | <title>lfs-support</title>
|
---|
67 |
|
---|
68 | <para>The lfs-support mailing list provides support to users building an
|
---|
69 | LFS system as far as the end of the main book. Requests for help with
|
---|
70 | installing software beyond the base system should go to the blfs-support
|
---|
71 | list.</para>
|
---|
72 |
|
---|
73 | </sect2>
|
---|
74 |
|
---|
75 | <sect2>
|
---|
76 | <title>lfs-dev</title>
|
---|
77 |
|
---|
78 | <para>The lfs-dev mailing list discusses matters strictly related to the
|
---|
79 | LFS-BOOK. If problems with the book come up, a bug or two need to be
|
---|
80 | reported, or suggestions to improve the book should be made,
|
---|
81 | this mailing list is the right one.</para>
|
---|
82 |
|
---|
83 | <para>Requests for help should go to lfs-support or blfs-support.</para>
|
---|
84 |
|
---|
85 | </sect2>
|
---|
86 |
|
---|
87 | <sect2>
|
---|
88 | <title>lfs-announce</title>
|
---|
89 |
|
---|
90 | <para>The lfs-announce list is a moderated list. It can be subscribed
|
---|
91 | to, but
|
---|
92 | you can't post any messages to this list. This list is used to announce
|
---|
93 | new stable releases. The lfs-dev list will carry information about
|
---|
94 | development releases as well. If a user is already on the lfs-dev
|
---|
95 | list, there's little use subscribing to
|
---|
96 | this list as well because everything that is posted to the lfs-announce
|
---|
97 | list will be posted to the lfs-dev list as well.</para>
|
---|
98 |
|
---|
99 | </sect2>
|
---|
100 |
|
---|
101 | <sect2>
|
---|
102 | <title>lfs-security</title>
|
---|
103 |
|
---|
104 | <para>The lfs-security mailing list discusses security-related matters.
|
---|
105 | Security concerns or security problems with a package used by LFS,
|
---|
106 | should be addressed on this list.</para>
|
---|
107 |
|
---|
108 | </sect2>
|
---|
109 |
|
---|
110 | <sect2>
|
---|
111 | <title>lfs-book</title>
|
---|
112 |
|
---|
113 | <para>The lfs-book list is used by the LFS-BOOK editors to co-ordinate
|
---|
114 | lfs-book's maintenance, like XML issues and the like. Actual discussion
|
---|
115 | on what should be added and removed take place on lfs-dev.</para>
|
---|
116 |
|
---|
117 | </sect2>
|
---|
118 |
|
---|
119 | <sect2>
|
---|
120 | <title>alfs-discuss</title>
|
---|
121 |
|
---|
122 | <para>The alfs-discuss list discusses the development of ALFS, which
|
---|
123 | stands for
|
---|
124 | Automated Linux From Scratch. The goal of this project is to develop an
|
---|
125 | installation tool that can install an LFS system automatically.
|
---|
126 | It's main goal is to speed up compilation by taking away the need to
|
---|
127 | manually enter the commands to configure, compile, and install
|
---|
128 | packages.</para>
|
---|
129 |
|
---|
130 | </sect2>
|
---|
131 |
|
---|
132 | <sect2>
|
---|
133 | <title>Mail archives</title>
|
---|
134 |
|
---|
135 | <para>All these lists are archived and can be viewed online at
|
---|
136 | <ulink url="http://archive.linuxfromscratch.org/mail-archives"/> or downloaded
|
---|
137 | from <ulink url="&ftp-root;/mail-archives"/>.</para>
|
---|
138 |
|
---|
139 | </sect2>
|
---|
140 |
|
---|
141 | <sect2>
|
---|
142 | <title>How to subscribe?</title>
|
---|
143 |
|
---|
144 | <para>Any of the above-mentioned mailinglists can be subscribed to by
|
---|
145 | sending an email to <ulink
|
---|
146 | url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org</ulink>
|
---|
147 | and writing <emphasis>subscribe listname</emphasis> as the subject
|
---|
148 | header of the message.</para>
|
---|
149 |
|
---|
150 | <para>Multiple lists at the same time can be subscribed to by using
|
---|
151 | one email. This is done by leaving the subject blank and putting all the
|
---|
152 | commands in the body of the email. The email will look like:</para>
|
---|
153 |
|
---|
154 | <blockquote><literallayout>To: listar@linuxfromscratch.org
|
---|
155 | Subject:
|
---|
156 |
|
---|
157 | subscribe lfs-dev
|
---|
158 | subscribe blfs-support
|
---|
159 | subscribe alfs-discuss</literallayout></blockquote>
|
---|
160 |
|
---|
161 | <para>After the email is sent, the Listar program will reply with an
|
---|
162 | email requesting a confirmation of the subscription request. After
|
---|
163 | this confirmation email is sent back, Listar will send an
|
---|
164 | email again with the message that the user has been subscribed to the
|
---|
165 | list(s) along with an introduction message for that particular
|
---|
166 | list.</para>
|
---|
167 |
|
---|
168 | </sect2>
|
---|
169 |
|
---|
170 | <sect2>
|
---|
171 | <title>How to unsubscribe?</title>
|
---|
172 |
|
---|
173 | <para>To unsubscribe from a list, send an email
|
---|
174 | to <ulink url="mailto:listar@linuxfromscratch.org"/> and
|
---|
175 | write <emphasis>unsubscribe listname</emphasis> as the subject header of
|
---|
176 | the message.</para>
|
---|
177 |
|
---|
178 | <para>Multiple lists can be unsubscribed at the same time
|
---|
179 | using one email. This is done by leaving the subject header blank and
|
---|
180 | putting all the commands in the body of the email. The email will look
|
---|
181 | like: </para>
|
---|
182 |
|
---|
183 | <blockquote><literallayout>To: listar@linuxfromscratch.org
|
---|
184 | Subject:
|
---|
185 |
|
---|
186 | unsubscribe lfs-dev
|
---|
187 | unsubscribe blfs-support
|
---|
188 | unsubscribe alfs-discuss</literallayout></blockquote>
|
---|
189 |
|
---|
190 | <para>After the email is sent, the Listar program will reply with an
|
---|
191 | email requesting a confirmation of the unsubscription
|
---|
192 | request. After this confirmation email is sent back, Listar will
|
---|
193 | send an email again with the message that the user has been unsubscribed
|
---|
194 | from the list(s).</para>
|
---|
195 |
|
---|
196 | </sect2>
|
---|
197 |
|
---|
198 | <sect2>
|
---|
199 | <title>Other list modes</title>
|
---|
200 |
|
---|
201 | <para>The modes that can be set by a user require sending an email to
|
---|
202 | <ulink
|
---|
203 | url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org</ulink>.
|
---|
204 | The modes themselves are set by writing
|
---|
205 | the appropriate commands in the subject header of the message.</para>
|
---|
206 |
|
---|
207 | <para>As the name implies, the <emphasis>Set command</emphasis> tells
|
---|
208 | what
|
---|
209 | to write to set a mode. The <emphasis>Unset command</emphasis> tells
|
---|
210 | what to write to unset a mode.</para>
|
---|
211 |
|
---|
212 | <para>The listname in the example subject headers should be replaced
|
---|
213 | with the
|
---|
214 | listname to which
|
---|
215 | the mode is going to be applied to. If more than one mode is to be set
|
---|
216 | (to
|
---|
217 | the same list or multiple lists) with one email, this can be done by
|
---|
218 | leaving the subject header blank and writing all the commands in the
|
---|
219 | body of
|
---|
220 | the message instead.</para>
|
---|
221 |
|
---|
222 | </sect2>
|
---|
223 |
|
---|
224 | <sect2>
|
---|
225 | <title>Digests</title>
|
---|
226 |
|
---|
227 | <literallayout>
|
---|
228 | Set command: <emphasis>set listname digest</emphasis>
|
---|
229 | Unset command: <emphasis>unset listname digest</emphasis>
|
---|
230 | </literallayout>
|
---|
231 |
|
---|
232 | <para>All lists have the digest mode available which can be set after a
|
---|
233 | user
|
---|
234 | has subscribed to a list. Being in digest mode will
|
---|
235 | cause you to stop receiving individual messages as they are posted to
|
---|
236 | the list and instead receive one email a day containing all
|
---|
237 | the messages posted to the list during that day.</para>
|
---|
238 |
|
---|
239 | <para>There is a second digest mode called digest2. When a user is set
|
---|
240 | to this
|
---|
241 | mode he will receive the daily digests but will also continue to
|
---|
242 | receive the individual messages to the lists as they are posted. To
|
---|
243 | set this mode, substitute <emphasis>digest</emphasis> for
|
---|
244 | <emphasis>digest2</emphasis> in the command.</para>
|
---|
245 |
|
---|
246 | </sect2>
|
---|
247 |
|
---|
248 | <sect2>
|
---|
249 | <title>Vacation</title>
|
---|
250 |
|
---|
251 | <literallayout>
|
---|
252 | Set command: <emphasis>set listname vacation</emphasis>
|
---|
253 | Unset command: <emphasis>unset listname vacation</emphasis>
|
---|
254 | </literallayout>
|
---|
255 |
|
---|
256 | <para>If a user is going to be away for a while or wishes to stop
|
---|
257 | receiving
|
---|
258 | messages from the lists but doesn't want to unsubscribe, he can change
|
---|
259 | to vacation mode. This has the same effect as unsubscribing,
|
---|
260 | but without having to go through the unsubscribe process and
|
---|
261 | then later through the subscribe process again.</para>
|
---|
262 |
|
---|
263 | </sect2>
|
---|
264 |
|
---|
265 | </sect1>
|
---|
266 |
|
---|