March 2008


开始宁mm说要听这歌,回头找找~~~
都说了做人要HD,我总是忘记,看昨天高呼米元疲软万岁,今天就遭报应了。DisappointedSurprisedSad
 
去年夏天公司裁员的时候,老板向我解释,公司因为不景气,必须让一些同事走,但是公司真心希望剩下的员工继续坚守岗位,所以设了一个stay bouns. 我连多少钱都没有打听,觉得就是个怀柔的计量,没有当真。
 
一早,老板来邮件说,黑,还记得么,我们去年8月说,你如果你呆到3月底,就有bonus, 4/15号到帐!
 
我连忙回了一个谢谢,觉得老板,和HR都很有口齿,毫不犹豫的为飞来横财开心了18s, 3000美刀,Hyahyahya~~~, 18s后,一想,米元狂跌,我也遭殃了,缩水20%, 苍天啊,昨天还在看别人笑话,真不应该。报应啊!!ざまミロ~~~~~~~~~~~~~~~~~~~~~~~~下不为例(大家监督)Sarcastic。
 
* 今日の運気は 財成 です。     年運:再会 月運:陰影
 
12年后,日元兑米元从新突破100了, 期待有一天突破80-娃哈哈,米元万岁。
 
我这唯恐天下不乱的新栽了火风姿
说真的,我还是挺害怕享乐的。
 
从去年年底开始进入半乌政府状态到现在全乌政府边缘, 抗着不安ding但又没有丝毫恐惧的矛盾,承受着想自己管好自己又忍不住放纵贪玩的压抑,我不容易阿我。。一个正常一点的工作环境,哪里会有这样的烦恼。
 
比如周一,早上去见客户,为了中午会见电通mm, 把3个小时的事情两个小时做完,白白替客户节省了3w.
和mm吃了韩国参鸡汤,告别,因为挺饱,于是去逛街,买了一些零食,文具。。。终于鱼3点多,晃悠到公司。
 
哎,在这么下去可怎么办呢。
 
而今天,就现在,别说管我的,连陪我吃饭的人跑光了, 查了查esfortaçš„schedule,下午没有yoga。干吗好呢,,突发奇想发明了一个新词语,云在天边,我在逛街。我也就这点出息了,偶去mid town逛逛吧。。。。。。。。。。。。。。。。。。。。。要不去银座剪头发顺便逛街。。。。。。。。。。。。要不就乖乖在公司更新blog……….晚上sales说要带点数据回来,都怪她,否则俺就回家乐!
 
后记,因为想起3点多有预约去洗牙,所以所有计划都取消了。本觉得去了也谈不上享乐-仿佛处于一种快乐太多的沮丧,也许是这‘乐极生悲’的新解。
享乐应该是享受追求快乐的过程。恩=
 
 
嗯,总算有时间可以写状子控诉一下这个stupid bank.
 
2006,我应该也控诉过一次。本次控诉,其实是上次事件的伴随品。
 
几个月前,觉得应该给该帐号补充些米,一次去UFO的ATM存钱. 从UFO的aTM都可以提我最爱的西提的钱,而且不收手续费,不费吹灰之力提了50w出来,打算要存的时候,谁曾想傻银行居然出错了,然后他拔,不光傻而且还小家败气,容不得你在他家得阿童木上给别家存钱,我走投无路,我不得不揣着50w (没有预想到这个下场,没有带包,只有钱包,放不下50w), 半遮半掩,鬼鬼淙淙,横穿马路,冒着被车撞,钞票漫天飞舞的危险,跑到对面再对面的我的第二爱油储把钱存了。
我没有严肃地对待那次的出错,还确定的认为一切都是我的错。不是我操作有误,就是没有选好良辰吉日。想着过一阵子再去就会好的,再说了,那个银行不欢迎你去存钱啊,怎么会出错呢,tssd.
 
