Changeset 5a8fca6


Ignore:
Timestamp:
01/03/2003 02:14:20 AM (21 years ago)
Author:
Gerard Beekmans <gerard@…>
Branches:
10.0, 10.0-rc1, 10.1, 10.1-rc1, 11.0, 11.0-rc1, 11.0-rc2, 11.0-rc3, 11.1, 11.1-rc1, 11.2, 11.2-rc1, 11.3, 11.3-rc1, 12.0, 12.0-rc1, 12.1, 12.1-rc1, 6.0, 6.1, 6.1.1, 6.3, 6.4, 6.5, 6.6, 6.7, 6.8, 7.0, 7.1, 7.2, 7.3, 7.4, 7.5, 7.5-systemd, 7.6, 7.6-systemd, 7.7, 7.7-systemd, 7.8, 7.8-systemd, 7.9, 7.9-systemd, 8.0, 8.1, 8.2, 8.3, 8.4, 9.0, 9.1, arm, bdubbs/gcc13, ml-11.0, multilib, renodr/libudev-from-systemd, s6-init, trunk, v4_1, v5_0, v5_1, v5_1_1, xry111/arm64, xry111/arm64-12.0, xry111/clfs-ng, xry111/lfs-next, xry111/loongarch, xry111/loongarch-12.0, xry111/loongarch-12.1, xry111/mips64el, xry111/pip3, xry111/rust-wip-20221008, xry111/update-glibc
Children:
fa7b512
Parents:
30a2c84
Message:

applied seth's mailinglist changes

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@2270 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689

Location:
chapter01
Files:
12 edited

Legend:

