Forráskód Böngészése

mailing list changes

git-svn-id: http://svn.linuxfromscratch.org/LFS/trunk/BOOK@1244 4aa44e1e-78dd-0310-a6d2-fbcd4c07a689
Mark Hymers 24 éve
szülő
commit
4be7361f6b

+ 0 - 8
chapter01/alfsbackend.xml

@@ -1,8 +0,0 @@
-<sect2>
-<title>alfs-backend</title>
-
-<para>The alfs-backend mailinglist discusses matters regarding the ALFS
-backend.</para>
-
-</sect2>
-

+ 0 - 8
chapter01/alfsdocs.xml

@@ -1,8 +0,0 @@
-<sect2>
-<title>alfs-docs</title>
-
-<para>ALFS-docs is the ALFS documentation project which creates and maintains
-all of the ALFS documentation.</para>
-
-</sect2>
-

+ 0 - 7
chapter01/alfsipc.xml

@@ -1,7 +0,0 @@
-<sect2>
-<title>alfs-ipc</title>
-
-<para>The alfs-ipc list discusses the ALFS InterProcess Communication issues.</para>
-
-</sect2>
-

+ 0 - 8
chapter01/alfsprofile.xml

@@ -1,8 +0,0 @@
-<sect2>
-<title>alfs-profile</title>
-
-<para>The alfs-profile list discusses the development of the ALFS XML profile
-and DTD.</para>
-
-</sect2>
-

+ 4 - 4
chapter01/blfsbook.xml

@@ -1,10 +1,10 @@
 <sect2>
 <title>blfs-book</title>
 
-<para>The blfs-book list is used by the BLFS-BOOK (Beyond LFS) editors to
-co-ordinate blfs-book's maintenance. For now, actual discussions will
-take place on the lfs-apps list (like lfs-discuss is used instead of
-lfs-book).</para>
+<para>The blfs-book list is used by the BLFS-BOOK editors 
+to co-ordinate blfs-book's maintenance, like XML issues and the like. 
+Actual discussion on what should be added and removed should take place 
+on blfs-dev.</para>
 
 </sect2>
 

+ 15 - 0
chapter01/blfsdev.xml

@@ -0,0 +1,15 @@
+<sect2>
+<title>blfs-dev</title>
+
+<para>The blfs-dev mailing list discusses matters related to the
+BLFS-BOOK (Beyond LFS).  If problems with the book come up, a bug 
+or two need to be
+reported, or suggestions to improve the book (such as suggestions as to
+installation instructions to add) are to be made, this mailing list 
+is the right one.</para>
+
+<para>Requests for help with programs beyond the base LFS setup (not
+just those in BLFS) should go to blfs-support.</para>
+
+</sect2>
+

+ 10 - 0
chapter01/blfssupport.xml

@@ -0,0 +1,10 @@
+<sect2>
+<title>blfs-support</title>
+
+<para>The blfs-support list deals with support requests for any software
+not installed in the LFS book.  The list is not just for help with
+software explicitly mentioned in the BLFS book, any software beyond that
+installed as part of the base LFS system can be discussed here.</para>
+
+</sect2>
+

+ 5 - 0
chapter01/changelog.xml

@@ -15,6 +15,11 @@
 
 </para></listitem>
 
+<listitem><para>September 20th, 2001 [markh]: Chapter 1+7: Changed the
+mailing list information to reflect the new ml
+structure.  The Ch7 change is that the rc and rcS scripts now ask people
+to report problems to lfs-dev instead of lfs-discuss.</para></listitem>
+
 <listitem><para>September 18th, 2001 [gerard]: Chapter 5+6 - GCC:
 Added --enable-threads=posix to chapter 5, and changed --enable-threads to
 --enable-threads=posix in chapter 6. Although the default is posix threads when

+ 4 - 5
chapter01/lfsannounce.xml

