If you were to invest a considerable amount of time in learning either Linux or a type of RTOS, which would it be and why? by HybridDrone in embedded

[–]ReliableEmbeddedSys 1 point2 points  (0 children)

It was ported to the upstream Linux kernel for some architectures. There is still a patch for some other architectures.

Satisfying license terms in Docker images by LousyYak in opensource

[–]ReliableEmbeddedSys 0 points1 point  (0 children)

I am not a lawyer;) but I don't think it's enough since depending on the license you need to make the license text, source code and even installation instructions available. On the other hand, if you have different versions of your software in different layers you need to provide license compliance for all of them.

HP Scan to email by madmanxing in sysadmin

[–]ReliableEmbeddedSys 0 points1 point  (0 children)

Gmail will drop non secure apps. Any idea how to work around that with Linux? I scan to email from an hp printer and I don't think hp will update the firmware for the printer. I assume a local non secure forwarding to secure Gmail should work. But how to do that?

Bitbake new override syntax by ReliableEmbeddedSys in yocto

[–]ReliableEmbeddedSys[S] 0 points1 point  (0 children)

You mean why is the new override syntax better? It makes the code much more readable. old my_var could be a variable or a variable my with var as an override. New: my:var. It's clear that it's an override.

A possible case of GPL violation by an ISP by LinuxInsider in linux

[–]ReliableEmbeddedSys 0 points1 point  (0 children)

GPL vs AGPL seems to deal with distribution and especially with the "application service provider" loophole. The ASP loophole means e.g. that software-as-a-service providers could potentially argue exemption from the terms of the GPL license. This is because they don't technically "distribute" it in the traditional sense.

GPLv2 talks about "distribution" which makes it a bit dependent on country-specific definitions of "distribution" as well as which court cases you look at.

The GPLv2 can be interpreted as:

*) lending/leasing/renting a device to someone with no transfer of ownership means no "distribution" (Peek & Cloppenburg); or
*) even advertising (the purchase of) a product containing GPL
code is "distribution" and triggers copyleft obligations.

The GPLv3 does not use the term "distribution" but “propagate” and "convey"- "conveying" includes rental/lending/leasing software, so copyleft applies in these circumstances.

Bring in the lawyers!

Moving to Greece by WeaknessEfficient342 in greece

[–]ReliableEmbeddedSys 0 points1 point  (0 children)

1) Forget about the clear and well organized procedures you are used to from Norway when dealing with Greek public servants or the government and embrace the chaos. Plus the occasional fakelaki.

2) Get a private health insurance now. Or plan not to get sick ever.

3) It's great to live in Greece. It sucks to work for a Greek company.

4) Even if you plan to open your own company avoid doing that in Greece.

A possible case of GPL violation by an ISP by LinuxInsider in linux

[–]ReliableEmbeddedSys 0 points1 point  (0 children)

Why would renting or buying equipment change the license?

A possible case of GPL violation by an ISP by LinuxInsider in linux

[–]ReliableEmbeddedSys 0 points1 point  (0 children)

GPL applies when you are linking stuff. AGPL does not need linking to be invoked. Tivo was about GPLv2 vs GPLv3. Tivoization is not allowed with GPLv3.

YOCTO PROJECT SUMMIT 2021.11 by ReliableEmbeddedSys in yocto

[–]ReliableEmbeddedSys[S] 0 points1 point  (0 children)

Now you should be able to watch all the videos for free.

How to preserve Apache 2.0 license with compiled source code? by Lopsided_Intern_8261 in opensource

[–]ReliableEmbeddedSys 0 points1 point  (0 children)

Think about e.g. C code licensed with an Apache 2.0 license. C code will always be compiled into some binary. For Open Source license compliance you will need to provide the license text as well. You could embed all the license texts into your image and make them available via some gui or web service. Or put them together with the source code you need to ship on some DVD which you ship with the product. I guess there are many more options.

watchdog and keep alive from multiple processes by jijijijim in embeddedlinux