前天,我又蠢蠢欲动,于是去了,再次败北。加上在寒风中为它我首冷风吹,加上我的帐号不能只出不进,我第二天决议给她们打电话,问问究竟,把这个问题搞个水落石出。
电话通常都是很忙,我没有太在意,一边玩,一边耐心的等着。经过一番确认,调查,研究,被告知,我的卡卡,其实已经作废了。。。我狠狠的搜索一年半前发生的事,大概是他们推荐我换某IC卡,我同意了。然后,卡寄到的时候,我去密国出差,不在家,卡被退回银行了,我现在手里的卡也不能用了。这是啥GP service啊,也罢,有时间谴责还不如问问现在该怎么办。又一通确认,调查,研究,被告知,要去他们某支店,让他们从新给发一个。
我想,没办法,就只好去了。我这个人这么好说话,还爱跑腿,我去。可是,接着,人家又说,当天你不能拿到卡,去,就是申请,要‘后日‘才能出卡。我不乐意了,我说,那你现在不能给申请么?– 我摆出一大通argument, 诸如我想不起来到底啥时候申请的,你们啥时候给我发的卡,我还想知道我为啥没有拿到卡,我别的邮便似乎都没有丢?等等。
于是,人家有让我等着,其间,告诉我,说,她的时间快到了,她要找另外一个人和我接着说,%$@%@$^@$^@, 我气过头了,漏气了,漏到一定程度,觉得不想再多和他们理论了,在接下来的对话中,我爽快地告诉他们,好,我去店里申请。
 
这时候,我MSN已经挂起了,UFO最差的标语,以示不忿,以告世人.
 
昨天,我去了三田支店,一进去,拿了个号,立刻就被叫到,接应我的是个丑女,我是后来才觉得他很丑的。我告诉她情况,她说,你去二楼。
我考,我刚和你白说了亚,不行,我又和她说了一遍,她说你去二楼。口气就是希望我快点消失,我气鼓鼓的消失了,丑女就是说啥都不回吐出象牙来的。去二楼就去二楼。
 
二楼,接待我的明显是一个新人。 化妆boroboro, 夸张的眼影,naked lip很突兀。指甲油,退色的粉红,惨不忍睹。罢罢,赶快把事情办完,漂走~~
最后证实漂走~~这个小小的愿望实在是一个奢望,鬼画胡mm让我陪了她至少一个小时。
在我言简意赅的告诉她偶得来意后,她和她的上司样子的人开始了长达20分钟的讨论。
上司穿着和别人不一样颜色的衬衫,等级分明的地方,就是会明目张胆的体现这种差别(歧视)。上司一直在摇头,鬼画胡忽闪着掉银粉的好奇的大眼睛,一言不发。
最后,我百无聊赖,给同事发email的途中,她回到我的对面,等我邮件出去,她让我填表。 问我要换哪种卡,我说原来发行的是啥就要那个,昨天人家说是IC.
她说,昨天不是IC ,¥%·¥%,靠,你们社内的数据难道不一样么。 我也不知道原来要的是啥了,你告诉我,他们有什么区别,我从新选。 他,,,#¥!#%!离开座位,带回来几张介绍。靠,让我看文档啊,不行,我让她给我解释,一知半解的说明,听了也是白听,我告诉他我要IC的。 我忽然想起通胀这个问题。我的卡是没有通胀的,网上可以看近几个月的履历,但是以前的没有办法查。我问她又设么办法。她又走了,带回来一张表,我以前,我tssd去年底,就为了看以前,花了840手续费,看了,我告诉他,并且强调我不要workaround, 我要一个solution, 更本解决这个问题。她说,那你只能在网上看和纸上看作个选择,不能都选,我说,那我要纸上看。她说好,不过, 每个月要630手续费。我#¥%#%!。我又生他们的gp service的气了。我说,我2006年,就提出了这个issue,,当时的mm告诉我,可以,也没有说要手续费,现在为啥要了,当然,我那以后,也没有受到过什么免费的明细。 她很无辜的看着我。我看着她也没辙,0.01s脑筋一转,问我可不可以要通胀。她说应该可以。再次离开座位,消失无影踪。
等他回来的时候,还是一如既往的戴了几张表格,外加一个问题,你的口座是公司给开的么。 我说不是,是我自己开的。 我考,你要不相信我,就不要问我,直接问原支点。好不好,这叫基本的信任,尊重。好家伙,她不,她问完我,很从容的给原支点打电话,让他们给查查我的口座,是不是公司开的。由此又是10分钟。确认,是个人开的,她自信的微笑了,我们可以给你换有通胀的。我心想,常识都知道是可以的,不过你们的傻银行叫UFO,什么事情都能让你们变成‘惊喜’,你要是告诉我不可以,我也只能忍气吞声,悄悄的走开。
 