@@ -3,12 +3,11 @@
 
 <para>The lfs-announce list is a moderated list. It can be subscribed to, but
 you can't post any messages to this list. This list is used to announce
-new stable releases. The lfs-discuss list will carry information about
-development
-releases as well. If
-a user is already on the lfs-discuss list, there's little use subscribing to
+new stable releases. The lfs-dev list will carry information about
+development releases as well. If a user is already on the lfs-dev 
+list, there's little use subscribing to
 this list as well because everything that is posted to the lfs-announce
-list will be posted to the lfs-discuss list as well.</para>
+list will be posted to the lfs-dev list as well.</para>
 
 </sect2>
 

+ 0 - 8
chapter01/lfsapps.xml

@@ -1,8 +0,0 @@
-<sect2>
-<title>lfs-apps</title>
-
-<para>The lfs-apps list deals with everything that does not fit on the
-lfs-discuss list.</para>
-
-</sect2>
-

+ 1 - 1
chapter01/lfsbook.xml

@@ -3,7 +3,7 @@
 
 <para>The lfs-book list is used by the LFS-BOOK editors to co-ordinate
 lfs-book's maintenance, like XML issues and the like. Actual discussion
-on what should be added and removed take place on lfs-discuss.</para>
+on what should be added and removed take place on lfs-dev.</para>
 
 </sect2>
 

+ 3 - 3
chapter01/lfsdiscuss.xml → chapter01/lfsdev.xml

@@ -1,12 +1,12 @@
 <sect2>
-<title>lfs-discuss</title>
+<title>lfs-dev</title>
 
-<para>The lfs-discuss mailing list discusses matters strictly related to the
+<para>The lfs-dev mailing list discusses matters strictly related to the
 LFS-BOOK. If problems with the book come up, a bug or two need to be
 reported, or suggestions to improve the book should be made, 
 this mailing list is the right one.</para>
 
-<para>Any other mail is to be posted on the lfs-apps list.</para>
+<para>Requests for help should go to lfs-support or blfs-support.</para>
 
 </sect2>
 

+ 10 - 0
chapter01/lfssupport.xml

@@ -0,0 +1,10 @@
+<sect2>
+<title>lfs-support</title>
+
+<para>The lfs-support mailing list provides support to users building an
+LFS system as far as the end of the main book.  Requests for help with
+installing software beyond the base system should go to the blfs-support
+list.</para>
+
+</sect2>
+

+ 14 - 4
chapter01/maillists.xml

@@ -6,9 +6,9 @@ accessible mailing lists:</para>
 
 <itemizedlist>
 
-<listitem><para>lfs-discuss</para></listitem>
+<listitem><para>lfs-support</para></listitem>
 
-<listitem><para>lfs-apps</para></listitem>
+<listitem><para>lfs-dev</para></listitem>
 
 <listitem><para>lfs-announce</para></listitem>
 
@@ -18,18 +18,28 @@ accessible mailing lists:</para>
 
 <listitem><para>alfs-discuss</para></listitem>
 
+<listitem><para>blfs-dev</para></listitem>
+
 <listitem><para>blfs-book</para></listitem>
 
+<listitem><para>blfs-support</para></listitem>
+
 </itemizedlist>
 
-&c1-ma-lfsdiscuss;
-&c1-ma-lfsapps;
+&c1-ma-lfssupport;
+&c1-ma-lfsdev;
 &c1-ma-lfsannounce;
 &c1-ma-lfssecurity;
 &c1-ma-lfsbook;
+
 &c1-ma-alfsdiscuss;
+
+&c1-ma-blfsdev;
 &c1-ma-blfsbook;
+&c1-ma-blfssupport;
+
 &c1-ma-mailarchive;
+
 &c1-ma-subscribe;
 &c1-ma-unsubscribe;
 &c1-ma-othermodes;

+ 2 - 2
chapter01/subscribe.xml

@@ -13,8 +13,8 @@ commands in the body of the email. The email will look like:</para>
 <blockquote><literallayout>To: listar@linuxfromscratch.org
 Subject:
 
