7 ms·

Wrong, or at the least misleading. What do you mean by 'maintain' here? Because Arch is trying to stay on the bleeding edge side of things in a reasonable mann

Wrong, or at the least misleading. What do you mean by 'maintain' here? Because Arch is trying to stay on the bleeding edge side of things in a reasonable manner and is rolling release, they almost stay 1:1 with upstream, "maintains its own kernel" makes it sound like they would do some heavy patching and do active maintenance with certain kernel versions, et cetera. You can have a look yourself if you want to https://git.archlinux.org/linux.git/commit/?h=v5.7.5-arch1&id=35f8fcadda6fd6d6eb582a7750ee307b2b822686 https://git.archlinux.org/linux.git/commit/?h=v5.7.5-arch1&i...

bluedays 6y ago
They have their own kernel as can be seen here: https://i.imgur.com/jP6Pdvq.png https://i.imgur.com/jP6Pdvq.png Also if you look at the diffstat you can see that there were a number of changes here: https://i.imgur.com/J2em78v.png https://i.imgur.com/J2em78v.png It may be align with the majority of the kernel, but these patches exist in every version of the kernel that is released by Arch. What else could that be called aside from maintaining your own kernel? These changes are extremely small within scope which is the nature of Arch, but they still exist. A more hands-on distro will see many more changes than Arch, naturally. However, as evidenced from the above you can see that Arch does have it's own kernel and I cited Arch as an example because it strives so hard to maintain 1:1 with upstream. Btw, I use Arch.
- phh 6y ago
  "maintaining your own kernel" in this context means that you're bringing bugfixes (including security) independently from the mainline Linux kernel, which would usually involve cherry-picking commits from the mainline. Archlinux doesn't do that, and straight merges Linux mainline.
- bonzini 6y ago
  The RHEL8 kernel has a few tens of thousands of commits on top of 4.18. That's a bit more than Arch. :)

bluedays 6y ago

They have their own kernel as can be seen here: https://i.imgur.com/jP6Pdvq.png https://i.imgur.com/jP6Pdvq.png Also if you look at the diffstat you can see that there were a number of changes here: https://i.imgur.com/J2em78v.png https://i.imgur.com/J2em78v.png It may be align with the majority of the kernel, but these patches exist in every version of the kernel that is released by Arch. What else could that be called aside from maintaining your own kernel? These changes are extremely small within scope which is the nature of Arch, but they still exist. A more hands-on distro will see many more changes than Arch, naturally. However, as evidenced from the above you can see that Arch does have it's own kernel and I cited Arch as an example because it strives so hard to maintain 1:1 with upstream. Btw, I use Arch.

phh 6y ago
"maintaining your own kernel" in this context means that you're bringing bugfixes (including security) independently from the mainline Linux kernel, which would usually involve cherry-picking commits from the mainline. Archlinux doesn't do that, and straight merges Linux mainline.
bonzini 6y ago
The RHEL8 kernel has a few tens of thousands of commits on top of 4.18. That's a bit more than Arch. :)