r330 - html/trunk/faq

jhuntwork at linuxfromscratch.org jhuntwork at linuxfromscratch.org
Sat Jun 25 19:15:44 PDT 2005


Author: jhuntwork
Date: 2005-06-25 20:15:44 -0600 (Sat, 25 Jun 2005)
New Revision: 330

Modified:
   html/trunk/faq/index.html
Log:
Copied over FAQ content from current site - still want to rework how it's managed

Modified: html/trunk/faq/index.html
===================================================================
--- html/trunk/faq/index.html	2005-06-26 01:15:39 UTC (rev 329)
+++ html/trunk/faq/index.html	2005-06-26 02:15:44 UTC (rev 330)
@@ -3,11 +3,315 @@
 <!--#include virtual="menu.html" -->
     <div class="main">
      <h1>Frequently Asked Questions</h1>
-     <h2>LFS FAQ</h2>
-     <h2>BLFS FAQ</h2>
-     <h2>Who's who:</h2>
-     <ul>
-        <li>Project Leader: ????</li>
-     </ul>
+<h2 id="generalfaq">General FAQ</h2>
+<p>The FAQ is divided in three documents. The general FAQ has links to all questions and answers. The <a href="../lfs/faq.html">the LFS FAQ</a> is a selection of LFS-specific FAQ's and the <a href="../blfs/faq.html">the BLFS FAQ</a> is a selection of BLFS-specific FAQ's.</p>
 
