* Substitue instances of 216 with 218

* Add more debugging information to include when reporting problems with HAL
* Cleanup trailing whitspace
This commit is contained in:
Joe Marcus Clarke 2007-04-16 05:08:27 +00:00
parent c1f618335d
commit 77ba06cd53
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/www/; revision=30047

View file

@ -1,6 +1,6 @@
<!DOCTYPE HTML PUBLIC "-//FreeBSD//DTD HTML 4.01 Transitional-Based Extension//EN" [
<!ENTITY base CDATA "../..">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.121 2006/11/06 20:55:41 marcus Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.122 2007/02/05 01:37:28 pav Exp $">
<!ENTITY title "FreeBSD GNOME Project: GNOME &gnomever; FAQ">
<!ENTITY % navinclude.gnome "INCLUDE">
]>
@ -235,7 +235,7 @@ options _KPOSIX_PRIORITY_SCHEDULING
<p>Starting with 2.16, GNOME now lives in
<tt>LOCALBASE</tt> instead of <tt>X11BASE</tt>.
This move can cause strange build problems if <a
href="&base;/gnome/docs/faq216.html">the proper
href="&base;/gnome/docs/faq218.html">the proper
upgrade steps</a> are not followed. However, if
after following all the steps, you may still see
errors like the following:</p>
@ -357,7 +357,7 @@ libtool: link: `/usr/X11R6/lib/libglade-2.0.la' is not a valid libtool archive
<!-- A5 -->
<p>The &gnomeoldver; to &gnomever; may have a few
caveats. You are strongly advised to read the
<a href="faq216.html">upgrade FAQ</a> for detailed
<a href="faq218.html">upgrade FAQ</a> for detailed
instructions.</p>
</li>
@ -686,7 +686,7 @@ perm pass0 0666
<p>If you encounter problems burning to discs with
nautilus-cd-burner, set the following GConf
<tt>/apps/nautilus-cd-burner/debug</tt> to
<em>true</em> using
<em>true</em> using
<b>Applications &gt; System Tools &gt; Configuration Editor</b>
(<tt>gconf-editor</tt> from the command line). Then
run <tt>nautilus-cd-burner</tt> from the command line,
@ -817,6 +817,15 @@ hald_enable="YES"
<li>Contents of <tt>/etc/fstab</tt></li>
<li>Output of <tt>mount</tt></li>
<li>Full <tt>dmesg</tt> output</li>
<li>Stop hald, then run it manually using
<tt>/usr/local/sbin/hald --daemon=no --verbose-yes</tt>
and provide the output</li>
<li>If using GNOME, and a volume is not mounting
properly, include the output of <tt>gnome-mount --block
--no-ui --verbose --hal-udi &lt;Device UDI&gt;</tt>
(&lt;Device UDI&gt; is the Unique Device Identifier
obtained from the output of <tt>lshal</tt> for the
device that is not mounting properly)</li>
</ol>
<p>You can also mount fixed storage media such as FAT or