public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Theodore Tso <tytso@mit.edu>
To: jmerkey@wolfmountaingroup.com
Cc: Rik van Riel <riel@redhat.com>, linux-kernel@vger.kernel.org
Subject: Re: [REQUEST] Clarification from Copyright Holders on FUSE/NDISWRAPPER
Date: Sun, 28 Sep 2008 21:57:30 -0400	[thread overview]
Message-ID: <20080929015730.GK8711@mit.edu> (raw)
In-Reply-To: <58677.166.70.238.43.1222644857.squirrel@webmail.wolfmountaingroup.com>

On Sun, Sep 28, 2008 at 05:34:17PM -0600, jmerkey@wolfmountaingroup.com wrote:
> One nice thing about putting out a kernel debugger is it gives me a unique
> view into the numbers and status developers working on Linux -- and it's
> shrinking from the download patterns and the types of folks downloading
> it.

You're assuming that your metrics of people downloading your kernel
debugger is an accurate way of measuring how many people are
developing Linux.

> Linux is pervasive, but based upon my observations, development is
> declining and almost non-existent in commercial companies except for a
> small handful of companies.  I do not believe that Free BSD or some other
> Unix is going to replace Linux, but what I see happening is a loss of
> interest in Unix platforms generally.

You may find these research reports interesting:

http://www.linuxfoundation.org/publications/linuxkerneldevelopment.php
http://www.linux-foundation.org/publications/IDC_Workloads.pdf

The former shows that the development rate is if anything, increasing
based on analyzing the rate that changes are flowing into the Linus's
git tree --- something which I think everyone would agree is a better
way of measuring the rate of development than the number of downloads
of mdb.

The latter is a report from IDC which calculates total enterprise
spending in the Linux ecosystem at $21 billion in 2007, and predicts
that by 2011 the figure will more than double to $49 billion.

So the health of Linux, both in terms of the rate of development and
the enterprise server ecosystem, seems to be doing quite well (never
mind the surge of interest of Linux for mobile platforms).  But if you
want to develop on FreeBSD, hey, don't let us stop you.  Different
licensing strokes for different folks, after all...

Regards,

						- Ted

  reply	other threads:[~2008-09-29  1:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-28 17:15 [REQUEST] Clarification from Copyright Holders on FUSE/NDISWRAPPER jmerkey
2008-09-28 19:45 ` Theodore Tso
2008-09-28 19:24   ` jmerkey
2008-09-28 23:46   ` Rik van Riel
2008-09-28 23:34     ` jmerkey
2008-09-29  1:57       ` Theodore Tso [this message]
2008-09-29  3:27         ` jmerkey
2008-09-30  4:06           ` Eric W. Biederman
2008-09-30  4:18             ` jmerkey
2008-10-05 10:12           ` Pavel Machek

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=20080929015730.GK8711@mit.edu \
    --to=tytso@mit.edu \
    --cc=jmerkey@wolfmountaingroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.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