+<h3><a href="#intro">General information about these FAQ's</a></h3>
+<ul>
+	<li><a href="#why-faq">Why this FAQ?</a></li>
+	<li><a href="#what-is-lfs">What is LFS?</a></li>
+	<li><a href="#what-is-blfs">What is BLFS?</a></li>
+	<li><a href="#contribute">How can I contribute to this FAQ?</a></li>
+</ul>
+
+<h3><a href="#support">Support guidelines</a></h3>
+<ul>
+	<li><a href="#newbie">I'm a newbie to Linux or LFS and I need some help?</a></li>
+	<li><a href="#getting-help">Where is the best place to get help?</a></li>
+	<li><a href="#which-list">Which list should I use for what topic?</a></li>
+	<li><a href="#netiquette">How do I address the LFS community?</a></li>
+</ul>
+
+<h3><a href="#frb">Frequently Reported Bugs</a></h3>
+<ul>
+	<li><a href="#wrong-ln-s-command">The "ln -s" commands in the Book are wrong.</a></li>
+	<li><a href="#its-hardlink-not-copy">/bin/foo is a copy of /bin/bar.</a></li>
+	<li><a href="#why-not-version">Can I use a version newer than the one in the Book?</a></li>
+	<li><a href="#new-version">There's a new version of package Foo.</a></li>
+	<li><a href="#delete_key_not_work">The Delete key doesn't work.</a></li>
+	<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>
+
+<h2>LFS FAQ:</h2>
+<h2><a href="../lfs/faq.html#fre">Frequently Requested Enhancements</a></h2>
+<ul>
+	<li id="add-grub"><a href="../lfs/faq.html#add-grub">Why not use LILO instead of GRUB?</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>
+	<li id="hjl-binutils"><a href="../lfs/faq.html#hjl-binutils">Why is HJL's Binutils not in the book?</a></li>
+	<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>
+
+<h2><a href="../lfs/faq.html#resources">When reading and building LFS</a></h2>
+<ul>
+	<li id="what-dist"><a href="../lfs/faq.html#what-dist">What distribution should I use to start from?</a></li>
+	<li id="kernel-modules"><a href="../lfs/faq.html#kernel-modules">How do I compile a kernel or set up modules?</a></li>
+	<li id="gcc-warnings"><a href="../lfs/faq.html#gcc-warnings">Are compiler warnings from GCC bad?</a></li>
+	<li><a href="../lfs/faq.html#dirty-sources">Do I need to keep the source after installing?</a></li>
+	<li id="really-small"><a href="../lfs/faq.html#really-small">How do I make that really small install the book mentions?</a></li>
+	<li id="alpha-fixes"><a href="../lfs/faq.html#alpha-fixes">Is there information about LFS on the Alpha?</a></li>
+	<li id="cross-compile"><a href="../lfs/faq.html#cross-compile">How do I cross compile LFS?</a></li>
+	<li id="dos-text"><a href="../lfs/faq.html#dos-text">What's a DOS format text file?</a></li>
+</ul>
+
+<h2 id="generrors"><a href="../lfs/faq.html#generrors">General compilation errors</a></h2>
+<ul>
+	<li id="gnu-patches"><a href="../lfs/faq.html#gnu-patches">I used a patch from GNU to upgrade. Is that OK?</a></li>
+	<li id="optimizations"><a href="../lfs/faq.html#optimizations">When using optimization flags (setting CFLAGS)</a></li>
+	<li id="config-hang-size_t"><a href="../lfs/faq.html#config-hang-size_t">Why does configure hang at "checking for signed size_t type..."?</a></li>
+	<li id="dirty-sources"><a href="../lfs/faq.html#dirty-sources">I didn't delete the source tree after my last attempt. Do I need to?</a></li>
+	<li id="perm-denied"><a href="../lfs/faq.html#perm-denied">I'm getting `/dev/null: Permission denied'</a></li>
+	<li id="sig11"><a href="../lfs/faq.html#sig11">signal 11 (internal error: Segmentation fault)</a></li>
+	<li id="any-no-such-file"><a href="../lfs/faq.html#any-no-such-file">No such file or directory</a></li>
+	<li id="configure-no-such-file"><a href="../lfs/faq.html#configure-no-such-file">bash: ./configure: No such file or directory</a></li>
+	<li id="bad-interpreter-permission-denied"><a href="../lfs/faq.html#bad-interpreter-permission-denied">./configure: bad interpreter: Permission denied</a></li>
+	<li id="conf-guess-fail"><a href="../lfs/faq.html#conf-guess-fail">configure can't guess my host type.</a></li>
+	<li id="config-not-gnu-c"><a href="../lfs/faq.html#config-not-gnu-c">checking whether we are using GNU C... no</a></li>
+	<li id="cannot-find-lc"><a href="../lfs/faq.html#cannot-find-lc">ld: cannot find -lc</a></li>
+	<li id="where-ncurses-mandrake"><a href="../lfs/faq.html#where-ncurses-mandrake">Where's libncurses.a in Mandrake?</a></li>
+</ul>
+
+<h2 id="packerrors"><a href="../lfs/faq.html#packerrors">Package-specific errors</a></h2>
+<ul>
+	<li id="conflicting-gethostname"><a href="../lfs/faq.html#conflicting-gethostname">Bash: conflicting types for `gethostname'</a></li>
+	<li id="yytext_ptr-undeclared"><a href="../lfs/faq.html#yytext_ptr-undeclared">Modutils: lex.l:429: `yytext_ptr' undeclared"while building modutils</a></li>
+	<li id="perl-missing-separator"><a href="../lfs/faq.html#perl-missing-separator">Perl fails with "*** missing separator.  Stop."</a></li>
+	<li id="unknown-pseudo-op-hidden"><a href="../lfs/faq.html#unknown-pseudo-op-hidden">GCC: Error: Unknown pseudo-op: `.hidden'</a></li>
+	<li id="no-asneeded"><a href="../lfs/faq.html#no-asneeded">GCC: Error: unrecognized option '--as-needed'</a></li>
+	<li id="no-linuxthreads"><a href="../lfs/faq.html#no-linuxthreads">Glibc: "... it is normal to compile GNU libc with the `linuxthreads' add-on..."</a></li>
+	<li id="asm-global-directive"><a href="../lfs/faq.html#asm-global-directive">Glibc: "cannot determine asm global directive".</a></li>
+	<li id="glibc-no-ld_map"><a href="../lfs/faq.html#glibc-no-ld_map">Glibc: "ld.map: No such file or directory".</a></li>
+	<li id="glibc-awk-fail"><a href="../lfs/faq.html#glibc-awk-fail">Glibc fails and mentions BEGIN and END.</a></li>
+	<li id="glibc-nss"><a href="../lfs/faq.html#glibc-nss">Glibc compilation errors out due to a missing nss.h header file</a></li>
+	<li id="sh-utils-getloadavg"><a href="../lfs/faq.html#sh-utils-getloadavg">Sh-tuils: "undefined reference to `getloadavg'".</a></li>
+	<li id="cpp-fails-sanity-check"><a href="../lfs/faq.html#cpp-fails-sanity-check">Ncurses: C++ preprocessor "/lib/cpp" fails sanity check</a></li>
+</ul>
+
+<h2 id="confboot"><a href="../lfs/faq.html#confboot">Configuration and booting issues</a></h2>
+<ul>
+	<li id="lilo-errors"><a href="../lfs/faq.html#lilo-errors">What do those LILO errors mean?</a></li>
+	<li id="unable-to-mount-root"><a href="../lfs/faq.html#unable-to-mount-root">Kernel panic: VFS: unable to mount root fs</a></li>
+	<li id="respawning-too-fast"><a href="../lfs/faq.html#respawning-too-fast">init: Id "1" respawning too fast: disabled for 5 minutes</a></li>
+	<li id="net-pf-x"><a href="../lfs/faq.html#net-pf-x">I'm getting errors about net-pf-?.</a></li>
+	<li id="char-major-10-135"><a href="../lfs/faq.html#char-major-10-135">modprobe: Can't locate module char-major-10-135</a></li>
+	<li id="no-dev-rtc"><a href="../lfs/faq.html#no-dev-rtc">modprobe: Can't locate module /dev/rtc</a></li>
+	<li id="eth0-unknown-interface"><a href="../lfs/faq.html#eth0-unknown-interface">eth0:unknown interface</a></li>
+	<li id="spurious-8259A-interrupt"><a href="../lfs/faq.html#spurious-8259A-interrupt">spurious 8259A interrupt: IRQ14</a></li>
+	<li id="f-hostname"><a href="../lfs/faq.html#f-hostname">My hostname is getting set to "-f"!</a></li>
+	<li id="less-prints-ad"><a href="../lfs/faq.html#less-prints-ad">Why does less (and therefore man) print <AD> instead of hyphens?</a></li>
+</ul>
+
+<h2 id="genblfs"><a href="../blfs/faq.html#genblfs">General BLFS questions</a></h2>
+<ul>
+	<li id="bootcd"><a href="../blfs/faq.html#bootcd">How do I make a bootable CD?</a></li>
+	<li id="quake3"><a href="../blfs/faq.html#quake3">You LFSers play Quake?!?</a></li>
+	<li id="seti"><a href="../blfs/faq.html#seti">Where do I join the LFS SETI team?</a></li>
+</ul>
+
+<h2 id="compissues"><a href="../blfs/faq.html#compissues">Compilation issues</a></h2>
+<ul>
+	<li id="gtk-2_0"><a href="../blfs/faq.html#gtk-2_0">I'm getting errors building a package that requires GTK+,but I've installed GTK+ 2.x.</a></li>
+	<li id="undefined-deflate"><a href="../blfs/faq.html#undefined-deflate">undefined reference to `deflate'</a></li>
+	<li id="missing-x-includes"><a href="../blfs/faq.html#missing-x-includes">X11/Xlib.h: No such file or directory</a></li>
+	<li id="gnome-versions"><a href="../blfs/faq.html#gnome-versions">Any error while building part of Gnome</a></li>
+	<li id="xfree-missing-seperator"><a href="../blfs/faq.html#xfree-missing-seperator">XFree86: Makefile.proto:32: *** missing separator</a></li>
+</ul>
+
+<h2 id="confissues"><a href="../blfs/faq.html#confissues">Configuration issues</a></h2>
+<ul>
+	<li id="how-to-print"><a href="../blfs/faq.html#how-to-print">How do I print?</a></li>
+	<li id="konsole-ps1"><a href="../blfs/faq.html#konsole-ps1">How do I set PS1 in Konsole?</a></li>
+</ul>
+
+<h3 id="intro">General information about these FAQ's</h3>
+
+<dl>
+	<dt id="why-faq">Why this FAQ?</dt>
+		<dd>
+			<p>The FAQ tries to answer questions before they're asked. This saves the trouble of asking them, and sometimes, the trouble of encountering a problem.</p>
+			<p>This does reduce traffic and improve the signal to noise ratio but that is merely a useful side effect.</p>
+			<p>Since the FAQ isn't the natural place to look for information, items should be added to it only if they can't be added to the appropriate documentation. Sometimes it will be necessary to add a pointer to the information in the documentation.</p>
+		</dd>
+	<dt id="what-is-lfs">What is LFS?</dt>
+		<dd>
+			<p>LFS stands for Linux From Scratch which is a project that aims to  teach you about the inner workings of Linux by building a Linux system by downloading, building, and installing the packages yourself.</p>
+			<p>Also check out the <a href="../lfs/whatislfs.html">introduction to LFS</a> written by Gerard Beekmans, the project leader and initiator.</p>
+		</dd>
+	<dt id="what-is-blfs">What is BLFS?</dt>
+		<dd>
+			<p>LFS is a very basic system, in massive contrast to traditional distributions. The reason is this: LFS is not intended to create your system as you want it. It's intended to be just enough to allow you to build your system as you want it. It's not an end, it's a beginning. When you're done with LFS, you've just started building your system.</p>
+			<p>This can be a problem if you're new to Unix systems and want a typical desktop install with X and a web browser but have no idea what packages you need. For this reason, there is Beyond Linux From Scratch, or <a href="../blfs/whatisblfs.html">BLFS</a>.</p>
+		</dd>
+	<dt id="contribute">Contributing to this FAQ.</dt>
+		<dd>
+			<p>Suggestions are more than welcome. The FAQ maintainer can be reached either via direct email or on the <a href="http://linuxfromscratch.org/mailman/listinfo/faq">FAQ mailing list</a>.</p>
+			<p>Useful suggestions include the addition of questions that are actually frequently asked (with well researched answers) and the removal of questions that are obsolete.</p>
+			<p>If you intend to regularly contribute to this FAQ, you might want to subscribe to the FAQ mailinglist. All suggestions, additions (and sometimes removals) of the FAQ's are discussed there. Patches against the FAQ's are also welcome, allthough regular text-based contributions are accepted as well.</p>
+			<p>Everything intended to go in the FAQ without substantial editing must be well thought out, checked, and researched; and written in a style consistent with the existing content.</p>
+		</dd>
+</dl>
+<p><a href="#header">Back to the top.</a></p>
+
+<h3 id="support">Support guidelines</h3>
+<dl>
+	<dt id="newbie">What if I'm a newbie to Linux or LFS?</dt>
+		<dd>
+		<p>If you've read the <a href="../lfs/view/stable/prologue/prerequisites.html">Prerequisites</a> and <a href="../lfs/view/stable/prologue/audience.html">Audience</a> pages you know that the target audience of LFS are intermediate and advanced Linux users. Anybody who has a couple of months experience with Linux and especially the console should be able to successfully assemble his LFS system.</p>
+			<p>While LFS seems like a good guide for newbies to Linux, the reality is actually quite different. Experience with the support channels shows that LFS is hard to grasp and a frustrating experience for newbies because they lack understanding of the basic concepts.</p>
+			<p>Practically, this means that newbies should get some experience before starting with LFS. The <a href="../lfs/view/stable/prologue/prerequisites.html">Prerequisites page</a> lists the minimal required Linux knowledge, but please also read the <a href="../hints/downloads/files/">"Essential pre-reading for life with LFS"</a> hint.</p>
+			<p>These documents and this FAQ are your basic Linux survival guide. You'll have a great time with LFS if you've read them, and may have some difficulty with LFS and the community, but most likely yourself, if you haven't read them.</p>
+		</dd>
+	<dt id="getting-help">Where is the best place to get help?</dt>
+		<dd>
+			<p>When this FAQ fails to help, there are several places to go.</p>
+			<p>If you're having a problem with something in the book, it never hurts to go back over the book. It's surprising how easy it is to overlook little things.</p>
+			<p>If nothing else, reading the appropriate man and info pages will yield useful information on some subject, if not what you were looking for, and ensure that you know enough not to embarrass yourself if you have to ask someone.</p>
+			<p><a href="http://www.tldp.org/">The Linux Documentation Project</a> has the HOW-TOs and a great deal of other documentation. You might find something there.</p>
+			<p>The <a href="../search.html">website's search</a> includes the mailing lists. Many questions have been discussed there at least once. </p>
+			<p>For support-type help, IRC is often best. It's faster, and doesn't clog the mailinglists. There's more information about <a href="../irc.html">the IRC channels</a> on the website.</p>
+			<p>There are two IRC channels of interest. #LFS, which is a community channel, and #lfs-support, which is for support questions. If you are asking a support question, you are more likely to attract competent and friendly help in #lfs-support.</p>
+			<p>As a last resort, there are the mailing lists. People will get frustrated with you if you use the wrong one or cross post. Mailing list information is <a href="../mail.html">on the website</a> and tells which list to use.</p>
+			<p>Please remember to provide enough information when you post to the mailing lists. In <a href="../lfs/view/stable/chapter01/askforhelp.html">chapter 1 of LFS</a> you find a good method for posting. Additionally, someone has written <a href="../hints/downloads/files/errors.txt">a hint</a> which details the error reporting procedure.</p>
+		</dd>
+	<dt id="which-list">Which list should I use for what topic?</dt>
+		<dd>
+			<p>The full answer is on <a href="../mail.html">the mailinglists page</a>, but here is a summary:</p>
+			<ul>
+				<li>Send <em>support</em> questions for the stable released books to lfs-<span
+class="strong">support</span>. For anything which doesn't belong in LFS, use blfs-<span class="strong">support</span>. Users using
+the testing branch or the unstable branch do so at their own risk; we don't have a support list for them. Bug reports are gladly
+accepted however; you can use bugzilla or the respective branch mailing list (lfs-dev for testing, lfs-hackers for unstable). </li>
+				<li>If you are not having trouble following the <em>LFS</em> Book itself, do <em>not</em> email <span class= "strong">lfs</span>-support.</li>
+				<li>Unless you are <em>suggesting an improvement</em> to the LFS Book itself, do not email lfs-dev.</li>
+				<li>Only suggestions concerning the BLFS Book are acceptable on blfs-dev.</li>
+				<li>Things are a little different with blfs-support. Everything that doesn't fit one of the preceding lists fits there except for the price of beer and GNU versus BSD flamewars.</li>
+				<li>The price of beer, GNU versus BSD, and Microsoft versus Linux flamewars are restricted to lfs-chat. These days, hardware discussion should go there as well.</li>
+			</ul>
+			<p>Of special note is that if you mention XFree86, KDE, or GNOME you may be sure that your post does not belong on lfs-dev or lfs-support.</p>
+		</dd>
+	<dt id="netiquette">What about netiquette?</dt>
+		<dd>
+			<p>Here are some practical points of etiquette. They include only those items that will draw mention if missed. Those who've been around project mailing lists awhile will find the first few obvious. There are less obvious items toward the end.</p>
+			<p>The reasons for these points are omitted for brevity, but rest assured, these guidelines are more than just an individual's personal preference.</p>
+			<p>While the text refers to "the lists" exclusively, it doesn't intend to ignore the news groups that mirror the mailing lists.</p>
+			<p>With that out of the way, here are a couple manners oriented items followed by more "mechanical" stuff:</p>
+			<p>Please remember that it is rude to post questions that are answered in commonly available documentation such as the LFS and BLFS Books, this FAQ, the LFS Hints, the appropriate man pages, the list archives, and Google searches. As long as you can demonstrate that you've made an effort to find the answer and you're not offended by a pointer to documentation, no reasonable person will object to your question.</p>
+			<p>Most of the bothersome flamewars start when a newbie posts an obvious question, is then criticized (even in a kindly manner), and becomes publically offended. Please try to avoid this situation. "Wordlessly" pointing to the exact spot in the documentation is sufficient. If you feel you must criticize, please do it via private email, not on the lists. The same applies to anything else that may become heated.</p>
+			<p>The lists have an international membership so slang of all sorts and idiom are likely to be misunderstood. (Witness the recent discussion of "bootstrapping".) Any mention of profanity, politics, war, or religion (even in signatures) is likely to upset someone somewhere in the world so please avoid them as well. Finally, it is considered polite to post in English since many more people on the lists know it than any other language.</p>
+			<p>Now for the more "mechanical" stuff.</p>
+			<ul>
+				<li><strong>Do not post in HTML.</strong> If you use Yahoo, Hotmail, or Outlook and haven't turned HTML off, then it is on. If you're using another mail client, please do check before posting. If you don't know how to turn HTML off, see <a href="http://www.expita.com/nomime.html">http://www.expita.com/nomime.html</a>. <strong>All posts which contain HTML tags will be sent to /dev/null and never reach the list</strong>. Unfortunately, Spamassassin's HTML filter is very strict and will block all posts with HTML or XML-like tags, keep this in mind when posting XML snippets to a list. A commonly used trick is to replace the triangle brackets < > with angel brackets [].</li>
+				<li><strong>Wrap text at 72 characters.</strong> If you do not wish to do this by hand, set your mail client to do it automatically when sending.</li>
+				<li><strong>Reply <em>below</em> quoted text.</strong> Outlook makes this difficult. There is a <a href="http://home.in.tum.de/%7Ejain/software/outlook-quotefix/">plugin to fix Outlook</a>, and <a href="http://home.in.tum.de/%7Ejain/software/oe-quotefix/">one for Outlook Express</a>.</li>
+				<li><strong>Limit signatures to four lines.</strong></li>
+				<li><strong>Trim quoted text,</strong> especially signatures. But <strong>do not trim so that it is confusing to read your reply</strong> without consulting the original.</li>
+				<li><strong>Do not click reply unless you're actually replying to a post.</strong> Use new, or compose, or whatever your mail client calls it, to ask a new question or start a new thread. Reply sets more than just the subject line and will cause your post to appear in the wrong place unless you're actually answering.</li>
+			</ul>
+			<p>The following isn't major, but is useful to know. On the LFS lists, people usually clear the CC field and just mail the list with replies. This is probably not a good idea but is existing practice due to a political situation which is unlikely to change.</p>
+			<p><a href="http://www.ietf.org/rfc/rfc1855.txt">RFC 1855</a> "provides a minimum set of guidelines for Network Etiquette (Netiquette) and functions as a minimum set of guidelines for individuals, both users and administrators</p>
+		</dd>
+</dl>
+<p><a href="#header">Back to the top.</a></p>
+
+<h3 id="frb">Frequently Reported Bugs</h3>
+<dl>
+	<dt id="wrong-ln-s-command">The "ln -s" commands in the Book are wrong.</dt>
+		<dd>
+			<p>No, the "ln -s" commands in the Book are correct. A symlink is just a special file containing the given filename. So that filename is relative to the link, not the working directory when the link is created. Try it and see. More information in <code>man ln</code>.</p>
+		</dd>
+	<dt id="its-hardlink-not-copy">/bin/foo is a copy of /bin/bar.</dt>
+		<dd>
+			<p>Try "ls -i /bin/foo /bin/bar". Are the inode numbers the same? If so, they're not copies, they're hardlinked.</p>
+		</dd>
+	<dt id="why-not-version">Can I use a version newer than the one in the Book?</dt>
+		<dd>
+			<p>If this is your first time building LFS, using a version not in the book or varying from the book in any way is not a good idea. The IRC channel regulars have a saying, "FBBG". As bugz, the resident bot, is quick to say, this means, "Follow Book, Book Good." They and the people on the lists have helped many an unhappy newbie who deviated from the book during that first build.</p>
+			<p>Once you've built a system "by the book", you have a stable knowledge base from which to experiment to your heart's content (or pain, as is often the case.)</p>
+			<p>If you'd like to experiment then check out <a href="http://wiki.linuxfromscratch.org/index.php?pagename=UpdatedVersions">the Wiki page</a> about using the latest versions. Another good resource is <a href="http://www.linuxfromscratch.org/~matthew/lfs_packages.html">Matthew Burgess' homepage</a>.</p>
+		</dd>
+	<dt id="new-version">There's a new version of package Foo.</dt>
+		<dd>
+			<p>If the new version is more than a day old, it is likely that someone has tested the release and reported it on the mailing lists. Please search the archives before posting questions about whether it works.</p>
+			<p>If you'd like to report the new release, follow these steps to avoid making a duplicate report.</p>
+			<ul>
+				<li>Check the <a href="http://freshmeat.net/">freshmeat</a> page for the project to see if it has been updated. If it hasn't, report the release there.</li>
+				<li>If freshmeat has been updated, check <a href="http://bugs.linuxfromscratch.org/">LFS bugzilla</a> (or <a href="http://blfs-bugs.linuxfromscratch.org/">BLFS bugzilla</a>) to see if the release has been posted there.</li>
+				<li>If the release is not in bugzilla, report it to lfs-book (or blfs-book for packages in BLFS). And if you like, test it and report any problems or changes in compilation instructions, too.</li>
+			</ul>
+		</dd>
+	<dt id="delete_key_not_work">The Delete key doesn't work.</dt>
+		<dd>
+			<p>Please read the BLFS <a href="../blfs/view/svn/postlfs/inputrc.html">inputrc page</a>.</p>
+		</dd>
+	<dt id="shutdown-on-fsck-error">The system shuts down when fsck errors out!</dt>
+		<dd>
+			<p>Unix systems normally run sulogin if the normal bootup fsck run errors out so that root can log in and fix it. Because sulogin will accept any password if /etc/passwd is corrupt, the LFS developers decided this was a security risk. Therefore, the LFS bootscripts shut the machine down if fsck errors, and it must be booted with the "init=/bin/bash" kernel parameter to get a root shell. Whether this is wise is beyond the scope of the FAQ, but if it doesn't work for you you'll want to change that boot script before it's too late.</p>
+		</dd>
+	<dt id="missing-fm-project">The freshmeat project page doesn't exist.</dt>
+		<dd>
+			<p>The following Freshmeat pages have been removed recently:</p>
+			<ul>
+				<li>http://freshmeat.net/projects/gnufileutils/</li>
+				<li>http://freshmeat.net/projects/sh-utils</li>
+			</ul>
+			<p>These projects are discontinued and now maintained in the <a href="http://freshmeat.net/projects/coreutils">coreutils</a> project. Future LFS versions will be updated to this package. For LFS-4.1, refer to <a href="../lfs/packages.html">the new LFS packages webpage</a>.</p>
+		</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>
+
+<h3 id="oldfaq">Old and expired FAQ's</h3>
+<dl>
+	<dt id="where-lfs-packages"><a href="#where-lfs-packages">Where are the lfs-packages tarballs or wget scripts?</a></dt>
+		<dd>This entry is obseleted by <a href="../lfs/packages.html">the LFS packages webpage</a>.</dd>
+	<dt id="version-not-in-book"><a href="#version-not-in-book">I'm using a version not in the book. Is that a problem?</a></dt>
+		<dd>There's already a <a href="#why-not-version">FAQ entry</a> which describes this. Since hardly anyone refers to this entry it's obseleted.</dd>
+	<dt id="wheres-which"><a href="#wheres-which">Where's which?</a></dt>
+		<dd>Obseleted by the <a href="../blfs/view/stable/general/which.html">BLFS</a> book.</dd>
+	<dt id="portmap"><a href="#portmap">Where's portmap?</a></dt>
+		<dd>Obseleted by the <a href="../blfs/view/stable/basicnet/portmap.html">BLFS</a> book.</dd>
+	<dt id="lfs-logos"><a href="#lfs-logos">Where can I get LFS Logos?</a></dt>
+		<dd>This entry is obseleted by <a href="../blfs/artwork/">the BLFS artwork webpage</a>.</dd>
+	<dt id="old-sources"><a href="#old-sources">I'm having trouble compiling something really old.</a></dt>
+		<dd>This entry is just really old and probably not relevant anymore.</dd>
+	<dt id="no-dev-eth0"><a href="#no-dev-eth0">Where is /dev/eth0?</a></dt>
+		<dd>Duplicate of <a href="../lfs/faq.html#eth0-unknown-interface">#eth0-unknown-interface</a>. The latter however properly explains how to setup the eth0 interface, which is a much more common question then wether or not it's a device in /dev.</dd>
+	<dt id="how-to-create-user"><a href="#how-to-create-user">How do I create a non-root user?</a></dt>
+		<dd>This information is now <a href="../lfs/view/stable/chapter05/addinguser.html">integrated in the LFS book</a>.</dd>
+	<dt id="xfree-png-lz"><a href="#xfree-png-lz">undefined reference to `deflate'</a></dt>
+		<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>
+
+<h3 id="thanks">Thanks</h3>
+	<p>This FAQ is dedicated to all the hard-working people on the support lists who keep me busy with this FAQ ;-). </p>
+	<p>Thanks go to...</p>
+	<ul>
+		<li>Seth W. Klein for creating and maintaining this FAQ before me.</li>
+		<li>All the guys (and all of the few girls as well, wish there were more of you) on the lists, from whose answers so many of these answers come.</li>
+		<li>Especially those of you who sort out a question, its symptoms, and its answer and mail the lot to me. Your IDs are immortalized in the commit logs (though only for the span of a digital forever, but hey, I try :-)</li>
+		<li>Tushar Teredesai, Chris Lingard, Jeremy Utley, The Cheeze and countless other people who regularly post FAQ links to the support lists.</li>
+		<li>The BLFS editors whose book produces so delightfully few FAQs.</li>
+	</ul>
+
 <!--#include virtual="/common/footer.html" -->




More information about the website mailing list