public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Pavel Machek <pavel@suse.cz>
To: jmerkey@wolfmountaingroup.com
Cc: Theodore Tso <tytso@mit.edu>, Rik van Riel <riel@redhat.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [REQUEST] Clarification from Copyright Holders on FUSE/NDISWRAPPER
Date: Sun, 5 Oct 2008 12:12:19 +0200	[thread overview]
Message-ID: <20081005101219.GC2351@ucw.cz> (raw)
In-Reply-To: <49203.166.70.238.43.1222658858.squirrel@webmail.wolfmountaingroup.com>

On Sun 2008-09-28 21:27:38, jmerkey@wolfmountaingroup.com wrote:
> > 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...
> 
> The figures I am quoting are based on who is downloading not how many.  I
> had over 27,000 downloads the first week but only a few of them were from
> fortune 1000 of 500 companies.  After two weeks it dropped off sharply to
> a very low level.  Most of the downloads are still from my primary
> servers, and not google or sourceforge.  I agree Linux is pervasive

Noone cares about mdb, so there must be something wrong with
Linux. Oh, right.

-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

      parent reply	other threads:[~2008-10-05 10:12 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
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 [this message]

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=20081005101219.GC2351@ucw.cz \
    --to=pavel@suse.cz \
    --cc=jmerkey@wolfmountaingroup.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=riel@redhat.com \
    --cc=tytso@mit.edu \
    /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