public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Wayne.Brown@altec.com
To: Venkatesh Ramamurthy <Venkateshr@ami.com>
Cc: "'Alan Cox'" <alan@lxorguk.ukuu.org.uk>, linux-kernel@vger.kernel.org
Subject: RE: Microsoft begining to open source Windows 2000?
Date: Thu, 8 Mar 2001 10:49:21 -0600	[thread overview]
Message-ID: <86256A09.005C726C.00@smtpnotes.altec.com> (raw)



No, the Linux way is to send the patch to everyone else who's developing or
testing the kernel.  Even if Linus doesn't accept it into the "official" kernel,
there's nothing to stop you (or anyone else) from using it yourself or
distributing it to others.  The Microsoft agreement prevents you from changing
the source, and if they decide to ignore your bug report, there's nothing you
can do about it.  Oh, and you have to pay (at least 1500 licenses' worth) for
the "privilege" of doing their debugging work for them.  That's about as far
from the Linux way of doing things as you can get.

Wayne




Venkatesh Ramamurthy <Venkateshr@ami.com> on 03/08/2001 10:04:25 AM

To:   'Alan Cox' <alan@lxorguk.ukuu.org.uk>
cc:   linux-kernel@vger.kernel.org (bcc: Wayne Brown/Corporate/Altec)

Subject:  RE: Microsoft begining to open source Windows 2000?



My initial thought after seeing this article was that microsoft was testing
its waters on open sourcing. If i have 1500 licenses then i would get the
source. If i find any bug in thier source , i  would report to microsoft or
send a patch and they would put it in thier next version. Is this not the
same way Linux Kernel is developed?. Only thing microsoft does not want to
immediately go full open sourcing and get embarrased at the hands of linux
people.



             reply	other threads:[~2001-03-08 16:51 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-03-08 16:49 Wayne.Brown [this message]
  -- strict thread matches above, loose matches on Subject: below --
2001-03-08 21:21 Microsoft begining to open source Windows 2000? Jason Venner
2001-03-08 19:40 Venkatesh Ramamurthy
2001-03-08 16:04 Venkatesh Ramamurthy
2001-03-08 16:21 ` Rik van Riel
2001-03-08 16:28 ` Mohammad A. Haque
2001-03-08 18:07   ` Richard B. Johnson
2001-03-08 18:32   ` Joseph Pingenot
2001-03-09 10:40   ` Graham Murray
2001-03-09 12:05     ` Jesse Pollard
2001-03-09 12:47       ` Rogier Wolff
2001-03-10  2:10         ` Jesse Pollard
2001-03-09 13:26     ` Mohammad A. Haque
2001-03-09 17:01       ` Ralf Baechle
2001-03-09 19:34         ` Mohammad A. Haque
2001-03-08 16:31 ` Anton Altaparmakov
2001-03-08 17:36   ` James A. Sutherland
2001-03-08 17:53   ` Anton Altaparmakov
2001-03-08 19:14     ` Jeff V. Merkey
2001-03-09  3:35 ` Werner Almesberger
2001-03-08 15:24 Jesse Pollard
2001-03-08 18:34 ` Ian Stirling
2001-03-08 20:41   ` Jesse Pollard
2001-03-08 15:01 Venkatesh Ramamurthy
2001-03-08 15:52 ` Mohammad A. Haque
2001-03-08 16:06 ` Alan Cox
2001-03-09  5:43   ` J. Dow
2001-03-09  6:34     ` Mike Galbraith
2001-03-09 11:11       ` Dr. Michael Weller
2001-03-08 19:10 ` Roeland Th. Jansen
2001-03-08 19:38 ` Lars Gaarden
2001-03-09 18:16   ` Kai Henningsen
2001-03-10  3:49     ` Steve Underwood
2001-03-11 17:23     ` Mark H. Wood

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=86256A09.005C726C.00@smtpnotes.altec.com \
    --to=wayne.brown@altec.com \
    --cc=Venkateshr@ami.com \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    /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