心开天籁

Firefox 1.5 新鲜出炉

很少见OOS社区这样期盼一个软件的release
29号N多人期待“今天下午Firefox 1.5就release了”
仿佛中国小孩盼过年一样
我本来也等了等菜单条的蓝色有新update的标志
等了两天还没有，只好手动下载安装
下载的时候只有一个thread被允许，估计也是临时性的限制吧
升级完发现20多个extension有十多个被disable了
因为不兼容于1.5
不过1.5extension 下边提供了一个find update的按钮
以前有么？我没注意过
check update后发现了大部分都有了兼容1.5的升级
现在还有6个不能用的，只有慢慢等了
LiveLines居然也没有，bloglines这就有点不像画了

另外，某些错误提示信息好看了

emerge apmd failed

root@abc ~ # emerge gnome
Calculating dependencies ...done!
>>> emerge (1 of 29) sys-apps/apmd-3.2.1_p4 to /
>>> md5 files ;-) apmd-3.0.2-r3.ebuild
>>> md5 files ;-) apmd-3.2.0.ebuild
>>> md5 files ;-) apmd-3.2.1_p4.ebuild
>>> md5 files ;-) files/apmsleep.c.diff
>>> md5 files ;-) files/apmd.rc6
>>> md5 files ;-) files/apmd-3.2.0.kernel26x.patch
>>> md5 files ;-) files/apmd.confd
>>> md5 files ;-) files/apmd.kernel26x.patch
>>> md5 files ;-) files/apmsleep.c.diff.3.2.0
>>> md5 files ;-) files/digest-apmd-3.0.2-r3
>>> md5 files ;-) files/digest-apmd-3.2.0
>>> md5 files ;-) files/digest-apmd-3.2.1_p4
>>> md5 src_uri ;-) apmd_3.2.1.orig.tar.gz
>>> md5 src_uri ;-) apmd_3.2.1-4.diff.gz
>>> Unpacking source...
>>> Unpacking apmd_3.2.1.orig.tar.gz to /var/tmp/portage/apmd-3.2.1_p4/work
>>> Unpacking apmd_3.2.1-4.diff.gz to /var/tmp/portage/apmd-3.2.1_p4/work
* Applying apmd_3.2.1-4.diff ... [ ok ]
>>> Source unpacked.
libtool --quiet --mode=compile gcc -c -O -g -Wall -pipe -I. -I/usr/src/linux/include -I/usr/src/linux-2.2/include -I /usr/src/linux-2.0/include -DVERSION=\"3.2.1\" -DDEFAULT_PROXY_NAME=\"/etc/apmd_proxy\" apmlib.c
libtool --quiet --mode=compile gcc -c -O -g -Wall -pipe -I. -I/usr/src/linux/include -I/usr/src/linux-2.2/include -I /usr/src/linux-2.0/include -DVERSION=\"3.2.1\" -DDEFAULT_PROXY_NAME=\"/etc/apmd_proxy\" apm.c
libtool --quiet --mode=compile gcc -c -O -g -Wall -pipe -I. -I/usr/src/linux/include -I/usr/src/linux-2.2/include -I /usr/src/linux-2.0/include -DVERSION=\"3.2.1\" -DDEFAULT_PROXY_NAME=\"/etc/apmd_proxy\" apmd.c
libtool --quiet --mode=compile gcc -c -O -g -Wall -pipe -I. -I/usr/src/linux/include -I/usr/src/linux-2.2/include -I /usr/src/linux-2.0/include -DVERSION=\"3.2.1\" -DDEFAULT_PROXY_NAME=\"/etc/apmd_proxy\" -DNARROWPROTO xapm.c
libtool --quiet --mode=compile gcc -c -O -g -Wall -pipe -I. -I/usr/src/linux/include -I/usr/src/linux-2.2/include -I /usr/src/linux-2.0/include -DVERSION=\"3.2.1\" -DDEFAULT_PROXY_NAME=\"/etc/apmd_proxy\" apmsleep.c
libtool --quiet --mode=link gcc -o libapm.la apmlib.lo -rpath /usr/lib -version-info 1:0
apmsleep.c:60: warning: `rcsid' defined but not used
i686-pc-linux-gnu-g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/../../../crti.o: No such file or directory
i686-pc-linux-gnu-g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/crtbeginS.o: No such file or directory
i686-pc-linux-gnu-g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/crtendS.o: No such file or directory
i686-pc-linux-gnu-g++: /usr/lib/gcc-lib/i686-pc-linux-gnu/3.3.5/../../../crtn.o: No such file or directory
make: *** [libapm.la] Error 1
make: *** Waiting for unfinished jobs....
rm apm.o

!!! ERROR: sys-apps/apmd-3.2.1_p4 failed.
!!! Function src_compile, Line 43, Exitcode 2
!!! emake failed
!!! If you need support, post the topmost build error, NOT this status message.

root@abc ~ #

-------------------------------------------------
emerge libtool先
参见bugs.gentoo.org

谁都有梦

每天看bloglines里的RSS feeds
看到planet gentoo blog里有一篇It's good that others have a dream...
写了好长，鹰文，就没打算看下去，继续往下别人的
又一个I have a dream too, 哈哈，脑筋一转，往下看
果然看到又一个I　ｈａｖｅ　ａ　ｄｒｅａｍ
：）
ｂｌｏｇｌｉｎｅｓ里是按时间倒序排的
有兴趣了，先看Ｉ　ｈａｖｅ　ａ　ｄｒｅａｍ:
I’d like to see Gentoo as the perl developers platform of choice.
果然是程序员本色，梦里都是自己的产品变成别人选择
往上看Ｉ　ｈａｖｅ　ａ　ｄｒｅａｍ　ｔｏｏ
Currently i found that i dream about Gentoo to have one of the best xmms support available
还是程序员本色，没意思啊，做点别的梦不好么？
再往上看Ｉt's good that others have a dream
about making Gentoo the platform of choice for . We're already working hard on making Gentoo the best choice for webserving using Apache, PHP, and web-based applications.
没治了，脑子里除了程序还是程序阿

我也有梦。。。
我的梦是。。。。。。太多了 ：（

new AT&T logo

西南小贝尔底气不足？

有些人是不是真的有病？

而且数量高达9999人。

Top Tech Index 2005

Top Tech Index 2005

HOWTO do Linux kernel development

From: Greg KH suse.de>
Subject: [RFC] HOWTO do Linux kernel development
Newsgroups: gmane.linux.kernel
Date: 2005-11-14 22:07:09 GMT (4 hours and 39 minutes ago)

Over time, I get a lot of the same kind of emails from developers.
Messages asking how to do this or that, or how this process works. I
also see a lot of new developers make the same mistakes (wrong patch
format, no signed-off-by:, not sent to the proper developer, wrong
coding style, etc.)

Along with these requests, I have heard a lot of complaints over time,
about how there is no single place to go to to figure out how to do
Linux kernel development, and where to point other people to.

So, I've been working on a document for the past week or so to help
alleviate a lot of these problems. If nothing else, it should be a place
where anyone can point someone to when they ask the common questions, or
do something in the not-correct way. I'd like to add this to the Linux
kernel source tree, so it will be kept up to date over time, as things
change (like the development process.) Ideally I'd like to put it in
the main directory as HOWTO, but I don't know how others feel about
this.

Anyway, I'd like to get comments on what has been produced so far. I
know the section about the development process is still not complete (it
has a mark), and if anyone wants to fill that in, I'd really
appreciate it.

I would like to thank Pat Mochel, Hanna Linder, Randy Dunlap, Kay
Sievers, Vojtech Pavlik, and Jan Kara for their review and comments on
early drafts of this document.

thanks,

greg k-h

------------------------------

HOWTO do Linux kernel development
---------------------------------

This is the be-all, end-all document on this topic. It contains
instructions on how to become a Linux kernel developer and how to learn
to work with the Linux kernel development community.

If anything in this document becomes out of date, please send in patches
to the maintainer of this file, who is listed at the bottom of the
document.

Intro
-----

So, you want to learn how to become a Linux kernel developer? Or you
have been told by your manager, "Go write a Linux driver for this
device." This document's goal is to teach you everything you need to
know to achieve this by describing the process you need to go through,
and hints on how to work with the community. It will also try to
explain some of the reasons why the community works like it does.

The kernel is written mostly in C, with some architectural-dependent
parts written in assembly. A good understanding of C is required to
kernel development. Assembly (any architecture) is not required unless
you plan to do low-level development for that architecture. Though they
are not a good substitute for a solid C education and/or years of
experience, the following books are good, if anything for reference:

"The C Programming Language" by Kernighan and Ritchie [Prentice Hall]
"Practical C Programming" by Steve Oualline [O'Reilly]
"Programming the 80386" by Crawford and Gelsinger [Sybek]
"UNIX Systems for Modern Architectures" by Curt Schimmel [Addison Wesley]

The kernel is written using GNU C and the GNU toolchain. While it
adheres to the ISO C99 (??) standard, it uses a number of extensions
that are not featured in the standard. It can sometimes be difficult to
understand the assumptions the kernel has on the toolchain and the
extensions that it uses, and unfortunately there is no definitive
reference for them. Please check the gcc info pages (`info gcc`) for
some information on them.

Please remember that you are trying to learn how to work with the
existing development community. It is a very diverse group of people,
with very high standards for coding, style and procedure. These
procedures have been created over time based on what they have found to
work best for such a large and geographically dispersed team. Try to
learn as much as possible about these procedures ahead of time, as they
are well documented, and not expect people to adapt to you, or your
company's way of doing things.

Legal Issues
------------

The Linux kernel source code is released under the GPL. Please see the
file, COPYING, in the main directory of the source tree, for details on
the license. If you have further questions about the license, please
contact a lawyer, and do not ask on the Linux kernel mailing list. The
people on the mailing lists are not lawyers, and you should not rely on
their statements on legal matters.

Documentation
------------

The Linux kernel source tree has a large range of documents that are
invaluable in learning how to interact with the kernel community. When
new features are added to the kernel, it is recommended that new
documentation files are also added, that explain how to use the feature.
Here is a list of files that are in the kernel source tree that are
required reading:
Documetation/CodingStyle
This describes the Linux kernel coding style, and some of the
rationale behind it. All new code is expected to follow the
guidelines in this document. Most maintainers will only accept
patches if these rules are followed, and many people will only
review code if it is in the proper style.

Documentation/SubmittingPatches
Documentation/SubmittingDrivers
These files describe in explicit detail how to successfully create
and send a patch, including (but not limited to):
- Email contents
- Email format
- Who to send it to
Following these rules will not guarantee success (as all patches are
subject to scrutiny of content and style), but not following them
will almost always prevent it.

Other excellent descriptions of how to create patches properly are:
"The Perfect Patch"
http://www.zip.com.au/~akpm/linux/patches/stuff/tpp.txt
"Linux kernel patch submission format"
http://linux.yyz.us/patch-format.html

Documentation/stable_api_nonsense.txt
This file describes the rationale behind the conscious decision to
not have a stable API within the kernel, including for things like:
- Subsystem shim-layers (for compatibility?)
- Driver portability between Operating Systems.
- Mitigating rapid change within the kernel source tree (or
preventing rapid change)
This document is crucial for understand the Linux development
philosophy and is very important for people moving to Linux from
development on other Operating Systems.

Documentation/SecurityBugs
If you feel you have found a security problem in the Linux kernel,
please follow the steps in this document to help notify the kernel
developers, and help solve the issue.

Documentation/ManagementStyle
This document describes how Linux kernel maintainers operate and the
shared ethos behind their methodologies. This is important reading
for anyone new to kernel development (or anyone simply curious about
it), as it resolves a lot of common misconceptions and confusion
about the unique behavior of kernel maintainers.

Documentation/stable_kernel_rules.txt
This file describes the rules on how the stable kernel releases
happen, and what to do if you want to get a change into one of these
releases.

Documentation/kernel-docs.txt
A list of external documentation that pertains to kernel
development. Please consult this list, if you do not find what you
are looking for within the in-kernel documentation.

The kernel also has a large number of documents that can be
automatically generated from the source code itself. This includes a
full description of the in-kernel api, and rules on how to handle
locking properly. The documents will be created in the
Documentation/DocBook/ directory and can be generated as PDF,
Postscript, HTML, and man pages by running:
make pdfdocs
make psdocs
make htmldocs
make mandocs
respectively from the main kernel source directory.

Becoming A Kernel Developer
---------------------------

If you do not know anything about Linux kernel development, you should
look at the Linux KernelNewbies project:
http://kernelnewbies.org
It consists of a helpful mailing list, where you can ask almost any type
of basic kernel development question (make sure to search the archives
first, before asking something that has already been answered in the
past.) It also has a IRC channel that you can use to ask questions in
real-time, and a lot of helpful documentation that is useful for
learning about Linux kernel development.

The website has basic information about code organization, subsystems,
and current projects (both in-tree and out-of-tree). It also basic
logistical information, like compiling a kernel and applying a patch.

If you do not know where you want to start, but you want to look for
some task to start doing to join into the kernel development community,
go to the Linux Kernel Janitor's project:
http://janitor.kernelnewbies.org/
It is a great place to start. It describes a list of relatively simple
tasks that need to be cleaned up and fixed within the Linux kernel
source tree. Working with the developers in charge of this project, you
will learn the basics of getting your patch into the Linux kernel tree,
and possibly point you in the direction of what to go work on next, if
you do not already have an idea.

If you already have a chunk of code that you want to have go into the
kernel tree, but need some help getting it in the proper form, the
kernel-mentors project was created to help you out with this. It is a
mailing list, and can be found at:
http://selenic.com/mailman/listinfo/kernel-mentors

The development process
-----------------------

Mailing lists
-------------

As some of the above documents describe, the majority of the core kernel
developers participate on the Linux Kernel Mailing list. Details on how
to subscribe and unsubscribe from the list, can be found at:
http://vger.kernel.org/vger-lists.html#linux-kernel
There are archives of the mailing list on the web in many different
places. Use a search engine to find these archives. It is highly
recommended that you search the archives about the topic you want to bring
up, before you post it to the list. A lot of things are already discussed
in detail and are only recorded at the mailing list archives.

Most of the individual kernel subsystems also have their own separate
mailing list where they do their development efforts. See the
MAINTAINERS file for a list of what these lists are, for the different
groups.

Many of the lists are hosted on kernel.org. Information on them can be
found here:
http://vger.kernel.org/vger-lists.html

Please remember to follow good behavioral habits when using the lists.
Though a bit cheesy, the following URL has some simple guidelines for
interacting with the list (or any list):
http://www.albion.com/netiquette/

If multiple people respond to your mail, the CC: list of recipients may
get pretty large. Don't remove anybody from the CC: list without a good
reason, or don't reply only to the list address. Get used to receive the
mail twice, one from the sender and the one from the list and don't try
to tune that by adding fancy mail-headers, people will not like it.

Remember to keep the context and the attribution of your replies intact,
keep the "John Kernelhacker wrote ...:" lines at the top of you reply and
add your statements between the individual quoted sections instead of
writing at the top of the mail.

If you add patches to your mail, make sure they are plain readable text
as stated in Documentation/SubmittingPatches. Kernel developers don't
want to deal with attachments or compressed patches, they may want
to comment individual lines of your patch, which works only that way.
Make sure you use a mail program that does not mangle spaces and tab
characters. A good first test is to send the mail to yourself and try
to apply your own patch by yourself. If that doesn't work, get your
mail program fixed or change it until it works.

Above all, please remember to show respect to other subscribers.

Working with the community
--------------------------

The kernel community works differently than most traditional corporate
development environments. Here are a list of things that you can try to
do to try to avoid problems:
Good things to say regarding your proposed changes:
- "This solves multiple problems."
- "This deletes 2000 lines of code."
- "Here is a patch that explains what I am trying to describe."
- "I tested it on 5 different architectures..."
- "Here is a series of small patches that..."
- "This increases performance on typical machines..."

Bad things you should avoid saying:
- "We did it this way in AIX/ptx/Solaris, so therefore it must be
good..."
- "I've being doing this for 20 years, so..."
- "It makes this proprietary benchmark go faster"
- "This is required for my company to make money"
- "This is for our Enterprise product line."
- "Here is my 1000 page design document that describes my idea"
- "I've been working on this for 6 months..."
- "Here's a 5000 line patch that..."
- "I rewrote all of the current mess, and here it is..."
- "I have a deadline, and this patch needs to be applied now."

Another way the kernel community is different than most traditional
software engineering work environments is the faceless nature of
interaction. One benefit of using email and irc as the primary forms of
communication is the lack of discrimination based on gender or race.
The Linux kernel work environment is accepting of women and minorities
because all you are is an email address. The international aspect also
helps to level the playing field because you can't guess gender based on
a person's name. A man may be named Andrea and a woman may be named Pat.
Most women who have worked in the Linux kernel and have expressed an
opinion have had positive experiences. Here is a group that is a good
starting point for women interested in contributing to Linux:
http://www.linuxchix.org/

The language barrier can be present for some people who are not
comfortable with English. A good grasp of the language can be needed in
order to get ideas across properly on mailing lists, so it is
recommended that you check your emails to make sure they make sense in
English before sending them.

Break your changes up
---------------------

The Linux kernel community does not gladly accept large chunks of code
dropped on it all at once. The changes need to be properly introduced,
discussed, and broken up into tiny, individual portions. This is almost
exactly opposite of what companies are used to doing. Your proposal
should also be introduced very early in the development process, so that
you can receive feedback on what you are doing. It also lets the
community feel that you are working with them, and not simply using them
as a dumping ground for your feature. However, don't send 50 emails at
one time to a mailing list, your patch series should be smaller than
that almost all of the time.

The reasons for breaking things up are the following:

1) Small patches increase the likelihood that your patches will be
applied, since they don't take much time or effort to verify for
correctness. A 5 line patch can be applied by a maintainer with
barely a second glance. But, a 500 line patch may take hours to
review for correctness (the time it takes is exponentially
proportional to the size of the patch, or something).

Small patches also make it very easy to debug when something goes
wrong. It's much easier to back out patches one by one, than it is
to dissect a very large patch after it's been applied (and broken
something).

2) It's important not only to send small patches, but also to rewrite
and simplify (or simply re-order) patches before submitting them.

Here is an analogy from kernel developer Al Viro:
"Think of a teacher grading homework from a math student. The
teacher does not want to see the student's trials and errors
before they came up with the solution. They want to see the
cleanest, most elegant answer. A good student knows this, and
would never submit her intermediate work before the final
solution."

The same is true of kernel development. The maintainers and
reviewers do not want to see the thought process behind the
solution to the problem one is solving. They want to see a
simple and elegant solution."

That may be challenging to keep the balance between presenting an elegant
solution and working together with the community and discuss your
unfinished work. Therefore it is good to get early in the process to
get feedback to improve your work, but also keep your changes in small
chunks that they may get already accepted, even when your whole task is
not ready for inclusion now.

Also realize that it is not acceptable to send patches for inclusion
that are unfinished and will be "fixed up later."

Justify your change
-------------------

Along with breaking up your patches, it is very important for you to let
the Linux community know why they should add this change. New features
must be justified as being needed and useful.

All of these things are sometimes very hard to do. It can take years to
perfect these practices (if at all). It's a continuous process of
improvement that requires a lot of patience and determination. But,
don't give up. It's possible. Many have done it before, and each had to
start exactly where you are now.

----------
Thanks to Randy Dunlap and Gerrit Huizenga for the list of things you
should and should not say. Also thanks to Pat Mochel, Hanna Linder,
Randy Dunlap, Kay Sievers, Vojtech Pavlik, and Jan Kara for their review
and comments on early drafts of this document.

Maintainer: Greg Kroah-Hartman kroah.com>

emerge world 20051113

应该把以后每次emerge world记录下来，从今天这次开始
kernel 升级到2.6.14-r2，config 加上了relayfs
vim升级到6.4
mono用1.1.9的ebuild试了一下，还是有问题，不过和1.1.8.3好像不太一样
没时间研究了
触摸板驱动要加到module autoload里才行 还要建立/dev/input/mouse0到/dev/mouse

vidalinux

在DistroWatch中叫VLOS。怪不得我没找到。
直接装gentoo stage 3的一个distribution。

New Gentoo-based desktop adds system update capabilities
Jul. 22, 2004

Based on Gentoo Linux, the Vidalinux Desktop OS has been announced on the project's website, and the first beta of the software is expected to be available on Gentoo mirrors soon. The goal of the Vidalinux Desktop OS is to make Linux easier to use and administer for daily work for home or office users.

Described as a "metadistribution", the software uses a technology called Portage that is said to allow the Gentoo-based desktop to become a secure server, development workstation, professional desktop, gaming system, embedded solution, among possible uses for the system.

This "near-unlimited" adaptability allows users to increase their desktop productivity by enabling updates and the installation of applications, the project claims. Portage technology keeps systems up-to-date with the most current application and security patches, compiling from source code or downloading precompiled binaries. Portage also resolves dependencies, according to the project's website.

A "Porthole" system (see image on right -- click to enlarge) provides automated software updates and patching, including desktop alerts/notifications and dependency checking/analysis, to ensure that systems are secure and are running the latest software.

Vidalinux Desktop OS includes a GNOME desktop environment, Ximian edition of OpenOffice.org, Mozilla browser, Evolution mail and calendar client, Gentoo Linux system, and portage package manager. The project says that the distribution includes additional multimedia and productivity applications for the home user, including media players, browser plugins for flash, real player, pdf viewer, media, graphics design, and administration tools.

The recommended requirements for running Vidalinux are a Pentium III compatible processor (500 MHz or faster), a 10 GB hard disk, and a minimum of 256MB RAM. Additionally, Vidalinux requires 1024x768 screen resolution or better.

hide my ass

hide my ass

无话可说

变态的iDoom

lost 人物点评

jack, 美剧中主角的典型，完人中的完人，十全十美。无懈可击的人往往会让人腻烦，jack还好。
kate，有时候挺讨厌她的，不过女角中又没谁更招人喜欢。孤独地坐在海边的样子让人心动。
sawyer，好多女孩喜欢这个唯一一个有点坏的人。大概是一群好人中与众不同吧。
sayid，中东版jack，主要是一个医生会修电子设备说不大通。
locke，如果我有他之前那悲惨的经历早挺不下去了，如新东方罗胖子所说，骠悍的人生不需要解释。
Sun/Jin，韩国人可能就是这么250。
Charlie，最好玩的哥们，不过当我知道他就是指环王里演霍比特人的之后就怎么看他都是霍比特人。
shannon/Bonne，俩250。
hurley，旧小说里都会有的牛皋程咬金之类的角色。
Micheal，远远不如他儿子，一根筋。
Walt，比他爸强多了

买书两本,CD一张

周末半夜在dangdang下单买了两本书和一张CD
一本是《基地》，joyo上一直没有这本，只好买了其他所有基地系列
然后等阿等，最后还是在dangdang买了。不知什么时候有时间看。。。。。。
还有一本《坐牢家爸爸给女儿的八十封信》
第一次看这本书已经是十几年前
后来好像还买过一本，不知什么时候丢失在颠沛流离中
一张CD是最近正火的吉祥三宝。什么时候火的不清楚，上周去香山路上
交通台放的才知道。
很精致，价格也精致，打完折还要49。少见的金光闪闪的盘

geek何苦为难geek？

看到slashdotcn的头一条就是域名换了，编辑们欲言又止
我估计是受到/.的压力了吧
都是geek一家，何必呢

使用CustomizeGoogle-zh_CN突破GFW

http://yro.slashdot.org/yro/05/10/31/1414203.shtml?tid=217&tid=17
经常在/.看到GFW相关的讨论，觉得真是丢脸阿