Unmodified
Added
Removed
  • chapter01/alfsdiscuss.xml

    r30a2c84 r5a8fca6  
    22<title>alfs-discuss</title>
    33
    4 <para>The alfs-discuss list discusses the development of ALFS, which is short
    5 for Automated Linux From Scratch. The goal of this project is to develop an
    6 installation tool that installs an LFS system automatically, thus speeding
    7 up compilation by taking away the need to manually enter the commands.</para>
     4<para>The alfs-discuss list is for discussion of ALFS development.</para>
    85
    96</sect2>
  • chapter01/blfsbook.xml

    r30a2c84 r5a8fca6  
    22<title>blfs-book</title>
    33
    4 <para>The blfs-book list is used by the BLFS-BOOK editors to co-ordinate
    5 the maintenance of the BLFS book, such as XML source code issues and the
    6 like. Actual discussion on what should be added and removed should take place
    7 on blfs-dev.</para>
     4<para>The blfs-book list is used for coordinating
     5the BLFS Book's maintenance.
     6Traffic on it is mostly Bugzilla and CVS commit messages.
     7It is important that all development discussion
     8of interest to the Book's users take place on blfs-dev, not here.</para>
    89
    910</sect2>
  • chapter01/blfsdev.xml

    r30a2c84 r5a8fca6  
    22<title>blfs-dev</title>
    33
    4 <para>The blfs-dev mailing list discusses development of the
    5 BLFS-BOOK (Beyond LFS). This is the maillist to submit bug reports,
    6 and make suggestions to improve the BLFS book.</para>
    7 
    8 <para>Requests for help with programs beyond the base LFS build and setup
    9 (not just those in the BLFS book) should be made in blfs-support.</para>
     4<para>The blfs-dev list is for discussion of BLFS Book development.</para>
    105
    116</sect2>
  • chapter01/blfssupport.xml

    r30a2c84 r5a8fca6  
    22<title>blfs-support</title>
    33
    4 <para>The blfs-support list handles support requests for any software
    5 that is not built or installed in the LFS book. Any software beyond what is
    6 installed as part of the base LFS system can be discussed here.</para>
     4<para>The blfs-support list is for the BLFS Book and beyond.
     5
     6It includes requests for help following the BLFS Book,
     7requests for help with packages not (yet) in
     8either the LFS Book or the BLFS Book,
     9and other requests and discussion concerning software
     10that might be installed on an LFS system.
     11
     12It does not include topics such as
     13the price of beer, what hardware to buy,
     14or GNU versus BSD or Microsoft versus Linux flamewars.
     15These belong on lfs-chat,
     16and since blfs-support is high traffic,
     17please follow this rule strictly.
     18</para>
    719
    820</sect2>
  • chapter01/howtopost.xml

    r30a2c84 r5a8fca6  
    22<title>How to post to a list</title>
    33
    4 <para>You do not need to be subscribed to a mailing list in order to post to it.
    5 However, if you post to a list you're not subscribed to, make sure you
    6 mention this in your email so the list members can put you in the CC:
    7 header of an email in order for you to receive the replies.</para>
    8 
    94<para>The post address for a list is in the format of
    105<emphasis>listname@linuxfromscratch.org</emphasis> where
    11 <emphasis>listname</emphasis> can be one of the lists in the Available lists
    12 section above. Examples of post addresses are
    13 <emphasis>lfs-dev@linuxfromscratch.org, lfs-support@linuxfromscratch.org and
    14 blfs-support@linuxfromscratch.org</emphasis>.</para>
     6<emphasis>listname</emphasis> is one of the above lists names.
     7Example post addresses are
     8<emphasis>lfs-support@linuxfromscratch.org and</emphasis>
     9<emphasis>blfs-support@linuxfromscratch.org</emphasis>.</para>
    1510
    1611</sect2>
  • chapter01/lfsannounce.xml

    r30a2c84 r5a8fca6  
    22<title>lfs-announce</title>
    33
    4 <para>The lfs-announce list is a moderated list. It can be subscribed to, but
    5 you can't post any messages to this list. This list is used to announce
    6 new stable releases. The lfs-dev list will carry information about
    7 development releases as well. If a user is already on the lfs-dev
    8 list, there's little use subscribing to
    9 this list as well because everything that is posted to the lfs-announce
    10 list will be posted to the lfs-dev list as well.</para>
     4<para>The lfs-announce list is a moderated list for those who want
     5notification of new stable releases
     6without the higher traffic of lfs-dev.</para>
    117
    128</sect2>
  • chapter01/lfsbook.xml

    r30a2c84 r5a8fca6  
    22<title>lfs-book</title>
    33
    4 <para>The lfs-book list is used by the LFS-BOOK editors to co-ordinate
    5 lfs-book's maintenance, like XML issues and the like. Actual discussion
    6 on what should be added and removed take place on lfs-dev.</para>
     4<para>The lfs-book list is used for coordinating the LFS Book's maintenance.
     5Traffic on it is mostly Bugzilla and CVS commit messages.
     6It is important that all development discussion
     7of interest to the Book's users take place on lfs-dev, not here.</para>
    78
    89</sect2>
  • chapter01/lfschat.xml

    r30a2c84 r5a8fca6  
    22<title>lfs-chat</title>
    33
    4 <para>The lfs-chat list is a hangout place for members of the LFS Community
    5 (that includes you as well) and just chat about stuff. Doesn't even have to
    6 be computer related. Anything goes, nothing is off-topic.</para>
     4<para>The lfs-chat list is the place for community chatter.
     5It's a place where anything goes, nothing is off-topic.
     6You can discuss the price of beer or what hardware to buy.
     7Even GNU versus BSD and Microsoft versus Linux flamewars
     8are okay in lfs-chat.</para>
    79
    810</sect2>
  • chapter01/lfsdev.xml

    r30a2c84 r5a8fca6  
    22<title>lfs-dev</title>
    33
    4 <para>The lfs-dev mailing list discusses matters strictly related to the
    5 LFS-BOOK. If problems with the book come up, a bug or two need to be
    6 reported, or suggestions to improve the book should be made,
    7 this mailing list is the right one.</para>
    8 
    9 <para>Requests for help should go to lfs-support or blfs-support.</para>
     4<para>The lfs-dev list is for discussion of LFS Book development.</para>
    105
    116</sect2>
  • chapter01/lfssecurity.xml

    r30a2c84 r5a8fca6  
    22<title>lfs-security</title>
    33
    4 <para>The lfs-security mailing list discusses security-related matters.
    5 Security concerns or security problems with a package used by LFS,
    6 should be addressed on this list.</para>
     4<para>The lfs-security list discusses security issues.
     5Vulnerability alerts, configuration questions,
     6security related packages, and other things to do with secure systems
     7are appropriate on this list.</para>
    78
    89</sect2>
  • chapter01/lfssupport.xml

    r30a2c84 r5a8fca6  
    22<title>lfs-support</title>
    33
    4 <para>The lfs-support mailing list provides support to users building an
    5 LFS system as far as the end of the main book. Requests for help with
    6 installing software beyond the base system should go to the blfs-support
    7 list.</para>
     4<para>The lfs-support list is the place to get help
     5following the instructions in the LFS Book itself.</para>
     6
     7<para>If you're finished with the LFS Book, use blfs-support instead.</para>
    88
    99</sect2>
  • chapter01/maillists.xml

    r30a2c84 r5a8fca6  
    1414<listitem><para>lfs-announce</para></listitem>
    1515
    16 <listitem><para>lfs-security</para></listitem>
    17 
    1816<listitem><para>lfs-book</para></listitem>
    1917
    2018<listitem><para>lfs-chat</para></listitem>
     19
     20<listitem><para>lfs-security</para></listitem>
    2121
    2222<listitem><para>alfs-discuss</para></listitem>
     
    3333&c1-ma-lfsdev;
    3434&c1-ma-lfsannounce;
    35 &c1-ma-lfssecurity;
    3635&c1-ma-lfsbook;
    3736&c1-ma-lfschat;
     37&c1-ma-lfssecurity;
    3838
    3939&c1-ma-alfsdiscuss;
Note: See TracChangeset for help on using the changeset viewer.