通过china-overlay安装pidgin来使用qq和msn

1。在use标记里添加qq，msn
2。在root下面执行以下命令：
emerge layman
sed -i -e 's/\(nocheck.*\)no/\1yes/' /etc/layman/layman.cfg
echo "source /usr/local/portage/layman/make.conf" >> /etc/make.conf
mkdir -p /usr/local/portage/layman
echo PORTDIR_OVERLAY=\"\" > /usr/local/portage/layman/make.conf
USE="-nowebdav" emerge subversion
l ayman -f -a gentoo-china
layman -S
3。emerge pidgin
4。ok，搞定。。。。。。

Firefox关联mplayer打开mms的方法

默认在Linux下mms:// rtsp://关联的都是totem这个播放器
不过这个破烂播放器偏偏又非常不争气，什么都不放不了，只能想办法让Firefox关联mplayer了
上网Google了一番，最后发现能这么处理：
在Firefox的地址栏输入： about:config
在设置页面的任意空白处点击鼠标右键，选择“新建”－>“字符串“。
在弹出的对话框内输入：network.protocol-handler.app.mms
点击确定，在出现的第二个对话框中输入： mplayer
然后确定。
rtsp的也按照同样的方法解决。

最近安装了一边gentoo 的amd64版本的，按照上面的方法性不同了，怎么办呢？
到google搜了很久也解决不了，后来到firefox的官方的社区，找到了解决办法
网址：http://kb.mozillazine.org/Register_protocol#Linux_and_Mac

* Type about:config into the address bar and press Enter.
* Right-click -> New -> Boolean -> Name: network.protocol-handler.external.foo -> Value -> true (Replacing foo with the protocol you're specifying)
* Right-click -> New -> String -> Name: network.protocol-handler.app.foo -> Value -> /path/to/app (Replacing foo with the protocol you're specifying and /path/to/app with the path to the application you want to run.
* Ensure network.protocol-handler.expose-all is set to true.

但是，我发现还有一个方法：
到“Edit->preferences->Applications”
找“mms”和“rtsp”，选择相应的程序就行了。
我就是这么干的。。。呵呵。

关于mask，missing keyword等

1。missing keyword 的解决办法是：
编辑/etc/portage/package.keywrods，加入
比如：
app-emulation/emul-linux-x86-xlibs ~amd64
或者：
= - 比如：
=app-emulation/emul-linux-x86-xlibs-20081109 ~amd64

2。masked by...的解决办法：
编辑/etc/portage/package.unmask，加入
比如：
app-emulation/emul-linux-x86-xlibs
或者：
= - 比如：
=app-emulation/emul-linux-x86-xlibs-20081109
（就是比package.keywords少了个keyword）

毛毛电脑的profile

# /etc/profile: login shell setup
#
# That this file is used by any Bourne-shell derivative to setup the
# environment for login shells.
#

# Load environment settings from profile.env, which is created by
# env-update from the files in /etc/env.d
if [ -e /etc/profile.env ] ; then
. /etc/profile.env
fi

# 077 would be more secure, but 022 is generally quite realistic
umask 022

# Set up PATH depending on whether we're root or a normal user.
# There's no real reason to exclude sbin paths from the normal user,
# but it can make tab-completion easier when they aren't in the
# user's PATH to pollute the executable namespace.
#
# It is intentional in the following line to use || instead of -o.
# This way the evaluation can be short-circuited and calling whoami is
# avoided.
if [ "$EUID" = "0" ] || [ "$USER" = "root" ] ; then
PATH="/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:${ROOTPATH}"
else
PATH="/usr/local/bin:/usr/bin:/bin:${PATH}"
fi
export PATH
unset ROOTPATH

# Extract the value of EDITOR
[ -z "$EDITOR" ] && EDITOR="`. /etc/rc.conf 2>/dev/null; echo $EDITOR`"
[ -z "$EDITOR" ] && EDITOR="/bin/nano"
export EDITOR

if [ -n "${BASH_VERSION}" ] ; then
# Newer bash ebuilds include /etc/bash/bashrc which will setup PS1
# including color. We leave out color here because not all
# terminals support it.
if [ -f /etc/bash/bashrc ] ; then
# Bash login shells run only /etc/profile
# Bash non-login shells run only /etc/bash/bashrc
# Since we want to run /etc/bash/bashrc regardless, we source it
# from here. It is unfortunate that there is no way to do
# this *after* the user's .bash_profile runs (without putting
# it in the user's dot-files), but it shouldn't make any
# difference.
. /etc/bash/bashrc
else
PS1='\u@\h \w \$ '
fi
else
# Setup a bland default prompt. Since this prompt should be useable
# on color and non-color terminals, as well as shells that don't
# understand sequences such as \h, don't put anything special in it.
PS1="`whoami`@`uname -n | cut -f1 -d.` \$ "
fi

for sh in /etc/profile.d/*.sh ; do
if [ -r "$sh" ] ; then
. "$sh"
fi
done
unset sh