Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S263735AbTEFONZ (ORCPT ); Tue, 6 May 2003 10:13:25 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S263770AbTEFOMY (ORCPT ); Tue, 6 May 2003 10:12:24 -0400 Received: from zeus.kernel.org ([204.152.189.113]:7568 "EHLO zeus.kernel.org") by vger.kernel.org with ESMTP id S263735AbTEFOLS (ORCPT ); Tue, 6 May 2003 10:11:18 -0400 Subject: Re: The disappearing sys_call_table export. From: "David S. Miller" To: Yoav Weiss Cc: D.A.Fedorov@inp.nsk.su, terje.eggestad@scali.com, 76306.1226@compuserve.com, linux-kernel@vger.kernel.org In-Reply-To: References: Content-Type: text/plain Content-Transfer-Encoding: 7bit Organization: Message-Id: <1052212504.983.16.camel@rth.ninka.net> Mime-Version: 1.0 X-Mailer: Ximian Evolution 1.2.2 (1.2.2-5) Date: 06 May 2003 02:15:05 -0700 Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 801 Lines: 17 On Tue, 2003-05-06 at 01:45, Yoav Weiss wrote: > In fact, in linux which is opensource, you can probably write a script > that extracts any unexported symbol from the source code, find a path to > it from some exported symbol, and automagically create a module that > re-exports this symbol for your legacy driver to use. You might have a derivative work after obtaining access to a non-exported interface. If this is correct, binary-only modules can't do this and therefore they must stick to exported interfaces. -- David S. Miller - 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/