听说很久了，一直没试过，因为那些反动的带色的网站看够了，曾经为wiki和google cache烦恼过，时间一长居然习惯了。
不过最近被GFW封的网站越来越多，甚至flickr.com。简直没有天理。
看到洪文《互动：一个网络警察的自白-》让我想起还有Tor可用。
装之，Tor支持Windows, MAC OSX还有linux，我就挨个装个遍。
再上wikipedia, flickr，都没问题了，就是慢点。上网慢了点，机器速度好像也拖慢了不少。
看最近twitter类服务火爆,也去注册了twitter和饭否
贴在blog的边上
感觉这都是80后,90后甚至00后才喜欢的咚咚吧
虽然自己也不时改改msn的名字,好像自己到不感兴趣别人是不是对我的改名感兴趣
不过不妨尝试一下流行的东西,省得自己老的太快
上边的Application应该为Java Application才对，native application肯定还是直接和QT API打交道
TUAW的大饼，居然有更多的人认为No, I have better things to do
|
Will you line up for an iPhone?
|
||||||||||||||||||||||||||||
一声叹息
Prologue: Google!
I am jubilant to announce that I have accepted an offer of employment from Google, a public corporation specializing in search, advertising, and unabated innovation.
Joining the staff of the Open Source Program Office, purveyors of such wonderful offerings as the Summer of Code, I shall remain in Boston.
I will leverage a few weeks of anything-but-relaxing unemployment to finish my latest book, move across the river, and advise political campaigns, then I will hit the ground running.
by Henry Kingman (Apr. 30, 2007)
LinuxDevices.com’s survey results consistently show Debian to be the most popular distribution among device developers. For example, our 2007 survey indicated that Debian was used in device-related projects by 13 percent of the survey’s 932 participants, roughly double the score of MontaVista, the most popular strictly-embedded distribution.
What sources of Linux were/will be in your (company’s) embedded designs?
(Click to enlarge)
Spread the word:
digg this story
In addition to Debian’s 13 percent score, Ubuntu, which is based on Debian packages, jumped to 6 percent this year, its first year in our survey. In contrast, Red Hat, achieved a 5 percent score and Fedora came in at 6 percent, while SUSE scored just 2 percent. The complete results and analysis are here.
Why do device developers prefer Debian?
Here are what I believe are the top reasons:
1. All the latest packages –Ironically, Debian is sometimes faulted for infrequent stable releases. But developers don’t care so much about the kind of “stability” that the stable branch buys you — desktop integration and UI fit and finish. They all run the “unstable” branch, and generally apt-get important packages weeks, days, or hours after they are released upstream — and months before they appear in packaged distributions.
2. It’s comprehensive — Last time I checked, Debian had more than 14,000 packages. It’s rare to find an open source software package that is not maintained in Debian. The average maintainer’s age is about 23. Learning to build and package software is a great introduction to open source programming.
3. It’s never going out of business — Debian is not in any way affiliated with any commercial venture, and thus is pretty much not going to be the next BeOS.
4. It’s convenient — Hm, I wonder if there’s an open source software package that does xyz. Apt-cache search xyz. Dpkg -l ‘*xyz*’. Apt-cache show xyz-utils. Apt-get install xyz-utils. It’s as simple as that. And probably even simpler with aptitude, which is what we’re all supposed to be using by now, you know.
5. 11 architectures — Actually, I think there are more architectures than this, but only 11 appear to have installation manuals (those incredibly prolix things! Someone should take a machete to them). Developers (especially device developers) like lots of architectures, since they all have their strengths (x86 for complex multi-tasking UIs, ARM for low power, MIPS and PowerPC for extensibility, etc).
6. It’s infinitely malleable — When you install Debian, you can opt for one of the “tasksel” packages, such as “desktop” or “print server,” etc., etc. However, you don’t have to. You can still very easily install only the most minimal of components, and then simply add what you need, as you need it. After a week or so, you’ve got everything you need, and nothing you don’t — a great strategy for increasing security and getting the most from your system.
7. You’re not stuck inside Debian — If you have to install RPMs, you can convert them into DEBs using the alien scripts. If you want to build stuff from source, you can “hold” packages so your custom-built stuff won’t get clobbered by the next system-wide upgrade.
8. Easy system maintenance, even between major releases — With each new release, instead of downloading a CD and wiping out your root filesystem, just apt-get dist-upgrade. And, you can sync up to the latest and greatest versions of everything as often as you like.
9. Support of other Debian users — Debian users tend toward omniscience, or at least fiercely competitive peer review, even of support advice. The #debian channel on freenode is a great place to observe this in action, and get help solving any question you like (as long as it’s actually a Debian question).
为什么编辑忽视几点：
1，最高的是kernel.org
2，debian比例在下降
3，比例上升的几个幅度很大
4，最commecial的是MontaVista
5，Ubuntu是更好的debian
Linux: The Completely Fair Scheduler
April 18, 2007 – 5:51am
Submitted by Jeremy on April 18, 2007 – 5:51am.
Linux news
Ingo Molnar [interview] released a new patchset titled the “Modular Scheduler Core and Completely Fair Scheduler”. He explained, “this project is a complete rewrite of the Linux task scheduler. My goal is to address various feature requests and to fix deficiencies in the vanilla scheduler that were suggested/found in the past few years, both for desktop scheduling and for server scheduling workloads.” The patchset introduces Scheduling Classes, “an extensible hierarchy of scheduler modules. These modules encapsulate scheduling policy details and are handled by the scheduler core without the core code assuming about them too much.” It also includes sched_fair.c with an implementation of the CFS desktop scheduler, “a replacement for the vanilla scheduler’s SCHED_OTHER interactivity code,” about which Ingo noted, “I’d like to give credit to Con Kolivas [interview] for the general approach here: he has proven via RSDL/SD that ‘fair scheduling’ is possible and that it results in better desktop scheduling. Kudos Con!”
Regarding the actual implementation, Ingo explained, “CFS’s design is quite radical: it does not use runqueues, it uses a time-ordered rbtree to build a ‘timeline’ of future task execution, and thus has no ‘array switch’ artifacts (by which both the vanilla scheduler and RSDL/SD are affected). CFS uses nanosecond granularity accounting and does not rely on any jiffies or other HZ detail. Thus the CFS scheduler has no notion of ‘timeslices’ and has no heuristics whatsoever. There is only one central tunable, /proc/sys/kernel/sched_granularity_ns, which can be used to tune the scheduler from ‘desktop’ (low latencies) to ’server’ (good batching) workloads.” He went on to note, “due to its design, the CFS scheduler is not prone to any of the ‘attacks’ that exist today against the heuristics of the stock scheduler”.
During the followup discussion, Ingo explained that he wrote the 100K patch in 62 hours. In response to concerns that his efforts had not been discussed first on the Linux Kernel Mailing List, Ingo explained, “I prefer such early releases to lkml _alot_ more than any private review process. I released the CFS code about 6 hours after i thought ‘okay, this looks pretty good” and i spent those final 6 hours on testing it (making sure it doesnt blow up on your box, etc.), in the final 2 hours i showed it to two folks i could reach on IRC (Arjan and Thomas) and on various finishing touches.” He went on to add, “the ‘design consultation’ phase you are talking about is _NOW_! 
” Later in the discussion that touched on egos, Linux creator Linus Torvalds noted, “one of the most motivating things there *is* in open source is ‘personal pride’,” going on to add, “it’s a really good thing, and it means that if somebody shows that your code is flawed in some way (by, for example, making a patch that people claim gets better behaviour or numbers), any *good* programmer that actually cares about his code will obviously suddenly be very motivated to out-do the out-doer!”
Embedded OS的战争最后往往是API的战争。
Windows CE有广大的Windows 程序作基础， Linux有Posix API。只有Symbian（以前）是与众不同的。虽然Symbian是smartphone OS的老大，也养活了一堆小公司，但是对于一个第三方公司想为不同的系统写程序去维护几套API是痛不欲生的。Porting现有的程序也很困难。
直到今天看到Symbian的这个举措，我才相信Symbian的未来是可持续发展的。
——————————————————–
Symbian OS to gain POSIX libraries
Jan. 17, 2007
Symbian plans to beta test POSIX libraries for its Symbian OS this quarter. The PIPS (PIPS is POSIX on Symbian) libraries provide C and C++ APIs (application programming interfaces) in standard “libc,” “libm,” “lipthread,” and “libdl” libraries, with the aim of helping programmers migrate existing middleware and applications to Symbian.
The PIPS libraries were announced Jan. 16 in Beijing, where Symbian opened an office.
Symbian says PIPS will significantly reduce the work of migrating existing desktop and server components to Symbian OS. Typical applications might include web servers and file sharing software, the company says. For instance, mobile phone marketshare leader Nokia, which licenses Symbian for its smartphones, ported Apache to Symbian last summer.
Symbian executive VP Jorgen Behrens stated, “It is now realistic and desirable to migrate desktop and server code onto mobile devices.”
Symbian claims that there are about 100 million Symbian-based smartphones in the market, making it the top smartphone OS. However, Symbian’s fortunes may be falling, according to research reports last year from ARCchart, ABI, and The Diffusion Group.
Availability
A beta version of PIPS will be available for Symbian OS v9.1 (and above) as a downloadable .SIS file from the Symbian Developer Network by the end of Q1 2007, Symbian says.
45%
17%
9%
29%
