linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Justin Guyett <justin@soze.net>
Cc: Chris Wedgwood <cw@f00f.org>, Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org, jmerkey@timpanogas.org
Subject: Re: NWFS Submitted to Alan Cox
Date: Sun, 1 Jul 2001 17:45:07 -0700	[thread overview]
Message-ID: <20010701174507.A12097@vger.timpanogas.org> (raw)
In-Reply-To: <20010702025418.B14068@weta.f00f.org> <Pine.LNX.4.33.0107011220090.27557-100000@gw.soze.net>
In-Reply-To: <Pine.LNX.4.33.0107011220090.27557-100000@gw.soze.net>; from justin@soze.net on Sun, Jul 01, 2001 at 12:23:17PM -0700

On Sun, Jul 01, 2001 at 12:23:17PM -0700, Justin Guyett wrote:
> On Mon, 2 Jul 2001, Chris Wedgwood wrote:
> 
> > On Sun, Jul 01, 2001 at 01:50:00PM +0100, Alan Cox wrote:
> >
> > > I'm not a file sustem hacker, nor since I work for one vendor the
> > > appropriate owner for larg chunks of code in some people's eyes. I
> > > suspect the FSF is a much much better asignee for the code itself
> >
> > I assume the legal threats that Jeff has experience will follow the
> > code? Surely before anyone wishes to adopt such a thing they should
> > get legal advice about the situation?
> >
> > It would be shame to let potentially useful code be left to die for
> > fear of bully-tactics if their claims are unfounded.
> 
> presuming they are unfounded, given the history of attacks by Novell,
> perhaps the best move would be to turn it over to a company like compaq or
> ibm given a written contract that they will keep it open source.  



> Novell can't be that stupid.

Don't count on it.  I had completed a fully 64-bit OS in 1997 for IA64, 
four years before everyone else.  It's been sitting in an archive 
somewhere inside of Novell -- unused for no other reason than I 
wrote it.  I am waiting to see who would want it.  It's open to 
any takers.  Alan may be in a conflict of interest with Red Hat 
since Novell is an investor in them, so this I understand.  I'll 
wait and see who's interested.  I would not be surprised if 
someone from Novell asks to take it over.   

Jeff


> 
> 
> justin

  reply	other threads:[~2001-07-01 23:39 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-01  0:35 NWFS Submitted to Alan Cox Jeff V. Merkey
2001-07-01  1:12 ` Jeff V. Merkey
2001-07-01  3:59 ` Paul Fulghum
2001-07-01 10:34   ` Jeff V. Merkey
2001-07-01  4:16 ` Trever L. Adams
2001-07-01 10:32   ` Jeff V. Merkey
2001-07-01 12:50 ` Alan Cox
2001-07-01 14:54   ` Chris Wedgwood
2001-07-01 19:23     ` Justin Guyett
2001-07-02  0:45       ` Jeff V. Merkey [this message]
2001-07-01 20:18     ` Jeff V. Merkey
2001-07-01 20:16   ` Jeff V. Merkey

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=20010701174507.A12097@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=cw@f00f.org \
    --cc=jmerkey@timpanogas.org \
    --cc=justin@soze.net \
    --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;
as well as URLs for NNTP newsgroup(s).