med-mastodon.com is one of the many independent Mastodon servers you can use to participate in the fediverse.
Medical community on Mastodon

Administered by:

Server stats:

354
active users

#kernel

4 posts4 participants0 posts today
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://hachyderm.io/@edboythinks" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>edboythinks</span></a></span> personally I'm in the process of.migrating from <a href="https://infosec.space/tags/Ubuntu" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Ubuntu</span></a> fonts to <a href="https://infosec.space/tags/B612" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>B612</span></a> because they are superior yet more permissively licensed.</p><ul><li>Sadly I've not found an elegant way to force <a href="https://infosec.space/tags/SunGalatDemi" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SunGalatDemi</span></a> into the <a href="https://infosec.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://infosec.space/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> as <a href="https://infosec.space/tags/Console" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Console</span></a> <a href="https://infosec.space/tags/Font" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Font</span></a> and <a href="https://infosec.space/tags/license" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>license</span></a>-wise that would not work (<a href="https://infosec.space/tags/CDDL" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>CDDL</span></a> is incompatible with <a href="https://infosec.space/tags/GPLv2" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>GPLv2</span></a>) nor would it make sense as any machine that I can't <a href="https://infosec.space/tags/SSH" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>SSH</span></a> into runs in <a href="https://infosec.space/tags/MDA" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>MDA</span></a> mode thus only has the hardware fonts of that mode anyway...</li></ul>
Val Packett 🧉<p><span class="h-card" translate="no"><a href="https://social.treehouse.systems/@angelthorns" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>angelthorns</span></a></span> update: actually i get full framebuffer console if i do console=efifb (NOT tty0!!) <a href="https://social.treehouse.systems/tags/pmos" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>pmos</span></a> <a href="https://social.treehouse.systems/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> <a href="https://social.treehouse.systems/tags/qualcomm" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>qualcomm</span></a></p>
Khurram Wadee ✅<p>Now running <a href="https://mastodon.org.uk/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://mastodon.org.uk/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> 6.15.7.</p>
Collabora<p>Stuck on a debugging issue? Check out our practical guide that outlines which tool to use for the media subsystem: <a href="https://www.collabora.com/news-and-blog/blog/2025/07/22/a-practical-debugging-guide-for-media-driver-developers/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">collabora.com/news-and-blog/bl</span><span class="invisible">og/2025/07/22/a-practical-debugging-guide-for-media-driver-developers/</span></a></p><p><a href="https://floss.social/tags/Kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kernel</span></a> <a href="https://floss.social/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a></p>
Val Packett 🧉<p>Sometimes… fixing things… <a href="https://lore.kernel.org/all/ece307c3-7d65-440f-babd-88cf9705b908@packett.cool/" rel="nofollow noopener" target="_blank">actually breaks things</a> <a href="https://social.treehouse.systems/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a></p>
OSTechNix<p>Linux Kernel 6.16 RC7 Released: Small Fixes, Big Stability <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://floss.social/tags/Kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kernel</span></a> <a href="https://floss.social/tags/Opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Opensource</span></a> <br><a href="https://ostechnix.com/linux-kernel-6-16-rc7-released/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ostechnix.com/linux-kernel-6-1</span><span class="invisible">6-rc7-released/</span></a></p>
Aptivi<p><strong>Linux 6.16 RC7&nbsp;released!</strong></p><p>Linux 6.16 RC7 is now live for developers and curious users to try out. All the interesting changes from performance improvements to bug fixes have been integrated to this release candidate.</p><p>In addition to that, the release announcement has indirectly confirmed (with the statement of “we’re in good shape”) that the final release (July 28th) is the only release remaining for the development of the 6.16.x series before moving on to 6.17 RC1 (August 11th) two weeks later. Those are expected dates, though.</p><p>In the release announcement for this version of the kernel, <a href="https://lore.kernel.org/lkml/CAHk-=wgdXcZfQEL2Xa+GEEtcC7Ez9SEWnGaB76R76VZsYcMOnA@mail.gmail.com/T/#u" rel="nofollow noopener" target="_blank">Linus Torvalds</a> said:</p><blockquote><pre>So last week started very quiet and that always makes me happy. Then on Thursday I started getting some updates, and I went "ok, so at least we have some networking fixes", but things otherwise still felt like this was going to be a tiny rc7.<br><br>And then Friday came along.<br><br>And the weekend.<br><br>And here we are, with a not inconsiderable rc7.<br><br>That said, the last few days I ended up getting a fair amount of pull requests, but pretty much all of them were tiny. A lot of single-fix pulls, and while rc7 isn't the tiny release it looked like mid-week, it's also not really any bigger than usual.<br><br>So there are fixes all over, they are all pretty small.<br><br>Nothing really stands out - the biggest patches in here are for some documentation and self-tests or tooling, not actual kernel code changes.<br><br>So unlike the week before, it all feels very trivial and I think we're in good shape.</pre></blockquote><p><strong>Why not try out this awesome pre-release of Linux 6.16?</strong></p><p><span></span></p><p><a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/computer/" target="_blank">#Computer</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/computers/" target="_blank">#Computers</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/kernel/" target="_blank">#Kernel</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/laptop/" target="_blank">#Laptop</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/laptops/" target="_blank">#Laptops</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/linux/" target="_blank">#Linux</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/linux-kernel/" target="_blank">#LinuxKernel</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/news/" target="_blank">#news</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/tech/" target="_blank">#Tech</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/technology/" target="_blank">#Technology</a> <a rel="nofollow noopener" class="hashtag u-tag u-category" href="https://officialaptivi.wordpress.com/tag/update/" target="_blank">#update</a></p>
Orion Ussner kidder<p>It's looking like <a href="https://mas.to/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://mas.to/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> 6.14+ will contain the driver I need for an intel AX201 on a <a href="https://mas.to/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Debian</span></a> 12, which doesn't work on my <a href="https://mas.to/tags/thinkpad" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>thinkpad</span></a> right now (no wifi! agh!). </p><p>I'm telling you all that for the context behind this question:</p><p>Is it bad/dangerous/unstable to run Debian 12 on kernel 6.14?</p><p>Further, should I use the Ubuntu kernel or get the "raw" kernel?</p><p>Edit: 6.14 might not be necessary after all. Sigh.</p><p><a href="https://mas.to/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>foss</span></a> <a href="https://mas.to/tags/floss" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>floss</span></a> <a href="https://mas.to/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a></p>
st1nger :unverified: 🏴‍☠️ :linux: :freebsd:<p><a href="https://infosec.exchange/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> users who have <a href="https://infosec.exchange/tags/Secure" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Secure</span></a> Boot enabled on their systems knowingly or unknowingly rely on a key from <a href="https://infosec.exchange/tags/Microsoft" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Microsoft</span></a> that is set to expire in September. After that point, Microsoft will no longer use that key to sign the shim first-stage <a href="https://infosec.exchange/tags/UEFI" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>UEFI</span></a> <a href="https://infosec.exchange/tags/bootloader" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bootloader</span></a> that is used by Linux distributions to boot the <a href="https://infosec.exchange/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> with Secure Boot. </p><p>But the replacement key, which has been available since 2023, may not be installed on many systems; worse yet, it may require the <a href="https://infosec.exchange/tags/hardware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>hardware</span></a> vendor to issue an update for the system <a href="https://infosec.exchange/tags/firmware" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>firmware</span></a>, which may or may not happen. It seems that the vast majority of systems will not be lost in the shuffle, but it may require extra work from distributors and users.</p><p><a href="https://lwn.net/SubscriberLink/1029767/43b62a7a7408c2a9/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">lwn.net/SubscriberLink/1029767</span><span class="invisible">/43b62a7a7408c2a9/</span></a></p>
Kevin Karhan :verified:<p><span class="h-card" translate="no"><a href="https://mastodon.social/@GabeMoralesVR" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>GabeMoralesVR</span></a></span> <br><a href="https://infosec.space/tags/IRC" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>IRC</span></a> and <a href="https://infosec.space/tags/Mailinglists" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Mailinglists</span></a> with their problems, [and they both have many] are at least <a href="https://infosec.space/tags/indexable" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>indexable</span></a> and <a href="https://infosec.space/tags/searchable" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>searchable</span></a> to the point that I could propable make a <a href="https://infosec.space/tags/supercut" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>supercut</span></a> of <a href="https://infosec.space/tags/LKML" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LKML</span></a> folks shouting at each other...</p><ul><li>I mean they already to so <a href="https://www.youtube.com/watch?v=WvXSSPovi9I" rel="nofollow noopener" target="_blank">in the code</a> of the <a href="https://infosec.space/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a>!</li></ul>
Jarkko Sakkinen<p>I made lsiommu as I just wanted to get rid of the shitty combination of bash and python I had before:</p><pre><code>~/work/staging/lsiommu master* ❯ build/lsiommu IOMMU Group 0 00:07.1 Class 060400: Vendor 8086 Device 9a25 [8086:9a25] (rev 01) IOMMU Group 1 00:07.0 Class 060400: Vendor 8086 Device 9a23 [8086:9a23] (rev 01) IOMMU Group 2 00:02.0 Class 030000: Vendor 8086 Device 9a49 [8086:9a49] (rev 01) IOMMU Group 3 00:00.0 Class 060000: Vendor 8086 Device 9a14 [8086:9a14] (rev 01) IOMMU Group 4 00:04.0 Class 118000: Vendor 8086 Device 9a03 [8086:9a03] (rev 01) IOMMU Group 5 00:0a.0 Class 118000: Vendor 8086 Device 9a0d [8086:9a0d] (rev 01) IOMMU Group 6 00:0d.0 Class 0c0330: Vendor 8086 Device 9a13 [8086:9a13] (rev 01) 00:0d.2 Class 0c0340: Vendor 8086 Device 9a1b [8086:9a1b] (rev 01) IOMMU Group 7 00:0e.0 Class 010400: Vendor 8086 Device 9a0b [8086:9a0b] (rev 00) IOMMU Group 8 00:14.0 Class 0c0330: Vendor 8086 Device a0ed [8086:a0ed] (rev 20) 00:14.2 Class 050000: Vendor 8086 Device a0ef [8086:a0ef] (rev 20) IOMMU Group 9 00:14.3 Class 028000: Vendor 8086 Device a0f0 [8086:a0f0] (rev 20) IOMMU Group 10 00:15.0 Class 0c8000: Vendor 8086 Device a0e8 [8086:a0e8] (rev 20) IOMMU Group 11 00:16.0 Class 078000: Vendor 8086 Device a0e0 [8086:a0e0] (rev 20) IOMMU Group 12 00:1d.0 Class 060400: Vendor 8086 Device a0b0 [8086:a0b0] (rev 20) IOMMU Group 13 00:1f.0 Class 060100: Vendor 8086 Device a082 [8086:a082] (rev 20) 00:1f.3 Class 040100: Vendor 8086 Device a0c8 [8086:a0c8] (rev 20) 00:1f.4 Class 0c0500: Vendor 8086 Device a0a3 [8086:a0a3] (rev 20) 00:1f.5 Class 0c8000: Vendor 8086 Device a0a4 [8086:a0a4] (rev 20) IOMMU Group 14 55:00.0 Class 010802: Vendor 144d Device a808 [144d:a808] (rev 00) </code></pre><p>Perhaps the most interesting implementation note is that it uses libudev for PCI discovery, instead of traversing sysfs (because the latter sucks).</p><p>Right and I made my own shitty teardown manager framwork:</p><pre><code>/* SPDX-License-Identifier: GPL-3.0-or-later */ /* * Copyright(c) Opinsys Oy 2025 */ <a class="hashtag" href="https://social.kernel.org/tag/ifndef" rel="nofollow noopener" target="_blank">#ifndef</a> TEARDOWN_H <a class="hashtag" href="https://social.kernel.org/tag/define" rel="nofollow noopener" target="_blank">#define</a> TEARDOWN_H <a class="hashtag" href="https://social.kernel.org/tag/include" rel="nofollow noopener" target="_blank">#include</a> &lt;libudev.h&gt; <a class="hashtag" href="https://social.kernel.org/tag/define" rel="nofollow noopener" target="_blank">#define</a> teardown(func) __attribute__((cleanup(func))) void teardown_udev(struct udev **udev); void teardown_udev_device(struct udev_device **dev); void teardown_udev_enumerate(struct udev_enumerate **enumerate); <a class="hashtag" href="https://social.kernel.org/tag/endif" rel="nofollow noopener" target="_blank">#endif</a> /* TEARDOWN_H */ </code></pre><p>Dependencies:</p><pre><code>❯ ldd build/lsiommu linux-vdso.so.1 (0x00007f083ccd5000) libargtable2.so.0 =&gt; /lib/x86_64-linux-gnu/libargtable2.so.0 (0x00007f083cc8a000) libudev.so.1 =&gt; /lib/x86_64-linux-gnu/libudev.so.1 (0x00007f083cc5c000) libsystemd.so.0 =&gt; /lib/x86_64-linux-gnu/libsystemd.so.0 (0x00007f083cb8c000) libc.so.6 =&gt; /lib/x86_64-linux-gnu/libc.so.6 (0x00007f083c9ab000) /lib64/ld-linux-x86-64.so.2 (0x00007f083ccd7000) libcap.so.2 =&gt; /lib/x86_64-linux-gnu/libcap.so.2 (0x00007f083c99f000) libgcrypt.so.20 =&gt; /lib/x86_64-linux-gnu/libgcrypt.so.20 (0x00007f083c856000) liblzma.so.5 =&gt; /lib/x86_64-linux-gnu/liblzma.so.5 (0x00007f083c827000) libzstd.so.1 =&gt; /lib/x86_64-linux-gnu/libzstd.so.1 (0x00007f083c76b000) liblz4.so.1 =&gt; /lib/x86_64-linux-gnu/liblz4.so.1 (0x00007f083c745000) libgpg-error.so.0 =&gt; /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007f083c71d000) </code></pre><p>I can throw this to some Git repository if anyone is interested any of this. It’s really just “by me for me”, but I neither mind sharing it.</p><p><a class="hashtag" href="https://social.kernel.org/tag/linux" rel="nofollow noopener" target="_blank">#linux</a> <a class="hashtag" href="https://social.kernel.org/tag/kernel" rel="nofollow noopener" target="_blank">#kernel</a> <a class="hashtag" href="https://social.kernel.org/tag/iommu" rel="nofollow noopener" target="_blank">#iommu</a></p>
Kevin Russell<p><span class="h-card" translate="no"><a href="https://mastodon.social/@mcc" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>mcc</span></a></span> </p><p>The Debian community forums would love to see your bug. Good luck, however you search. </p><p><a href="https://mstdn.social/tags/debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>debian</span></a> <a href="https://mstdn.social/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> <a href="https://mstdn.social/tags/ReturnFromSleep" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>ReturnFromSleep</span></a> <a href="https://mstdn.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a></p>
Boiling Steam<p>Tilck: A Tiny Linux-Compatible Kernel: <a href="https://github.com/vvaltchev/tilck" rel="nofollow noopener" target="_blank"><span class="invisible">https://</span><span class="">github.com/vvaltchev/tilck</span><span class="invisible"></span></a> <br><a href="https://mastodon.cloud/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://mastodon.cloud/tags/update" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>update</span></a> <a href="https://mastodon.cloud/tags/release" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>release</span></a> <a href="https://mastodon.cloud/tags/foss" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>foss</span></a> <a href="https://mastodon.cloud/tags/tilck" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>tilck</span></a> <a href="https://mastodon.cloud/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> <a href="https://mastodon.cloud/tags/embedded" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>embedded</span></a></p>
Khurram Wadee ✅<p>Now running <a href="https://mastodon.org.uk/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://mastodon.org.uk/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> 6.15.6.</p>
OSTechNix<p>Linux Kernel 6.16 RC6 Released <a href="https://floss.social/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://floss.social/tags/Kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Kernel</span></a> <a href="https://floss.social/tags/Opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Opensource</span></a> <br><a href="https://ostechnix.com/linux-kernel-6-16-rc6-released/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ostechnix.com/linux-kernel-6-1</span><span class="invisible">6-rc6-released/</span></a></p>
Thorsten Leemhuis (acct. 1/4)<p>""The latest alpha of the upcoming <a href="https://hachyderm.io/tags/Blender" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Blender</span></a> 5.0 release comes with High Dynamic Range (HDR) support for <a href="https://hachyderm.io/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> on <a href="https://hachyderm.io/tags/Wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Wayland</span></a> […]</p><p>It’s been a lot of personal blood, sweat and tears, paid for by <a href="https://hachyderm.io/tags/RedHat" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>RedHat</span></a> across the Linux graphics stack for the last few years to enable applications like Blender to add <a href="https://hachyderm.io/tags/HDR" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>HDR</span></a> support. From <a href="https://hachyderm.io/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> work, like helping to get the HDR mode working on Intel laptops, and improving the Colorspace and HDR_OUTPUT_METADATA KMS properties, to creating a new library for EDID and DisplayID parsing, and helping with wiring things up in <a href="https://hachyderm.io/tags/vulkan" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>vulkan</span></a>.</p><p>I designed the active color management paradigm for Wayland compositors, figured out how to properly support HDR, created two wayland protocols to let clients and compositors communicate the necessary information for active color management, and created documentation around all things color in FOSS graphics. This would have also been impossible without <span class="h-card" translate="no"><a href="https://floss.social/@pq" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>pq</span></a></span> from Collabora and all the other people I can’t possibly list exhaustively. […] ""</p><p><a href="https://blog.sebastianwick.net/posts/blender-hdr-reference-white/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">blog.sebastianwick.net/posts/b</span><span class="invisible">lender-hdr-reference-white/</span></a> (written by <span class="h-card" translate="no"><a href="https://hachyderm.io/@swick" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>swick</span></a></span>)</p>
Linux Magazine<p>From the Linux Update newsletter: <span class="h-card" translate="no"><a href="https://opensocial.at/profile/linuxnews" class="u-url mention" rel="nofollow noopener" target="_blank">@<span>linuxnews</span></a></span> looks at Linux 6.12 LTS, which makes real-time support an official part of the operating system kernel<br><a href="https://www.linux-magazine.com/Issues/2025/295/Linux-6.12-LTS?utm_source=mlm" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">linux-magazine.com/Issues/2025</span><span class="invisible">/295/Linux-6.12-LTS?utm_source=mlm</span></a><br><a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://fosstodon.org/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> <a href="https://fosstodon.org/tags/support" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>support</span></a> <a href="https://fosstodon.org/tags/LTS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>LTS</span></a> <a href="https://fosstodon.org/tags/FOSS" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>FOSS</span></a> <a href="https://fosstodon.org/tags/extensions" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>extensions</span></a> <a href="https://fosstodon.org/tags/OpenSource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>OpenSource</span></a></p>
Khurram Wadee ✅<p>Now running <a href="https://mastodon.org.uk/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://mastodon.org.uk/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> 6.15.5.</p>
Linux Magazine<p>After a clash over some late fixes and disagreements between bcachefs's lead developer and Linus Torvalds, Linux kernel 6.17 may drop bachefs<br><a href="https://www.linux-magazine.com/Online/News/Linux-Kernel-6.17-Drops-bcachefs?utm_source=mlm" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://www.</span><span class="ellipsis">linux-magazine.com/Online/News</span><span class="invisible">/Linux-Kernel-6.17-Drops-bcachefs?utm_source=mlm</span></a><br><a href="https://fosstodon.org/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>Linux</span></a> <a href="https://fosstodon.org/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> <a href="https://fosstodon.org/tags/bachefs" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>bachefs</span></a> <a href="https://fosstodon.org/tags/patches" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>patches</span></a></p>
OSTechNix<p>Linux Kernel 6.16 RC5 Released: Steady Progress with Key Fixes <a href="https://floss.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>linux</span></a> <a href="https://floss.social/tags/kernel" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>kernel</span></a> <a href="https://floss.social/tags/opensource" class="mention hashtag" rel="nofollow noopener" target="_blank">#<span>opensource</span></a> <br><a href="https://ostechnix.com/linux-kernel-6-16-rc5-released/" rel="nofollow noopener" translate="no" target="_blank"><span class="invisible">https://</span><span class="ellipsis">ostechnix.com/linux-kernel-6-1</span><span class="invisible">6-rc5-released/</span></a></p>