Sunday, December 05, 2010

折腾的一个星期:喉咙疼

近期的健康真的下滑的许多,支撑不住的身体渐渐发出许多‘警报’,先是发烧、背椎酸痛,紧接着就是喉咙疼痛。这痛楚折腾了我整整一个星期,无论三餐都是白粥蒸鱼,满肚子也每时每刻都装着玉米水,这喉疼就是不愿离我而去,导致吞每一口口水都像是将一根根坚韧的针吞进喉咙似的疼痛。

自己在服用药物后,趁药力还未发效,在床上自己静思:即使多有权力、财力的人;又或是拥有千万个仇恨,只要病倒在床上,这一切都要归零!

听起来好悲哀,不过这就是事实。想到自己病倒的样子,爸妈、至爱、朋友担心的模样,其他的,都不重要了,就只有和自己说:
“我一定要赶紧好起来...”

喉咙就像这些堆积的石砖一样,好干硬,尽管你洒多少水,也于事无补...

Thursday, November 25, 2010

终于都病了…

好久没有这种感觉了,觉得身体都垮了!昨晚,下班回家后,就突然累得像干了一整天搬运工作似的,倒在沙发呼呼大睡了…

睡了两个小时,发现好几通电话都没接,头也重得像石头,连转身也都很辛苦。洗了澡,到楼下时感到双脚轻浮,觉得那时的梯级变得特别高,走得相当吃力。想说看看电视节目,不到15分钟,眼皮又变得很沉重了…跑到房间时,看看墙壁上的时钟,仿佛在对我说:
“现在才9点12分而已,你就要睡了吗?”

我无力理会什么有的没有的,倒在床上,又睡了!

起身了,看不见昨晚讥讽我的壁钟,走到厕所,感觉很陌生。再看看自己的脸孔,想问问‘他’到底是谁,怎么会跑到和我一样的厕所?

回到房间,靠着厕所一丝微光,显示了壁钟长短针的方向,原来,才凌晨4点多而已。我又睡了...

这样醒醒睡睡,也忘了摸摸发热的额头,就下楼去准备上班了...吃早餐时,觉得今天妈妈有点失手,我吃不出味道来了...抬起头来,眼前景物有点模糊,头的重量也只会偏向两边...

这时候,我很确定,我真的病了....


身体像是这个生锈的机械般的无奈....我应该好好休息了~

Wednesday, November 10, 2010

水灾后的合艾 - this is the Hatyai after the flood

好久没有和家人远行了,难得有机会和爸妈、姐到合艾去拜佛,带了心爱的Nikon D700一起去了。途中,还一直担心那里水灾的状况是否会影响我们的拜佛之旅...

到了那边情况虽然没有我想象的糟,但也还蛮不堪...

#1
最后一天在合艾,决定到大巴杀买东西时,发现没人在所谓的巴杀开档,反而在路边摆起许多摊子来了,买的都是真正的‘水货’ -〉浸过水的货品...
途中,我们就可以看见很多商店都关闭,为的是清洗商店被水浸过的家私、货品。

#2
许多东西都被这场水灾破坏了....

#3
难得这个仁兄还能苦中作乐,被我拍下来了...

#4
在路边,几乎都是堆积如山的垃圾....

#5
其实,着一堆堆的垃圾,给合艾带来了异味!

#6
很多当地人都在抢购水货!

#7
这些都是水灾遗留下来的证据!

#8
这场水灾似乎也带来许多商机 :-)

#9

#10
垃圾堵住了大水沟的水流,那里真的是臭味熏天...

Thursday, November 04, 2010

槟城观音亭 2010

很久都没有到处走走,拍拍照了;难得同事约出去,我也选了一个对槟城摄影师来说最普通不过的地方-观音亭,希望自己能够跳出自己之前的框框,拍出自己喜欢,并且跨越自己的另一个观音亭...

感谢OngTc, Soh Pey Jin, Look Chee Wai, Patrick Lim, Barry Chang; 为这个摄影活动增添了不少颜色。

#1

一个很普通的观音亭外观...

#2
整百年了,屋顶上的雕刻还是保存的很好!

#3
有点旧,但是很有味道...

#4
经过了岁月的侵袭,它们还是那么引人入胜...

#5
这根柱子也有上百岁了...

#6
拿着相机,我才发现到这些手工雕刻的字是多么漂亮...

#7
我到那里的时候还算很早,因此很少蜡烛和信徒...

#8
一盘简单的菊花,也可以让人看得出信徒对观音那种虔诚的心..祈求的都是天下太平,顺顺利利!

#8
我注意了这个阿伯很久了,他在每一个香炉都是那么虔诚的膜拜着,忍不住,就拍下了这一幕!

#9
这位阿伯,在这里卖了整半个世纪,每天还是可以风雨无阻的在这里开档。每次到哪里,我都会光顾阿伯卖的花生饼,太好吃,太有味道了....

#10

摄影师的悲哀:都是要自拍,才勉强看见自己的影子...

Saturday, October 30, 2010

VMWare ESX 3.x not able to detect Intel Gigabit adapters

Few days back, I received a customer's complaint about the VMWare ESX 3.X not able to detect the brand new Intel Network adapter. After check through the setup/configuration, I confirm there something to do with the product compatibility between this two famous company. This issue leave me no choice, but had to research by my own in order to appease this customer from bugging me through phone or email.

I'm lucky enough to get the below information within 15 mins, and I have to not only thank god, but need to thank Google - the powerful search engine as well.

From VMWare Knowledge-base, stated that the below Intel Adapter need to load the specify IGB driver, in order to get detected.

Networking devices based on the Intel® 82575 Gigabit Ethernet Controller:
  • Intel® 82575EB Gigabit Network Connection
  • Intel® 82575EB Gigabit Backplane Connection
  • Intel® Gigabit VT Quad Port Server Adapter
Networking devices based on the Intel® 82576 Gigabit Ethernet Controller:
  • Intel® 82576 Gigabit Network Connection
  • Intel® Gigabit ET Dual Port Server Adapter
  • Intel® Gigabit EF Dual Port Server Adapter

Solution from VMWare:

  • Enable NetQueue in VMkernel using VMware Infrastructure Client:

    1. Choose Configuration > Advanced Settings > VMkernel.
    2. Select VMkernel.Boot.netNetqueueEnabled.
  • Enable the igb module in the service console of the ESX host:

    # esxcfg-module -e igb
  • Set the required load option for igb to turn on VMDq:

    The option IntMode=3 must exist to indicate loading in VMDq mode. A value of 3 for the IntMode parameter specifies using MSI-X and automatically sets the number of receive queues to the maximum supported (devices based on the 82575 Controller enable 4 receive queues per port; devices based on the 82576 Controller enable 8 receive queues per port). The number of receive queues used by the igb driver in VMDq mode cannot be changed.

    For a single port, use the command:

    # esxcfg-module -s "IntMode=3" igb


    For two or more ports, use a comma-separated list of values as shown in the following example (the parameter is applied to the igb-supported interfaces in the order they are enumerated on the PCI bus):

    # esxcfg-module -s "IntMode=3,3, ... 3" igb
  • Reboot the ESX host system.

    Note: If you are using jumbo frames, you also need to change the values for
    netPktHeapMinSize to 32 and netPktHeapMaxSize to 128.

    For more information:

    one of my favorite shots during wedding day..
  •