BMTD 's Yard of Fun

Technology, Sports, Music, Chinese Essays

Browsing Posts in Uncategorized

I currently own a zt-180 “epad” android pad… it’s ok running android 2.1 but kinda slow when running 2.2. I also don’t like its resistance touch screen and the short battery life (2 hours)… so I am looking for a new one now.

now the question is : which to buy?

here is a list after some quick google searches:
— Nook color: 7 inch, battery good; no video cam and gps. $245 +tax; cortex a-8 1G hz 512M ram.
— Dell streak wifi: 7 inch. 2 camares; screen resolution lower and other complaints. fast CPU (tegra 2 ) dual core 512M memory. No usb charging. $278 @ newegg.
— samsum galaxytab 7 inch wifi: about $350.
— Viewsonic gTablet: 10 inch. 1.3M camera. tegra 2 cpu 512 MB ram.
— Asus – Eee Pad Transformer Table: 10 inch. tegra 2 cpu 1GB ram. good reviews. $399.
— Toshiba: 10,1 inch. fulle size sd card slot; full usb 2.0; replaceable battery; $479



Since this problem seems to popup on different lists, this message has
been cross-posted to the general Red Hat discussion list, the RHEL3
(Taroon) list and the RHEL4 (Nahant) list. My apologies for not having
the time to post this summary sooner.

I would still be banging my head against this problem were it not for
the generous assistance of Tom Sightler <ttsig@xxxxxxxxxxxxx> and Brian
Long <brilong@xxxxxxxxx>.

In general, the out of memory killer (oom-killer) begins killing
processes, even on servers with large amounts (6Gb+) of RAM. In many
cases people report plenty of “free” RAM and are perplexed as to why the
oom-killer is whacking processes. Indications that this has happened
appear in /var/log/messages:
Out of Memory: Killed process [PID] [process name].

In my case I was upgrading various VMware servers from RHEL3 / VMware
GSX to RHEL4 / VMware Server. One of the virtual machines on a server
with 16Gb of RAM kept getting whacked by the oom-killer. Needless to
say, this was quite frustrating.

As it turns out, the problem was low memory exhaustion. Quoting Tom:
“The kernel uses low memory to track allocations of all memory thus a
system with 16GB of memory will use significantly more low memory than a
system with 4GB, perhaps as much as 4 times. This extra pressure
happens from the moment you turn the system on before you do anything at
all because the kernel structures have to be sized for the potential of
tracking allocations in four times as much memory.”

You can check the status of low & high memory a couple of ways:

# egrep 'High|Low' /proc/meminfo
HighTotal:     5111780 kB
HighFree:         1172 kB
LowTotal:       795688 kB
LowFree:         16788 kB

# free -lm
total       used       free     shared    buffers     cached
Mem:          5769       5751         17          0          8       5267
Low:           777        760         16          0          0          0
High:         4991       4990          1          0          0          0
-/+ buffers/cache:        475       5293
Swap:         4773          0       4773

When low memory is exhausted, it doesn’t matter how much high memory is
available, the oom-killer will begin whacking processes to keep the
server alive.

There are a couple of solutions to this problem:
continue reading…

转自: http://www1.haiguinet.com/bbs/viewtopic.php?p=1360281#1360281

作者:安普若海归茶馆 发贴, 来自【海归网】 http://www.haiguinet.com

安氏大俗商业学:甲方和乙方,到底怎么了?

做甲方或者乙方,你将期待什么?你要防范什么?为什么在中国会出现这种中国特有的甲方和乙方的特殊关系?

甲乙双方本应是合同契约关系,如果大家都严格遵守合同,而且该合同起草的全面、完整、准确、规范,那么甲乙双方的关系就很简单,照着合同办事就是了。 但是,在中国首先一个问题就是往往商业合同都写得十分简单而且不规范,因为中国的商人还不习惯使用律师起草合同,许多合同都是下面的一般工作人员自己堆鼓 出来的,既没有法律知识又没有商业经验,而且老总也觉得合同并不那么重要,写个一页纸的合同就行了,所以就省了律师这两个眼珠子钱了。我见过的合同里,使 用不准确的语言,漏洞,甚至自相矛盾的比比皆是,甚至到了搞笑的程度。

中国人喜欢用简单的合同的另外一个原因还是不太习惯“先小人后君子”的办事方式,认为有些话说出来会伤了对方的面子。事实上也确实如此,有些人喜欢把许多商业上的事情take it personally,一句话,还是不够professional!

简单的合同也有好处,那么就是提高了合同签署之前和当时的效率,甲乙双方不需要为了每个条款逐字逐句的讨论了。但是合同签了之后,执行起来不 出问题则已,一旦遇到问题(而且是肯定遇到问题),那么麻烦就大了。所以美国人说:在中国,签了合同只是谈判的开始,而且不是谈判的结束。

中国的简单合同把过多的事情列为“未尽事宜,另行商议”,这样就给甲乙双方在执行合同时带来了太多变化的空间,一旦遇到合同里没有阐述的问 题,甲乙双方就可能各自按照自己的意愿去做,“一个中国,各自表述”,各自发挥自己的政治智慧,但是你要碰上对方是马英九还好,要是碰上陈水扁,那么肯定 是要闹翻脸了。这就是甲乙双方遇到的第一个风险。

就算合同写的全面、完整、准确、规范,那么在执行合同的时候,甲乙双方仍然可能不按合同办事。比如甲方到时不付款,乙方到时不交货,或者以次充好,欺骗甲方。这是甲方或者乙方经常面临的第二个风险。
continue reading…

朋友的朋友做的.

卢冠廷, 光头身瘦满脸胡子茬, 一副不入偶像fans法眼的老土形象, 唱腔"怪异", 却是香港流行乐坛最有才的音乐人之一.

内地的年轻人或许听过他的歌,不过多半是来自电影大话西游片尾的曲子"一生所爱", 甚至有人把那歌声当成是罗文.

作为唱作人, 他的经典:
–天鸟
–但愿人长久
–陪着你走
–漆黑将不再面对
–快乐老实人
–一生所爱

作为创作人, 他的作品通过80年代的不少歌手流传:

— 天籁 星际传说 (关正杰)
— 凭着爱 (苏芮), 再回首(姜育恒)
–你在何地 (张国荣)
–最爱是谁 (林子祥, 电影"最爱")
— 天变地变情不变 (张学友)
— 如果你是我的传说 (刘德华)
— 长伴千世纪 (陈百强)

其中很喜欢的有这首"快乐老实人"…原因? 如歌词 : "喜欢即是喜欢…"

这首歌如他的许多其他作品一样也是夫妻档–作词的乃是卢的太太唐书琛.

快乐老实人

演唱:卢冠廷
曲 : 卢冠廷 词 : 唐书琛

讲出心里见解
不需多顾虑
附和声不响朗震荡又如何
豪强人自重

可憎即说可憎
不讲谎话
是自信不感到世上做人难
盲从成祸患

快乐老实人
敢想敢当敢说每段老实话
又是数十年
我要每天展笑阔步朗日下
喜欢即说喜欢
不需多顾忌
莫自欺解心困惑莫迟疑
何其容易事

一生爽朗坦率
终生不抱憾
莫自卑不需要背著别人愁
抬头人自傲

快乐老实人
敢想敢当敢说每段老实话
又是数十年
我要每天展笑阔步朗日下

快乐老实人
敢想敢当敢说每段老实话
来日又是数十年
我要每天展笑阔步朗日下