Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id ; Wed, 9 Jan 2002 04:43:01 -0500 Received: (majordomo@vger.kernel.org) by vger.kernel.org id ; Wed, 9 Jan 2002 04:42:55 -0500 Received: from adsl-62-128-214-206.iomart.com ([62.128.214.206]:58360 "EHLO localhost.localdomain") by vger.kernel.org with ESMTP id ; Wed, 9 Jan 2002 04:41:36 -0500 Date: Wed, 9 Jan 2002 09:37:52 +0000 From: Andy Jeffries To: linux-kernel@vger.kernel.org Subject: Difficulties in interoperating with Windows Message-Id: <20020109093752.31ae1e79.lkml@andyjeffries.co.uk> Organization: Scramdisk Linux X-Mailer: Sylpheed version 0.6.6 (GTK+ 1.2.10; i686-pc-linux-gnu) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org IANAL, but I wondered why there is such difficulty with making Linux work completely with Windows systems? I guess part of it may be that Windows is closed source but as reverse engineering for interoperability is legal in the UK (regardless of what the End User License states), is the problem that it is difficult to read the Assembly easily? Is there not a project on Linux to convert assembly back to C? Would this be exceptionally hard? Just wondered why Linux has struggled for a while to interoperate with Windows completely... Cheers, -- Andy Jeffries | Scramdisk Linux Project http://www.scramdisklinux.org | Lead developer "testing? What's that? If it compiles, it is good, if it boots up it is perfect." --- Linus Torvalds - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/