What is Linux

Why you cannot make your command or parameter complete by pushing TAB under Ubuntu

2012-01-12T14:37:00.003+08:00

Just find out the package name for this function, and keep this info here in case forget this name.
*bash-completion

Who enable this function? The answer is bash script.

1. ~/.bashrc
2. /etc/profile

You can also check which package support this or program it by yourself.
/etc/bash_completion.d

Adobe Reader cht fontpack for Ubuntu

2011-05-09T17:01:00.002+08:00

- Install adobereader 9 in s/w center
- download the fontpack from [1]
- unpack the fontpack and execute the INSTALL file
- Done

[1] ftp://ftp.adobe.com/pub/adobe/reader/unix/9.x/9.1/misc/

How to change the "indicator" default setting, like mail agent

2010-07-26T11:02:00.004+08:00

There is no setting option in gconf-editor or panel properties.
But you can just use the file to change the preferred application.

- In /usr/share/indicators/messages/applications/ there are some files, like empathy/evolution/gwibber in my folder by default.
- You can add a "thunderbird" file.
- And add a line in it as "/usr/share/applications/thunderbird.desktop".
- Then~~~you will see the indicator show you "Mozilla Thunderbird" dynamically.

Enable/Calibrate touch screen on EeeTop ET1602 for Ubuntu 10.04 (Lucid)

2010-07-23T08:48:00.003+08:00

Have a chance to port Lucid on the EeeTop machine. There are some problems in touchscreen and resolution, and here is how to fix it.

1. touchscreen
In Lucid, evdev is the default driver for X input devices, but it's not useful for this type machine. So you need to install the "evtouch" driver, the package name is "xserver-xorg-input-evtouch".

aptitude install xserver-xorg-input-evtouch

Then you need to modify the default xorg.conf (create a new one under /etc/X11/), and below is the details.

--------------------------
Section "ServerLayout"
Identifier "Default Serverlayout"
Screen 0 "Default Screen" 0 0
InputDevice "Touch0"
EndSection

Section "Device"
Identifier "Configured Video Device"
Driver "intel"
Option "monitor-VGA" "VGA"
Option "monitor-VGA1" "VGA1"
Option "NoDCC"
Option "FramebufferCompression" "off"
EndSection

Section "InputDevice"
Identifier "Touch0"
Driver "evtouch"
Option "device" "/dev/input/evtouch"
Option "MinX" "1"
Option "MinY" "1"
Option "MaxX" "4096"
Option "MaxY" "4096"
Option "ReportingMode" "Raw"
Option "Emulate3Buttons" "false"
Option "Emulate3Timeout" "50"
Option "SendCoreEvents" "on"
Option "MoveLimit" "0"
EndSection

Section "Monitor"
Identifier "VGA"
ModeLine "1366x768" 85.600 1366 1430 1542 1798 768 771 777 795 +hsync +vsync
EndSection

Section "Monitor"
Identifier "VGA1"
ModeLine "1366x768" 85.600 1366 1430 1542 1798 768 771 777 795 +hsync +vsync
EndSection

Section "Monitor"
Identifier "Configured Monitor"
ModeLine "1366x768" 85.600 1366 1430 1542 1798 768 771 777 795 +hsync +vsync
EndSection

Section "Screen"
Identifier "Default Screen"
Monitor "Configured Monitor"
Device "Configured Video Device"
DefaultDepth 24
Subsection "Display"
Modes "1366x768"
EndSubsection
EndSection

--------------------------

And also need to add "69-touchscreen.rules" udev rule under /etc/udev/rules.d
notes: check sysfs by the command
udevadm info -ap /sys/class/input/event8

--------------------------
KERNEL=="event*", SUBSYSTEM=="input", ATTRS{idVendor}=="1bfd", ATTRS{idProduct}=="1688", SYMLINK+="input/evtouch"
--------------------------

BTW, explain how I have the right "ModeLine" parameters here.
We can use the "PowerStrip" tool (Windows tool) to have the values.
Below is the link to teach you how to get the right values by PowerStrip.

http://www.x.org/wiki/FAQVideoModes#ObtainingmodelinesfromWindowsprogramPowerStrip

Some Linux tips

2010-03-15T11:32:00.004+08:00

1. share the shell screen
user a# screen -S test
user b# screen -x test
then both a and b can use the shared shell screen to watch the status.

2. how to show your IP address (a little boring and stupid...^^)
ifconfig | grep "eth0" -A 1|sed '1d'|awk '{print $2}'|awk -F: '{print $2}'

3. how to show your VGA driver name (still need to see /var/log/Xorg.0.log for details)
lspci -v|grep VGA -A 10|grep modules

4. How to clean all gnome panel applet default settings
gconftool-2 --recursive-unset /apps/panel
kill gnome-panel --> it will make gnome-panel refresh again.

-- Need to maintain ---

Linux sound architecture - pulseaudio/alsa/codecs

2009-11-18T13:21:00.008+08:00

