lkml.org 
[lkml]   [2003]   [May]   [6]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
    /
    From
    SubjectRE: The disappearing sys_call_table export.
    Date

    > 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.

    Obviously you don't have much experience getting around licenses. ;)

    You GPL the part that does the dirty work. Then your closed-source module
    only uses exported interfaces and the boundary between GPL and closed-source
    code is a clear license boundary.

    DS


    -
    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/

    \
     
     \ /
      Last update: 2005-03-22 13:35    [W:0.022 / U:1.028 seconds]
    ©2003-2016 Jasper Spaans. hosted at Digital OceanAdvertise on this site