linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: linux-kernel@vger.kernel.org
Cc: jmerkey@timpanogas.org
Subject: NWFS Submitted to Alan Cox
Date: Sat, 30 Jun 2001 17:35:58 -0700	[thread overview]
Message-ID: <20010630173558.A8066@vger.timpanogas.org> (raw)



Alan,

I would like for you to take over NWFS if you are willing.  I have dissolved
TRG as a Utah Corporation and I am now focused on a variety of projects 
for various clients related to Linux development.  Novell has recently 
threatened to try to take my house and assets if I post any more 
NWFS releases or MANOS.  

I am doing very well with my consulting projects, but to be honest, 
my family has sufferred horribly in the past four years fighting with
Novell every other week, and there's a very strong chance I will be 
moving shop to either New Mexico or Arizona, since they own the 
local courts here in Utah (all the judges are mormons in Utah Valley 
and pro-Novell).  

There are several areas that need restructuring and work, and I am 
available to answer questions, and assist with technical consulting,
but I can no longer post releases of NWFS on Linux.  My children 
need a house over their heads, and I believe what Novell says about 
taking it and putting us out on the street.  They are wounded in the 
market, and very dangerous at present, so I am trying very hard to 
stay out of their way.  If you choose to decline, it's up for grabs
with whomever else wants to take it over, but you have first dibs.  

If you elect take it over, I will have my attorneys prepare an 
agreement transferring legal ownership to you.  I will retain M2FS
and the clustered versions, since I have a clients abroad who want this 
technology, and it does not utilitze any NetWare specific technologies.
I would also retain IP rights to NWFS to use future incarnations in 
products should I set up in another state. 

I do not want to see NWFS fall by the wayside and not get supported,
so I would really like it if you would be willing to take it over 
and get it 2.4 clean.  

Please advise,

Jeff



             reply	other threads:[~2001-06-30 23:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-07-01  0:35 Jeff V. Merkey [this message]
2001-07-01  1:12 ` NWFS Submitted to Alan Cox 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
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=20010630173558.A8066@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=jmerkey@timpanogas.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 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).