If you are tracking -stable or -current, make sure that you - do not have NOLIBC_R set in +
If you are tracking -STABLE or -CURRENT, make sure that you
+ do not have NO_LIBPTHREAD set in
/etc/make.conf. If you do, remove it, then rebuild world.
If you still have trouble, please send email to
@@ -310,9 +310,9 @@ ggv
What is the best way to upgrade from GNOME &gnomeoldver; to GNOME &gnomever;? The &gnomeoldver; to &gnomever; does have a few
+ The &gnomeoldver; to &gnomever; may have a few
caveats. You are strongly advised to read the
- upgrade FAQ for detailed
+ upgrade FAQ for detailed
instructions. How do I keep my GNOME &gnomever; components and applications
up-to-date? You are emphatically encouraged to use portupgrade --
- and only portupgrade -- to keep your GNOME
+ You are emphatically encouraged to use portupgrade
+ or portmaster to keep your GNOME
&gnomever; components and applications up-to-date. Update your ports with portupgrade. Update your ports with portupgrade or
+ portmaster. Once you have updated your ports tree (presumably with
cvsup), the following two simple commands will update
@@ -336,16 +337,22 @@ ggv
# portupgrade -a
+ OR Start from scratch. Despite consistent utilization of portupgrade, if
+ Despite consistent utilization of portupgrade
+ or portmaster, 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: Right-click on the Applications menu, and select
Edit Menus. This will invoke the
- gnome-menu-editor tool. Another popular, and
- more fully-featured menu editor, is
- deskutils/alacarte.
+# portmaster -a
+
+
-# pkgdb -fF
# pkg_delete -rf pkg-config\*
# cd /usr/ports/x11/gnome2
# make clean
@@ -500,9 +507,7 @@ Load "type1"
How do I mount my removable media in Nautilus?
-In order for removable volumes (e.g. CD-ROMs, floppy - drives, etc.) to be visible in Nautilus, you must first - set the vfs.usermount sysctl to 1. To - do that, add the following to /etc/sysctl.conf - then reboot:
+As of GNOME 2.16, FreeBSD supports HAL, + a component from the FreeDesktop + 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 + sysutils/gnome-volume-manager is installed. If + you installed x11/gnome2 you already have + gnome-volume-manager installed.
+ +The daemons that must be started prior to logging into + GNOME are, dbus, polkitd, and hald in + that order. To do this, add the following to + /etc/rc.conf, and reboot:
-vfs.usermount=1 +dbus_enable="YES" +polkitd_enable="YES" +hald_enable="YES"-
Next, each user mountpoint must be added to - /etc/fstab. For example, if user marcus - wants to be able to mount a CD under - /home/marcus/cdrom, the following must be in - /etc/fstab:
+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 troubleshooting + information):
--/dev/acd0 /home/marcus/cdrom cd9660 ro,noauto 0 0 -- -
Each additional user would require a similar entry. - Note: the user must own the mountpoint, and have - write access to the device node in question. In the - example above, /home/marcus/cdrom must be owned - by the user marcus, and marcus must have - write access to the /dev/acd0 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.
- -Another important caveat with removable media mounting - to keep in mind is that mount points must be specified - with fully-qualified path names in - /etc/fstab. For example, if /home is - a symlink to /usr/home, you must specify - /usr/home/marcus/cdrom in the example above. - If you do not do this, you will encounter strange - problems trying to access or unmount your volume.
+-http://www.marcuscom.com/tb/packages/6.0-FreeBSD/Latest/ +http://www.marcuscom.com/tb/packages/6.1-FreeBSD/Latest/-
If you are installing on amd64 FreeBSD 6.0, set +
If you are installing on amd64 FreeBSD 6.1, set PACKAGESITE to the following:
-http://www.marcuscom.com/tb/packages-amd64/6.0-FreeBSD/Latest/ +http://www.marcuscom.com/tb/packages-amd64/6.1-FreeBSD/Latest/-
Ade Lovett (ade) offers periodically built amd64 package sets - for all the GNOME 2 meta-ports on his - package building - server.
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 - ${LOCALBASE}/share/mime or - ${X11BASE}/share/mime, where as local MIME types + must be added to + ${LOCALBASE}/share/mime , where as local MIME types must be added to ~/.local/share/mime. In both cases, the procedure is the same.
@@ -926,12 +926,15 @@ gdm-autologin session required pam_permit.soOnce PAM is configured to allow GDM automatic logins, - edit /usr/local/etc/gdm/gdm.conf, and set + edit /usr/local/etc/gdm/custom.conf, and set AutomaticLoginEnable=true, and AutomaticLogin equal to the username for which - you wish to enable automatic logins. For example:
+ you wish to enable automatic logins. Both of these + properties should be placed under the + [security] heading. For example:+[security] AutomaticLoginEnable=true AutomaticLogin=marcus@@ -1026,12 +1029,12 @@ gtk-key-theme-name = "Emacs"
Why do I need confirm access to keyring - every time Nautilus tries to open external share?
+Why do I need confirm access to my keyring + every time Nautilus tries to open an external share?
-You did not mount procfs file system. Which is off - by default in latest releases. Consider adding following - line to your /etc/fstab file:
+You did not mount the procfs file system. Which is off + by default in recent releases of FreeBSD. Consider adding + the following line to your /etc/fstab file:
proc /proc procfs rw 0 0