On Jun 21, 2007, [email protected] wrote: > how exactly can they prevent a system that's been tampered with from > accessing their network? By denying access to their servers? By not granting whatever is needed to initiate network sessions? And note, "it's been tampered with" is not necessarily enough of a reason to cut someone off, it has to meet these requirements: > when the modification itself materially and adversely affects the > operation of the network or violates the rules and protocols for > communication across the network. > (something even you say they have a right to do) as long as this right is not used by the software distributor to impose restrictions on the user's ability to adapt the software to their own needs. The GPLv3 paragraph above makes a fair concession in this regard, don't you agree? -- Alexandre Oliva http://www.lsd.ic.unicamp.br/~oliva/ FSF Latin America Board Member http://www.fsfla.org/ Red Hat Compiler Engineer aoliva@{redhat.com, gcc.gnu.org} Free Software Evangelist oliva@{lsd.ic.unicamp.br, gnu.org} - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- References:
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Ingo Molnar <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alan Cox <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Bernd Schmidt <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Al Viro <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Linus Torvalds <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Linus Torvalds <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Linus Torvalds <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Andrew McKay <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alan Cox <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Andrew McKay <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: [email protected]
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: Alexandre Oliva <[email protected]>
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- From: [email protected]
- Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Prev by Date: Re: [Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls
- Next by Date: Re: [Intel IOMMU 06/10] Avoid memory allocation failures in dma map api calls
- Previous by thread: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Next by thread: Re: Dual-Licensing Linux Kernel with GPL V2 and GPL V3
- Index(es):