Below is the processes of sound architecture what I know.
Only base on alsa architecture, and be aware OSS is not supported by Linux anymore.
*recording
mic --> audio codec --> audio codec interface (snd_hda_codec) --> alsa kernel driver --> /dev/snd/* --> alsa api --> alsa lib (you can have the different recording type here) --> sound recorder

*playing
totem --> gstreamer --> pulseaudio --> alsa lib --> alsa api --> alsa kernel --> /dev/snd/* --> alsa kernel driver --> audio controller driver --> audio controller --> speaker

** Vocabulary **
gstreamer : for some codecs that default doesn't support, like mp3 or divx.
alsa kernel driver : like soundcore, snd, snd_pcm, snd_timer...etc
audio controller driver : snd_hda_intel
audio codec interface : snd_hda_codec

** notes **
gnome-sound-recorder only support ogg and wav
packages:
helix for realplayer (non-free), and will touch the alsa lib directly.
gstreamer for the others free audio codecs, below lists the main packages.
-gst-plugins-base
contains a basic set of well-supported plug-ins
-gst-plugins-ugly
contains a set of well-supported plug-ins, but might pose problems for distributors
-gst-plugins-bad
contains a set of less supported plug-ins that haven't passed the rigorous quality testing we expect

tips or useful diag tools under Linux

2009-11-10T15:45:00.002+08:00

* audio
audacity -- professional audio editor
(help to see the audio wave pattern or spectrum)
amixer -- command line mixer tuning program
(another is alsamixer in GUI mode)
arecord -- alsa command line audio recording program

*video
glxgears -- 3D testing tool
(quick to figure out the 3D performance)
xrandr -- command line interface to check and use the video port
(can check the all connecting video interface and output the video signal to dedicate device)

where is the Firefox default settings, like cookies

2009-10-02T08:49:00.002+08:00

In /home/username/.mozilla/firefox there has a file named "profiles.ini".
This file contains the [Profile0], and that defines which folder will be used for default settings, use "abc" to be example.
That means /home/username/.mozilla/firefox/abc will have lots of files about the firefox settings.
Like cookies, the file is "cookies.sqlite".

Useful deploy tool -- DRBL (Clonezilla SE)

2009-07-03T09:28:00.002+08:00

My environment is Ubuntu jaunty (9.04).

sudo aptitude install nis dhcp3-server tftpd
sudo ifconfig eth0:1 192.168.0.1 (when system only has 1 nic port)

# import gpg key
wget -q http://drbl.sourceforge.net/GPG-KEY-DRBL -O- | sudo apt-key add -

# add following line into source list
# then aptitude update and install drbl
deb http://drbl.sourceforge.net/drbl-core drbl stable testing unstable

# For setting up system environment, here has lots of setting, and choose which IP to be the PXE interface should be the most important portion.
sudo /opt/drbl/sbin/drblsrv -i
sudo /opt/drbl/sbin/drblpush -i
-----------------------------------
# start to use clonezilla
sudo /opt/drbl/sbin/dcs
# clone the client image
All --> clonezilla-start --> Beginner --> save-disk
# restore the local image to the client
All --> clonezilla-start --> Beginner --> restore-disk

Now you can boot up your client, then it will show you the GRUB menu with deploy option.

Change wireless on/off status in general user mode

2009-06-15T18:23:00.003+08:00

list some different ways, but need to verify by yourself carefully.

1. silly way....killall nm-applet

2. /etc/acpi/wireless.sh

3. script file by Paul Liu
For old/new version (remark lines are for old version)
#!/bin/sh

#dbus-send --system --type=method_call \
# --dest=org.freedesktop.NetworkManager \
# /org/freedesktop/NetworkManager \
# org.freedesktop.NetworkManager.setWirelessEnabled \
# boolean:false

#dbus-send --system --print-reply --type=method_call \
# --dest=org.freedesktop.NetworkManager \
# /org/freedesktop/NetworkManager \
# org.freedesktop.NetworkManager.getWirelessEnabled

STAT=`dbus-send --system --print-reply --type=method_call \
--dest=org.freedesktop.NetworkManager \
/org/freedesktop/NetworkManager \
org.freedesktop.DBus.Properties.Get \
string:org.freedesktop.NetworkManager \
string:WirelessEnabled | grep variant | awk '{ print $3 }'`
case "$STAT" in
true)
NEWSTAT="false"
;;
*)
NEWSTAT="true"
;;
esac
dbus-send --system --type=method_call \
--dest=org.freedesktop.NetworkManager \
/org/freedesktop/NetworkManager \
org.freedesktop.DBus.Properties.Set \
string:org.freedesktop.NetworkManager \
string:WirelessEnabled variant:boolean:$NEWSTAT

how to build a debian package (.deb)

2009-06-11T14:33:00.006+08:00

need some packages first
dh-make
build-essential
devscripts
pbuilder
cdbs

00 change the changelog and control file to be your own files, it will be authorize through internet.
1. create a test folder
2. in test folder create a project-version folder (like abc-1.1)
3. in abc-1.1 folder, exec "dh_make native" and select "s" option
4. then we have "debian" folder there, inside has example files
** replace some files **
5. in abc-1.1 folder, create etc/pm/config.d/unload file
6. in debian folder, create a file named "install"
7. add "etc/pm/config.d/unload /etc/pm/config.d" in replace file.
*** script file ***
8. add your script into postinst file (you can remove all *.ex file, only left one for modifying.)
9. script better includes #!/bin/bash
10. back to abc-1.1 folder, and run "debuild -i -I -sa" or try this "debuild -us -uc -b"

list some example files.
changelog:
minix-config (1.1) jaunty; urgency=low

* update for ppa

-- Juergen Chiu Thu, 11 Jun 2009 10:38:49 +0000

postinst:
#!/bin/sh
set -e
#Sound

amixer sset "Input Source" "Front Mic"
amixer -q set "Front Mic" 0% unmute
amixer -q set "Front Mic Boost" 10% unmute
amixer -q set "Capture" 100% unmute

#DEBHELPER#
rules:
#!/usr/bin/make -f
include /usr/share/cdbs/1/rules/debhelper.mk

binary-install/minix-config::
install -d $(CURDIR)/debian/minix-config/etc/pm/config.d/
install -m 644 $(CURDIR)/etc/pm/config.d/10minix_module $(CURDIR)/debian/minix-config/etc/pm/config.d/

binary-fixup/minix-config::
dh_gconf --priority=16

ALC662錄音的問題 (Intel 82801G)

2009-04-21T11:16:00.007+08:00

在試ALC662 chipset時...發現不能錄音
一開始找不出問題
但後來發現原來是因為mic的回朔太大聲, 造成錄音無法正常運作
若使用alsa內建的指令錄音, 就都沒有問題
相關用到的指令如下

alsamixer
asoundconf set-default-card 0 (do this only when alsamixer has trouble)
aplay -l
arecord -f cd -t wav -d 5 test.wav
aplay test.wav

好用的測試聲音小工具
xoscope

還是用指令比較保險

最後....
在Volume Control/options/input srouce change to front Mic (system use front mic to be default)
and...壓低front mic與front mic boost的音量....
目前看到多一個問題,ogg type不能使用,換成wave type就好了
可以用下面方式解決
gstreamer-properties程式把原本的input plugin從"alsa"轉為"OSS"

參考用的command, 可直接修改聲音的設定
amixer sset "Input Source" "Front Mic"
amixer -q set "Front Mic" 50% unmute
...

How to change keycode or keybinding behavior

2009-04-15T11:13:00.009+08:00

You can check whole hot key architecture here.
https://wiki.ubuntu.com/Hotkeys/Architecture

* Relative commands
1. input-utils package
a. lsinput: shows some information about each input device the kernel reports. This is useful to make sure you have the right device number for other testing.
b. input-events: tell you the events passing through the queue for any device
c. input-kbd: show you the keymap available for any device that provides keyboard events
2. acpi_listen: listen to acpi channel if the keycode send to acpi.
3. showkey : show the keycodes by -k and scancodes by -s parameter.
4. xev : show the key symbol in X environment like below.
5. xmodmap : GNOME mapping table
KeyRelease event, serial 33, synthetic NO, window 0x4400001,

. root 0x13b, subw 0x0, time 9487761, (321,324), root:(399,415), state 0x0, keycode 23 (keysym 0xff09, Tab), same_screen YES, XLookupString gives 1 bytes: (09) " " XFilterEvent returns: False

*How to find out the root cause of hot key
For kernel clarification
1. use "lsinput" to check which device file you used.
2. use "input-events 4" to listen if kernel get the right signal from device (4 means /dev/input/event"4")

For acpi clarification
3. excute "#showkey -s" to capture the keyboard signal.
4. Check the scancodes and refer to /usr/includes/linux/input.h file.
5. check the keycodes definition in /usr/share/acpi-support/key-constants
6. check the scripts file for acpi event in /etc/acpi/*.sh
7. you can use acpi-fakekey to simulate the keycode.

For GNOME system
8. use "xmodmap -pke" to check the key map
9. use "xev" to see which keycode or behavior under GNOME
10. Or you can use "gnome-keybinding-properties" to check the GNOME keybinding status.
============
gnome-keybinding-properties save the system default setting in following path
/var/lib/gconf/debian.defaults/%gconf-tree.xml
and save the user settings in
/home/juergen/.gconf/desktop/gnome/keybindings/"your-key-name"/%gconf.xml
============

---------------------------------------------------------------------------

For example: 0xe0 0x20 for fn-f9 audio mute binding code by showkey -s
xmodmap -pke (look for the available keycode number)
less /usr/share/X11/XKeysymDB (check which X Window default function)
setkeycodes e020 255 (that means keycode 255 will be 0xe0 0x20, change keybinding to keycode.)

For example: change keybinding 121->mute to 113->mute
$sudo xmodmap -e "keycode 113 = XF86AudioMute"
$xmodmap -pke | grep 113

For example: for acpi event
when acpi script needs 121 to mute, but mute button is 113.
add "$setkeycodes e020 121" to /etc/event.d/rc2 script section before exec line.
reboot and mute function keycode will change to 121.
modify /usr/share/acpi-support/key-constants 113 to 121

refer to the page
http://darkknight9.blogspot.com/2005/08/custom-keybinding-gnome.html
"Application/System Tools/Configuration Editor" for metacity "keybindings" function.

Command line wireless enablement

2009-04-15T11:02:00.004+08:00

It's just refer to someone readme file, but properly useful when no GUI.

"ifconfig wlan0 up"
"ifconfig" to check the "wlan0" section
"iwlist scan" to scan all AP (The essid "testap" for example)
"iwconfig wlan0 essid testap" to set up essid
"ifconfig wlan0 broadcast 192.168.0.255 netmask 255.255.255.0 192.168.0.100"
"route add default gw 192.168.0.1 dev wlan0"

Useful basic information for hibernate function under RHEL or SuSE

2008-12-08T09:08:00.006+08:00

I use Ubuntu with rtl8187 module for realtek chipset.
The sleep/suspend/hibernate function all fail in just starting stage and without any errors.
The solution and information:

Hibernate issues almost caused by driver, especially network and storage driver.
No screen, just can remove some drivers first.
Use pm-suspend/pm-hibernate or /sys/power/ folder to test.

Method 1
in /etc/pm/conf.d/ create a file name "unload_module" (any name is fine)
in unload_module add a line "SUSPEND_MODULES="rtl8187 rt8189 .....""

Method 2
add "02wireless" file in /usr/lib/pm-utils/sleep.d/ and the content as followings.

#!/bin/sh

case $1 in
suspend|hibernate) ifdown wlan0 ; rmmod rtl8187 ;;
resume|thaw) modprobe rtl8187 ;;
*) exit $NA ;;
esac
exit 0

** Still need to clean something in the future.

RHEL

package: hal/pm-utils
folder: /etc/pam.d;/etc/hal;/usr/lib64/hal;/usr/lib/pm-utils/sleep.d (hibernate stage folder)
command: pm-hibernate;lshal
script file: /usr/lib64/hal/scripts/linux/hal-system-power-hibernate-linux
(can check hal package list.)
log: /var/log/pm/suspend.log

SuSE

package: hal/powersave
folder: /etc/hal;
command: powersave;lshal
script file:
1. /usr/lib64/hal/scripts/hal-system-power-hibernate
2. /usr/lib/powersave/scripts/prepare_suspend_to_disk (include GRUB info)
3. /usr/lib/powersave/scripts/sleep_helper_functions
log: /var/log/suspend2disk.log

一篇對RHEL Performance不錯的文章

2008-10-04T16:07:00.001+08:00

According to below link.
http://searchenterpriselinux.techtarget.com/tip/0,289483,sid39_gci1332851,00.html

Linux下的Hibernate（Suspend to Disk） – ACPI定義的睡眠模式之一

2008-09-10T16:36:00.003+08:00

延續上一篇“電源管理—Linux下的ACPI”，這次談談更深入的Linux Hibernate的作法。Linux在許多使用上，其實都已經做到Desktop所需要的功能，像我所要介紹的Hibernate功能就是其中之一。

從上圖中可以發現，Hibernate和關機的差異是非常大的，可以說是完全不一樣的事情，在一般看得到的書中，Hibernate就是一般我們在ACPI中所謂的G1S4。
G1指得是“Sleeping”，也就是睡眠狀態，一般會用到G1的情況有兩種，Standby或Hibernate，分別為G1S3與G1S4，這兩種的差異主要在於Suspend to RAM（STR）及Suspend to Disk（STD）。
因此S4指得則是第四個階段，也就是Suspend to Disk（STD），所以G1S4整體的意思就是讓系統睡得程度到“Hibernate”階段。之前使用者較常會用到的應該是S3，因此電源都無法完全關掉，會有些許的電源用來供應記憶體，但S4則可以做到將電源完全關掉，而保留住系統目前的狀態。
但Hibernate的動作在Linux中是如何達到，以及到底做了哪些事情，當Hibernate進行時又是參考哪些檔案，是這篇文章中要介紹給各位的。
1. Hibernate所參考的檔案
Hibernate所參考檔案都是由pm-utils套件所提供的，pm-utils是一套電源管理的工具軟體，在2.6的kernel之後，都已經支援ACPI的功能，所以可以做到像Hibernate的省電模式，但這些動作在啟動時，若還有硬體（像USB設備）在系統上該如何處理，就可以透過pm-utils來做一些關閉硬體的動作，但其實pm-utils是透過一個『HAL』的服務程式（在Redhat中此服務的檔案名稱為haldaemon）在控制，所以一般看不到pm的字眼。不過雖然是透過HAL在操作，但使用者一樣可以加一些自己的動作在其中，做細部的調整。
基本上pm-utils除了【/etc/pm】這一個目錄外，【/usr/lib/pm-utils】也是主要的目錄之一，其實如果細看【/etc/pm】，裡面是空無一物，因為這是預留給使用者自行使用的地方，系統真正在執行的，是在【/usr/lib/pm-utils】底下的檔案，不過【/etc/pm】是可以使用的，只是檔案要自行產生。
在【/usr/lib/pm-utils】下，最好用的目錄就要屬sleep.d這一個（如下圖所示），因為當使用者在進行Hibernate（休眠模式）時，就會依據這目錄中的檔名前兩碼數字的大小（由小到大），依序進行執行的動作（正常應該說是關閉的動作，但因為可以自行設定，不在這邊定義為關閉）；相同的，在【/etc/pm】的目錄下，也有和這邊類似的目錄，只是都是空的，這在上面有提過。不過這邊有幾點是要特別注意的：
a. 系統在進行Hibernate時，是先執行【/etc/pm】的目錄，再執行【/usr/lib/pm-utils】目錄中的檔案；但啟動是相反的，會先執行【/usr/lib/pm-utils】後，再執行【/etc/pm】目錄下的檔案。
b. 系統在進行Hibernate時，會從目錄中檔名的前兩碼數字由小到大進行執行動作；但再開機時，是相反的，也就是會由數字大到小執行。
這兩點要注意的原因，主要是一般預設立場是要進行關閉的動作，所以往往會忽略開機時是要進行啟動，剛好目的是相反的，自然順序也就跟著變動，在細節的設計上要特別注意。

2. Hibernate所進行的方式
最簡單要進行Hibernate的方式，就是在X Window關機時，不要用原本關機的選項，而改用『Hibernate』的方式（如下圖所示），只要點選下去，系統就會自動進行Hibernate，但要注意，若系統中的“haldaemon”沒有啟動，是不會有這選項的。

如果需要比較進階的使用，就必需要參考到/sys/power目錄，該目錄是主要Hibernate在進行時的“開關”，這一個目錄只存放和電源模式有關的檔案，更正確的說法，是只有電源管理機制的檔案。裡面只有幾個屬性檔案在其中，屬性名稱（也就是檔案名稱）及其值都請參考下圖

每個屬性的意義介紹如下：
1. disk：當使用者在做休眠模式中S4的STD（suspend to disk，或稱為Hibernate）時，要將系統的狀況寫入到硬碟中，因此這邊是在定義當狀態寫入到硬碟後，“系統”該如何運作。基本上目前2.6的kernel支援以下五種模式：
a. platform：不知其運作方式，但只有在該平台有支援時才可使用。
b. shutdown：當進入休眠時進入關機狀態。
c. reboot：當進入休眠時進入重新開機狀態。
d. testproc：testproc與下一個test，這兩者的模式比較特別，都是屬於即時測試休眠功能所可可以使用的狀態，也就是可以讓使用者進入模擬的休眠模式，再自動回複到原本的系統狀態，所以一直都在原本的使用狀態下。
testproc主要有以下幾個步驟（系統訊息如下圖所示）：
關閉未使用的CPU  凍結所有的工作  等五秒鐘  將原本的工作還原  打開原本未啟動的CPU

e. test：和前一個testproc的不同，是在測試時更完整，連記憶體和硬體設備的部份也加入模擬的階段。
test主要有以下幾個步驟（系統訊息如下圖所示）：
關閉未使用的CPU  凍結所有的工作  壓縮記憶體  關閉設備  等五秒鐘  恢復設備的狀態  將原本的工作還原  打開原本未啟動的CPU

這五種中最常被使用的就是“shutdown”（a不知其作用為何，但一定要系統有支援才可使用），後三者（“reboot”、“testproc”、“test”）則較少為人知，因為這三種大部份是在測試單位（可能也只在專門測試休眠功能的單位）才有機會被使用到，不然使用的機會少之又少，但實在是一個造福測試者的功能。不過使用上真的很簡單，如筆者電腦的“disk”檔案預設設定為“shutdown”，如果更改為“reboot”，當休眠完成後，將不會關機，而是“重開”。
所以想當然，誰會在做休眠時的下一步要“重新開機”，這樣完全無法省電，所比這一個機制其實是還是為了測試休眠模式所定義的，只是可能會將測試的範圍擴大到整個系統的流程，而不是像“testproc”和“test”僅限於測試休眠的部份功能，畢竟完整的動作是包含關機與開機。
2. image_size：目前系統可接受的最大image大小，預設為512MB。
3. pm_trace：這是一個控制開關，可比決定是否要記錄在多次的重新開機後，最後一次存在RTC中的事件點，預設值為“0”，代表不記錄，若改為“1”，則可進行記錄的動作。
4. resume：當系統進行S4（suspend to disk）時，系統要將系統狀態寫入的位置。所以這屬性其實是代表某一個分割區的major及minor ID（一般都是SWAP分割區），若需要使用resume分割區，就必須在開機時先在GRUB的開機參數中，加入resume=/dev/xxxx的參數，才可以讓系統知道要使用該分割區當寫入的分割區。在下圖中的resume值之所以為“0:0”，是因為主機中沒有設定該參數（SuSE在預設就會加入該參數）。
5. state：目前系統可支援的休眠模式，一般只會有以下三種（或只有其中一兩種）狀態（S2一般電腦都不會支援）：
a. standby：就是一般所謂的S1，S1是在睡眠狀態中最吃電的一種狀態，CPU中的cache都持續供電，但停止執行指令。在CPU及記憶體的部份都有電力在供應，但其他的裝置就沒有硬性規定，可斷電也可供電。
b. mem：就是S3（suspend to ram），在此狀態下，只有主記憶體有接受供電的權利。但值得注意的是，雖然大部份的資料都會回寫到記憶體，但硬碟本身的Buffer有可能來不及回寫到硬碟，這樣就會造成資料流失。
c. disk：就是S4（suspend to disk），俗稱休眠狀態（Hibernet，或稱冬眠狀態），其技術上的名稱則為Suspend to Disk (STD)，這一階段會將所有執行中的資料全部寫入到硬碟中，而之所以要寫入硬碟，就是因為要完全的斷電，但也因為如此，在回覆到原本工作狀態所使用的時間會比S3來得久。
更簡單的說，其實如果將“state”檔案以“disk”值寫入（如：【echo “disk” > /sys/power/state】），這動作等於切換“state”開關至“disk”選項，因此系統就會直接進入休眠，並且將休眠模式認定為前面我們提過的“disk”檔案中所記載的方式，像“shutdown”。

第二本書完成了 -- Linux系統架構與目錄之解析

2008-08-29T15:53:00.002+08:00

http://www.delightpress.com.tw/book.aspx?book_id=SKNS00002
這本書寫了大概快一年的時間, 一開始寫這本書主要的目的, 是為了讓Linux的使用者, 當操作時遇到問題或是卡在某一些檔案無法進行或運作下去, 卻無法知道這些目錄或檔案的作用為何時, 可以用來查詢的一本實用工具書, 當然也是因為市面上一直找不到類似的書, 所以只好自己寫一本, 雖然花了很多時間, 但看到成品出來, 還是很值得的.
只是這本書, 怕會有一些爭議, 畢竟每一個版本的Linux多少會有不同的地方, 因為我個人覺得大多數初學者應該都會以Redhat的系統為一開始的作業系統, 所以就以Fedora為整本書的範例, 實在沒辦法顧到每一個版本, 但主要的幾個常用目錄, 像設定檔/etc, VFS /proc, /sys, /dev等等, 這些相當重要的目錄就不會是哪一個Linux版本, 一定都是一致的, 所以對真正核心的重要性, 我想是一樣的, 只怕慣用不同版本的讀者, 會不習慣裡面的某些目錄檔案.
其實有了出書的經驗, 會知道讀者的反應是真得很重要的, 因為不然根本無法得知自己寫出來的成品, 是不是讓大家真的有所收穫, 畢竟在台灣寫這些資訊相關的"店頭書", 說真的是沒啥賺頭的, 除非像鳥哥知名度大開的, 應該就可以賺個好幾翻, 不然像我這樣, 大概也只是做一些讓自己開心, 可以留做回憶的事情, 再來就是可以吃幾頓大餐...所以重點...真的是在讀者的反應, 第一本書"Linux作業系統之奧義"讓我知道有用心是會有回報的(可不是$$唷, 雖然是有一些些啦...^^), 現在也在等看看, 看第二本是不是也可以讓我看到一些讀者的反應, 又要緊張幾個星期囉.

點(dot) (.)對目錄及shell scirpt的意義

2008-05-08T15:26:00.005+08:00

###目錄中###
cd . 代表進入"目前這目錄"

###script file中###
. /etc/init.d/functions 代表在"同一個shell"中執行
這意思是, 原本
shell --> shell
--> sub shell --> functions --> kill sub shell
變為
shell --> functions --> shell
差別在於所有執行後的變數及結果都會留在原本的shell中
在functions檔案中有一些函式, 像pidofproc() (系統原本只有pidof程式)
原本無法執行, 經過". /etc/init.d/functions"就變為區域變數, 就可以執行了
可以用"setgrep pidofproc", 看到所有functions留在shell中的資訊
當然在登出後或其他shell中是沒有的

socket與協定的觀念 - 以nc與http為例

2008-05-08T09:25:00.004+08:00

port這東西有時候好像很難解釋, 但如果透過實際的操作就很好理解
先在該台主機上要產生一個192.1.1.1:1111的門,也就是socket, 讓大家可以連線
nc -l 192.1.1.1 1111
可以在另一台主機上使用
telnet 192.1.1.1 1111
這樣就可以雙方進行對話

因此協定的目的, 就在讓雙方可以透過socket進行"對話", 對話的規範就叫協定
像Web Server, 其實是可以透過telnet的方式將網頁抓回來
只是要知道HTTP協定的對話模式, 以及對方應有的網頁檔名
簡單的可以用下面的範例
telnet 192.1.1.1 80
進入後再輸入
GET /index.html
就可以看到index.html的內容

一些shell script的小技巧

2008-05-05T13:47:00.005+08:00

Shell script真的是蠻好用的, 一行字就可以做很多的事情, 這邊舉一些常用的當例子:

1.
for i in filename*; do echo "123" > $i;done
假設要修改的是stu開頭的檔案, 這樣每一個檔案的內容都會變成123

2.
while [ 1 ]; do echo "1" ; done
會不間斷的列印"1"這字串, 這方式可以將single core的CPU操到100%的使用率, 若是multi core的, 就多跑幾個吧.

3.
萬用字元與正規表示法的差異
grep ^[^#] filename
代表要尋找 "非" # "開頭" 的內容

^ 開頭
$ 尾巴
[^#] 非#開頭的
[] 裡面代表的只有一個字元

所以在使用grep時要注意, 因為grep所接的字串是使用正規表示法
grep a..ther filename
正規表示法和萬用字元的差異
.代表單一字元....
*代表a或多個a
.*代表0或多個任意字元

一本書把自己用瘋了

2008-03-14T09:13:00.003+08:00

現在在寫一本覺得對大家都很有用的書, 不過發現東西太多太多, 和Linux的關聯度太廣, 和之前的Linux流程比起來真的是有點小屋見大屋的感覺, 但現在又還不能說是寫什麼樣的題材...唉....想抱怨都不知該如何說起, 只希望可以儘快的寫完, 可以再寫一些別的東西.
在煩的時候也已經想過Linux的領域有哪些應該要有人跳出來, 卻遲遲沒有人要做的事情, 其實也不知道是沒人寫還是大家都不想做這些事, 反正看起來我的能力還可以幫很多人整理出一些頭緒, 就繼續完成.
只是經過這兩本書, 我肯定的說, 要完成一本從無到有的書(自己想出的題材), 除了理想還是理想, 要是沒了這動力, 大概也不會想寫下去吧.

我的第一本書--Linux作業系統之奧義

2008-01-08T17:09:00.004+08:00

這本書其實是在偶然的機會下產生的, 原本只是覺得目前市面上沒有Linux的書適合讓基礎的讀者了解到底何謂Linux, 大部份都是在談一些Server...設定...架站...X Window等等非觀念的書, 所以才會興起出版一本我個人認為比較像是在介紹Linux為何物的觀念書, 當然也沒想到很多讀者在看過這本書後, 都給予我正面的肯定, 感動中~~~~
但對讀者比較抱歉的是, 因為是第一次出版, 所以在沒有經驗的情況下, 第一版的書有比較多的錯誤需要修正, 出版社也以最快的速度修正完畢, 只是自己對已經買到書的讀者感到抱歉, 不過在悅知的網站上已經放有堪誤表供讀者下載, 希望可以解決很多讀者的問題, 也感謝很多讀者來信告訴我錯誤的地方.
在看這本書的過程中, 相信有很多讀者會有很多的問題, 因為這本書當初的設計和大部份作業系統的書很不一樣, 雖然沒有很多頁, 但其實提到的東西非常多, 也是我自己累積下來的一些觀念, 所以如果有無法理解的部份(書中儘量以簡單的方式闡述), 也歡迎直接透過這篇文章的回覆來詢問, 或是用我書中的email和我聯絡都好(只是這樣別的讀者就無法看到您當初遇到的問題), 我會儘快回覆給每一個讀者.

-------------------------------------------------------------------------------
在2008底找到的一些讀者相關建議, 這些不論好壞反正我找得到的就都貼出來(之前一些文章好像已經不見了), 目的只是希望如果有人想參考或是我自己需要再回頭看一下當初大家的意見, 要是有人希望我將連結刪除, 就請mail給我, 謝謝.

http://www.wretch.cc/blog/sclin0323/25986650
http://www.dbanotes.net/review/linux_hardware.html
http://bbs.phpchina.com/thread-61806-1-3.html
http://www.hiadmin.com/%E4%B9%A6%E8%AF%84-linux%E6%93%8D%E4%BD%9C%E7%B3%BB%E7%BB%9F%E4%B9%8B%E5%A5%A5%E7%A7%98/
http://www.anobii.com/books/Linux%E4%BD%9C%E6%A5%AD%E7%B3%BB%E7%B5%B1%E4%B9%8B%E5%A5%A7%E7%BE%A9/9789866761065/017b696892e1d8208b/
http://dango-akachan.appspot.com/?p=40002
http://www.seo-space.net/blog/129-Linux-Book-System-Directory.html

My all Reference documents

2008-01-08T16:29:00.007+08:00

Catagory File Location
Network RelatedIP address
Network RelatedWhat is IPv6 by me
Network RelatedWhat is IPv6 by others
Network RelatedFull ICMP code
Network RelatedTCP+ICMP
Network RelatedVLAN
Network Related802.11 Introduction
Network RelatedIntroduce NAS,SAN and Blade

Cluster RelatedWhat is clustering by TYAN
Cluster RelatedMPICH Introduce
Cluster RelatedInterface introduce like PMB
Cluster RelatedQueueing system introduce like Cmeta
Cluster RelatedBenchmark Method
Cluster RelatedMonitoring Tool

VoIP RelatedWhat is H.323
VoIP RelatedH.323 vs. SIP
VoIP RelatedIntroduce Secure VoIP
VoIP RelatedConcept of Interactive Video
VoIP RelatedWhat is visual collaboration
VoIP RelatedContinous Mode vs. Voice Actived

ACPIACPI Information

Security應用密碼學

房貸相關房貸試算表

在2007/09/12 於悅知網站所發表的"電源管理—Linux下的ACPI"

2008-01-08T15:50:00.004+08:00

ACPI的全名為Advanced Configuration and Power Interface，是在1996年12月由HP、Intel、Microsoft、Phoenix及Toshiba一同推出的，主要的作用就是在控制與管理系統上所有和電源相關的硬體或設備，當然也包括了外接的週邊設備。在【Linux作業系統之奧義】一書中有提到有關Intel及AMD在Linux下省電模式，這一部份就是ACPI針對CPU的電源管理的其中一種表現方式，所以其實ACPI是一個非常浩大且重要的管理機制。
大家都知道開機與關機，但這一兩個動作所牽涉到的層面其實非常廣，從CPU的電源要吃多少、關機要關到哪一個程度、關機後的動作為何，一直到要如何回覆到原本的狀態，都在ACPI的規範中。舉一個最簡單的例子，在Windows95或Linux 2.4 kernel之前，是不是一按系統的Power Button就會直接斷電，但在Windows98及Linux 2.6 kernel之後的版本，就可以進入所謂的關機階段，自動一步一步的將電源關閉。這中間的差別在哪裡？是硬體還是軟體？其實就在於整個電源的管理模式更新為ACPI的方式。

針對系統的電源管理，ACPI處理電源的方式可以分為G0、G1、G2、G3四個主要的全系統狀態（Global State），分別介紹如下：
1、
G0：一般正常的“工作”狀態，使用者開機進入作業系統後便是屬於此一階段，在這一個正常的用電階段，使用者還是可以進行細部的調整，例如等一下會介紹到針對設備的省電模式。。
2、
G1：就是較常聽到的“睡眠”狀態（sleeping），也是一般使用者比較有機會在作業系統下做調整的模式，在G1的狀態下，可以再細分為S1、S2、S3、S4四個子狀態：

S1：S1是在睡眠狀態中最吃電的一種狀態，Notebook中有時使用的"Standby"選項就是採用S1的方式，但比較好的做法，現在都會以S3為標準。CPU中的cache都持續供電，但停止執行指令。在CPU及記憶體的部份都有電力在供應，但其他的裝置就沒有硬性規定，可斷電也可供電。S1的狀態一般都是在較舊的電腦中才會看到，因為很多新型的主機都將G1S1的功能拿掉，或是廠商會支援使用者在BIOS中做設定，讓使用者可以選擇使用S1或是S3。

S2：所謂的沉睡（Deeper Sleep），連CPU都會斷電，但鮮少電腦會支援G1S2。

S3：這對大家而言一定最為熟悉，因為這就是在Windows選項中會出現的“Standby”，但在技術上的名稱則為Suspend to RAM (STR)。在此狀態下，只有主記憶體有接受供電的權利。但值得注意的是，雖然大部份的資料都會回寫到記憶體，但硬碟本身的Buffer有可能來不及回寫到硬碟，這樣就會造成資料流失，因此在用S3的狀態時，最好是先將硬碟的buffer及cache都關掉，以免造成上述的問題發生。另外，因為ACPI並不是一個世界通用標準，只是由幾間公司所在推的一個功能，因此Linux並沒有完全的支援，像談到現在為止的S1、S2、S3到目前為止Linux都沒有加到預設的功能，只有接下來提到的S4已經變為Fedora 7、RHEL5及SLES10的標準配備。

S4：俗稱冬眠狀態（Hibernet），其技術上的名稱則為Suspend to Disk (STD)，這一階段會將所有執行中的資料全部寫入到硬碟中，而之所以要寫入硬碟，就是因為要完全的斷電，但也因為如此，在回覆到原本工作狀態所使用的時間會比S3來得久。在Fedora 7中，已經將S4加入到關機的功能之一，這也是G1中唯一可以在Linux下所使用的“睡眠”方式。

3、
G2：可稱為Soft Off或是S5，在主機完全關機時，僅供少許的電力給一些像網路卡、鍵盤或像USB設備等，俱有“喚醒”功能（Wake）的設備，當需要開機時，只要透過網路或鍵盤就可以將遠端或近端直接打開電腦。但有個限制，比如說原本設定從網路開機，如果關機後使用者將網路卡拔掉，就會破壞G2的狀態，意即進入G3。在Linux中可以設定網路卡的等待狀態，也就是說直接指定某一張網路卡，當關機時要傾聽有沒有需要被“喚醒”，

設定完成後，只要在同一個網段內的電腦，執行“喚醒”指令，就可以透過在等待中的網路卡的MAC Address，將電腦“喚醒”，也就是進入開機程序。

4、
G3：Mechanical Off，這時的供電大小近乎於零，其實就是各位使用者一般的關機，在正常關機程序結束時便進入G3的狀態，但為何指明是“近乎於零”，因為其實還是有些許的電力在等待使用者開機使用，所以如果在家中要省電，還是把插頭拔掉吧，不然電腦是永遠都在吃電狀態的。

剛剛所提到的這些全系統狀態，指的都是整體的電源管理，而ACPI同時針對CPU也定義了電能以及效能狀態的規範，只是Linux到目前為止大部份沒有完全照著ACPI的方式執行。

以電能狀態而言，CPU分為C0、C1、C2、C3四種狀態，裝置也同樣被區分為D0、D1、D2、D3四種狀態，基本上大同小異，都是數字越小就越耗電，越大就越省電，但在Linux下可以看到，其實不會完全遵照這些狀態的定義，也就是功能雖然有部份做到，但不會完全照著ACPI的定義。

就CPU的效能狀態來說，ACPI定義了17個狀態，稱為P-States，從P0一直到P16。P0的效能最高，P16最低；但相對來說，也就是P0最耗電，而P16是最省電。在Linux 2.6 kernel下，要看到Linux針對ACPI所定義出的CPU效能狀態（P-States），就必須在/sys目錄下才看得到。在圖中可以看到，雖然定義了17種狀態，但實際上只會使用到2到3種的速度去因應CPU的效能變化，但在實際的運作中，只能說夠用了。

當然ACPI定義了不只這一些，另外還有很多的表格要去參考，真的是蠻複雜的一個機制，尤其ACPI並非完全由作業系統來控制的，一樣是透過作業系統與BIOS不斷的溝通才有辦法達到各個狀態。但ACPI對目前全球正熱門的節能概念來說，非常的實用，尤其是一些長期使用NOTEBOOK的使用者來說，更可以讓電力更持久。但有些特殊情況並不適合使用類似的節能方式，會造成反效果（連電力都會更浪費），這在【Linux作業系統之奧義】一書中也已經解釋過，其原因是出在於處理節奏上的差異。適不適用於系統上，還是要等待使用者細心的評估過才能決定，不過，身為一個系統管理者，勢必多了一份為地球省一點電的責任。

2008-01-08T15:28:00.001+08:00

Solaris DHCP server configuration tips

#hostname pxeserver
Create DHCP tables in /var/dhcp
#dhcpconfig -D -r SUNWfiles -p /var/dhcp
Start and Stop DHCP service
dhcpconfig -S -d <-- stop dhcpconfig -S -e <-- start PXE default settings # dhtadm -A -m PXEClient:Arch:00000:UNDI:002001 -d ':BootSrvA=192.1.1.254:' Create options # dhtadm -A -s SrootIP4 -d ’Vendor=SUNW.i86pc,2,IP,1,1’ # dhtadm -A -s SrootNM -d ’Vendor=SUNW.i86pc,3,ASCII,1,0’ # dhtadm -A -s SrootPTH -d ’Vendor=SUNW.i86pc,4,ASCII,1,0’ # dhtadm -A -s SinstIP4 -d ’Vendor=SUNW.i86pc,10,IP,1,1’ # dhtadm -A -s SinstNM -d ’Vendor=SUNW.i86pc,11,ASCII,1,0’ # dhtadm -A -s SinstPTH -d ’Vendor=SUNW.i86pc,12,ASCII,1,0’ # dhtadm -A -s SsysidCF -d ’Vendor=SUNW.i86pc,13,ASCII,1,0’ # dhtadm -A -s SjumpsCF -d ’Vendor=SUNW.i86pc,14,ASCII,1,0’ # dhtadm -A -s SbootURI -d ’Vendor=SUNW.i86pc,16,ASCII,1,0’ Add a PXE client # ./add_install_client -d -e "00:a0:d1:e1:a5:3d" \ <-- Client's MAC address # > -s 192.1.1.1:/export/home/sol10 \
# > i86pc
Create private macro for MAC
# dhtadm -A -m 0100A0D1E1173C -d ':SinstNM=192.1.1.254:SinstIP4=192.1.1.254:SinstPTH=/export/home/sol10_ga:SrootNM=client:SrootIP4=192.1.1.254:SrootP
TH=/export/home/sol10_ga/Solaris_10/Tools/Boot:BootFile=nbp.0100A0D1E1173C:SbootURI=tftp\://192.1.1.254/0100A0D1E1173C:'
# dhtadm -A -m 192.1.1.0 -d ':Subnet=255.255.255.0:RDiscvyF=1:Broadcst=192.1.1.255:'
Create IP to suit the macro
# pntadm -C 192.1.1.0
# pntadm -A 192.1.1.100 192.1.1.0
# pntadm -M 192.1.1.100 -m 0100A0D1E1173C 192.1.1.0

2008-01-08T15:21:00.000+08:00

How to boot Linux system by XP and use XP to create multiboot menu

1. Make sure you have install stage1 (GRUB) to MBR or boot sector first.
2. Install XP and use Linux DVD boot into Linux system.
3. "dd if=/dev/hda1 of=/boot.img bs=512 count=1" to dump MBR or boot sector's bootloader into 1 file, and name it boot.img.
4. Copy boot.img file into XP system C: and add 1 line into tail of c:\boot.ini file as followings.
c:\boot.lnx="Linux system name"
5. Reboot and then you will see the multi boot option, and sure you should can get into that Linux OS.

2008-01-08T15:06:00.000+08:00

How to show tranditional chinese font under Linux samba service

Samba下要顯示繁體中文
local，如果為：zh_TW.UTF-8：
在 /etc/samba/smb.conf 中的 [global] 段加上：
display charset = UTF-8
nix charset = UTF-8
dos charset = cp950
#service samba restart

2008-01-08T15:04:00.000+08:00

Solaris PXE server installation and configuration

DHCP
1. /usr/sadm/admin/bin/dhcpmgr command under GUI
2. Now finish configuring DHCP service
3. You can start and stop service by this tool

NFS Image files
1. create /export/home/sol10 directory
2. insert the first CD in the CDROM. Go to /cdrom/cdrom0/s2/Solaris_10/Tools
3. Execute the following command:
# ./setup_install_server /export/home/sol10
4. After finishing the CD1, change to another disk step by step(CD2,3,4) and into the same directory
5. Execute the following command:
# ./add_to_install_server /export/home/sol10

NFS
1. Edit /etc/dfs/dfstab file and add a following line.
share –F nfs –o ro,anon=0 –d "install server directory” /export/home/sol10
2. Do "shareall" command
3. Type "share" command to see if it works.
4. Do command "svcadm enable network/nfs/server"
5. "showmount -e" to see if it works or check "ps -efgrep nfs".
6. If not, do it by yourself like below.
/usr/lib/nfs/nfsd -a
/usr/lib/nfs/statd
/usr/lib/nfs/nfsmapid
/usr/lib/nfs/lockd
/usr/lib/nfs/mountd
7. It should be work now. If not, call the police.....:)

PXE and DHCP
1. Get into /export/home/sol10/Solaris_10/Tools
2.
# ./add_install_client -d -e "00:a0:d1:e1:a5:3d" \ <-- Client's MAC address # > -s 192.1.1.1:/export/home/sol10 \
# > i86pc

$$$$ It shows some messages and VERY IMPORTANT about the PXE function.

3.
Do following command to make the same option for dhcp.
# dhtadm -A -s SrootIP4 -d ’Vendor=SUNW.i86pc,2,IP,1,1’
# dhtadm -A -s SrootNM -d ’Vendor=SUNW.i86pc,3,ASCII,1,0’
# dhtadm -A -s SrootPTH -d ’Vendor=SUNW.i86pc,4,ASCII,1,0’
# dhtadm -A -s SinstIP4 -d ’Vendor=SUNW.i86pc,10,IP,1,1’
# dhtadm -A -s SinstNM -d ’Vendor=SUNW.i86pc,11,ASCII,1,0’
# dhtadm -A -s SinstPTH -d ’Vendor=SUNW.i86pc,12,ASCII,1,0’
# dhtadm -A -s SsysidCF -d ’Vendor=SUNW.i86pc,13,ASCII,1,0’
# dhtadm -A -s SjumpsCF -d ’Vendor=SUNW.i86pc,14,ASCII,1,0’
# dhtadm -A -s SbootURI -d ’Vendor=SUNW.i86pc,16,ASCII,1,0’

4. And then use “/usr/sadm/adm/bin/dhcpmgr&” to call the GUI programe to configure following items.
5. Create 2 macros as it said. (0100xxxxxx and the PXEClientxxxxx)
6. Create the Address FOR the macro.
7. Now finish configuring DHCP with PXE service
8. You can start and stop service by this tool

Trouble Shooting
1. If cannot boot from the client and cause by the driver.
a. Modify path
/export/home/sol10/Solaris_10/Tools/Boot/boot/solaris/devicedb/master
Change driver name from none to “bge.bef” or something like that.
b. Modify path
/export/home/sol10/Solaris_10/Tools/Boot/etc/driver_aliases
Add a line bge “pci14e4,16a8” <-- It shows on your client’s error message. 2. If cannot put into the CDs, please do following command in CLI mode. # svcadm enable smserver 3. The command “lspci” usage in Solaris # prtconf –pv

PXE Server configuration tips

2008-01-08T14:51:00.001+08:00

chkconfig tftp on
chkconfig xinetd on
chkconfig nfs on
chkconfig dhcpd on

##Copy all DVD source into NFS folder
cp -a /mnt/* /var/ftp/fedora7

##Copy needed files into tftp folder
mkdir /tftpboot/linux-install/fedora7
cp /var/ftp/fedora7/image/pxeboot/vmlinuz /tftpboot/linux-install/fedora7
cp /var/ftp/fedora7/image/pxeboot/initrd /tftpboot/linux-install/fedora7

##Edit PXE config file
vi /tftpboot/linux-install/pxelinux.cfg/default
--------------------------------------------------------
default 0
timeout 2000
prompt 1
display msgs/boot.msg
label 1
kernel fedora7/vmlinuz
append initrd=fedora7/initrd.img ramdisk_size=65536

## Edit message config file
vi /tftpboot/linux-install/msgs/boot.msg
--------------------------------------------------------
1. Install Fedora Core 7

## NFS has to share /var/ftp/fedora7 folder
##DHCP config file notice
ddns-update-style none;
ignore client-updates;
allow booting;
allow bootp;
class "pxeclients" {
match if substring(option vendor-class-identifier, 0, 9) = "PXEClient";
next-server 192.10.0.1;
filename "linux-install/pxelinux.0";
}
subnet 192.10.0.0
netmask 255.255.255.0 {
range 192.10.0.150 192.10.0.180;
option broadcast-address 192.10.0.255;
option routers 192.10.0.1;
option subnet-mask 255.255.255.0;
}

2008-01-08T14:42:00.000+08:00

Boot System by redirect function via serial port

[Test steps]

1. Completing Linux installation.

2. Change BIOS settings /Server/Serial Console Features/BIOS Redirection Port to [Serial port 1 or 2]

3. Power on System.

4. Edit the file /boot/grub/grub.conf, change some arguments to redirects Linux console to ttyS0 (ttyS1) as followings:
"kernel /vmlinuz ro root=/dev/hda3 console=ttyS0,19200,vt100"

5. Edit the file /etc/inittab, add some arguments as followings:

c0:2345:respawn:/sbin/agetty ttyS0 19200 vt100
c1:2345:respawn:/sbin/agetty ttyS1 19200 vt100

6. Modify /etc/securetty, and add some arguments in the tail of the file:

ttyS0 ttyS1

2008-01-08T14:25:00.000+08:00

Nagios installation and configuration tips

### Environment###

Client IP address: 10.6.116.59

Node1 (Server) IP address:
10.6.116.64
192.1.1.1

Node2 IP address: 192.1.1.2
################

[ipvsadm section]

tar zxvf ipvsadm-1.24.tar.gz
cd ipvsadm-1.24
Modify Makefile and libipvs/Makefile for /usr/src/linux/include to /usr/src/kernels/2.6.15xxx/include
make;make install
ipvsadm -C
ipvsadm -A -t 10.6.116.64:80 -s rr
ipvsadm -a -t 10.6.116.64:80 -r 192.1.1.2:80 -w 1
ipvsadm -a -t 10.6.116.64:80 -r 192.1.1.3:80 -w 2
ipvsadm -A -t 10.6.116.64:23
ipvsadm -a -t 10.6.116.64:23 -r 192.1.1.2:23 -w 1
ipvsadm -a -t 10.6.116.64:23 -r 192.1.1.3:23 -w 2
ipvsadm

[ab section]
cd /usr/local/apache2/bin
./ab -n 100 node3/

[webmin section]

tar zxvf webmin-1.300.tar.gz
cd webmin-1.300
./setup.sh /usr/local/webmin

[nagios section]

tar zxvf nagios-1.0.tar.gz
adduser nagios
passwd nagios
./configure
make all;make install
make install-init
make install-config

For /usr/local/apache2/conf/httpd.conf modification

######

## For Nagios Use Only ## ScriptAlias /nagios/cgi-bin/ "/usr/local/nagios/sbin/" Alias /nagios "/usr/local/nagios/share/"## Finish ##
## For Nagios Use Only##AllowOverride AuthConfigOptions +ExecCGIAddHandler cgi-script .cgi .plAllow from allOrder allow,deny
Options NoneAllowOverride AuthConfigOrder allow,denyAllow from all## Finish ##

######
Try it… http://localhost/nagios/

[nagiosplus section]
tar zxvf nagios-plugins-1.4.3.tar.gz
cd nagios-plugins-1.4.3/
./configure
make;make install

[nagios configuration]
cd /usr/local/nagios/etc
make all sample file to cfg file
all cfg file as notes, use minimal.cfg to be default

(cgi.cfgminimal.cfgnagios.cfgcheckcommands.cfgmiscommands.cfgresource.cfg)

Only need to modify the minimal.cfg file as followings
contact area

####

define contact{ contact_name juergen alias Juergen Chiu service_notification_period 24x7 host_notification_period 24x7 service_notification_options w,u,c,r host_notification_options d,r service_notification_commands notify-by-email host_notification_commands host-notify-by-email email juergen@localhost.localdomain }

####
contactgroup area

####

define contactgroup{ contactgroup_name Cluster-Manager alias Cluster Administrators members juergen }

####
host area

####

define host{ host_name node2 alias Cluster Server 2 address 192.1.1.2 check_command check-host-alive max_check_attempts 10 notification_interval 120 notification_period 24x7 notification_options d,r contact_groups Cluster-Manager }

####
hostgroup area

####

define hostgroup{ hostgroup_name Juergen alias Cluster Servers members node2,node3 }

####
service area
####

define service{ host_name node2 service_description HTTP is_volatile 0 check_period 24x7 max_check_attempts 3 normal_check_interval 3 retry_check_interval 1 contact_groups Cluster-Manager notification_interval 120 notification_period 24x7 notification_options w,u,c,r check_command check_http }

####

Modify cgi.cfg file for authentication (use_authentication=0)
Remark the checkcommands.cfg and misccommands.cfg line in nagios.cfg file
add the notes into minimal to add the check_http function

####

define command{ command_name check_http command_line $USER1$/check_http -H $HOSTADDRESS$ }

####

[nagios startup section]
cd /usr/local/nagios/bin
"./nagios -v ../etc/nagios.cfg" to check the config status
./nagios ../etc/nagios.cfg

NetPIPE (Network Protocol Independent Performance Evaluator) installation tips with mpirun

2008-01-08T14:23:00.001+08:00

Needed failes
1. mpich.tar.gz (http://www-unix.mcs.anl.gov/mpi/mpich2/downloads/mpich2-1.0.tar.gz)
2. NetPIPE_3.6.2.tar.gz (http://www.scl.ameslab.gov/netpipe/code/NetPIPE_3.6.2.tar.gz)
Installation
tar zxvf mpich.tar.gz
tar zxvf NetPIPE.tar.gz
######### NetPIPE ##################
Get into NetPIPE directory
modify makefile MP_Lite_home --> mpich directory
mpicc --> mpich/bin/mpicc
make mpi
*******************************************************
example command
Get into NetPIPE directory first.
mpirun -np 4 ./NPmpi

HPL (Linpack) installation and how to start to test

2008-01-08T14:21:00.001+08:00

Needed files
1. mpich.tar.gz (http://www-unix.mcs.anl.gov/mpi/mpich2/downloads/mpich2-1.0.tar.gz)
2. tvcpp0p8.tar.gz (http://www.vsipl.org/software/tvcpp0p8.tar.gz)
3. hpl.tar.gz (http://www.netlib.org/benchmark/hpl/hpl.tgz)
Installation
tar zxvf mpich.tar.gz
tar zxvf tvcpp0p8.tar.gz
tar zxvf hpl.tar.gz
######### tvcpp0p8 ##################
Get into tvcpp0p8 directory
make all
######### hpl ##################
Get into hpl directory
cp ./setup/Make.Linux_PII_VSIPL ./ (VSIPL is suit for tvcpp0p8 program)
modify Make.Linux_PII_VSIPL file.
1. TOPdir
2. MPdir
3. LAdir
4. LAlib --> libvsip_c.a to libvsip.a
make all arch=Linux_PII_VSIPL
*********************************************
example command
mpirun -np 4 xhpl (at least 4 processes)
*run this command in Xwin mode.

PMB utility howto and now change to IMB by Intel

2008-01-08T14:18:00.001+08:00

Needed files
1. mpich.tar.gz (http://www-unix.mcs.anl.gov/mpi/mpich2/downloads/mpich2-1.0.tar.gz)
2. PMB2.2.1.tar.gz (ftp://ftp.pallas.com/pub/PALLAS/PMB/PMB2.2.1.tar.gz)
Installation
tar zxvf mpich.tar.gz
tar zxvf PMB2.2.1.tar.gz
######### PMB ##################
Get into PMB2.2.1 directory
modify make_Linux file. MPI_HOME --> mpich directory
modify Makefile to enable "include make_Linux".
make (do not use parameter "all")
chmod 755 PMB2.2.1
chmod 755 SRC_PMB
*******************************************************
example command
Get into mpich/bin directory.
./mpirun -nolocal -np 4 PMB-MPI1 PingPong PingPing Sendrecv

MPICH2 briefly installation tips and howto to check

2008-01-08T14:15:00.001+08:00

Needed Packages
1. mpich.tar.gz (http://www-unix.mcs.anl.gov/mpi/mpich2/downloads/mpich2-1.0.tar.gz)
2. RSH
3. NIS (ypserv)
Needed Daemon
1. nfs
2. netfs
3. network
4. nfs (server)
5. rstatd (for RPC)
6. portmap
7. rsh
8. xinetd
9. ypserv (server)
10. yppasswdd (server)
11. ypbind (client) <-- chkconfig ypbind on Installation tar zxvf mpich2.tar.gz ######### HOSTS ################## All /etc/hosts file in all client should contain all nodes information or it will fail. ######### mpich ################## use another user login and use these tools. Get into mpich directory ./configure --prefix=/home/hpcuser/mpich2 <-- not the same with the source folder make;make all;make install add "export PATH=/home/hpcuser/mpich2/bin/:$PATH" to ~/.bash_profile ######### mpd ################## cd $HOME touch .mpd.conf chmod 600 .mpd.conf add "secretword=111111" into this file #mpd& --> start the mpd daemon for mpiexec command.
You can test by "mpiexec -n 1 /bin/hostname" to see if you can run mpi2.
Or use "mpdallexit" to exit the mpd daemon.
######### RSH ##################
It used on client OS.
Open rsh daemon with xinetd service
modify PAM rule under /etc/pam.d/rsh
**remove the "pam_rhosts_auth" option
DON'T USE RSH AS ROOT!!!!!! (Permission Deny)
######### yp (NIS server) ##################
common settings
add "NISDOMAIN=hpcdomain" to /etc/sysconfig/network file
modify /etc/nsswitch passwd item to "nis files"
Server
add following items to /etc/ypserv.conf
127.0.0.0/255.255.255.0 :* :* :none
192.1.0.0/255.255.255.0 :* :* :none
add "/usr/lib/yp/ypinit -m" to /etc/rc.d/rc.local
add "/home (rw,sync)" to /etc/exports and do "/etc/rc.d/init.d/nfs reload"
add "/usr/local/src (rw,sync)" to /etc/exports and do "/etc/rc.d/init.d/nfs reload"
Client
add "domain pxe server 192.1.0.254" to /etc/yp.conf
add "/usr/lib/yp/ypinit -s pxe" to /etc/rc.d/rc.local
add "192.168.0.1:/home" to /etc/fstab
add "192.168.0.1:/usr/local/src" to /etc/fstab
add the mpi user's GID to /etc/group
*******************************************************
example command
cup stress
~/mpich/bin/mpirun -np 4 ~/mpich/mpe/contrib/life/life_g <-- make first, and type 100,1000 arter enter mpirun -np 2 ~/mpich/mpe/contrib/mandel/pmandel <-- xwin demo, "make" first (reference in README file) mpirun -np 4 PMB-MPI1 PingPong PingPing Sendrecv ********* Demo Used ********** cd ~/mpich/mpe ./configure --disable-checkMPI --disable-slog2 make all ~/mpich/examples/basic make mpirun -np 4 ./cpilog --> You will see all processes where they are.
~/mpich/examples/perftest
./configure
make all

MPICH installation and setting tips under Linux platform

2008-01-08T14:05:00.001+08:00

Needed Packages
1. mpich.tar.gz (http://www-unix.mcs.anl.gov/mpi/mpich2/downloads/mpich2-1.0.tar.gz)
2. RSH
3. NIS (ypserv)
Needed Daemon
1. nfs
2. netfs
3. network
4. nfs (server)
5. rstatd (for RPC)
6. portmap
7. rsh
8. xinetd
9. ypserv (server)
10. yppasswdd (server)
11. ypbind (client) <-- chkconfig ypbind on Installation tar zxvf mpich.tar.gz ######### HOSTS ################## All /etc/hosts file in all client should contain all nodes information or it will fail. ######### mpich ################## use another user login and use these tools. Get into mpich directory ./configure make modify ($MPI_HOME)/util/machines/machines.LINUX to suit your client's hostname or FQDN. (These hostname should be included in /etc/hosts file) add "export PATH=/home/hpcuser/mpich/bin/:$PATH" to ~/.bash_profile ######### RSH ################## It used on client OS. Open rsh daemon with xinetd service modify PAM rule under /etc/pam.d/rsh **remove the "pam_rhosts_auth" option DON'T USE RSH AS ROOT!!!!!! (Permission Deny) ######### yp (NIS server) ################## common settings add "NISDOMAIN=hpcdomain" to /etc/sysconfig/network file modify /etc/nsswitch passwd item to "nis files" Server add following items to /etc/ypserv.conf 127.0.0.0/255.255.255.0 :* :* :none 192.1.0.0/255.255.255.0 :* :* :none add "/usr/lib/yp/ypinit -m" to /etc/rc.d/rc.local add "/home (rw,sync)" to /etc/exports and do "/etc/rc.d/init.d/nfs reload" add "/usr/local/src (rw,sync)" to /etc/exports and do "/etc/rc.d/init.d/nfs reload" Client add "domain pxe server 192.1.0.254" to /etc/yp.conf add "/usr/lib/yp/ypinit -s pxe" to /etc/rc.d/rc.local add "192.168.0.1:/home" to /etc/fstab add "192.168.0.1:/usr/local/src" to /etc/fstab add the mpi user's GID to /etc/group ******************************************************* example command cup stress ~/mpich/bin/mpirun -np 4 ~/mpich/mpe/contrib/life/life_g <-- make first, and type 100,1000 arter enter mpirun -np 2 ~/mpich/mpe/contrib/mandel/pmandel <-- xwin demo, "make" first (reference in README file) mpirun -np 4 PMB-MPI1 PingPong PingPing Sendrecv ********* Demo Used ********** cd ~/mpich/mpe ./configure --disable-checkMPI --disable-slog2 make all ~/mpich/examples/basic make mpirun -np 4 ./cpilog --> You will see all processes where they are.
~/mpich/examples/perftest
./configure
make all

Cluster manager tool usage and samba HA howto

2008-01-08T11:50:00.003+08:00

#cluadmin
>service add
Service name: clusamba
Preferred member [None]: node2
Relocate when the preferred member joins the cluster (yes/no/?) [no]: yes
User script (e.g., /usr/foo/script or None) [None]:
Status check interval [0]: 90
Do you want to add an IP address to the service (yes/no/?) [no]: yes

IP Address Information

IP address: 10.1.1.254
Netmask (e.g. 255.255.255.0 or None) [None]:
Broadcast (e.g. X.Y.Z.255 or None) [None]:
Do you want to (a)dd, (m)odify, (d)elete or (s)how an IP address, or
are you (f)inished adding IP addresses [f]:
Do you want to add a disk device to the service (yes/no/?) [no]: yes

Disk Device Information

Device special file (e.g., /dev/sdb4): /dev/sdb1
Filesystem type (e.g., ext2, ext3 or None): ext2
Mount point (e.g., /usr/mnt/service1) [None]: /mnt
Mount options (e.g., rw,nosuid,sync): rw,nosuid,sync
Forced unmount support (yes/no/?) [yes]:
Would you like to allow NFS access to this filesystem (yes/no/?)\
[no]: no
Would you like to share to Windows clients (yes/no/?) [no]: yes

You will now be prompted for the Samba configuration:
Samba share name: clushare

The samba config file /etc/samba/smb.conf.clushare does not exist.

Would you like a default config file created (yes/no/?) [no]: yes

Successfully created /etc/samba/smb.conf.clushare.
Please remember to make necessary customizations and then copy the file
over to the other cluster member.

Do you want to (a)dd, (m)odify, (d)elete or (s)how DEVICES, or
are you (f)inished adding DEVICES [f]: f
name: clusamba
preferred node: node2
relocate: yes
user script: None
monitor interval: 90
IP address 0: 10.1.1.254
netmask 0: None
broadcast 0: None
device 0: /dev/sdb1
mount point, device 0: /mnt
mount fstype, device 0: ext2
mount options, device 0: rw,nosuid,sync
force unmount, device 0: yes
samba share, device 0: clushare
Add clusamba service as shown? (yes/no/?) yes

Test procedure:
You can reboot or shutdown one of these 2 nodes and observe the smb daemon in another node.
#smbclient -L 10.1.1.254
You have to see a sharename with "clushare" and Comment is "High Availability Samba Service" and done.

Reference site:
http://www.redhat.com/docs/manuals/enterprise/RHEL-AS-2.1-Manual/cluster-manager/s1-service-samba.html

Use iscsi driver to integrate NAS storage in Linux system

2008-01-08T11:46:00.001+08:00

##### Environment Settings############
OS: RedHat AS2.1 u5
Kernel: 2.4.9-e.49smp
rpm file: clumanager-1.0.27-1

node1 --> 10.1.1.101
node2 --> 10.1.1.102
Service IP --> 10.1.1.254 (Public IP)
################################

#### iSCSI settings with NAS Storage #########
Install NAS with linux-iscsi-.tgz from http://sourceforge.net/index.php
uncompress the file and into the iscsi directory
make
make install
Do next 3 steps

#vi /etc/iscsi.conf
----------------------------------------------------------------------
DiscoveryAddress=10.1.1.1:3260 --> your NAS' IP and port number
----------------------------------------------------------------------

#vi /etc/initiatorname.iscsi
----------------------------------------------------------------------------
InitiatorName=host1--> your NAS’ share hosts name
---------------------------------------------------------------------------

#/etc/init.d/iscsi start
You should find out your NAS share disk in /proc/partition as /dev/sda
##########################################

####### raw devices settings ##########
fdisk /dev/sda as /dev/sda1 and /dev/sda2
***Don't use mke2fs or something to format these 2 partition.***
Modify /etc/sysconfig/rawdevices file to add:
/dev/raw/raw1 /dev/sda1
/dev/raw/raw2 /dev/sda2
/etc/rc.d/init.d/rawdevices start
Until now your 2 raw devices are workable.
##########################################

########## Cluster HA settings #########
You can use relative softwares like clu* to manage cluster members.
*** The sample settings below focus on node1, if you use node2 will be reversed.
#cluconfig
Enter cluster name: ha1
Enter IP address for cluster alias: 10.1.1.254 --> This is your service IP, NOT real IP for NIC.
---- Next step is configure your Member 0 --> yourself ----
Enter name of cluster member: node1
Enter number of heartbeat channels:1 --> We only use 1 NIC to connect to another node
Channel type:net
Enter hostname of the cluster member on heartbeat channel 0: node1
---- Next step is configure your raw devices ----
Enter Primary Quorum Partition: /dev/raw/raw1 --> such as your raw devices list in /etc/sysconfig/rawdevices
Enter Shadow Quorum Partition: /dev/raw/raw2 --> such as your raw devices list in /etc/sysconfig/rawdevices
Power switch: NONE

---- Next step is configure your Member 1 --> node2 ----
Enter name of cluster member: node2
Enter hostname of the cluster member on heartbeat channel 0: node2
---- Next step is configure its raw devices ----
Enter Primary Quorum Partition: /dev/raw/raw1 --> such as its raw devices list in /etc/sysconfig/rawdevices
Enter Shadow Quorum Partition: /dev/raw/raw2 --> such as its raw devices list in /etc/sysconfig/rawdevices
Power switch: NONE

*** It will save your configuration in /etc/cluster.conf
Remember if you want to remove the cluster.rpm file, delete the /etc/cluster.conf after you remove.
########################################

Now you can use ifconfig to show your NIC information.
It should add a virtual IP address eth0:0 as 10.1.1.254. --> Your service IP is in eth0:0.

Test procedure
1. Shutdown the node2 directly (power off).
2. Use ifconfig in node1 to observe if its NIC will add a eth0:0 directly.
3. It should less than 30 sec and under my testing is 15 sec.

Reference site:
http://www.redhat.com/docs/manuals/enterprise/RHEL-AS-2.1-Manual/cluster-manager/