license-list-XML
linux
Our great sponsors
license-list-XML | linux | |
---|---|---|
8 | 974 | |
318 | 168,342 | |
3.8% | - | |
9.6 | 10.0 | |
9 days ago | 3 days ago | |
Makefile | C | |
GNU General Public License v3.0 or later | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
license-list-XML
-
ZeroMQ – Relicense from LGPL3 and exceptions to MPL 2.0
The LGPLv3 exception had an atypical feature (for *GPL exceptions) and was possibly misdrafted, see: https://github.com/spdx/license-list-XML/issues/1672
-
BSV is no longer open source as defined by the Open Source Definition
Shortly after, they had the gall to ask for that garbage fire of a license to be included in a catalog of open source licenses. And then claimed to not understand how that request could possibly be denied...
-
How to use SPDX for licensing?
My doubt is if there is some programmatic use of SPDX. If not why they have such a strict syntax as specified here. Also there are multiple extra tools on the github repo for parsing, comparing and even generating spdx files like this. Now if user is just mentioning the license identifiers why do we need all these? And what does it mean to compare licenses as it seems that they're using string comparison techniques to find closest match to license in their catalogue.
Recently, I came to know about SPDX but I am not sure about how to use it. From the articles that I've read, it seems like SPDX mainly consists of all common licenses here and then we mention the license and some other data inside our project. Is it legible to replace actual License file with this SPDX config file or do we need to keep the license file in the project as well? So far it seems like the syntax for specifying license and other data in SPDX file is just for convenience and doesn't serve any actual purpose. For Ex- It would've been better if it could generate license files from it or even if it just validates the data. Maybe I'm missing something because there isn't much resource on the internet regarding this.
-
The CSW Organizational Chart
Yes, they acted very puzzled when an open source license catalog refused to include their weird thing.
-
Craig Wright trying to sue people sharing the Bitcoin Whitepaper is probably the least "Satoshi" thing someone claiming to be Satoshi could do.
At some point, Daniel Connolly applied for OpenBSV to be included in the SPDX license list, but was promptly rejected due its field of use restriction.
linux
-
TinyMCE (also) moving from MIT to GPL
Correct. And the combined work needs to carry the MIT license text and copyright attributions for the MIT software authors. With binary distribution it must also be overt, not hidden in some source code drop, but directly accompanying the binary.
Many people who talk about relicensing never credit the MIT developers or distribute the MIT license text. "Because it's GPL now."
I don't think that you believe that, but many developers do.
Some don't see the need for source code scans for Open Source compliance, because the license.txt says GPL, so it's GPL. Prime example is the Linux kernel. There is code under different licenses in there, but people don't even read https://github.com/torvalds/linux/blob/master/COPYING till the end ("In addition, other licenses may also apply.") and conclude it's simply GPL 2 and nothing else.
Also be aware that sublicensing is not the same as relicensing.
-
The Linux Kernel Prepares for Rust 1.77 Upgrade
So If we would only count code and not comments, it is only 9489 LoC Rust. Which would be about 0.03% and if we take all lines and not only LoC it would be around 0.05%
[0] https://github.com/XAMPPRocky/tokei
[1] https://github.com/torvalds/linux/commit/b401b621758e46812da...
-
Proposed Windows NT sync driver brings big Wine/Proton performance improvements
AIUI fsync is built on futex_waitv which has been upstreamed. So this has to be more than that.
https://github.com/torvalds/linux/commit/a0eb2da92b715d0c97b...
-
Tell HN: GitHub no longer readable without JavaScript
git clone --no-checkout --depth 1 https://github.com/torvalds/linux.git $dir
-
PixieFail: Nine Vulnerabilities UEFI Implementations
Device trees are what you get if you don't implement ACPI.
While there are alternatives, you generally seem to get "device trees and a barebones bootloader" on ARM and "UEFI + ACPI" on amd64.
ACPI will list hardware and necessary hardware properties based on some basic API calls to the system interface. UEFI initialises the ACPI data structure and exposes it to the bootloader so the appropriate drivers can be loaded and configured.
With device trees, you basically configure and build the drivers and configuration into the kernel/OS you're trying to load. That's why compiling Linux on amd64 is generally easy and produces a single image, while for many other devices (smartphones, some SBCs) you need to compile a kernel per device. The device trees only need to be imported/written once per device (or device type, depending on how nice the manufacturers are), but that's how you get stuff like this: https://github.com/torvalds/linux/tree/master/arch/arm64/boo...
On ARM there are actually a few devices that implement UEFI, but most of them have Secure Boot locked in and configured to only boot Windows.
ACPI is not perfect and it's not technically required to have UEFI to implement something better than device trees, but I'm not sure if reinventing the wheel here is necessary or even preferable. UEFI already has open source implementations ready to go, with kernels and other tools already containing code to interact with those APIs, whereas a custom ACPI replacement protocol would need more implementation work,
-
Maestro: A Linux-compatible kernel in Rust
The Linux Kernel Driver Interface
(all of your questions answered and then some)
https://github.com/torvalds/linux/blob/master/Documentation/...
-
Uniting the Linux random-number devices
A bit later another commit [1] was merged that makes reads from /dev/urandom opportunistically initialize the RNG. In practice this has the same result as the reverted commit on non-obsolete architectures, which do have a cycle counter and thus jitter entropy.
[1] https://github.com/torvalds/linux/commit/48bff1053c172e6c7f3...
The commit [1] was eventually reverted [2]
[1] https://github.com/torvalds/linux/commit/6f98a4bfee72c22f50a...
-
Linux: Ext4 data corruption in 6.1.64-1
Here's my understanding so far:
In the upstream Linux kernel there were two fixes posted months from each other, one for direct io [0] and the other one for ext4 [1]. The ext4 one was marked for backport to stable (CC: [email protected]), the other was not. The problem is that these commits depend on each other for things to work properly. If you have both, you're fine. If you have only the backported one, you have a problem.
What versions are affected? We know for sure that 6.1.64 is affected, 6.1.55 is not (because it doesn't have the commit). As of right now, 6.1.64 is still marked as "stable" in Debian [2] but if you actually try to install it from the official mirrors (deb.debian.org), you will get error 403. The fix is included in version 6.1.66 which will soon be available.
The issue seems to be only highlighted in the context of Debian but it is not specific to it. The issue is/was in the official upstream release.
[0] https://github.com/torvalds/linux/commit/936e114a245b6e38e0d...
What are some alternatives?
zen-kernel - Zen Patched Kernel Sources
DS4Windows - Like those other ds4tools, but sexier
winapps - Run Windows apps such as Microsoft Office/Adobe in Linux (Ubuntu/Fedora) and GNOME/KDE as if they were a part of the native OS, including Nautilus integration.
Open and cheap DIY IP-KVM based on Raspberry Pi - Open and inexpensive DIY IP-KVM based on Raspberry Pi
DsHidMini - Virtual HID Mini-user-mode-driver for Sony DualShock 3 Controllers
serenity - The Serenity Operating System 🐞
RyzenAdj - Adjust power management settings for Ryzen APUs
void-packages - The Void source packages collection
edk2-sdm845 - (Maybe) Generic edk2 port for sdm845
illumos-gate - An open-source Unix operating system
vscode-gitlens - Supercharge Git inside VS Code and unlock untapped knowledge within each repository — Visualize code authorship at a glance via Git blame annotations and CodeLens, seamlessly navigate and explore Git repositories, gain valuable insights via rich visualizations and powerful comparison commands, and so much more
AutoEq - Automatic headphone equalization from frequency responses