Changeset bf0878c8 for introduction/welcome/maillists.xml
- Timestamp:
- 05/13/2004 06:40:06 AM (20 years ago)
- Branches:
- 10.0, 10.1, 11.0, 11.1, 11.2, 11.3, 12.0, 12.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, kea, ken/TL2024, ken/inkscape-core-mods, ken/tuningfonts, krejzi/svn, lazarus, lxqt, nosym, perl-modules, plabs/newcss, plabs/python-mods, python3.11, qt5new, rahul/power-profiles-daemon, renodr/vulkan-addition, systemd-11177, systemd-13485, trunk, upgradedb, v5_1, v5_1-pre1, xry111/intltool, xry111/llvm18, xry111/soup3, xry111/test-20220226, xry111/xf86-video-removal
- Children:
- ee177c02
- Parents:
- 244a44e5
- File:
-
- 1 edited
Legend:
- Unmodified
- Added
- Removed
-
introduction/welcome/maillists.xml
r244a44e5 rbf0878c8 8 8 lists.</para> 9 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,40 requests for help with packages not (yet) in41 either the LFS Book or the BLFS Book,42 and other requests and discussion concerning software43 that might be installed on an LFS system.</para>44 45 <para>It does not include topics such as46 the price of beer, what hardware to buy,47 or GNU versus BSD or Microsoft versus Linux flame wars.48 These belong on lfs-chat,49 and since blfs-support is high traffic,50 please 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 coordinating65 the BLFS Book's maintenance.66 Traffic on it is mostly Bugzilla and CVS commit messages.67 It is important that all development discussion68 of 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.76 It's a place where anything goes, nothing is off-topic.77 You can discuss the price of beer or what hardware to buy.78 Even GNU versus BSD and Microsoft versus Linux flame wars79 are 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 help87 following 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 want104 notification of new stable releases105 without 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.113 Traffic on it is mostly Bugzilla and CVS commit messages.114 It is important that all development discussion115 of 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.123 Vulnerability alerts, configuration questions,124 security related packages, and other things to do with secure systems125 are 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 at140 <ulink url="http://archive.linuxfromscratch.org/mail-archives"/> or downloaded141 from <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 by149 sending an email to <ulink150 url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org</ulink>151 and writing <emphasis>subscribe listname</emphasis> as the subject152 header of the message.</para>153 154 <para>Multiple lists at the same time can be subscribed to by using155 one email. This is done by leaving the subject blank and putting all the156 commands in the body of the email. The email will look like:</para>157 158 <blockquote><literallayout>To: listar@linuxfromscratch.org159 Subject:160 161 subscribe lfs-dev162 subscribe blfs-support163 subscribe alfs-discuss</literallayout></blockquote>164 165 <para>After the email is sent, the Listar program will reply with an166 email requesting a confirmation of the subscription request. After167 this confirmation email is sent back, Listar will send an168 email again with the message that the user has been subscribed to the169 list(s) along with an introduction message for that particular170 list.</para>171 172 </sect2>173 174 <sect2>175 <title>How to unsubscribe?</title>176 177 <para>To unsubscribe from a list, send an email178 to <ulink url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org179 </ulink> and write <emphasis>unsubscribe listname</emphasis> as the subject180 header of the message.</para>181 182 <para>Multiple lists can be unsubscribed at the same time183 using one email. This is done by leaving the subject header blank and184 putting all the commands in the body of the email. The email will look185 like: </para>186 187 <blockquote><literallayout>To: listar@linuxfromscratch.org188 Subject:189 190 unsubscribe lfs-dev191 unsubscribe blfs-support192 unsubscribe alfs-discuss</literallayout></blockquote>193 194 <para>After the email is sent, the Listar program will reply with an195 email requesting a confirmation of the unsubscription196 request. After this confirmation email is sent back, Listar will197 send an email again with the message that the user has been unsubscribed198 from 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 to206 <ulink207 url="mailto:listar@linuxfromscratch.org">listar@linuxfromscratch.org</ulink>.208 The modes themselves are set by writing209 the appropriate commands in the subject header of the message.</para>210 211 <para>As the name implies, the <emphasis>Set command</emphasis> tells212 what213 to write to set a mode. The <emphasis>Unset command</emphasis> tells214 what to write to unset a mode.</para>215 216 <para>The listname in the example subject headers should be replaced217 with the218 listname to which219 the mode is going to be applied to. If more than one mode is to be set220 (to221 the same list or multiple lists) with one email, this can be done by222 leaving the subject header blank and writing all the commands in the223 body of224 the message instead.</para>225 226 </sect2>227 228 <sect2>229 <title>Digests</title>230 231 <literallayout>232 Set command: <emphasis>set listname digest</emphasis>233 Unset command: <emphasis>unset listname digest</emphasis>234 </literallayout>235 236 <para>All lists have the digest mode available which can be set after a237 user238 has subscribed to a list. Being in digest mode will239 cause you to stop receiving individual messages as they are posted to240 the list and instead receive one email a day containing all241 the messages posted to the list during that day.</para>242 243 <para>There is a second digest mode called digest2. When a user is set244 to this245 mode he will receive the daily digests but will also continue to246 receive the individual messages to the lists as they are posted. To247 set this mode, substitute <emphasis>digest</emphasis> for248 <emphasis>digest2</emphasis> in the command.</para>249 250 </sect2>251 252 <sect2>253 <title>Vacation</title>254 255 <literallayout>256 Set command: <emphasis>set listname vacation</emphasis>257 Unset 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 stop261 receiving262 messages from the lists but doesn't want to unsubscribe, he can change263 to vacation mode. This has the same effect as unsubscribing,264 but without having to go through the unsubscribe process and265 then later through the subscribe process again.</para>266 267 </sect2> -->268 269 10 <para>For more information regarding which lists are available, how to 270 11 subscribe to them, archive locations, etc. visit <ulink
Note:
See TracChangeset
for help on using the changeset viewer.