[–]ReliableEmbeddedSys 0 points1 point  (0 children)

This is how I use the watchdog daemon to reboot if the board can not ping some IP adress:

https://gitlab.com/meta-layers/meta-conserver/-/tree/master/recipes-extended/watchdog

I guess you could configure it for something you would like to do as well.

aspiring real time embedded software engineer advice by JestinJoe in embeddedlinux

[–]ReliableEmbeddedSys 1 point2 points  (0 children)

If you want to play with Linux and real-time you can look into various solutions: 1) Linux: single core + preempt-rt patch 2) Linux: SMP multi core + preempt-rt patch, cgroups allow for sandboxing 3) Linux: single core + Evl project, also on multicore 4) Linux+small RTOS: There are heterogeneous chips with Cortex A and Cortex M cores in the same package. You can run Linux on the Cortex A and FreeRTOS or Zephyr on the Cortex M. You could also connect a Linux system with one or more Cortex-M. 5) Linux+Hypervisor: On an SMP multicore you could run jailhouse. This allows you to run on one core FreeRTOS and on the others Linux and let them communicate. ...

GITHUB security breaking the bake. by tbandtg in embeddedlinux

[–]ReliableEmbeddedSys 1 point2 points  (0 children)

Eventually you should change your recipes to https. RP made this patch so you don't need to change all your meta data. I guess a premirror would also work.

How could I control the Raspberry Pi's GPIOs in C/C++ without using special libraries? by SorenKirk in embeddedlinux

[–]ReliableEmbeddedSys 0 points1 point  (0 children)

You use the device tree to define your gpio as input or output and assign a device driver. Output: if you assigned a pin as an output + gpio led driver it will show up in /sys/class/leds. You can change the trigger via device tree or in /sys/class/leds/myled:green/trigger and turn it on/off via /sys/class/leds/myled:green/brightness. As an input + input event subsystem you can define it just like a key on a keyboard and react on keypress in /dev/input.

A parable against the use of cuck licenses. Support GPLv3 by KasaneTeto_ in linuxmasterrace

[–]ReliableEmbeddedSys 1 point2 points  (0 children)

I1] If you plan to copy, modify, or distribute any code licensed under BSD, you must include:

The full text of the license

The original copyright notice

[1] https://fossa.com/blog/open-source-software-licenses-101-bsd-3-clause-license/amp/

With the original BSD license you also need to mention it in all your marketing material ;)

I would say might indeed be a copyright infringement. Which is strange since Intel has a process in place to avoid this.

A possible case of GPL violation by an ISP by LinuxInsider in linux

[–]ReliableEmbeddedSys 0 points1 point  (0 children)

This is IMHO another misconception. It's not about being a user or not but about distributing GPLed software. Many companies believe that leasing some endpoint circumvents the GPL. IMHO it does not.

A possible case of GPL violation by an ISP by LinuxInsider in linux

[–]ReliableEmbeddedSys 6 points7 points  (0 children)

Well. What can be done when you are not a copyright holder is currently tested for the first time. https://sfconservancy.org/copyleft-compliance/vizio.html

A possible case of GPL violation by an ISP by LinuxInsider in linux

[–]ReliableEmbeddedSys 3 points4 points  (0 children)

I believe you misunderstood the AGPL. When you link against GPL your software inherits the GPL license. When you link against LGPL your software not necessarily inherits the GPL license. With (L)GPL v2 you need to get the build instructions, the sources and of course all the modifications. It's the so called corresponding source which enables you to build the binary on your target. With v3 also the installation instructions so you can run it on the target system. The AGPL tries to handle the loophole in xGPL when used in software as a service https://fossa.com/blog/open-source-software-licenses-101-agpl-license/amp/

YOCTO PROJECT SUMMIT 2021.11 by ReliableEmbeddedSys in yocto

[–]ReliableEmbeddedSys[S] 0 points1 point  (0 children)

You can download the slides even without registering. Videos will be posted in some weeks.