于是乎为了一张被退回的卡,一张完全valid,完全可以重发的卡,他们的傻业务流程,他们的对傻业务只之甚少的鬼话糊mm, 1-加减的call center gg, 我的service被无辜停了1年多不说,又不眨眼的被浪费了这么多宝贵时间和他们对峙,我还不能就此解约,因为我最爱德西提不能做很多自动转账,因为她是外国银行,老日排外,虽然第二最爱可以,但是要一个一个换,毫不麻烦,而且我已经花了这么多时间和精力。。。我在忍忍吧。如果还有下次,我若还不能解约,我就去买块豆腐回家练9印白骨抓,然后去破坏他们的ATM,然后去劫富济贫,让他们吃不了兜着走,让他们死的很难看。
 
最后,希望各位,认清贼船,提高警惕,上了贼船,不管你打不打算下来,都会很劳民伤财的。
 
 
3/12/2008 11:56:14 AM みみころ 008✿玲瓏心-趣味:UFJ最悪!!! UFJ最悪の中悪いんだけど
3/12/2008 11:56:22 AM みみころ 008✿玲瓏心-趣味:UFJ最悪!!! 1つ質問
3/12/2008 11:56:38 AM 008✿玲瓏心-趣味:UFJ最悪!!! みみころ はい:$
。。。。
3/12/2008 11:57:52 AM 008✿玲瓏心-趣味:UFJ最悪!!! みみころ それはテスト?
3/12/2008 11:58:00 AM 008✿玲瓏心-趣味:UFJ最悪!!! みみころ それとも必要?
3/12/2008 11:58:05 AM みみころ 008✿玲瓏心-趣味:UFJ最悪!!! テスト
3/12/2008 11:58:31 AM みみころ 008✿玲瓏心-趣味:UFJ最悪!!! だから制限あるのかなって
3/12/2008 11:58:35 AM 008✿玲瓏心-趣味:UFJ最悪!!! みみころ 嫌がらせ? :D
3/12/2008 11:58:47 AM 008✿玲瓏心-趣味:UFJ最悪!!! みみころ 聞いたことない
3/12/2008 11:58:56 AM 008✿玲瓏心-趣味:UFJ最悪!!! みみころ 多分誰もやったことないから
3/12/2008 11:58:59 AM みみころ 008✿玲瓏心-趣味:UFJ最悪!!! アクセンチュアの嫌がらせw
3/12/2008 11:59:05 AM 008✿玲瓏心-趣味:UFJ最悪!!! みみころ なるほど
之前,对IT 几乎完全丧失了兴趣的我,被某BLOG改变,回心转意了
这里介绍的事迹,人物,五一不让我为IT 是高科技而喝彩。
 
随便铁一个,牛仁的光荣事迹,这才叫IT – 多一份对高科技的追求,少一点急功近利,自己的付出更多人生活更美好,这些是无法用金钱来很亮的!!
 

One man writes Linux drivers for 235 USB webcams

Face to Face Michel, the pipe-smoking French Linux guru

By Fernando Cassia: Monday, 30 April 2007, 3:40 PM

Adopt 10 good habits

Ten good habits to adopt are:

  1. Make directory trees in a single swipe.
  2. Change the path; do not move the archive.
  3. Combine your commands with control operators.
  4. Quote variables with caution.
  5. Use escape sequences to manage long input.
  6. Group your commands together in a list.
  7. Use xargs outside of find.
  8. Know when grep should do the counting — and when it should step aside.
  9. Match certain fields in output, not just lines.
  10. Stop piping cats.

Make directory trees in a single swipe

Listing 1 illustrates one of the most common bad UNIX habits around: defining directory trees one at a time.
Listing 1. Example of bad habit #1: Defining directory trees individually

~ $ mkdir tmp
~ $ cd tmp
~/tmp $ mkdir a
~/tmp $ cd a
~/tmp/a $ mkdir b
~/tmp/a $ cd b
~/tmp/a/b/ $ mkdir c
~/tmp/a/b/ $ cd c
~/tmp/a/b/c $

It is so much quicker to use the -p option to mkdir and make all parent directories along with their children in a single command. But even administrators who know about this option are still caught stepping through the subdirectories as they make them on the command line. It is worth your time to conscientiously pick up the good habit:
Listing 2. Example of good habit #1: Defining directory trees with one command

~ $ mkdir -p tmp/a/b/c

You can use this option to make entire complex directory trees, which are great to use inside scripts; not just simple hierarchies. For example:
Listing 3. Another example of good habit #1: Defining complex directory trees with one command

~ $ mkdir -p project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}

