All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mike Fedyk <mfedyk@matchmail.com>
To: Danek Duvall <duvall@emufarm.org>, linux-kernel@vger.kernel.org
Subject: Re: Code from ~2.4.4 going into Solaris 9 Alpha?
Date: Thu, 1 Nov 2001 13:10:50 -0800	[thread overview]
Message-ID: <20011101131050.B766@mikef-linux.matchmail.com> (raw)
In-Reply-To: <20011101111508.A412@mikef-linux.matchmail.com> <20011101115319.B2818@lorien.emufarm.org>
In-Reply-To: <20011101115319.B2818@lorien.emufarm.org>

On Thu, Nov 01, 2001 at 11:53:19AM -0800, Danek Duvall wrote:
> On Thu, Nov 01, 2001 at 11:15:08AM -0800, Mike Fedyk wrote:
> 
> > I just looked at http://perso.wanadoo.fr/levenez/unix/history.html, and
> > noticed a line from linux over to solaris 9 alpha.
> > 
> > Does anyone know what code they copied, and if they're now making solaris
> > GPL compatible?
> 
> That might simply be the inclusion of various "freeware" packages --
> shells, gzip, apache, samba, and so forth, not necessarily kernel code.
> All of those packages come with full source as well, so they should be
> compliant with the GPL if that's how they happen to be licensed.
> 
> Of course, the line should probably be connected to Solaris 8, since
> that's when most of these things started shipping with it.
> 

Oh, sorry about that...

I didn't mean to start a flame thread (like someone accused me of doing), it
just looked interesting to me, and I don't remember anything in kernel
traffic (which I was reading at the time) or on lkml (which I have been
reading more recently)... so I figured someone here would know more.

Mike

  reply	other threads:[~2001-11-01 21:11 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-01 19:15 Code from ~2.4.4 going into Solaris 9 Alpha? Mike Fedyk
2001-11-01 19:53 ` Danek Duvall
2001-11-01 21:10   ` Mike Fedyk [this message]
2001-11-01 21:29     ` Chris Ricker
2001-11-02  8:59       ` Christoph Hellwig

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=20011101131050.B766@mikef-linux.matchmail.com \
    --to=mfedyk@matchmail.com \
    --cc=duvall@emufarm.org \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.