cvs commit: www/lfs faq.html roadmap.html

jeroen at linuxfromscratch.org jeroen at linuxfromscratch.org
Sun Jan 11 16:52:35 PST 2004


jeroen      04/01/11 17:52:35

  Modified:    alfs     news-2004.txt
               blfs     faq.html
               faq      index.html
               lfs      faq.html roadmap.html
  Log:
  Added ALFS-1.2.1 release news item. Added new entries to the FAQ: how to upgrade an LFS system, and about using the 2.6 kernel.
  
  Revision  Changes    Path
  1.2       +9 -0      www/alfs/news-2004.txt
  
  Index: news-2004.txt
  ===================================================================
  RCS file: /home/cvsroot/www/alfs/news-2004.txt,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- news-2004.txt	30 Dec 2003 19:12:51 -0000	1.1
  +++ news-2004.txt	12 Jan 2004 00:52:35 -0000	1.2
  @@ -5,6 +5,15 @@
   
   
   --NEWS_ITEM_BOUNDARY
  +Title: nALFS-1.2.1 release
  +Author: Kevin P. Fleming
  +Date: 2004/01/12
  +
  +		<p>The nALFS development team released version 1.2.1 of nALFS today, incorporating three bug fixes from the development branch. The most important of these fixes addresses the issue of downloading files onto a filesystem different from the one nALFS is launched from, which caused errors during profile execution. A complete list of the enhancements in this release can be found in the CHANGES file in the distribution tarball.</p>
  +		<p>Users of version 1.2.0 are encouraged to update to this new release to avoid this problem. If you are interested in updating to this release, or trying it out for the first time, you can <a href="downloads/stable/nALFS-1.2.1.tar.bz2">download it</a>.</p>
  +		<p>We would appreciate any feedback on this release; please your comments or questions to the <a href="http://linuxfromscratch.org/mailman/listinfo/alfs-discuss">alfs-discuss mailing list</a>. </p>
  +
  +--NEWS_ITEM_BOUNDARY
   Title: nALFS-1.2.0 release
   Author: Kevin P. Fleming
   Date: 2003/12/22
  
  
  
  1.35      +1 -1      www/blfs/faq.html
  
  Index: faq.html
  ===================================================================
  RCS file: /home/cvsroot/www/blfs/faq.html,v
  retrieving revision 1.34
  retrieving revision 1.35
  diff -u -r1.34 -r1.35
  --- faq.html	29 Dec 2003 15:23:01 -0000	1.34
  +++ faq.html	12 Jan 2004 00:52:35 -0000	1.35
  @@ -61,7 +61,7 @@
   </div>
   
   <h2>Originally by Seth W. Klein - now maintained by <a href="mailto:jeroen@linuxfromscratch.org">Jeroen Coumans</a></h2>
  -<p>This is a subset of the <a href="../faq/">complete FAQ</a> which deals with BLFS specific questions. Check out the <a href="../faq/">complete FAQ</a> if your question is not BLFS-specific. If you're just beginning with LFS, don't forget to check <a href="../lfs/faq.html">the LFS FAQ</a>.</p>
  +<p><em class="highlight">This is a subset of the <a href="../faq/">complete FAQ</a> which deals with BLFS specific questions. Check out the <a href="../faq/">complete FAQ</a> if your question is not BLFS-specific. If you're just beginning with LFS, don't forget to check <a href="../lfs/faq.html">the LFS FAQ</a>.</em></p>
   
   <h3><a href="#genblfs">General BLFS questions</a></h3>
   <ul>
  
  
  
  1.81      +14 -11    www/faq/index.html
  
  Index: index.html
  ===================================================================
  RCS file: /home/cvsroot/www/faq/index.html,v
  retrieving revision 1.80
  retrieving revision 1.81
  diff -u -r1.80 -r1.81
  --- index.html	31 Dec 2003 09:57:26 -0000	1.80
  +++ index.html	12 Jan 2004 00:52:35 -0000	1.81
  @@ -56,7 +56,6 @@
   		<li><a href="../lfs/faq.html">LFS FAQ</a></li>
   		<li><a href="../blfs/faq.html">BLFS FAQ</a></li>
   		<li><a href="#oldfaq">Old FAQ's</a></li>
  -		<li><a href="#changelog">Changelog</a></li>
   		<li><a href="#thanks">Thanks</a></li>
   	</ul>
   </div>
  @@ -91,13 +90,13 @@
   	<li><a href="#shutdown-on-fsck-error">The system shuts down when fsck errors out!</a></li>
   	<li><a href="#missing-fm-project">The freshmeat project page doesn't exist.</a></li>
   	<li><a href="#how-to-find">How do I find a package or command?</a></li>
  +	<li><a href="#how-to-upgrade">How do I upgrade my LFS/BLFS system?</a></li>
   </ul>
   
   <h3>LFS FAQ:</h3>
   <h3><a href="../lfs/faq.html#fre">Frequently Requested Enhancements</a></h3>
   <ul>
  -	<li id="add-grub"><a href="../lfs/faq.html#add-grub">Why not use GRUB instead of LILO?</a></li>
  -	<li id="why-not-new-lilo"><a href="../lfs/faq.html#why-not-new-lilo">Why not upgrade LILO to the latest version?</a></li>
  +	<li id="add-grub"><a href="../lfs/faq.html#add-grub">Why not use LILO instead of GRYB?</a></li>
   	<li id="why-not-faq"><a href="../lfs/faq.html#why-not-faq">Why not include the FAQ in the book?</a></li>
   	<li id="why-vim"><a href="../lfs/faq.html#why-vim">Why is vim in the book?</a></li>
   	<li id="why-ed"><a href="../lfs/faq.html#why-ed">Why is ed in the book?</a></li>
  @@ -105,6 +104,7 @@
   	<li id="why-not-package-management"><a href="../lfs/faq.html#why-not-package-management">Why isn't some package manager in the book?</a></li>
   	<li id="no-poweroff"><a href="../lfs/faq.html#no-poweroff">How do I make my machine poweroff when shut down?</a></li>
   	<li id="kernel-header-copy"><a href="../lfs/faq.html#kernel-header-copy">Why copy the kernel headers instead of linking them?</a></li>
  +	<li id="kernel-2.6"><a href="../lfs/faq.html#kernel-2.6">I want to use linux-2.6.x in LFS-5.x?</a></li>
   </ul>
   
   <h3><a href="../lfs/faq.html#resources">When reading and building LFS</a></h3>
  @@ -318,6 +318,15 @@
   		</dd>
   	<dt id="how-to-find">How do I find a package or command?</dt>
   		<dd>Please refer to <a href="../lfs/packages.html">the LFS packages webpage</a>.</dd>
  +	<dt id="how-to-upgrade">How do I upgrade my LFS/BLFS system?</dt>
  +		<dd>
  +			<p>You probably know this already, but LFS is not a distro in the traditional sense. It's primary goal is: <cite><a href="http://www.linuxfromscratch.org/lfs/whatislfs.html">teaching people how a Linux system works internally. </a></cite></p>
  +			<p>While this means you have great control over your system ("Your distro. Your rules."), it also has the drawback of having to take care of updating it yourself.</p>
  +			<p>If you've built an LFS system and have extended it to become your primary system, the best thing to do is to decide on an upgrade policy. Do you want to keep the latest version of every package? Then be careful, because you're going to be burned. I recommend slight conservatism when upgrading to keep a healthy system. A general rule of thumb which works for most people is: only upgrade packages if they have security fixes. Subscribe to lfs-security and LWN to keep yourself informed about security fixes. Another rule of thumb is: don't upgrade the toolchain (gcc, glibc and binutils) unless you're going to rebuild your entire system. These packages form the heart of your LFS system, destroying them means destroying the ability to compile packages or even run binaries. </p>
  +			<p>Remember that updating packages is at your own risk. LFS takes great care to present a stable mix of packages which are compatible all the way up to BLFS so you can compile OpenOffice.Org and Java (which are real dinosaurs to compile). This means that your LFS system may get slightly outdated but ensures compatibility and stability. You can compare this to Debian's stable and testing releases, although LFS stable is generally bleeding-edge compared to other distro's. </p>
  +			<p>In general it is safe to upgrade single packages; they'll just overwrite the old contents. Package managers take care of uninstalling old versions, and it's really convenient to have some sort of package management system in place. Have a look at the hints; there are several, ranging from RPM to DEB to TGZ (Slackware) to Checkinstall to package users. </p>
  +			<p>A final comment: what package instructions should you use when updating a package? In general, you can use the standard LFS instructions, although you shouldn't blindly assume they will apply to all packages. To keep yourself informed about upgrades and new package instructions, subscribe to lfs-dev, and if you're really bleeding-edge, lfs-hackers. Keep in mind that these are not support lists but development lists.</p>
  +		</dd>
   </dl>
   <p><a href="#header">Back to the top.</a></p>
   
  @@ -343,15 +352,9 @@
   		<dd>Duplicate of <a href="../blfs/faq.html#undefined-deflate">undefined reference to `deflate'</a>.</dd>
   	<dt id="optimized-glibc-fail"><a href="#optimized-glibc-fail">My optimized build of glibc is failing in spinlock.c</a></dt>
   		<dd>Let's not encourage people to optimize glibc. Besides, <a href="../lfs/faq.html#optimizations">When using optimization flags (setting CFLAGS)</a> should take care of this question.</dd>
  +	<dt id="why-not-new-lilo">Why not upgrade LILO to the latest version?</dt>
  +		<dd>LFS up to 4.1 used LILO 22.2 because later versions require <a href="http://nasm.sourceforge.net/">nasm</a>. Since LFS-5.0, LILO was replaced by GRUB.</dd>
   </dl>
  -
  -<h4 id="changelog">Changelog</h4>
  -	<dl>
  -		<dt>21 October</dt>
  -			<dd>Added <a href="../lfs/faq.html#hjl-binutils">hjl-binutils</a>, text literally copied from Greg and Ryan's purelfs hint</dd>
  -		<dt>30 September</dt>
  -			<dd>Added <a href="../blfs/faq.html#seti">seti</a> on a suggestion from Tushar. Also added some more explanation of the current FAQ setup.</dd>
  -	</dl>
   
   <h4 id="thanks">Thanks</h4>
   	<p>This FAQ is dedicated to all the hard-working people on the support lists who keep me busy with this FAQ ;-). </p>
  
  
  
  1.42      +10 -7     www/lfs/faq.html
  
  Index: faq.html
  ===================================================================
  RCS file: /home/cvsroot/www/lfs/faq.html,v
  retrieving revision 1.41
  retrieving revision 1.42
  diff -u -r1.41 -r1.42
  --- faq.html	3 Jan 2004 19:13:10 -0000	1.41
  +++ faq.html	12 Jan 2004 00:52:35 -0000	1.42
  @@ -62,11 +62,11 @@
   </div>
   
   <h2>Originally by Seth W. Klein - now maintained by <a href="mailto:jeroen@linuxfromscratch.org">Jeroen Coumans</a></h2>
  -<p>This is a subset of the <a href="../faq/">complete FAQ</a> which deals with LFS specific questions. Check out the <a href="../faq/">complete FAQ</a> if your question is not LFS-specific. If you're proceeding with BLFS, don't forget to check <a href="../blfs/faq.html">the BLFS FAQ</a>.</p>
  +<p><em class="highlight">This is a subset of the <a href="../faq/">complete FAQ</a> which deals with LFS specific questions. Check out the <a href="../faq/">complete FAQ</a> if your question is not LFS-specific. If you're proceeding with BLFS, don't forget to check <a href="../blfs/faq.html">the BLFS FAQ</a>.</em></p>
   
   <h3><a href="#fre">Frequently Requested Enhancements</a></h3>
   <ul>
  -	<li><a href="#add-grub">Why not use GRUB instead of LILO?</a></li>
  +	<li><a href="#add-grub">Why not use LILO instead of GRUB?</a></li>
   	<li><a href="#why-not-new-lilo">Why not upgrade LILO to the latest version?</a></li>
   	<li><a href="#why-not-faq">Why not include the FAQ in the book?</a></li>
   	<li><a href="#why-vim">Why is vim in the book?</a></li>
  @@ -75,6 +75,7 @@
   	<li><a href="#why-not-package-management">Why isn't some package manager in the book?</a></li>
   	<li><a href="#no-poweroff">How do I make my machine poweroff when shut down?</a></li>
   	<li><a href="#kernel-header-copy">Why copy the kernel headers instead of linking them?</a></li>
  +	<li><a href="#kernel-2.6">I want to use linux-2.6.x in LFS-5.x?</a></li>
   </ul>
   
   <h3><a href="#resources">When reading and building LFS</a></h3>
  @@ -136,15 +137,11 @@
   
   <h3 id="fre">Frequently Requested Enhancements</h3>
   <dl>
  -	<dt id="add-grub">Why not use GRUB instead of LILO?</dt>
  +	<dt id="add-grub">Why not use LILO instead of GRUB?</dt>
   		<dd>
   			<p>Since LFS-5.0, released 5 November 2003, LFS uses Grub instead of Lilo. Grub was chosen because it doesn't require reinstallation after a kernel upgrade and has a very nice rescue console. </p>
   			<p> If your current setup uses LILO or you'd like to use it anyway, you can, but beware you will also need to install BIN86 and, for the latest LILO versions, NASM. However, don't preach about it on the LFS mailinglists, since we've had many flamewars about it in the past. </p>
   		</dd>
  -	<dt id="why-not-new-lilo">Why not upgrade LILO to the latest version?</dt>
  -		<dd>
  -			<p><em>This FAQ only applies to versions of LFS up until 4.1.</em> LFS-4.1 used LILO 22.2 because later versions require <a href="http://nasm.sourceforge.net/">nasm</a>. While there should be no problem installing nasm, the book and many users were reluctant to install an extra package just for LILO. </p>
  -		</dd>
   	<dt id="why-not-faq">Why not include the FAQ in the book?</dt>
   		<dd>
   			<p>Marc Heerdink may have said it best in a post to lfs-dev:</p>
  @@ -247,6 +244,12 @@
   	 			<li>A post by Linus himself: <a href="http://www.uwsg.iu.edu/hypermail/linux/kernel/0007.3/0587.html">http://www.uwsg.iu.edu/hypermail/linux/kernel/0007.3/0587.html</a>.</li>
   				<li>Kernel Traffic #80, 4. Symlinks In The Kernel; Kernel/Library/etc Interface Dispute: <a href="http://kt.zork.net/kernel-traffic/kt20000814_80.txt">http://kt.zork.net/kernel-traffic/kt20000814_80.txt</a>  (This covers the thread in which the above  post occurred.)</li>
   			</ul>
  +		</dd>
  +	<dt id="kernel-2.6">I want to use linux-2.6.x in LFS-5.x?</dt>
  +		<dd>
  +			<p>Currently, you can't build an LFS system by using linux-2.6.x instead of linux-2.4.x. This is because the kernel headers from 2.6.x are incompatible with other programs in LFS-5.x and will lead to compile errors. It is recommended until LFS releases a new version which includes the 2.6.x kernel; according to the <a href="roadmap.html">roadmap</a> this will be LFS-6.0. </p>
  +			<p>Of course, you are free to install the 2.6.x kernel after you've finished building the LFS system. For this, the <a href="../hints/downloads/files/kernel-2_6-migration.txt">kernel-2_6-migration hint</a> will be an excellent guide.</p>
  +			<p>If you really want to use linux-2.6.x while building LFS, please read the <a href="http://linuxfromscratch.org/pipermail/lfs-hackers/">archives of lfs-hackers</a> (and possibly subscribe to it) and read the excellent <a href="http://www.linuxfromscratch.org/hints/downloads/files/nptl.txt">NPTL hint</a>. </p>
   		</dd>
   </dl>
   <p><a href="#header">Back to the top.</a></p>
  
  
  
  1.5       +1 -0      www/lfs/roadmap.html
  
  Index: roadmap.html
  ===================================================================
  RCS file: /home/cvsroot/www/lfs/roadmap.html,v
  retrieving revision 1.4
  retrieving revision 1.5
  diff -u -r1.4 -r1.5
  --- roadmap.html	19 Dec 2003 12:37:25 -0000	1.4
  +++ roadmap.html	12 Jan 2004 00:52:35 -0000	1.5
  @@ -76,6 +76,7 @@
   	<li>Major Glibc update</li>
   </ul>
   <p>When one or more of the above occurs we will start planning a release date for LFS-6.0.</p>
  +<p>A more up-to-date - although unofficial - version of this document may be found <a href="http://wiki.linuxfromscratch.org/index.php?pagename=Roadmap"> on the Wiki</a>.</p>
   
   </div> <!-- end content -->
   
  
  
  



More information about the website mailing list