LFS Mailing Lists
Before you post to the mailing lists, please check if your answer has already been answered in the FAQ, on the search page or by other methods on the support page. If you don't understand an answer in the FAQ or would like some more information, send an e-mail to the FAQ maintainer.
If you're finished with the LFS Book, use blfs-support instead. Please read the netiquette rules before posting!
You must subscribe to a list before posting.
Mailing List Description
- The lfs-announce list is a moderated list for those who want notification of new stable releases without the higher traffic of lfs-dev.
- The lfs-support list is the place to get help following the instructions in the stable release of LFS Book itself. If you are finished with the LFS book, please use blfs-support instead.
- The lfs-book list is used for coordinating the LFS Book's maintenance. Traffic on it is mostly Trac and SVN commit messages. It is important that all development discussion of interest to the Book's users take place on lfs-dev, not here.
- The lfs-dev list is for discussion of LFS Book development.
- The lfs-chat list is the place for community chatter. It's a place where anything goes, nothing is off-topic. You can discuss the price of beer or what hardware to buy. Even GNU versus BSD and Microsoft versus Linux flamewars are okay in lfs-chat.
- The lfs-security list is a low-traffic list meant for security alerts.
- The blfs-support list for the BLFS Book and beyond. It includes requests for help following the BLFS Book, requests for help with packages not (yet) in either the LFS Book or the BLFS Book, and other requests and discussion concerning software that might be installed on an LFS system. It does not include topics such as the price of beer, what hardware to buy, or GNU versus BSD or Microsoft versus Linux flamewars. These belong on lfs-chat, and since blfs-support is high traffic, please follow this rule strictly.
- The blfs-book list is used for coordinating the BLFS Book's maintenance. Traffic on it is mostly Trac and SVN commit messages. It is important that all development discussion of interest to the Book's users take place on blfs-dev, not here.
- The blfs-dev list is for discussion of BLFS Book development.
- The CLFS lists are detailed on the CLFS lists wiki page.
- The hlfs-book list is used for coordinating the HLFS Book's maintenance. Traffic on it is mostly Trac and SVN commit messages. It is important that all development discussion of interest to the Book's users take place on hlfs-dev, not here.
- The hlfs-dev list is for discussion of Hardened LFS Book development.
- The livecd list is for discussion of the LFS LiveCD, as well as bug reports, feature requests and other things LiveCD related.
- The alfs-discuss list is for discussion of ALFS development.
- The alfs-log list is used for coordinating the ALFS Project maintenance. Traffic on it is mostly Trac and SVN commit messages. It is important that all development discussion of interest to the users of ALFS take place on alfs-discuss, not here.
- The hints list is for submission of hints or patches and updates to hints. This list is only for submission of hints, discussion related to hints should be on the appropriate support list, which is mostly blfs-support.
- The patches list is for submission of non-critical patches for various packages for LFS and BLFS. This list is only for submission of patches, discussion related to patches should be on the appropriate support or development list.
- The faq list is for FAQ submissions, or discussions related to the FAQ. It's also acceptable to CC this list when you answer a FAQ to inform the FAQ maintainer. Don't forget to read the entire FAQ before posting!
- The website list can be used to discuss the website, report broken links, submit content or a logo or anything else related to the website.
- The test-list can be used if you would like to check your mail setup or the availability of the server. It works exactly like the other lists and is thus suitable for testing. There is no need to send test-messages to any other list.
Every mailinglist is archived and can be browsed through online. The archives are always current. The links to the archives is available through each lists' information page.
Besides the current available lists, the archive also contains other mailinglists that used to exist but have been discontinued.
The archives are split by month. If you don't want to just browse but are actually looking for specific information, you'll be better off searching through the archives using the search engine.
The easiest way to subscribe is via the online forms.
You can also subscribe to any of the lists by sending an email to <listname>-firstname.lastname@example.org with "subscribe" in the subject line of the message.
After you have sent the email, the GNU Mailman program will send you an email back, one for every list you requested subscription to, requesting a confirmation of your subscribe request. After you have sent back this confirmation email, GNU Mailman will send you an email again with the confirmation that you have been subscribed to the list(s) (again, one confirmation email for every list you are subscribed to now).
The easiest way to unsubscribe is via the online forms.
You can also unsubscribe from any of the lists by sending an email to <listname>-email@example.com with "unsubscribe" in the subject line of the message.
It is very important to note that the address for unsubscribing, is DIFFERENT from the address used to post to the list.
Every email sent out by the mailinglist software at linuxfromscratch.org
comes with a
List-Id: header. This header will always have the
value of the mailinglist the email came from. So this header for an email
to lfs-dev will look like
lfs-dev.linuxfromscratch.org and an email to blfs-support will look
We suggest you use this
List-Id: header to filter incoming
LFS mail to your mail folders. Here's an example for procmail:
* ^List-Id: .*<listname.linuxfromscratch.org>
All lists have the digest mode available which can be set after a user has subscribed to a list. Being in digest mode will cause you to stop receiving individual messages as they are posted to the list and instead receive one email a day containing all the messages posted to the list during that day.
This setting can be configured via the online forms.
If you are going to be away for a while or wish to stop receiving messages from the lists but don't want to unsubscribe, you can change to vacation mode. This has the same effect as unsubscribing, but without having to go through the unsubscribe process and then later through the subscribe process again.
This setting can be configured via the online forms. Note that Mailman refers to this option as Mail delivery.