OSADL Latest Changeshttps://www.osadl.org/
This RSS channel will publish recent changes of the OSADL Website.Thu, 21 Mar 2019 15:08:53 GMTOSADL eGDownload the original documentsThe complete referenced documents are made available for the internal use of OSADL members only, it is not permitted to distribute them to third parties.]]>https://www.osadl.org/?id=3074#13651
c4a822d74e83fa56065d4fdefea974edThu, 21 Mar 2019 11:58:02 GMTManagement SummaryScenario

A machine builder purchased a proprietary software that calls functions of the glibc at runtime, but is delivered without the glibc. In consequence, the manufacturer of the proprietary software does not need to fulfill any Open Source license conditions. When redistributing the purchased software along with the glibc which is required to run the software, however, license obligations of the LGPL-2.1 must be fulfilled in order to obtain permission to copy and distribute the glibc. One of these obligations dictates that permission must be granted to modify and re-engineer the proprietary software for debugging such modifications, but the manufacturer of the proprietary software refuses to do so. The machine builder argues that the purchased software is useless for the intended purpose and seeks ways to enforce this obligation against the manufacturer.

Enforceability of LGPL-2.1 obligations against third-party providers

The fact that the third-party software is designed or advertised for exactly this use and the provided object code expects the existence of an LGPL-2.1 library is not sufficient to give the machine builder grounds for enforcing permission to modify and re-engineer the third-party software against the manufacturer. However, it gives the machine builder the right to demand rectification due to a defect of title which is given by the possibility that right holders of the LGPL-2.1 library can take legal actions based on copyright law against the machine builder because of lacking authorization to modify and re-engineer the software.

Legal consequences of LGPL-2.1 violation by the machine builder

If the required permission is not given by the manufacturer of the third-party software, but the machine builder still distributes the software together with the glibc, either without giving re-engineering permissions or with a blanket permission that they haven?t received themselves, the machine builder violates the LGPL-2.1, and the holders of the violated copyrights can assert the usual claims.

]]>https://www.osadl.org/?id=3074#13652
4b240cfbb40b5cd1ac67270c1ea43915Thu, 21 Mar 2019 11:56:22 GMTLicense obligations under the LGPL-2.1 when used with proprietary third-party applications or librariesIn general, providers of proprietary software assume that they are free to specify their own license conditions and to restrict the rights of use within the scope of their product. Problems, however, may arise in situations where customers of such providers use various third-party software components and combine them into their own product while the license conditions of the components are not compatible. This can also be the case when using Open Source software. The so-called copyleft effect of the GPL, for instance, makes it impossible to link software under this license with proprietary components. This is the reason why many Open Source libraries such as the GNU C library (glibc) are licensed under the LGPL-2.1 as this license allows applications to be linked with this library without triggering the copyleft effect. However, the LGPL-2.1 imposes an additional obligation when linked to proprietary software that is beyond the control of the customer. This legal assessment was carried out to explain the underlying principle of this additional license obligation and discusses its impact in the scope of a real-world scenario.]]>https://www.osadl.org/?id=3074#13653
9e77fe1270ef09a452b9f84cb7ea0434Thu, 21 Mar 2019 11:52:06 GMTLegal Assessmentshttps://www.osadl.org/?id=3074#13654
423d2efc77ffed6605b21131b9d37c08Thu, 21 Mar 2019 11:47:21 GMTAgenda

Technical Workshop: Real-time Linux Latency Fighting - March 26, 2019

08:30 ? 09:00

Get-together

09:00 ? 10:30

Linux kernel debug and trace interface

1. Raw access to the variables of the debug file system

2. Using command line tools

3. Using the graphical user interface

10:30 ? 11:00

Coffee break

11:00 ? 12:30

Latency monitoring I:

1. Standard methods to define a system?s worst-case latency

2. Special methods to monitor real-time capabilities of a system

3. The real-time framework of the OSADL QA Farm

12:30 ? 13:30

Lunch break

13:30 ? 15:00

Latency monitoring II:

1. Calibrating latency detection

2. Analysis of a deliberately created latency

3. The breaktrace functionality of cyclictest

15:00 ? 15:30

Coffee break

15:30 ? 17:00

Everyday?s practice of a latency fighter

1. Typical mistakes that may lead to prolonged latency values

2. Recently discovered sources of latency and fixes or workarounds

3. Live latency fighting*

17:00 ? 17:30

Discussion, questions, answers

17:30

End of workshop

*Participants are encouraged to take along with them, if possible, particular equipment that suffers from unexpected prolonged latency values.

By car:A map to calculate directions to the TP ConferenceCenter im Technologiepark Heidelberg is available here. A limited number of parking spaces is available and will be reserved for HOT participants.

Public transportation:The TP ConferenceCenter im Technologiepark Heidelberg is located about 2.5 kilometers away from Heidelberg main railway station. From there, the electric tram line RNV 24 direction ?Handschuhsheim? takes about seven minutes (Please note that due to a major contruction site at Heidelberg main railway station, the tram departure station has been moved to stop &quot;Hauptbahnhof West&quot;). Please leave the tram at stop ?Technologiepark?. The ConferenceCenter can be reached from there in a short walk. How to get to TP ConferenceCenter by public transportation.

By car:A map to calculate directions to the TP ConferenceCenter im Technologiepark Heidelberg is available here. A limited number of parking spaces is available and will be reserved for HOT participants.

Public transportation:The TP ConferenceCenter im Technologiepark Heidelberg is located about 2.5 kilometers away from Heidelberg main railway station. From there, the electric tram line RNV 24 direction ?Handschuhsheim? takes about seven minutes (Please note that due to a major contruction site at Heidelberg main railway station, the tram departure station has been moved to stop &quot;Hauptbahnhof West&quot;). Please leave the tram at stop ?Technologiepark?. The ConferenceCenter can be reached from there in a short walk. How to get to TP ConferenceCenter by public transportation.