大約在一年前,我寫了一篇 Twitter火熱之謎 ,在文末如是說:
雖然嘗試開了個 Twitter 戶口 ,有時會寫一些心情紀錄,但我認為自己在此上並不會很「活躍」就是了
這句話早就要被推翻了。
事實證明,這一年來,我的 Twitter 使用量不少,可以參
There are a number of awkward things about URL fragments, including thatthey commit you to a certain implementation of your page structure ifyou are going to provide cool URLs . At the same time,I believe that they're the only way to make a reference to a part of apage, so they're pretty essential if you want to aggregate informationon a page but still be able to point to specific bits.
For example, WanderingThoughts uses URL fragments to point to thecomments on a specific entry and
Both virtualization and iSCSI are fundamentally 'sharing' technologies,where multiple things use a shared infrastructure. This means that theyhave a shared set of general security risks, pretty much common to anysharing technologies: cross-contamination and base system compromise.
Cross contamination is the ability to interfere with other things usingthe shared environment and to compromise them in turn; having a sharedinfrastructure necessarily gives you a channel to attack other thingsthat are using that infrastructure. This isn't novel, but virtualizationand iSCSI make it

It's really simple: we installed the latest Ubuntu 6.06 kernel updatelast night, since it's a security fix. Today, our machines startedpanicing with 'kernel BUG at fs/nfs/inode.c:174' messages (threemachines so far, one of them three times), so we wanted to revertback to the old kernel.
Guess what: it wasn't there any more. Apparently Ubuntu feels freeto have (some) kernel updates overwrite your
大約在一年前,我寫了一篇 Twitter火熱之謎 ,在文末如是說:
雖然嘗試開了個 Twitter 戶口 ,有時會寫一些心情紀錄,但我認為自己在此上並不會很「活躍」就是了
這句話早就要被推翻了。
事實證明,這一年來,我的 Twitter 使用量不少,可以參

There is a certain habit in applications these days of onlyallowing you to run one copy of themselves; for example, Firefox . I find myself more and moreirritated by this, because it is usually implemented sloppily.
A good implementation must hide the fact that it is not actuallyrunning a second copy of the application. Sloppy implementations failto completely hide this fact, generally by missing various differencesbetween the environment that the original version of the application isrunning in and the environment that the second copy is running in.