IT ...

It's available as Keyboard Shortcut (menu -> Desktops -> Preferences -> Keyboard Shortcuts).

Good for people like me who opens a lot of gnome-terminals.

The symptom,
After displaying "Freeing unused kernel memory ... ", the sytem may or maynot display a few more line, then just stop there. You can still type on keyboard and it will display.

Possible reason,
RAM!!! The system happened to have 2x 128Mb DDR (IBM) and 2x 512Mb DDR (Kingston), remove either set of them, the system return to perfect normal.

We tried to install RedHat ES 3, installation no problem, but after installation, system stop just there, can't start.
CentOS 4.3 also tried, can't find root when boot from CD.
SuSE 10, CD boot stop at "Freeing unused kernel memory ..."

Waste me half a day to discover it.

Inherited from NetSaint, it's a very good tools for sysadmin.

Three main parts current explored by myself,

nagios, nagios-plugin and nagiosweb

Following this link, trying to get pvfs2 1.5.1 running on a small cluster.

./configure --prefix=/opt/pvfs2 --with-kernel=/usr/src/....
make && make install
make kmod && make kmod_install

need corresponding kernel-devel, specifically, kernel-smp-devel package to make kmod.

run pvfs2-client before mount (document not clear enough for me to see this :)

cp opendx-4.3.2-r1.ebuild opendx-4.4.0.ebuild
cp opendx-samples-4.3.2.ebuild opendx-samples-4.4.0.ebuild
(lazy way to upgrade packages :)

ebuild ... digest
motif-config openmotif hdf depended.

transcode + mplayer + ffmpeg for video conversion

msmpeg4v2 is a best format to choose if you want to play in Windows.

transcode -i test.mov -x mplayer,null -y ffmpeg,null -F msmpeg4v2 \
--export_asr 2 -o msmpeg4v2.avi -D0 -E 48000,16,2 -b 224 -N 0x2000 -s2 \
-J modfps --export_fps 15

emerge -avuD world

If you have 8.26.18, it will ask you to downgrade to 8.23.7, on the contrary, if current system has 8.23.7, it will ask you to upgrade to 8.26.18. Why?

---

Here comes the reason, because I have ati-drivers-extra which depends on ati-drivers same version 8.23.7. So when "emerge --deep" found that my system don't have ati-drivers-8.23.7, it will ask for it. But when upgrade from 8.23.7 to 8.26.18, it wont check replace 8.23.7 will break the dependency. A bug for "emerge --deep", right?

How did I find out? I just mask ati-drivers-8.23.7 and wait for emerg --deep to complain, haha.

iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE

Have to make sure the following modules is selected in kernel and preloaded,
/etc/modules.autoload.d/kernel-2.6
ip_tables
iptable_nat
ipt_MASQUERADE

Or else, iptables will give you unknown error, and a very big number, maybe they should detect and load the necessary modules?

modules iptable_filter is not necessary if you want internet sharing only.

BTW, if iptable_filter is not loaded, "iptables -L" will give you a friendly message, that should be the way.

iptables v1.3.5: can't initialize iptables table `filter': Table does not exist (do you need to insmod?)
Perhaps iptables or your kernel needs to be upgraded.

Happily using my MuVo N200, until it starts to auto off so frequently. Google leads me to the creative forums.

People says the problem is due to firmware, and a list of useful firmware list was given here, so I just picked the latest 1.20.04, since I am always going for the latest.

Firmware upgrade always looks quite straightforward, Recovery Mode, run the downloaded executable, Bingo! All problems are gone.

Wait a minute, in fact, it's old problems gone, new problem appears, the volume now goes 0-20 instead of 0-40. At night or other quiet environment, volume 1 is too loud already!

On the forum, someone said that the downgraded from 1.20.04 to 1.12.01 by luck, try and error, no exact steps to follow. So I started to try my luck.

Luckily, I did it also, and there are some steps to follow if you have not found your luck.

1. Connect the MuVo in Recovery Mode, use 1.20.04 firmware, after you see more than 3 blue block, unplug MuVo quickly.

2. Connect it back in normal mode, try to access the file system, it will tell you not formated, say yes to format it. Now you MuVo is just a USB thumb drive, don't worry.

3. Connect in Recovery Mode again, now use 1.12.01 firmware, and let it finish. It takes some time to find, if it can't finish, try again from step 1, or else, you are really unlucky.