Appendix C.docx
- 文档编号:25451370
- 上传时间:2023-06-08
- 格式:DOCX
- 页数:21
- 大小:26.67KB
Appendix C.docx
《Appendix C.docx》由会员分享,可在线阅读,更多相关《Appendix C.docx(21页珍藏版)》请在冰豆网上搜索。
AppendixC
AppendixC.ImportantLicensesandNotices
Theuseanddistributionofopensourceandfreesoftwareissubjecttoafewwell-knownandwidelyadvertisedlicenses,aswediscussedinChapter1.Thereare,nevertheless,someissuessurroundingLinux'slicensingthatkeepresurfacingandseemtocauseconfusion.TheseuncertaintiesrevolvearoundthefactthattheLinuxkernelisitselfdistributedunderthetermsoftheGNUGPL.
Overtime,LinusTorvaldsandotherkerneldevelopershavehelpedshedsomelightonthelimitsandreachesofthekernel'slicensing.ThisappendixpresentssomeofthemessagespublishedbyLinusandotherkerneldevelopersregardingthreeaspectsofthekernel'slicensing:
theuseofnon-GPLapplications,theuseofbinary-onlymodules,andthegenerallicensingissuessurroundingthekernel'ssourcecode.
C.1ExclusionofUser-SpaceApplicationsfromKernel'sGPL
ToavoidanyconfusionregardingthestatusofapplicationsrunningontopoftheLinuxkernel,LinusTorvaldsaddedthefollowingpreambletothekernel'slicense:
NOTE!
Thiscopyrightdoes*not*coveruserprogramsthatusekernel
servicesbynormalsystemcalls-thisismerelyconsiderednormaluse
ofthekernel,anddoes*not*fallundertheheadingof"derivedwork".
AlsonotethattheGPLbelowiscopyrightedbytheFreeSoftware
Foundation,buttheinstanceofcodethatitrefersto(theLinux
kernel)iscopyrightedbymeandotherswhoactuallywroteit.
AlsonotethattheonlyvalidversionoftheGPLasfarasthekernel
isconcernedis_this_license(iev2),unlessexplicitlyotherwise
stated.
LinusTorvalds
C.2NoticesonBinaryKernelModules
RecurringcontroversyhaseruptedoverloadablekernelmodulesnotdistributedunderthetermsoftheGPL.Manycompaniesalreadyshipsuchbinarymodulesandmanyindustryplayerscontendthatsuchmodulesarepermitted.YetmanyLinuxkerneldevelopershavecomeoutratherstronglyagainstthispractice.HerearesomemessagessenttotheLinuxkernelmailinglistbyLinusTorvaldsandAlanCoxthatprovidesomeinsightastotheuseofbinarymodules.
C.2.1FirstPostingbyLinusinKernelInterfaceThread
From:
torvalds@(LinusTorvalds)
Subject:
Re:
Kernelinterfacechanges(wasRe:
cdrecordproblemson
Date:
1999-02-057:
13:
23
Inarticle<36bab0c7.394438@>,
JohnAlvord
>OnThu,4Feb199922:
37:
06-0500(EST),"TheodoreY.Ts'o"
>
>>
>>Andasaresult,I'veseenmorethanafewMITusersdecidetogiveup
>>onLinuxandmoveovertoNetBSD.Ithinkthisisbad,andI'mhoping
>>wecantakejustalittlebitmorecareinthe2.2seriesthanwedidin
>>the2.0series.Isthatreallytoomuchtoask?
Yes.Ithinkitis.Iwillstriveforbinarycompatibilityfor
modules,butI_expect_thatitwillbebroken.It'sjusttooeasyto
havetomakechangesthatbreakbinary-onlymodules,andIhavetoo
littleincentivetotrytoavoidit.
Ifpeoplefeelthisisaproblem,Iseeafewalternatives:
-don'tusestuffwithbinary-onlymodules.Justsayno.
-workhardatmakingasource-versionofthethingavailable(it
doesn'thavetobeundertheGPLifit'samodule,butithastobe
availableassourcesothatitcanberecompiled).
-don'tupgrade
-dropLinux
>Isuggestwetreatbinarycompatibilityproblemsasbugswhichneedto
>beresolvedduringthe2.2lifetime.Evenwithallcare,somechanges
>willoccurbecauseofmistakes...ifwecurethem,therewillbe
>limitedimpacttousers.
It'softennotmistakes.Thingssometimeshavetochange,andI
personallydonotcareforbinary-onlymodulesenoughtoevencare.If
peoplewanttouseLinux,theyhavetolivewiththis.In2.2.x,the
basicsmaybestableenoughthatmaybethebinarymoduleinterfacewon't
actuallychange.Idon'tknow.Thatwouldbegood,butifitisnotto
be,thenitisnottobe.
I_allow_binary-onlymodules.IallowthembecauseIthinkthat
sometimesIcannotmorallyrequirepeopletomakesourcesavailableto
projectslikeAFSwherethosesourcesexistedbeforeLinux.HOWEVER,
thatdoesnotmeanthatIhaveto_like_AFSasabinary-onlymodule.
Quitefrankly,IhopeAFSdiesaslowandpainfuldeathwithpeople
migratingtobetteralternatives(coda,whatever).Orthatsomebody
makesanAFSclientavailableinsourceform,eitherasacloneor
throughtheoriginalpeople.
Asitis,whathasAFSdoneformelately?
Nothing.SowhyshouldI
care?
Linus
C.2.2SecondPostingbyLinusinKernelInterfaceThread
From:
torvalds@(LinusTorvalds)
Subject:
Re:
Kernelinterfacechanges(wasRe:
cdrecordproblemson
Date:
1999-02-078:
15:
24
Inarticle<79g5bu$spd$1@>,
H.PeterAnvin
>
>*LinusTorvaldshasnointerestwhatsoeverindevelopingsucha
>plug-inABI.Someoneelseiswelcometodoit.
No,it'sevenmorethanthat.
I_refuse_toevenconsidertyingmyhandsoversomebinary-onlymodule.
HannuSavolainentriedtoaddsomelayeringtomakethesoundmodules
more"portable"amongLinuxkernelversions,andIdislikeditfortwo
reasons:
-extralayersdecreasereadability,andsometimesmakeforperformance
problems.ThereadabilitythingisactuallythelargerbeefIhad
withthis:
Ijustdon'twanttoseedriversstartusingsomestrange
wrapperformatthathasabsolutelynothingtodowithhowtheywork.
-I_want_peopletoexpectthatinterfaceschange.I_want_peopleto
knowthatbinary-onlymodulescannotbeusedfromreleasetorelease.
IwantpeopletobereallyreallyREALLYawareofthefactthatwhen
theyuseabinary-onlymodule,theytietheirhands.
Notethatthesecondpointismainlypsychological,butit'sbyfarthe
mostimportantone.
Basically,Iwantpeopletoknowthatwhentheyusebinary-onlymodules,
it'sTHEIRproblem.Iwantpeopletoknowthatintheirbones,andI
wantitshoutedoutfromtherooftops.Iwantpeopletowakeupina
coldsweateveryonceinawhileiftheyusebinary-onlymodules.
Why?
BecauseI'maprick,andIwantpeopletosuffer?
No.
BecauseI_know_thatIwilleventuallymakechangesthatbreakmodules.
AndIwantpeopletoexpectthem,andIneverEVERwanttoseeanemail
inmymailboxthatsays"Damnyou,Linus,Iusedthisbinarymodulefor
overtwoyears,anditworkedperfectlyacross150kernelreleases,and
Linux-5.6.71brokeit,andyouhadbetterfixyourkernel".
See?
Irefusetobeatthemercyofanybinary-onlymodule.Andthat'swhyI
refusetocareaboutthem-notbecauseofanyreallytechnicalreasons,
notbecauseI'macallousbastard,butbecauseIrefusetotiemyhands
behindmybackandhearsomebodysay"BendOver,Boy,BecauseYouHave
ItComingToYou".
Iallowbinary-onlymodules,butIwantpeopletoknowthattheyare
_only_everexpectedtoworkontheoneversionofthekernelthatthey
werecompiledfor.Anythingelseisjustaveryniceunexpectedbonusif
ithappenstowork.
AndTHAT,myfriend,iswhywhensomebodycomplainsaboutAFS,Itell
themtogoscrewthemselves,andnotcomecomplainingtomebutcomplain
totheAFSboysandgirls.AndwhyI'mnotveryinterestedinchanging
that.
Linus
C.2.3PostbyAlanCoxinKernelHooksThread
ThisisaresponsetoapostingbyTheodoreTs'O.
From:
AlanCox
Subject:
Re:
[ANNOUNCE]GeneralisedKernelHooksInterface(GKHI)
Date:
2000-11-0914:
26:
33
>Actually,he'sbeenquitespecific.It'soktohavebinarymodulesas
>longastheyconformtotheinterfacedefinedin/proc/ksyms.
Whatiscompletelyunclearisifhehastheauthoritytosaythatgiventhat
thereiscodefromotherpeopleincludingtheFSFmergedintothetree.
I'vetakentotellingfolkswhoaskaboutbinarymodulestotalktotheirlegal
department.Thewholequestionissimplytocomplicatedforanyoneelseto
workon.
Alan
C.2.4FirstPostbyLinusinSecurityHooksLicenseThread
From:
LinusTorvalds
Subject:
Re:
[PATCH]makeLSMregisterfunctionsGPLonlyexports
Date:
2002-10-1717:
08:
19
Notethatifthisfightendsupbeingamajorissue,I'mjustgoingto
removeLSMandletthesecurityvendorsdotheirownthing.Sofar
-Ihavenotseenalotofactualusageofthehooks
-seenanumberofpeoplewhostillworrythatthehooksdegrade
performanceincriticalareas
-theworrythatpeopleuseitfornon-GPL'dmodulesisapparentlyreal,
consideringCrispin'sreply.
Iwillre-iteratemystanceontheGPLandkernelmodules:
ThereisNOTHINGinthekernellicensethatallowsmodulestobe
non-GPL'd.
The_only_thingthatallowsfornon-GPLmodulesiscopyrightlaw,and
inparticularthe"derivedwork"issue.Avendorwhodistributesnon-GPL
modulesis_not_protectedbythemoduleinterfaceperse,andshould
feelveryconfidentthattheycanshowinacourtoflawthatthecode
isnotderived.
ThemoduleinterfacehasNEVERbeendocumentedormeanttobeaGPL
barrier.TheCOPYINGclearlystatesthatthesystemcalllayerissucha
barrier,soifyoudoyourworkinuserlandyou'renotinanyway
beholdentotheGPL.Themoduleinterfacesarenotsystemcalls:
there
aresystemcallsusedto_install_them,buttheactualinterfacesare
not.
Theoriginalbinary-onlymoduleswereforthingsthatwerepre-existing
worksofcode,iedriversandfilesystemsportedfromotheroperating
systems,whichthuscouldclearlybearguedtonotbederivedworks,and
theoriginallimitedexporttablealsoactedsomewhatasabarrierto
showalevelofdistance.
Inshort,Crispin:
I'mgoingtoapplythepatch,andifyouasacopyright
holderofthatfiledisag
- 配套讲稿:
如PPT文件的首页显示word图标,表示该PPT已包含配套word讲稿。双击word图标可打开word文档。
- 特殊限制:
部分文档作品中含有的国旗、国徽等图片,仅作为作品整体效果示例展示,禁止商用。设计者仅对作品中独创性部分享有著作权。
- 关 键 词:
- Appendix