校内网好sx

只不过换了一个脑袋，居然不认我了...
你的资料完整度只有70%。

大家都能看出这个是我吧 ;)

大家新年快乐!
2008年注定不平凡，2009呢，也一定不平凡。

未知的精彩，不是么？

Adblock屏蔽校内广告

昨晚上校内的时候惊奇的发现好多广告，在使用adblock并订阅了若干列表之后这是一件很不可思议的事情。google到这篇文章，试验了一下，相当有效。从此和xiaonei广告say 88了。

新加的Rules：

• http://gg.xiaonei.com/*
• xiaonei.com#div(ad-bar)
• xiaonei.com#div(beta-bar)
• xiaonei.com#div(blank-holder)
• xiaonei.com#div(class*=selected)
• xiaonei.com#div(zidou_music)

小游Cornell

今天天气不错，微雪但是有太阳，于是驱车去康奈儿大学(Cornell University)。当然，驱车的不是我，是XY同学。尽管拿了XY同学的车熟悉了一段时间，但离马路杀手还是有点距离。杀手嘛，得保的住自己性命啊。回主题，一路上风景不错，可谓体验了一把美国式的山村小道。途经finger lakers，下去拍了几张小照，湖边好大的风。又经一酒庄，买了几瓶小酒带回来。驱车俩小时，终于到了Ithaca。Ithaca真不大，我们就直奔Cornell。

Cornell校园不小，似乎还分东西南北中五个校区，风景也是不错的，比起我那小小的学校那可是漂亮多了。我们就一路违章停车一路欣赏风景，只可惜是冬天，基本只剩下枯枝了。令人惊奇的是学校里有一瀑布，还非常壮观，一会儿上图便知。

回城之前在Ithaca吃了顿buffet，又一次论证了Pittsburgh不适合居住的命题。

流水帐完毕，上图。

The Elements of Programming Style

抽空读完了传说中经典图书之一的。虽然书是以Fortran和PL/I作为主体语言的，但大多数内容却一点都不过时。书中的大纲如下：

Introduction

1. Write clearly - don't be too clever.

Expression

2. Say what you mean, simply and directly.
3. Use library functions.
4. Avoid temporary variables.
5. Write clearly - don't sacrifice clarity for 'efficiency.'
6. Let the machine do the dirty work.
7. Replace repetitive expressions by calls to a common function.
8. Parenthesize to avoid ambiguity.
9. Choose variable names that won't be confused.
10. Avoid the Fortran arithmetic IF.
11. Avoid unnecessary branches.
12. Use the good features of a language; avoid the bad ones.
13. Don't use conditional branches as a substitute for a logical expression.
14. Use the 'telephone test' for readability.

Control Structure

15. Use DO-END and indenting to delimit groups of statements.
16. Use IF-ELSE to emphasize that only one of two actions is to be performed.
17. Use DO and DO-WHILE to emphasize the presence of loops.
18. Make your programs read from top to bottom.
19. Use IF, ELSE IF, ELSE IF, ELSE to implement multi-way branches.
20. Use the fundamental control flow constructs.
21. Write first in an easy-to-understand pseudo-language; then translate into whatever language you have to use.
22. Avoid THEN-IF and null ELSE.
23. Avoid ELSE GOTO and ELSE RETURN.
24. Follow each decision as closely as possible with its associated action.
25. Use data arrays to avoid repetitive control sequences.
26. Choose a data representation that makes the program simple.
27. Don't stop with your first draft.

Program Structure

28. Modularize. Use subroutines.
29. Make the coupling between modules visible.
30. Each module should do one thing well.
31. Make sure every module hides something.
32. Let the data structure the program.
33. Don't patch bad code - rewrite it.
34. Write and test a big program in small pieces.
35. Use recursive procedures for recursively-defined data structures.

Input and Output

36. Test input for validity and plausibility.
37. Make sure input cannot violate the limits of the program.
38. Terminate input by end-of-file or marker, not by count.
39. Identify bad input; recover if possible.
40. Treat end of file conditions in a uniform manner.
41. Make input easy to prepare and output self-explanatory.
42. Use uniform input formats.
43. Make input easy to proofread.
44. Use free-form input when possible.
45. Use self-identifying input. Allow defaults. Echo both on output.
46. Localize input and output in subroutines.

Common Blunders

47. Make sure all variables are initialized before use.
48. Don't stop at one bug.
49. Use debugging compilers.
50. Initialize constants with DATA statements or INITIAL attributes; initialize variables with executable code.
51. Watch out for off-by-one errors.
52. Take care to branch the right way on equality.
53. Avoid multiple exits from loops.
54. Make sure your code 'does nothing' gracefully.
55. Test programs at their boundary values.
56. Program defensively.
57. 10.0 times 0.1 is hardly ever 1.0.
58. Don't compare floating point numbers just for equality.

Efficiency and Instrumentation

