Brummbaer

Thanks for the clarification. I always thought that the GPL parts are also MIT then.

Thanks for the info.

So you can relicense MIT to GPL without the MiT parts staying MIT?

Do you have more on that?

I’m not sure you can relicense the MIT code under GPL if you are not the author or it doesn’t say so in the MIT license, that relicensing is permitted.

I’m speaking about the firmware and other blobs that are there because devices wouldn’t work without it.

https://git.kernel.org/pub/scm/linux/kernel/git/firmware/linux-firmware.git/tree/WHENCE

Nice, something running in an eBPF context with a blob in the middle, what could go wrong …

Also there are already a lot of binary blobs in the kernel, that also makes me nervous a bit.

What are you using to ship the logs to VL?

If you want to exclude “normal” logs you should start excluding them before they reach VL, so the only logs you have are the interesting ones.

The more you can filter and label at the source, the less you have to work out in VL.

I use alloy (which is kinda heavy) to extract and prepare only the data I want and it works great so far.

The world does not consist entirely of the US.

While I agree that openai can buy enough “law” in the US to do what it wants, the license is important in other jurisdictions and can be enforced.

Good luck - uv is under a MIT license, so every fork is just a free buffet for openai to incorporate into their enshittified version of uv. There is a reason the GPL exists and many people will learn this the hard way …

She’s a Joe Rogan with a university degree.