In the past, the only excuse to define directories individually was that your mkdir implementation did not support this option, but this is no longer true on most systems. IBM, AIX®, mkdir, GNU mkdir, and others that conform to the Single UNIX Specification now have this option.

For the few systems that still lack the capability, use the mkdirhier script (see Resources), which is a wrapper for mkdir that does the same function:

~ $ mkdirhier project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}

Change the path; do not move the archive

Another bad usage pattern is moving a .tar archive file to a certain directory because it happens to be the directory you want to extract it in. You never need to do this. You can unpack any .tar archive file into any directory you like — that is what the -C option is for. Use the -C option when unpacking an archive file to specify the directory to unpack it in:
Listing 4. Example of good habit #2: Using option -C to unpack a .tar archive file

~ $ tar xvf -C tmp/a/b/c newarc.tar.gz

Making a habit of using -C is preferable to moving the archive file to where you want to unpack it, changing to that directory, and only then extracting its contents — especially if the archive file belongs somewhere else.

Back to top

Combine your commands with control operators

You probably already know that in most shells, you can combine commands on a single command line by placing a semicolon (;) between them. The semicolon is a shell control operator, and while it is useful for stringing together multiple discrete commands on a single command line, it does not work for everything. For example, suppose you use a semicolon to combine two commands in which the proper execution of the second command depends entirely upon the successful completion of the first. If the first command does not exit as you expected, the second command still runs — and fails. Instead, use more appropriate control operators (some are described in this article). As long as your shell supports them, they are worth getting into the habit of using them.

Run a command only if another command returns a zero exit status

Use the && control operator to combine two commands so that the second is run only if the first command returns a zero exit status. In other words, if the first command runs successfully, the second command runs. If the first command fails, the second command does not run at all. For example:
Listing 5. Example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c && tar xvf ~/archive.tar

In this example, the contents of the archive are extracted into the ~/tmp/a/b/c directory unless that directory does not exist. If the directory does not exist, the tar command does not run, so nothing is extracted.

Run a command only if another command returns a non-zero exit status

Similarly, the || control operator separates two commands and runs the second command only if the first command returns a non-zero exit status. In other words, if the first command is successful, the second command does not run. If the first command fails, the second command does run. This operator is often used when testing for whether a given directory exists and, if not, it creates one:
Listing 6. Another example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c

You can also combine the control operators described in this section. Each works on the last command run:
Listing 7. A combined example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c && tar xvf -C tmp/a/b/c ~/archive.tar
Back to top

Adopt 10 good habits

Ten good habits to adopt are:

  1. Make directory trees in a single swipe.
  2. Change the path; do not move the archive.
  3. Combine your commands with control operators.
  4. Quote variables with caution.
  5. Use escape sequences to manage long input.
  6. Group your commands together in a list.
  7. Use xargs outside of find.
  8. Know when grep should do the counting — and when it should step aside.
  9. Match certain fields in output, not just lines.
  10. Stop piping cats.

Make directory trees in a single swipe

Listing 1 illustrates one of the most common bad UNIX habits around: defining directory trees one at a time.
Listing 1. Example of bad habit #1: Defining directory trees individually

~ $ mkdir tmp
~ $ cd tmp
~/tmp $ mkdir a
~/tmp $ cd a
~/tmp/a $ mkdir b
~/tmp/a $ cd b
~/tmp/a/b/ $ mkdir c
~/tmp/a/b/ $ cd c
~/tmp/a/b/c $

It is so much quicker to use the -p option to mkdir and make all parent directories along with their children in a single command. But even administrators who know about this option are still caught stepping through the subdirectories as they make them on the command line. It is worth your time to conscientiously pick up the good habit:
Listing 2. Example of good habit #1: Defining directory trees with one command

~ $ mkdir -p tmp/a/b/c

You can use this option to make entire complex directory trees, which are great to use inside scripts; not just simple hierarchies. For example:
Listing 3. Another example of good habit #1: Defining complex directory trees with one command

~ $ mkdir -p project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}

In the past, the only excuse to define directories individually was that your mkdir implementation did not support this option, but this is no longer true on most systems. IBM, AIX®, mkdir, GNU mkdir, and others that conform to the Single UNIX Specification now have this option.

For the few systems that still lack the capability, use the mkdirhier script (see Resources), which is a wrapper for mkdir that does the same function:

~ $ mkdirhier project/{lib/ext,bin,src,doc/{html,info,pdf},demo/stat/a}

