netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "David S. Miller" <davem@redhat.com>
To: jsd@monmouth.com
Cc: netdev@oss.sgi.com
Subject: Re: netlink tester program
Date: Mon, 02 Jun 2003 20:46:45 -0700 (PDT)	[thread overview]
Message-ID: <20030602.204645.48505284.davem@redhat.com> (raw)
In-Reply-To: <3EDC18F2.6090505@monmouth.com>

   From: "John S. Denker" <jsd@monmouth.com>
   Date: Mon, 02 Jun 2003 23:41:38 -0400
   
   If we are taking the legal system as our
   model of openness, then open-source software
   has come to a sorry pass indeed.
   
It does have connections where a "user" wants to
do something with FOO but does not wish to do the
legwork necessary to be an expert in FOO.  They hire
an expert.

Or, in our case, they make an expert interested in the
thing they want to do :-)))
   
   It is also important to distinguish what's best
   for *you* and what's best for the project.
   Maybe *you* don't want to be responsible for
   doing all the documentation.

I'm not even going to attempt to document something that
moves as fast as the kernel.

I go to bookstores and I see many excellent attempts to document
kernel internals, but these books are frozen in time.  Specifically
they are frozen in the time of the moment the kernel they write for is
published.  As a consequence they are all obsolete the moment they are
published.

Some poor student reads these books, written against 2.4.8 or
whatever, then they go and try to contribute to 2.5.x and it
doesn't work except for certain kinds of drivers where we've
kept the APIs more or less the same.

But I don't care that people do this, just don't require that I do
it.

I think this extra fluidity we get from being able to change so fast
is a strength not a weakness.

  reply	other threads:[~2003-06-03  3:46 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-05-30 16:00 netlink tester program Randy.Dunlap
2003-05-31  0:11 ` David S. Miller
2003-05-31  3:22   ` Randy.Dunlap
2003-05-31  6:42     ` David S. Miller
2003-05-31 12:09       ` Andi Kleen
2003-06-02 17:07         ` Randy.Dunlap
2003-06-02 21:04       ` Randy.Dunlap
2003-06-02 21:56         ` David S. Miller
2003-06-03  1:56           ` David Brownell
2003-06-03  2:02             ` David S. Miller
2003-06-03  3:34               ` David Brownell
2003-06-03  3:38                 ` David S. Miller
2003-06-03  3:49                   ` Randy.Dunlap
2003-06-03  3:51                     ` David S. Miller
2003-06-03  7:57                   ` Hisham Kotry
2003-06-09  1:35                     ` Jamal Hadi
2003-06-09 14:37                       ` Mr. James W. Laferriere
2003-06-09 17:16                       ` David S. Miller
2003-06-03  2:33           ` John S. Denker
2003-06-03  2:38             ` David S. Miller
2003-06-03  3:20               ` John S. Denker
2003-06-03  3:22                 ` David S. Miller
2003-06-03  3:41                   ` John S. Denker
2003-06-03  3:46                     ` David S. Miller [this message]
2003-06-03  3:54                       ` Randy.Dunlap
2003-06-03  3:54                         ` David S. Miller
2003-06-03  3:37             ` David Brownell
2003-06-03  3:32           ` Randy.Dunlap
2003-06-03  3:35             ` David S. Miller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20030602.204645.48505284.davem@redhat.com \
    --to=davem@redhat.com \
    --cc=jsd@monmouth.com \
    --cc=netdev@oss.sgi.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).