One of the primary reasons why I started the kernel summit ten
years ago was because I've found that people work better after they
have had a chance to meet each other face to face. If you only
know someone via e-mail, it's lot easier to get into flame wars.
But after you've met someone, broken bread and drunk beer with
them, it's easier to work with them as a colleague and fellow
developer. While the Linux Kernel development community has grown
significantly since March, 2001, this principle still holds true.
-- Ted Ts'o
This is one reason why I wrote the ARM Linux kernel booting
document some 8 years ago, which specifies the _minimum_ of
information that a boot loader needs to supply the kernel needs to
be able to boot. Fat lot of good that did - as far as I'm
concerned, writing documentation is a total and utter waste of my
time and resources. It just gets ignored.
So I now just don't bother with any documentation _at_ _all_.
-- Russell King
My gut reaction to this sort of thing is "run away in terror". It
encourages kernel developers to operate like lackadaisical
userspace developers and to assume that underlying code can perform
heroic and immortal feats. But it can't. This is the kernel and
the kernel is a tough and hostile place and callers should be
careful and defensive and take great efforts to minimise the strain
they put upon other systems.
-- Andrew Morton
to post comments)