Change the path; do not move the archive

Another bad usage pattern is moving a .tar archive file to a certain directory because it happens to be the directory you want to extract it in. You never need to do this. You can unpack any .tar archive file into any directory you like — that is what the -C option is for. Use the -C option when unpacking an archive file to specify the directory to unpack it in:
Listing 4. Example of good habit #2: Using option -C to unpack a .tar archive file

~ $ tar xvf -C tmp/a/b/c newarc.tar.gz

Making a habit of using -C is preferable to moving the archive file to where you want to unpack it, changing to that directory, and only then extracting its contents — especially if the archive file belongs somewhere else.

Back to top

Combine your commands with control operators

You probably already know that in most shells, you can combine commands on a single command line by placing a semicolon (;) between them. The semicolon is a shell control operator, and while it is useful for stringing together multiple discrete commands on a single command line, it does not work for everything. For example, suppose you use a semicolon to combine two commands in which the proper execution of the second command depends entirely upon the successful completion of the first. If the first command does not exit as you expected, the second command still runs — and fails. Instead, use more appropriate control operators (some are described in this article). As long as your shell supports them, they are worth getting into the habit of using them.

Run a command only if another command returns a zero exit status

Use the && control operator to combine two commands so that the second is run only if the first command returns a zero exit status. In other words, if the first command runs successfully, the second command runs. If the first command fails, the second command does not run at all. For example:
Listing 5. Example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c && tar xvf ~/archive.tar

In this example, the contents of the archive are extracted into the ~/tmp/a/b/c directory unless that directory does not exist. If the directory does not exist, the tar command does not run, so nothing is extracted.

Run a command only if another command returns a non-zero exit status

Similarly, the || control operator separates two commands and runs the second command only if the first command returns a non-zero exit status. In other words, if the first command is successful, the second command does not run. If the first command fails, the second command does run. This operator is often used when testing for whether a given directory exists and, if not, it creates one:
Listing 6. Another example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c

You can also combine the control operators described in this section. Each works on the last command run:
Listing 7. A combined example of good habit #3: Combining commands with control operators

~ $ cd tmp/a/b/c || mkdir -p tmp/a/b/c && tar xvf -C tmp/a/b/c ~/archive.tar
Back to top

Nintendo Wii and Linux

Filed under: 3. Other Distros, Hardware, HowTos/Tutorials/Tips — E@zyVG @ 1:00 pm

Nintendo Wii has been a bit tougher to crack than hacker-friendly hardware like the PS3, which even has a Sony-approved Linux distro. But now the Wii hacking community has figured out how to run homebrew applications on Nintendo’s latest console, and that includes a rather unpolished “proof of concept” version of Linux that can run on the Wii. Few days ago this news came from the GameCube Linux Wiki:

24 Feb 2008: Long time, no see Although we haven’t posted any news in the last 2 years, we have silently continued our work keeping the kernel patches up to date. With the latest 2.6.24 release we have added support for the USB Gecko adapter as a console and terminal, so you can now logon into your gc-linux distro using minicom or HyperTerminal (TM). And last but not least, we have finally run natively Linux on the Nintendo Wii through Team Tweezers’ twilight-hack. We have released a small usbgecko-enabled Proof of Concept mini-distro to prove it. Did I say have fun? :)

Now, keep in mind, the hacking process is not simple. You need an SD card, SD card adapter for the Wii, a copy of Zelda: Twilight Princess, the ability to follow complex instructions, infinite patience, and the willingness to completely muck up your video game console if things go wrong.

Wii Technical Specification:

  • CPU (Central Processing Unit): IBM ‘Broadway’ 729MHz
  • Internal Storage: 512MB Flash Memory

  • USB 2.0: 2 Ports
  • System Memory: 256MB
  • Memory Expansion: 2 SD Memory
  • GPU (Graphics Processing Unit): ATI ‘Hollywood’
  • Optical Disc Drive: 8cm GameCube / 12cm Wii (DVD discs)
  • Supported Resolution: up to 480p
  • 12 cm Disc Capacity: 4.7GB (single) / 8.5GB (dual)
  • Wii Controller Ports: Wireless (4 maximum)
  • GameCube Controller Ports: 4 Ports
  • Internet Connectivity: WiFi 802.11b/g
  • Disc Compatibility: GameCube
  • GameCube Memory Expansion: 2 Ports

Links for running Linux on Wii:

« Previous PageNext Page »