心开天籁

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

小圆棒是燃料电池？？？

摘自kerneltrap.org
JA: How can a person tell if their hardware supports kvm?
Avi Kivity: You can easily tell if your processor supports hardware extensions by running the command
$ egrep ‘^flags.*(vmx|svm)’ /proc/cpuinfo
If there’s any output at all, your processor supports kvm. Unfortunately, some early laptops that support kvm have VT extensions disabled in the BIOS, so a BIOS upgrade is required. There is also a comprehensive list on the Xen site, http://wiki.xensource.com/xenwiki/HVM_Compatible_Processors.

俺自己花钱买的第一台笔记本，2000年初，原配64M内存，升级为128，又买了一个10M的PCMCIA网卡，全价正好是20000元整人民的币。就是俺LP（当时还是女盆友）拎着两万的现金买地。
介台笔记本陪俺度过了早年的青葱岁月，陪俺在温暖的北图阅览室里睡觉，陪俺在酷热的出租房里写程序，陪俺在东北老家给俺爹妈亲戚朋友演示啥叫高科技。。。。。。在她身上俺装过Win98，W2K，各种版本的Linux。4年前升级了内存到256M（只能识别192M），3年前升级了硬盘（把10G摘下来放到移动硬盘盒里，换60G），两年前升级了无线网卡。即便这几年速度她的行动速度实在太慢了，也被我装上了SVN来做版本控制。
终于在去年被apple powerbook接班。只是测试新的投影系统才开过那么两三次。
直到昨天，俺Desktop PC的Ubuntu在unrar一个4G的xbox iso之后没有响应，在俺试图用俺的华硕
ssh login到linux，启动的时候发现硬盘不认识了。俺大惊失色，担心60G的硬盘千万不要出什么问题。7年的笔记本不值什么钱，硬盘里的数据倒是无价之宝。于是拆下硬盘，换到硬盘盒里，发现硬盘好好的，
把原配的10G硬盘再放到笔记本里还是不认识，知道盛宴总有散去的时候，电脑也该退休了。
相信不是大毛病，只是不值得修了。整理原配的电源，驱动光盘说明书等等丢进角落里的纸箱子。

哈哈哈哈

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!”

哪位泡网好心人以 X X 的名义给我发来的慰问信，附带joost的邀请。一个程序生成的url然后点进去变成 www.joost.com/download/ 不明白这样的下载和直接从首页点joost beta进来有什么区别下载，安装，sign up，sign in，点channel，点节目我的网速是1MADSL，偶尔有点卡，相对分辨率来说我觉得可以接受我是听说里面有1小时长度的NG授权节目去的，没找到在哪个频道今天有点晚了先不试改天用我的苹果电脑下载个MAC版的试试看多谢 X X
RedRox你试试直接download的能用不？不能用我给你发邀请
[update]joost目前还只支持MAC/Intel

FullerScreen

开切诺基人的综合症 !（俺的状态）
1.一定要把切停在自己看到到的最佳位置，有事儿没事要看两眼。 （me2)
2.家中LD对你的切开始怀有的敌意。 (me2)
3.在街上不论车再多,路再堵都能一眼看到躲在车堆里的切诺基来。 (me2)
4.登陆的第一个和停留的最久的网站都和切有关。 (paowang, paowang)
5.开车时最不能容忍的就是被超车。 (I did. but do not)
6.听到别人说切诺基有什么不好，一定会和那人争个刺刀见红。(没那么严重吧，陆虎买不起）
7.看到美切的眼神比看PLMM来得更炽热。(me2)
8.热衷义务做切诺基的宣传推广，且比JS的销售人员更专业、更敬业。(sometimes )
9.经常流露出对驾驶BORA、PST和AUDI人的同情。(actually, most car)
10.看到街上的切诺基，第一反映是看车屁股，希望找个4.0的字样。(me2，还要看后雨刷和排气管，假冒4.0的切还真不少)
11.看到装饰的NB哄哄的6420、7250，总是会说：唉！2驱车，没有小弟弟……(me2)
12.有切在前后，总想看看是什么人在开，或者看看贴了什么车标。(me2)
13.停好了车，走出几步还是要回头看它，并且有按2次以上中控关门的毛病。(me2)
14.经常见人就问：有没有多余的车标？（现在不了，更喜欢素车）
15.只要有机会，都很乐意让别人乘坐自己的切，但就是死活不借。(me2)
16.整天想着去FB。(me2)
17.见到马路施工，经常不由自主的冲着别的车不敢走的水塘里狂奔过去。(me2)
18.看到PLMM就会对她说：站我车顶上去吧，那儿视野好！(老婆不让）
19.洗车时经常会向小工要来水枪，对着车底盘没命的冲。（never)
20.路上见到切就闪灯，人家反应稍慢一点就会，气急败坏的狂闪灯、乱按喇叭。（never)
21.无论多高的减速带，心里从不发颤，嗷嗷叫的就冲过去了。(以前是，现在不了）
22.只要并肩起步者都认为是要和自己叫板。（以前是，现在偶尔）
23.看到顶框总是想装又不想装，进退两难。(me2)
24.永远认为只有开切诺基的才是识货者。(取决于你有多少钱）
25.看到开切诺基的男人，就觉得他一定是真正爷们儿；看到女同志开切诺基，不论人家多难看都惊为天人，乱拍马屁！
26.开车不关心车速，只关心百公里油耗。并经常为此或悲或喜。（sometimes）
27.经常会在切车里睡觉，尽管睡着并不是非常舒服。(曾经）
28.见到大坡就会伸手去挂4驱。（很少）
29.只要坐人家的车，便会大言不惭地说：切的视野比这好多了，这车……（心里这么想的）
30.最恨人家对你说：俺车的仪表盘灯，可真是漂亮……（哈哈）
31.看到长发女孩就会想：长发就是好，可以按个辫子（天线）……
32.鄙视在车中挂太多小饰物，并且恶言诅咒：一定是小时候缺乏母爱，看他的傻样……（点头）
33.看到稍高一点的车就会，琢磨：这鸟加的是钢板还是吊耳？（me2)
34.老婆要是想买车，你会说：过两天俺给你去买个6缸自动档的……
35.努力研究各种前后保险杠，并且对绞盘或绞盘状的物体(如工地上的圏扬机)有特殊癖好！(me2)
36.后备箱里总有一条拖绳，每天都在想：什么时候也让俺遇到个PLMM开的车坏在马路边…… (me2)