我一直碰到的問題是這樣:

# python
Python 2.5.2 (r252:60911, Mar 21 2008, 05:12:12)
[GCC 3.4.6 20060404 (Red Hat 3.4.6-9)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import pycurl
Traceback (most recent call last):
File "", line 1, in
ImportError: libcurl.so.4: cannot open shared object file: No such file or directory
>>>


把浪費的時間跳過，總之就是 pycurl 沒寫好 (怨念總是得目標來發洩)
setup 時候的 –curl-config 就跟你說在 ~/lib 了，還去 /usr/lib 下面找 libcurl.so.4
好吧或許摸 unix 環境的時間還不夠久，總之最後發現只要這樣子就解決掉了

export LD_LIBRARY_PATH=~/lib

真是浪費生命

簡單說就是輕輕碰到 scroll wheel 就會捲個整個畫面，非常的無法使用

剛剛在覺得很煩的時候下定決心去找一下，看看 GNOME 裡面有沒有選項來改變

找到了這篇: Change scroll wheel speed

裡面內容大致就是說那滑鼠會那麼敏感是因為發送出 multiple event

解法就是在 Linux 下面拔起來再重新插回去就好了

Wireless Receiver 似乎是在 Windows 下面時候會跟 Driver 談好送 multiple event

而 GNOME 下面還不認識那些 Event，就會造成捲動大暴走

省得要 root 權限或以後更新跟系統衝突，所以我把東西都安裝在自己的 home directory 下面。原始碼我都丟在 ~/work 下面，然後編好的執行檔是安裝到 ~/build 下面。

TCL

1. 在 ~/work 下面將 TCL 的原始碼抓下來
   

   cvs -d:pserver:anonymous@tcl.cvs.sourceforge.net:/cvsroot/tcl login
   ENTER
   cvs -z3 -d:pserver:anonymous@tcl.cvs.sourceforge.net:/cvsroot/tcl co -P tcl

2. 在 ~/work/tcl/unix 設定 + 編譯
   

   ./configure –prefix=/home/peter/build –includedir=/home/peter/build/include/tcl8.5 –enable-shared –enable-threads –enable-64bit –mandir=/home/peter/build/share/man –enable-man-symlinks –enable-man-compression=gzip && make CFLAGS=”-g -O2 -D_REENTRANT”

3. 安裝
   

   make install

TK

1. 在 ~/work 下面把 TK 的原始碼抓下來
   

   cvs -d:pserver:anonymous@tktoolkit.cvs.sourceforge.net:/cvsroot/tktoolkit login
   ENTER
   cvs -z3 -d:pserver:anonymous@tktoolkit.cvs.sourceforge.net:/cvsroot/tktoolkit co -P tk

2. 在 ~/work/tk/unix 下設定 + 編譯
   

   ./configure –prefix=/home/peter/build –includedir=/home/peter/build/include/tcl8.5 –with-tcl=/home/peter/build/lib –enable-shared –enable-threads –enable-64bit –enable-man-symlinks –enable-man-compression=gzip –enable-xft && make CFLAGS=”-g -O2 -D_REENTRANT”

3. 安裝
   

   make install

aMSN

1. 在 ~/work 把 aMSN 的原始碼抓下來
   

   svn co https://amsn.svn.sourceforge.net/svnroot/amsn/trunk/amsn amsn

2. 在 ~/work/amsn 下設定 + 編譯
   

   ./configure –with-tcl=/home/peter/build/lib –with-tk=/home/peter/build/lib –prefix=/home/peter/build
   make

3. 安裝
   

   make install

桌面捷徑

1. 建立 ~/bin/amsn.sh 並把 amsn.sh 設成執行檔
   

   #!/bin/sh
   /home/peter/build/bin/wish8.5 /home/peter/build/bin/amsn

2. 建立 ~/Desktop/aMSN.desktop
   

   [Desktop Entry]
   Version=1.0
   Encoding=UTF-8
   Name=aMSN
   Comment=Flock Web Browser
   Exec=”/home/peter/bin/amsn.sh”
   GenericName=aMSN
   Icon=/home/peter/work/amsn/desktop-icons/128×128/apps/amsn.png
   Path=$HOME/work/amsn
   StartupNotify=true
   Terminal=false
   TerminalOptions=
   Type=Application
   X-KDE-SubstituteUID=false
   X-KDE-Username=
   Categories=Network;Application;
   GenericName[en_US]=aMSN

效果比較

Blogged with Flock

Tags: amsn, antialiasing, font, ubuntu

1. 在 Restricted Drive Manager 停用 nVidia 的 Driver
2. 去 nVidia 官方網站抓最新的 Linux Driver 讓他裝
3. 在 Restricted Drive Manager 啟用 nVidia 的 Driver
4. 用 nVidia X Server Setting 來設定 TwinView

FASTTRAK 378 RAID 0

1. 安裝 dmraid: sudo apt-get install dmraid
2. 建立 mount point: sudo mkdir /media/raid0
3. 測試: sudo mount /dev/mapper/pdc_cbchadihee1 /media/raid0
4. 最後再把這個 mount point 寫入 /etc/fstab 讓下次重開時候自動 mount

GCIN

1. 在 Synaptic 裡面把 SCIM uninstall 掉然後安裝 GCIN
2. 在 shell 裡面輸入 im-switch -s gcin
3. 把 ~/.gtkrc.mine 改成:
   

   export GTK_IM_MODULE=gcin
   export LC_CTYPE=”zh_TW.UTF-8″

4. 登出再登入

Sound

1. 打開 System / Preferences / Sound
2. 把 Sound playback 選成 VIA 8237

Desktop Effect

1. sudo apt-get install ccsm
2. System / Advanced Desktop Effects Settings

Fonts

1. 安裝微軟正黑體:
   

   sudo cp msjh* /usr/share/fonts
   sudo chmod o+rx /usr/share/fonts/msjh*
   sudo fc-cache -f -v

2. 打開 Firefox: Edit / Preferences 然後把所有字體預設都改成 Microsoft JhengHei 省得麻煩

sshfs

sudo apt-get install sshfs
adduser peter fuse

GDM Dead Keyboard
這個奇怪的問題似乎有人碰過: Keyboard not funtioning at login。問題應該是像上面那篇文章寫的一樣，不知道為什麼 gdm 會比其他的 getty 開啟的更早，導致 keyboard 的控制被 getty 拿去，然後 gdm 下啥都不能做了囧。我用比較簡單的解法：

1. 把 gdm 預設關閉：mv /etc/rc2.d/S30gdm /etc/rc2.d/K70gdm
2. 在 /etc/rc.local 加入：service gdm start

Wine + Wine Doors

1. Wine:
   

   wget -q http://wine.budgetdedicated.com/apt/387EE263.gpg -O- | sudo apt-key add -
   sudo wget http://wine.budgetdedicated.com/apt/sources.list.d/feisty.list -O /etc/apt/sources.list.d/winehq.list
   sudo apt-get update
   sudp apt-get install wine

2. Wine Doors: 去這裡下載最新的 deb 然後讓 Package Manager 自動安裝

Microsoft IntelliMouse Explorer

1. 修改 /etc/X11/xorg.conf:
   

   Section “InputDevice”
   Identifier “Mouse0″
   Driver “mouse”
   Option “CorePointer”
   Option “Device” “/dev/psaux”
   Option “Protocol” “ExplorerPS/2″
   Option “Buttons” “7″Option ”
   ButtonMapping” “1 2 3 4 5″
   Option “ZAxisMapping” “6 7″
   Option “Resolution” “100″
   EndSection

2. 安裝 imwheel: sudo apt-get install imwheel
3. 修改 /etc/X11/imwheel/imwheelrc:
   

   “.*” None,Up,Alt_L|Left None,Down,Alt_L|Right”^firefox-bin$”
   None,Left,Alt_L|Left
   None,Right,Alt_L|Right

4. 新增 /etc/X11/Xsession.d/57xmodmap:
   

   #/bin/bash
   xmodmap -e “pointer = 1 2 3 6 7 4 5″

5. 把 /etc/X11/Xsession.d/57xmodmap 改成執行檔: sudo chmod 755 /etc/X11/Xsession.d/57xmodmapservice

ln -s /usr/include /opt/include
ln -s /usr/lib64 /opt/lib

Now configuring with new location:

./configure --prefix=/usr/local --enable-force-cgi-redirect --enable-fastcgi --with-libxml --with-zlib --with-bz2 --with-curl  --with-gd --enable-mbstring --with-mysql --with-jpeg-dir=/opt --with-png-dir=/opt --with-mysql=/opt

1. Launching remote firefox session, which takes your patient and the hassle of all those x window configs.
2. Setup VPN on the server, and use server’s IP to to whitelist itself.

But the connection between the VPS server and Shared Host’s MySQL database is insecure. It’s natural to come to this conclusion as the best option: ssh tunnel.

Assuming you have shell access to both VPS and Shared Host, and both are running OpsnSSH.

Setup Public Key Authentication

1. Login to VPS with account you want to create the tunnel

2. cd ~/.ssh

   (create it if not exist)

3. ssh-keygen -t dsa

4. Securely transfer id_dsa.pub to the Shared Hosting’s home directly, something like this:

   scp id_dsa.pub sharedhost:/home/username/.ssh/server_id_psa.pub

5. Login to Shared Host

6. cd ~/.ssh
   cat server_id_psa.pub >> authorized_keys

7. Switch back to VPS, try logging into Shared Host using public key authentication:

   ssh username@sharedhost

   If everything is setup properly, no password is prompted.

If in doubt, [this] is a good place to consult about Public Key Authentication.

Setting up a host name

When MySQL is connecting to localhost, it will try to use socket, regardless of the efforts trying to tell it the service is actually not running on localhost, but rather a tunnel to a remote host. To overcome this issue, create an entry in /etc/hosts:

127.0.0.1 localhost mysqlhost

This points the host name ‘mysqlhost’ to 127.0.0.1 which essentially is also localhost, but mysql is too dumb to understand.

Create the tunnel

1. First, stop the local mysqld. As root:

   service stop mysqld

2. Login to VPS with username previously configured with public key authentication to Shared Host
3. create tunnel:

   ssh -f username@sharedhost -N -L 3306:localhost:3306

   This creates a ssh tunnel in background and forward connection to port 3306 on localhost to port 3306 on sharedhost.

4. Make change in php to reflect the database names, users, password on Shared Host, and most importantly, instead of localhost, use mysqlhost in configuration files.

Automate the process

What if the ssh tunnel died? What if the VPS restarts? How to make sure the connection stays live? The answer is to use autossh.

1. As root:

   yum install autossh

2. Edit /etc/rc.d/rc.local, add this line at the bottom:

   su VPSusername -c 'autossh -M 5307 -f SHAREDHOSTusername@sharedhost -N -L 3306:*:3306' &

   This tells the server to execute the command in ‘ ‘ as VPSusername and put the process into background at startup. autossh will use port 5307 to monitor the ssh tunnel to sharedhost, and reconnect if it drops. Also make sure to disable the local MySQL daemon from starting automatically, or the tunnel cannot be created.

   ]]> http://blog.tarotoast.com/2007/04/15/364/feed/ 0 http://blog.tarotoast.com/2007/04/15/363/#utm_source=rss&utm_medium=rss&utm_campaign=openvpn-on-fc4-note http://blog.tarotoast.com/2007/04/15/363/#comments Sun, 15 Apr 2007 21:19:16 +0000 tarotoast http://blog.tarotoast.com/2007/04/15/363/ Server
   1. yum install openvpn
   2. cp -R /usr/share/openvpn/easy-rsa /etc/openvpn
   3. cd /etc/openvpn/easy-rsa
   4. vim vars:

      # easy-rsa parameter settings
      # NOTE: If you installed from an RPM,
      # don't edit this file in place in
      # /usr/share/openvpn/easy-rsa --
      # instead, you should copy the whole
      # easy-rsa directory to another location
      # (such as /etc/openvpn) so that your
      # edits will not be wiped out by a future
      # OpenVPN package upgrade.
      # This variable should point to
      # the top level of the easy-rsa
      # tree.
      
      export D=`pwd`
      
      # This variable should point to
      # the openssl.cnf file included
      # with easy-rsa.
      
      export KEY_CONFIG=$D/openssl.cnf
      
      # Edit this variable to point to
      # your soon-to-be-created key
      # directory.
      #
      # WARNING: clean-all will do
      # a rm -rf on this directory
      # so make sure you define
      # it correctly!
      
      export KEY_DIR="/etc/openvpn/keys"
      
      # Issue rm -rf warning
      
      echo NOTE: when you run ./clean-all, I will be doing a rm -rf on $KEY_DIR
      
      # Increase this to 2048 if you
      # are paranoid.  This will slow
      # down TLS negotiation performance
      # as well as the one-time DH parms
      # generation process.
      
      export KEY_SIZE=1024
      
      # These are the default values for fields
      # which will be placed in the certificate.
      # Don't leave any of these fields blank.
      
      export KEY_COUNTRY=US
      export KEY_PROVINCE=CA
      export KEY_CITY=SANDIEGO
      export KEY_ORG="TAROTOAST.COM"
      export KEY_EMAIL="chang.peter@gmail.com"

   5. chmod 700 *
   6. mkdir /etc/openvpn/keys
   7. make sure in Bash shell (still at /etc/openvpn/easy-rsa directory)
   8. ./vars
   9. ./clean-all
   10. ./build-ca
       Enter ROOTCA for common name
   11. ./build-key-server server
       Enter ROOT for common name
   12. ./build-key [computername] <– repeat for # of computers want to allow connect
       Enter [computername] as common name
       EX: ./build-key AMD64
       EX: ./build-key X40
   13. ./build-dh
   14. vim /etc/openvpn/server.conf:

       port 1194
       proto tcp
       dev tun
       ca keys/ca.crt
       cert keys/server.crt
       key keys/server.key
       dh keys/dh1024.pem
       server 10.11.12.0 255.255.255.0
       client-config-dir ccd
       push "dhcp-option DNS SERVERIP"
       push "dhcp-option DNS SERVERDNS"
       ifconfig-pool-persist ipp.txt
       push "redirect-gateway"
       keepalive 10 120
       comp-lzo
       persist-key
       persist-tun
       status server-tcp.log
       verb 3

   15. Create log files: touch /etc/openvpn/server-tcp.log /etc/openvpn/ipp.txt
   16. vim /etc/init.d/openvpn:
       Uncomment line 114

       /sbin/modprobe tun >/dev/null 2>&1

       Insert after line 115

       iptables -t nat -A POSTROUTING -s 10.11.12.3 -j SNAT --to SERVERIP
       iptables -t nat -A POSTROUTING -s 10.11.12.4 -j SNAT --to SERVERIP
       iptables -t nat -A POSTROUTING -s 10.11.12.5 -j SNAT --to SERVERIP
       iptables -t nat -A POSTROUTING -s 10.11.12.6 -j SNAT --to SERVERIP
       iptables -t nat -A POSTROUTING -s 10.11.12.7 -j SNAT --to SERVERIP
       iptables -t nat -A POSTROUTING -s 10.11.12.8 -j SNAT --to SERVERIP
       iptables -t nat -A POSTROUTING -s 10.11.12.9 -j SNAT --to SERVERIP
       iptables -t nat -A POSTROUTING -s 10.11.12.10 -j SNAT --to SERVERIP

   17. service openvpn start

   Client (Windows Vista with UAC on)

   1. Download and install OpenVPN Gui 1.0.3 with OpenVPN 2.0.9 [Here]
   2. Scary warning will pop up telling you the driver will not work, install it anyway. OpenVPN’s developers fixed it already.
   3. Make a shortcut on desktop to GUI executable “C:\Program Files\OpenVPN\bin\openvpn-gui-1.0.3.exe”
   4. Use WinSCP to download these files onto the client computer:
      /etc/openvpn/keys/ca.crt
      /etc/openvpn/keys/AMD64.key
      /etc/openvpn/keys/AMD64.crt
   5. Put above files along with this VPNServer.ovpn in C:\Program Files\OpenVPN\config
      VPNServer.ovpn

      client
      dev tun
      proto tcp
      remote SERVERIP 1194
      resolv-retry infinite
      nobind
      persist-key
      persist-tun
      ca ca.crt
      cert AMD64.crt
      key AMD64.key
      ns-cert-type server
      push "dhcp-option DNS SERVERIP"
      push "dhcp-option DNS SERVERDNSIP"
      comp-lzo
      verb 3
      route-method exe
      route-delay 2
      

   6. Right click on the shortcut to openvpn-gui-1.0.3.exe, select Run As Administrator
   7. On the taskbar, right click the openvpn gui icon, select connect

   DONE [aha

   The above mostly follows [this thread] except some minor changes in client side config.

   ]]> http://blog.tarotoast.com/2007/04/15/363/feed/ 1 http://blog.tarotoast.com/2007/04/04/360/#utm_source=rss&utm_medium=rss&utm_campaign=bluehost-%25e7%25ad%2586%25e8%25a8%2598 http://blog.tarotoast.com/2007/04/04/360/#comments Wed, 04 Apr 2007 22:47:32 +0000 tarotoast http://blog.tarotoast.com/2007/04/04/360/ 結果選了 Bluehost。原因很多而且說不清，但是簡單說就是讀了很多 BH Forum 上面的文章後最後 follow my heart 所作的決定。是不是因為裡面 moderator 說 BH 是 CEO 的 baby 我不知道，反正綜合了很多文章最後內心裡面的奇妙邏輯決定要 BH 的。

   有關 BH 的一些 note:

   Installing SVN 1.4.3 (source)

   #
   
   # this is how I installed subversion 1.4.3 on my bluehost account
   
   #mkdir ~/src
   
   # get and make 'apr-0.9.13' (this isn't included in the subversion tarball)
   
   cd ~/src
   
   wget http://apache.ausgamers.com/apr/apr-0.9.13.tar.gz
   
   tar -xzf apr-0.9.13.tar.gz
   
   cd apr-0.9.13
   
   ./configure --prefix=$HOME
   
   make
   
   make install
   
   # get and make 'apr-util 0.9.13' (this isn't included in the subversion tarball either)
   
   cd ~/src
   
   wget http://apache.planetmirror.com.au/dist/apr/apr-util-0.9.13.tar.gz
   
   tar -xzf apr-util-0.9.13.tar.gz
   
   cd apr-util-0.9.13
   
   ./configure --prefix=$HOME --with-apr=$HOME
   
   make
   
   make install
   
   # get and make 'subversion-1.4.3'
   
   cd ~/src
   
   wget http://subversion.tigris.org/downloads/subversion-1.4.3.tar.gz
   
   tar -xzf subversion-1.4.3.tar.gz
   
   cd subversion-1.4.3
   
   ./configure --prefix=$HOME --without-berkeley-db --with-zlib --with-ssl
   
   # at this point there's a bit of complaining about berkeley db, let's ignore that...
   
   make
   
   make install
   
   # check it works!
   
   cd
   
   svn --version
   
   # yay!

   SSH

   Helpdesk 裡面說要寫信到 support@bluehost.com，但是其實不是。寫過去只會被退回說現在必須開 ticket 才行。正確做法是進入 cPanel (BH 的 cPanel 好像比 HM 的好看) 然後注意看右下角會看到一個 SSH Access 的選像，點下去就會把你丟到正確的地方了。填好資料 (domain name 和 cPanel 的密碼) 然後送出後的下一頁就可以夾帶檔案。把駕照用數位相機拍下來夾上去就 ok 了。

   SSH 是個 chroot 的環境，但是但部分軟體像上面那樣，只要 configure 實後記得加 –prefix=$HOME 其實都可以裝。有個很爛的就是他對外所有連結只能 port 80。不能 ssh 回家耶，不能 sftp 回家耶，有沒有爛到這種程度 \囧/

   Domains

   BH 只收 5 個 addon domain，加上原本的 master domain，全部只能有 6 個。搞不好我會開始反悔了。不過說真的她資料夾的放法有夠弱，我還不知道有比 1&1 更弱的放法。她所有 addon domain 的資料夾都是掛在 ~/public_html/ 下面，並不能由選單上面選擇說你要放在 ~/domains/domain1/ 之類的更合邏輯的資料夾。根據 forum 上指出，其實打電話去可以叫 tech support 幫忙手動改，所以可能會等把所有 addon 都放上後再一次看哪些要改全部一起改吧。

   Support

   他們的 Support 系統如果拿 1&1 的來比的話，1&1 根本是大便。電話打進去如果沒有馬上接起來的話，會每分鐘跟妳說你前面還有幾個人在等，我等最久也才 5 分鐘左右。跟 1&1 的 3x 分再加後面的 1x 分 on hold 比起來，天使吧。

   他們的 Ticket 也回應頗快，每個丟出去的 Ticket 都有個 Due Time，都是 12 HR 內得回應。好吧目前為止我只丟了兩個，但是這兩個都有在時限內回，而且都回的頗快的。至少到目前為止都還很滿意。

   Bandwidth

   從台灣學網對 1&1 和對 BH 的速度比起來，BH 很明顯快太多了 (160KB/s vs 38KB/s)，然後我從家裡對 1&1 和 BH 的測試則是 1&1 略快。不過可能是 BH 對每個 TCP connection 有限制，所以我把 FlashGet 調成 6 條後速度也是一樣 max 在 cable 的頻寬。1&1 <–> BH 的速度還真黑皮，每個 TCP connection 的速度都是 1MB/s，然後同時 wget 四個檔，全部也都是 1MB/s。

   將陸續增加..

   ]]> http://blog.tarotoast.com/2007/04/04/360/feed/ 3 http://blog.tarotoast.com/2007/03/13/350/#utm_source=rss&utm_medium=rss&utm_campaign=logitechs-strategy-to-rip-you-off-with-windows-vista http://blog.tarotoast.com/2007/03/13/350/#comments Tue, 13 Mar 2007 12:04:05 +0000 tarotoast http://blog.tarotoast.com/2007/03/13/350/ So, I have this Logitech QuickCam® Messenger™ that I bought last summer, it’s a dual pack combo so I can put the other back at home. I recently upgraded my computer to Vista and guess what I find out:

   This Camera will not work with Windows Vista. Please see our list of newer Vista compatible cameras.

   This is the exact phrase I see when I tried to download driver from Logitech’s . So my first thought is that, ok, maybe it wasn’t working properly so they’d call it “will not work”. I decided to download its driver for XP and see if it will install. Following the instruction of the (32.2MB) installer, I need to restart my computer for it to finish the installation. Sure, will do. After restart, hmm, Windows still can’t find the drivers it wants, ok maybe Logitech is right, this is not working for Vista.

   My laptop is running Windows XP so I don’t really bother trying to get the webcam working on Vista. The (32.2MB) file just sits there and do nothing. I later installed WinRAR because I wanted to open some supposed to be lame video a friend sent me. Guess what, since now that I have WinRAR installed, I can right click on the driver installer (qc848enu.exe) and choose to extract to folder. I don’t need a stupid little icon on my taskbar just to make sure I am aware that a webcam is installed anyway.

   Now that I have WinRAR installed (I really didn’t want to install it actually), files extracted, I can try installing drivers manually. Windows Vista has more steps than XP to get to the browse-for-your-driver page. After I am there, I point the Wizard to look under the Drivers folder within the extracted files of the installer (qc848enu.exe). Guess what, Vista found all the drivers it needs and this webcam is working now.

   Yeah, it should right? You can pretty much use XP’s (32bit) driver in Vista (x86) anyway. My FastTrak 376/378 driver is for 2000/XP/2003 and it’s working like what it should under Vista. Now it makes me wonder why Logitech says it won’t work?

   • Geeksquad can show the message to an old granpa or grandma and charge them part and labor for getting a new webcam.
   • Some know-where-to-download-driver computer newbie sees that message and will decide to get a new webcam.
   • It’s technically way too difficult to have a properly written installer for this particular webcam.

   Maybe, but I think this makes the most sense:

   • Just say it won’t work and don’t even bother upgrading the installer so people who can’t install it will have to buy a new webcam. Yeah, go get that $120 Logitech QuickCam Orbit MP, it not only tracks your move, you also get a Vista driver installer (85MB)!!!

   Well, I guess this is how you push forward to “encourage” upgrade, maybe?

   Update (5/17) : Thanks for Shawn to point out that there is now a Vista ready driver that was in question.

   ]]> http://blog.tarotoast.com/2007/03/13/350/feed/ 4