public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Jesse Pollard <pollard@tomcat.admin.navo.hpc.mil>
To: lkml@andyjeffries.co.uk,
	"Jesse Pollard" <pollard@tomcat.admin.navo.hpc.mil>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Difficulties in interoperating with Windows
Date: Wed, 9 Jan 2002 13:06:45 -0600 (CST)	[thread overview]
Message-ID: <200201091906.NAA20993@tomcat.admin.navo.hpc.mil> (raw)
In-Reply-To: <20020109162944.1a48a5e7.lkml@andyjeffries.co.uk>

---------  Received message begins Here  ---------

> 
> On Wed, 9 Jan 2002 10:04:11 -0600 (CST), "Jesse Pollard"
> <pollard@tomcat.admin.navo.hpc.mil> wrote:
> > > But would it?  If you disassemble part/all of Windows and use the code
> > > to understand how it works, then use this to create a specification
> > > and write code to use that specification, there should be no problem?
> > 
> > As long as someone ELSE does the developement (this is the "clean room"
> > developement that lawyers like for the defence - it must also be fully
> > documented).
> 
> Hmmm, I don't know about that, as long as the (source) code is different,
> I don't think it can be argued that it was copied not created.  But that's
> probably a legal battle that no-one would want to get in to.

Yup - there are too many source code manglers that can make what appears to 
be significant changes that do nothing more that change field names, structure
names, and limited re-ordering of statements.

> > > Correct, but I'm not talking about recompiling Windows and selling it,
> > > I'm talking about decompiling it and using the decompiled source to
> > > make Linux work better with it.  That is completely legal.
> > 
> > Not really - M$ will come after you. That's why the problems with NTFS
> > still exist - the people that were working on it (even in a "clean
> > room") had to desist. They (as I understand it) eventually dropped their
> > M$ software. And NTFS is still read-only.
> 
> Are they US based developers?

I think they were/are.

> > > Reverse engineering for the sole:purpose of copying or duplicating
> > > programs constitutes a copyright:violation and is illegal. In some
> > > cases, the licensed use of software:specifically prohibits reverse
> > > engineering.
> >
> > And M$ will go after you because of the last two sentences. Especially
> > the "duplicating programs" part. They will (have?) claimed that
> > duplicating NTFS functionality is not legal. 
> 
> But the first of your two chosen sentences seems to read as
> copy/duplicating in the sense of piracy.  Obviously as it isn't 100%
> clear, then it would be a possible legal case for Microsoft, but to be
> honest I can't see the courts going with it.  Otherwise there would only
> be one product of each particular type of software.
> 
> As to the second: under UK law any license which tries to restrict the
> lawful users ability to decompile the product is expressly void.  They
> cannot enforce that portion of the contract under UK law (which a UK
> citizen buying Windows in the UK would come under).
> 
> > (I think Jeff Merkey was
> > the one doing this - He should the one to really comment on the problems
> > he had with M$).
> 
> I certainly would be interested in hearing his comments...is he here and
> watching this thread? :-)
> 
> > Also note - none of that definition addresses the ability to publish the
> > results.
> 
> OK, I understand not publishing the decompiled code, but what would be the
> problem is publishing your code.

Trade secrets, patented algorithms, DMCA ... I'm sure the lawyers can find
something.


-------------------------------------------------------------------------
Jesse I Pollard, II
Email: pollard@navo.hpc.mil

Any opinions expressed are solely my own.

  reply	other threads:[~2002-01-09 19:07 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-01-09  9:37 Difficulties in interoperating with Windows Andy Jeffries
2002-01-09 15:06 ` Jesse Pollard
2002-01-09 15:28   ` Andy Jeffries
2002-01-09 16:04     ` Jesse Pollard
2002-01-09 16:29       ` Andy Jeffries
2002-01-09 19:06         ` Jesse Pollard [this message]
2002-01-09 16:22     ` Alan Cox
2002-01-09 16:34       ` Andy Jeffries
2002-01-09 17:09         ` Alan Cox
2002-01-10  8:34           ` Helge Hafting
2002-01-10  3:32   ` David Schwartz
2002-01-09 16:14 ` Anton Altaparmakov
2002-01-09 16:48   ` Jesse Pollard
2002-01-09 17:17     ` Alan Cox
2002-01-09 17:29   ` Anton Altaparmakov

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=200201091906.NAA20993@tomcat.admin.navo.hpc.mil \
    --to=pollard@tomcat.admin.navo.hpc.mil \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lkml@andyjeffries.co.uk \
    /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