-subscribe lfs-discuss
-subscribe lfs-apps
+subscribe lfs-dev
+subscribe blfs-support
 subscribe alfs-discuss</literallayout></blockquote>
 
 <para>After the email is sent, the Listar program will reply with an

+ 2 - 2
chapter01/unsubscribe.xml

@@ -14,8 +14,8 @@ like: </para>
 <blockquote><literallayout>To: listar@linuxfromscratch.org
 Subject:
 
-unsubscribe lfs-discuss
-unsubscribe lfs-apps
+unsubscribe lfs-dev
+unsubscribe blfs-support
 unsubscribe alfs-discuss</literallayout></blockquote>
 
 <para>After the email is sent, the Listar program will reply with an  

+ 1 - 1
chapter07/rc.xml

@@ -39,7 +39,7 @@ print_error_msg()
         echo "to trace this error down "
         echo -n "to a bug in one of the files provided by this book, "
         echo "please be so kind to "
-        echo -n "inform us at lfs-discuss@linuxfromscratch.org"
+        echo -n "inform us at lfs-dev@linuxfromscratch.org"
         $NORMAL
         echo
         echo

+ 1 - 1
chapter07/rcS.xml

@@ -29,7 +29,7 @@ print_error_msg()
         echo "to trace this error down "
         echo -n "to a bug in one of the files provided by this book, "
         echo "please be so kind to "
-        echo -n "inform us at lfs-discuss@linuxfromscratch.org"
+        echo -n "inform us at lfs-dev@linuxfromscratch.org"
         $NORMAL
         echo
         echo

+ 6 - 4
index.xml

@@ -4,8 +4,8 @@
 
 <!ENTITY book SYSTEM "book/book.xml">
 
-<!ENTITY version "20010919">
-<!ENTITY releasedate "September 19th, 2001">
+<!ENTITY version "20010920">
+<!ENTITY releasedate "September 20th, 2001">
 
 <!ENTITY ftp-root "ftp://ftp.linuxfromscratch.org">
 <!ENTITY http-root "http://ftp.linuxfromscratch.org">
@@ -42,13 +42,15 @@
 <!ENTITY c1-acknowledgments SYSTEM "chapter1/acknowledgments.xml">
 <!ENTITY c1-changelog SYSTEM "chapter1/changelog.xml">
 <!ENTITY c1-maillists SYSTEM "chapter1/maillists.xml">
-<!ENTITY c1-ma-lfsdiscuss SYSTEM "chapter1/lfsdiscuss.xml">
-<!ENTITY c1-ma-lfsapps SYSTEM "chapter1/lfsapps.xml">
+<!ENTITY c1-ma-lfsdev SYSTEM "chapter1/lfsdev.xml">
 <!ENTITY c1-ma-lfsannounce SYSTEM "chapter1/lfsannounce.xml">
 <!ENTITY c1-ma-lfssecurity SYSTEM "chapter1/lfssecurity.xml">
+<!ENTITY c1-ma-lfssupport SYSTEM "chapter1/lfssupport.xml">
 <!ENTITY c1-ma-lfsbook SYSTEM "chapter1/lfsbook.xml">
 <!ENTITY c1-ma-alfsdiscuss SYSTEM "chapter1/alfsdiscuss.xml">
 <!ENTITY c1-ma-blfsbook SYSTEM "chapter1/blfsbook.xml">
+<!ENTITY c1-ma-blfssupport SYSTEM "chapter1/blfssupport.xml">
+<!ENTITY c1-ma-blfsdev SYSTEM "chapter1/blfsdev.xml">
 <!ENTITY c1-ma-subscribe SYSTEM "chapter1/subscribe.xml">
 <!ENTITY c1-ma-unsubscribe SYSTEM "chapter1/unsubscribe.xml">
 <!ENTITY c1-ma-mailarchive SYSTEM "chapter1/mailarchive.xml">