59. Make it right before you make it faster.
60. Keep it right when you make it faster.
61. Make it clear before you make it faster.
62. Don't sacrifice clarity for small gains in 'efficiency.'
63. Let your compiler do the simple optimizations.
64. Don't strain to re-use code; reorganize instead.
65. Make sure special cases are truly special.
66. Keep it simple to make it faster.
67. Don't diddle code to make it faster - find a better algorithm.
68. Instrument your programs. Measure before making 'efficiency' changes.

Documentation

69. Make sure comments and code agree.
70. Don't just echo the code with comments - make every comment count.
71. Don't comment bad code - rewrite it.
72. Use variable names that mean something.
73. Use statement labels that mean something.
74. Format a program to help the reader understand it.
75. Indent to show the logical structure of a program.
76. Document your data layouts.
77. Don't over-comment.

暴好玩的一组机器人

暴好玩的一个机器人对抗赛，虽然是遥控的...... 有的机器人还有出场动作... 国内怎么没这种比赛....

在engadget上看到的，原文地址

Install Brother HL-2140 on Arch Linux

I bought Brother HL-2140 laser printer months ago and that time it was automatically configured in Ubuntu Hardy. Since I replaced my system with Archlinux, I had to reinstall the driver. Today I tried to install the driver, following the article "Brother HL-2040" on archwiki.

The instructions are almost the same, as well as the drivers. I tried the official 2.0.2-1 driver which is for HL-2140, however, not working. Instead, the driver for HL-2040, which version is 2.0.1-1 works fine for me.

Here is the instructions.

1. install cups first

   > pacman -S cups
   > pacman -S lib32-libcups (if you're using x86-64)

2. downlaod the rpm packages of lpr driver and the cups wrapper
3. extract rpm files
   

   > rpmextract.sh brhl2040lpr-2.0.1-1.i386.rpm
   > rpmextract.sh cupswrapperHL2040-2.0.1-1.i386.rpm
   

   if u do not have rpmextract,

   > pacman -S rpmextract

4. replace all instances of /etc/init.d/ with /etc/rc.d/ in ./usr/local/Brother/cupswrapper/cupswrapperHL2040-2.0.1
5. replace all instances of /etc/printcap.local with /etc/printcap in ./usr/local/Brother/inf/setupPrintcap
6. copy ./usr/ and ./var/ (these are extracted from rpm files and already modified in step #4,5) to /usr/ and /var/ respectively
7. run the script to complete installation, it would aumatically restart cups server

   > /usr/local/Brother/cupswrapper/cupswrapperHL2040-2.0.1

8. finally, u can go to cups server http://localhost:631/ to have a test page as u like.
   

ps, if you meet some problem with cups error, you may refer to this post (link)

今天被科普了一下下

从水母上“万有引力是怎么产生的”一帖中，我发现我几乎就是不懂物理的人了。苹果为什么会落下来？高中的物理解答了，因为万有引力。为什么有万有引力？大学物理解答了，因为时空弯曲。为什么时空会弯曲呢？

好了，这个时候，众说纷纭了。但无外乎，就两种：要么如宗教信仰者说，是上帝创造的；要么就如人择原理告诉我们的，它就是这样的，不然就没有我们。然而，终究，没能解决本质问题，“为什么”。这个时候，也许哲学家们可以告诉我们答案。

关于“人择原理(Anthropic principle)”，可以看维基百科的页面，很白话的一种解释

问：为何宇宙是我们看到的这种样子?
答：如果它不是这个样子,我们就不会在这里.

一方面，这个解释近乎于无懈可击，另一方面，这个原理就是一个废话。当我们无法解释的时候，于是我们就说“它一定是这样的”。另外，人择原理也承认了宇宙中人类的参与。

Although our situation is not necessarily central, it is inevitably privileged to some extent.

--- Brandon Carter 1973

？？ in usb device

Issue: The file/directory names in file system are ?? when auto-mounted using HAL. [Archlinux/Gnome]

Solution:

1. open gconf-editor
2. system > storage > default_options > vfat
3. append "iocharset=utf8" to the value of "mount_options"
   

Tag Clouds in BLOG

see this

彩色man

今天新学一招，彩色man，让man变得多彩起来。说出来其实很简单，在~/.bashrc里增加一下内容

# For colourful man pages (CLUG-Wiki style)
export LESS_TERMCAP_mb=$'\E[01;31m'
export LESS_TERMCAP_md=$'\E[01;31m'
export LESS_TERMCAP_me=$'\E[0m'
export LESS_TERMCAP_se=$'\E[0m'
export LESS_TERMCAP_so=$'\E[01;44;33m'
export LESS_TERMCAP_ue=$'\E[0m'
export LESS_TERMCAP_us=$'\E[01;32m'

就这么简单，效果如下图:


ref: http://plog.longwin.com.tw/ost/1/409