os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Update the FAQ for GNOME 2.16, including some bits about HAL.

Browse source
This commit is contained in:
Joe Marcus Clarke 2006-10-28 05:53:48 +00:00
parent b106c0d7c7
commit c462a61889
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=28957
1 changed files with 69 additions and 66 deletions
Download patch file Download diff file Expand all files Collapse all files

135
en/gnome/docs/faq2.sgml
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.112 2006/08/19 21:20:35 hrs Exp $">
<!ENTITY date "$FreeBSD: www/en/gnome/docs/faq2.sgml,v 1.113 2006/10/19 13:20:44 pav Exp $">
<!ENTITY title "FreeBSD GNOME Project: GNOME &gnomever; FAQ">
<!ENTITY % navinclude.gnome "INCLUDE">
]>
@ -57,8 +57,8 @@
keybindings in GTK+ applications?</a>
<li> <a href="#q26">Why do I only see generic icons in
Nautilus?</a>
<li> <a href="#q27">Why do I need confirm access to keyring
every time Nautilus tries to open external share?</a>
<li> <a href="#q27">Why do I need confirm access to my keyring
every time Nautilus tries to open an external share?</a>
</ol>
<h2>Full Text </h2>
@ -181,8 +181,8 @@ undefined reference to 'strerror_r'
options _KPOSIX_PRIORITY_SCHEDULING
</pre>
<p>If you are tracking -stable or -current, make sure that you
do <b>not</b> have <tt>NOLIBC_R</tt> set in
<p>If you are tracking -STABLE or -CURRENT, make sure that you
do <b>not</b> have <tt>NO_LIBPTHREAD</tt> set in
<tt>/etc/make.conf</tt>. If you do, remove it, then rebuild world.
If you still have trouble, please send email to
<a href="mailto:&email;@FreeBSD.org">
@ -310,9 +310,9 @@ ggv
<li style="padding-bottom: 0.5em"><a name="q5"></a>
<p><b>What is the best way to upgrade from GNOME &gnomeoldver; to GNOME &gnomever;?</b></p>
<!-- A5 -->
<p>The &gnomeoldver; to &gnomever; does have a few
<p>The &gnomeoldver; to &gnomever; may have a few
caveats. You are strongly advised to read the
<a href="faq214.html">upgrade FAQ</a> for detailed
<a href="faq216.html">upgrade FAQ</a> for detailed
instructions.</p>
</li>
@ -321,11 +321,12 @@ ggv
<p><b>How do I keep my GNOME &gnomever; components and applications
up-to-date?</b></p>
<!-- A6 -->
<p>You are emphatically encouraged to use <tt>portupgrade</tt> --
and <em>only</em> <tt>portupgrade</tt> -- to keep your GNOME
<p>You are emphatically encouraged to use <tt>portupgrade</tt>
or <tt>portmaster</tt> to keep your GNOME
&gnomever; components and applications up-to-date.</p>
<p><u>Update your ports with <tt>portupgrade.</tt></u></p>
<p><u>Update your ports with <tt>portupgrade</tt> or
<tt>portmaster</tt>.</u></p>
<p>Once you have updated your ports tree (presumably with
<tt>cvsup</tt>), the following two simple commands will update
@ -336,16 +337,22 @@ ggv
# portupgrade -a
</pre>
<p>OR</p>
<pre>
# portmaster -a
</pre>
<p><u>Start from scratch.</u></p>
<p>Despite consistent utilization of <tt>portupgrade</tt>, if
<p>Despite consistent utilization of <tt>portupgrade</tt>
or <tt>portmaster</tt>, if
it seems like everything is refusing to build with everything
else, you might save yourself a headache or three by removing
all your GNOME apps and reinstalling them (your data files will
remain untouched). To do this, follow these commands:</p>
<pre>
# pkgdb -fF
# pkg_delete -rf pkg-config\*
# cd /usr/ports/x11/gnome2
# make clean
@ -500,9 +507,7 @@ Load "type1"
<!-- A12 -->
<p>Right-click on the Applications menu, and select
<b>Edit Menus</b>. This will invoke the
<b>gnome-menu-editor</b> tool. Another popular, and
more fully-featured menu editor, is
<tt>deskutils/alacarte</tt>.</p>
<b>alacarte</b> menu editing tool.</p>
</li>
<!-- Q13 -->
@ -687,44 +692,44 @@ Type=Application
<p><b>How do I mount my removable media in
Nautilus?</b></p>
<!-- A19 -->
<p>In order for removable volumes (e.g. CD-ROMs, floppy
drives, etc.) to be visible in Nautilus, you must first
set the <tt>vfs.usermount</tt> sysctl to <tt>1</tt>. To
do that, add the following to <tt>/etc/sysctl.conf</tt>
then reboot:</p>
<p>As of GNOME 2.16, FreeBSD supports <a
href="http://www.freedesktop.org/wiki/Software_2fhal">HAL</a>,
a component from the <a
href="http://www.freedesktop.org/wiki/">FreeDesktop</a>
project. HAL provides seamless hardware integration with
modern UNIX desktop environment such as GNOME. This
means auto-mounting of hardware is as easy as starting a
few daemons at boot time, and making sure
<tt>sysutils/gnome-volume-manager</tt> is installed. If
you installed <tt>x11/gnome2</tt> you already have
<tt>gnome-volume-manager</tt> installed.</p>
<p>The daemons that must be started prior to logging into
GNOME are, <b>dbus</b>, <b>polkitd</b>, and <b>hald</b> in
that order. To do this, add the following to
<tt>/etc/rc.conf</tt>, and reboot:</p>
<pre>
vfs.usermount=1
dbus_enable="YES"
polkitd_enable="YES"
hald_enable="YES"
</pre>
<p>Next, each user mountpoint must be added to
<tt>/etc/fstab</tt>. For example, if user <tt>marcus</tt>
wants to be able to mount a CD under
<tt>/home/marcus/cdrom</tt>, the following must be in
<tt>/etc/fstab</tt>:</p>
<p>That's it! You should now see your USB key drives and
CD-ROMs magically appear on your desktop. However, if
you are having problems with auto-mounting or HAL in
general, you should collect the following (in addition
to other <a
href="&base;/gnome/docs/bugging.html">troubleshooting</a>
information):</p>
<pre>
/dev/acd0 /home/marcus/cdrom cd9660 ro,noauto 0 0
</pre>
<p>Each additional user would require a similar entry.
<b>Note:</b> the user must own the mountpoint, and have
write access to the device node in question. In the
example above, <tt>/home/marcus/cdrom</tt> must be owned
by the user <tt>marcus</tt>, and <tt>marcus</tt> must have
write access to the <tt>/dev/acd0</tt> node. Once all of
that is setup, a CD-ROM icon will appear under the Computer
location in Nautilus. Double-clicking on that icon will mount
the CD, and place an icon on the desktop.</p>
<p>Another important caveat with removable media mounting
to keep in mind is that mount points must be specified
with <em>fully-qualified</em> path names in
<tt>/etc/fstab</tt>. For example, if <tt>/home</tt> is
a symlink to <tt>/usr/home</tt>, you must specify
<tt>/usr/home/marcus/cdrom</tt> in the example above.
If you do not do this, you will encounter strange
problems trying to access or unmount your volume.</p>
<ol>
<li>Output of <tt>lshal</tt></li>
<li>Output of <tt>sysctl -b kern.geom.conftxt</tt></li>
<li>Contents of <tt>/etc/fstab</tt></li>
<li>Output of <tt>mount</tt></li>
<li>Full <tt>dmesg</tt> output</li>
</ol>
<p>Gary Dunn also provides a <a
href="http://www.aloha.com/~knowtree/howto/gnomeSMBmount.html">
@ -798,24 +803,20 @@ net.inet.udp.blackhole
have the correct package directory, you should append
<tt>/Latest/</tt> to it so you can <tt>pkg_add gnome2</tt>
without knowing any additional version numbers. For example,
if you are installing on i386 FreeBSD 6.0, set
if you are installing on i386 FreeBSD 6.1, set
<tt>PACKAGESITE</tt> to the following:</p>
<pre>
http://www.marcuscom.com/tb/packages/6.0-FreeBSD/Latest/
http://www.marcuscom.com/tb/packages/6.1-FreeBSD/Latest/
</pre>
<p>If you are installing on amd64 FreeBSD 6.0, set
<p>If you are installing on amd64 FreeBSD 6.1, set
<tt>PACKAGESITE</tt> to the following:</p>
<pre>
http://www.marcuscom.com/tb/packages-amd64/6.0-FreeBSD/Latest/
http://www.marcuscom.com/tb/packages-amd64/6.1-FreeBSD/Latest/
</pre>
<p>Ade Lovett (ade) offers periodically built amd64 package sets
for all the GNOME 2 meta-ports on his
<a href="http://tinderbox.lovett.com/">package building
server</a>.
</li>
<!-- Q22 -->
<li style="padding-bottom: 0.5em"><a name="q22"></a>
@ -833,9 +834,8 @@ http://www.marcuscom.com/tb/packages-amd64/6.0-FreeBSD/Latest/
<p>New MIME types can be added in one of two places. They
can either be added system-wide for all users, or added
locally on a per-user basis. System-wide MIME types
must be added to either
<tt>${LOCALBASE}/share/mime</tt> or
<tt>${X11BASE}/share/mime</tt>, where as local MIME types
must be added to
<tt>${LOCALBASE}/share/mime</tt> , where as local MIME types
must be added to <tt>~/.local/share/mime</tt>. In
both cases, the procedure is the same.</p>
@ -926,12 +926,15 @@ gdm-autologin session required pam_permit.so
</pre>
<p>Once PAM is configured to allow GDM automatic logins,
edit <tt>/usr/local/etc/gdm/gdm.conf</tt>, and set
edit <tt>/usr/local/etc/gdm/custom.conf</tt>, and set
<tt>AutomaticLoginEnable=true</tt>, and
<tt>AutomaticLogin</tt> equal to the username for which
you wish to enable automatic logins. For example:</p>
you wish to enable automatic logins. Both of these
properties should be placed under the
<tt>[security]</tt> heading. For example:</p>
<pre>
[security]
AutomaticLoginEnable=true
AutomaticLogin=marcus
</pre>
@ -1026,12 +1029,12 @@ gtk-key-theme-name = "Emacs"
</li>
<!-- Q27 -->
<li style="padding-bottom: 0.5em"><a name="q27"></a>
<p><b>Why do I need confirm access to keyring
every time Nautilus tries to open external share?</b></p>
<p><b>Why do I need confirm access to my keyring
every time Nautilus tries to open an external share?</b></p>
<!-- A27 -->
<p>You did not mount <tt>procfs</tt> file system. Which is off
by default in latest releases. Consider adding following
line to your <tt>/etc/fstab</tt> file:</p>
<p>You did not mount the <tt>procfs</tt> file system. Which is off
by default in recent releases of FreeBSD. Consider adding
the following line to your <tt>/etc/fstab</tt> file:</p>
<pre>
proc /proc procfs rw 0 0