Well, well, well...

Asahi Linux is the reason you can run Linux on an Apple Silicon Mac today. For years, the project put most of its own code under the MIT license so that anyone, including the BSDs, could reuse it as needed.

That is changing because Asahi Linux is tired of code laundering. They have announced that Asahi is moving all of its repositories to the GNU General Public License version 2 or later. Going forward, all Asahi Linux code will be under strong copyleft licenses only.

This is because people were taking in-development code straight out of their personal forks, publishing it without credit, or rewriting it with AI to hide its origin for "replacing the project and aggressively monetising Linux on Apple Silicon."

What is code laundering?

Code laundering (also called license laundering) is the practice of taking someone else's code and passing it through a process that hides where it came from, so you can use it without honoring the original license or crediting the author.

Before AI, this usually meant manually rewriting code line by line, renaming variables and stuff, and shuffling functions around until it no longer looked like the original.

LLMs made it much more easy and cheaper of course.

The MIT license only asks you to keep the original copyright notice. It doesn't require you to share your changes or keep your version open. That's what makes it popular, and it's also what made things problematic for Asahi here.

Learning from history

The move has come after the Asahi team was made aware "some time ago" of multiple attempts to exploit its permissive licensing to hijack its work.

In the most extreme cases, feature code that was still under development was lifted from developers' personal forks before it was even publicly released. The report points out that the MIT license "explicitly allows this, and has no carveouts to protect against bad faith actors."

Asahi didn't name anyone in the report. It also didn't spell out how existing contributions will be relicensed or whether every past contributor agreed to it.

Asahi draws parallels with WINE's situation two decades ago. WINE, the compatibility layer that lets you run Windows apps on Linux, was originally MIT-licensed too. But in the late 90s and early 2000s, companies took the code, built proprietary forks on top of it, and sold them commercially. So, in 2002, the WINE team relicensed to the LGPL to discourage proprietary forks and push companies to contribute upstream.

Those who do not learn from history are doomed to repeat it

Asahi has been upset lately

Asahi didn't name anyone so we are left with guesswork on who they are targeting with this license move.

There have been at least two public forks of Asahi's work in recent months, both tied to AI-assisted development. In case you did not know, Asahi Linux forbids AI generated code contribution.

The first is Aurora Silicon and its Vulkan driver, Borealis. Borealis is a fork of Asahi's HoneyKrisp, the Vulkan driver for Apple GPUs. Aurora Silicon submitted a pull request to register its own Vulkan driver ID with Khronos (VK_DRIVER_ID_AURORA_BOREALIS), says the driver runs on M1 to M5 and the A18 Pro, and keeps it in its own Mesa fork rather than upstream.

The second is Gravity Linux, a Fedora-based distro for Apple Silicon. It was forked from Asahi over the disagreement about LLM use.

To be fair to Gravity, it is open source, it isn't selling anything, and it credits its AI use openly. It even says it plans to sunset the distro once its driver work lands upstream.

It isn't the kind of bad actor the progress report describes. But it does represent the "permissive fork that embraces AI" approach that Asahi has consistently pushed back against.

For clarification, Asahi's progress report does not mention Aurora Silicon or Gravity Linux by name. I have provided their conflict with Asahi as context.

Why this license change matters

As far as I can tell, this is the first time a major open source project has moved to copyleft specifically because of AI-assisted code laundering. Projects have relicensed before, but usually to stop cloud providers from reselling their work as a service. This one is specifically about AI.

I wouldn't be surprised if more hardware enablement and reverse-engineering projects follow. Making the first changes takes a lot of time and effort but they are easier to "rewrite" once someone has done the hard part.

Will the GPL actually help?

If the problem is people who already ignore the MIT license, why would they respect the GPL? After all, GPL cannot stop a determined bad actor. Nothing does, actually.

Stripping attribution from MIT code already breaks the MIT license, since keeping the copyright notice is its one real condition.

What the GPL changes is the commercial benefit. Under MIT, someone can take Asahi's code, close it up, and sell a product, and that's perfectly legal as long as the notice stays in.

Under the GPL, anyone who distributes a modified version has to release the source under the same license. You can't legally build a closed, paid Apple Silicon distro on top of GPL code. And if a product's source has to be public, the copying is easier to spot. Not everyone is happy

The move has drawn criticism, particularly from the BSD side, which was one of the main reasons Asahi chose MIT in the first place. OpenBSD's Apple Silicon support relies on Asahi's m1n1 bootloader.

OpenBSD developer Bryan Steele wrote on X:

"Sad to see Asahi out there burning bridges for no reason.. relicensing m1n1 and drivers under GPL2-or-later, seemingly without the consent of all prior contributors, under the guise of "defending against AI bad actors", seems entirely disingenuous and misguided."

Wrapping up

Asahi is betting that copyleft license provides a better defense in this changed world where anyone can launder code with a prompt.

It may not stop the bad actors from rewriting its code, but at least it reduces the chances of a closed commercial fork.

It would be interesting to see whether the BSD community finds a way to keep working with Asahi under the new terms.

Say the name "Chromium" out loud in Linux circles, and you will soon see what a mob looks like. Many people don't like how much of the web rests on one engine led by Google, and they prefer to keep it away from their systems.

Now we have Domicile, a new Rust-based Wayland compositor that uses a patched build of Chromium to draw the entire desktop as a web page.

Apps still run natively, and each Wayland window goes straight into Chromium's rendering system and shows up inside that page as an element. A window and a website can then sit side by side and be arranged the same way.

Domicile: Overview

Domicile is not a drop-in desktop like GNOME or KDE Plasma. It leaves the bar, the window layout, and the look to a shell, and that shell itself is a web page you have to write yourself.

Native app windows and websites both sit on that page, and because CSS decides where each one goes, layouts like tiling or floating take only a few lines of styling.

You can even swap the shell without closing a single window because loading a new one resets only the state held in the shell's own page. A single page can span every monitor, and shells are built from packages that anyone can publish on npm, whether it is a whole desktop, a bar, or a launcher.

The compositor still handles the lock screen, tray icons, notifications, and screen sharing, while the shell decides how they look. The built-in browser runs Manifest V3 Chrome extensions, but some of them behave differently than they do in Chrome.

Apps need Wayland support to run. Electron, SDL, and Qt apps start in Wayland mode, but X11-only ones will not run. Xwayland, the compatibility layer that lets X11 apps work on Wayland desktops, is something Domicile does not include.

The project is provided under the MIT license, and the Chromium files it modifies stick to Chromium's licenses. One more thing, and this could be a dealbreaker for some of you, the project is AI-assisted.

Manganese, the element?

Not quite. Manganese is the ready-made shell that comes with Domicile, and it works as a complete tiling desktop out of the box. Its keybindings follow Sway's on the Super key, and you get ten workspaces along with tabs, stacks, splits, floating windows, and a scratchpad.

Websites open as windows too, sitting next to native apps in the same layout, while extensions from the Chrome Web Store show up as buttons in the top bar.

It comes with a Settings app, clipboard history, launcher, screenshots tool, notifications, and a lock screen. Since every part of it is its own package, you can add a new item to the bar or replace the launcher while the rest stays as it is.

Getting started

Packages exist for Fedora, openSUSE, Debian, Ubuntu, and Arch Linux, plus an AUR package for Arch users. For NixOS, or Nix on any distro, you can use the project's flake.

It runs only on x86_64, and the project has no ARM builds.

A monolithic package carries Manganese, the login session, the domicile command, and the React packages that shells build against. After installing, you point a config file at the shell you want, then log out and pick "Domicile" on the login screen.

Linus Torvalds just released the second weekly release candidate of Linux 7.4 with some notable bug fixes and other changes routed in past the merge window. It's another big one in the AI era.

This week brought some adjustments to the AMD PerfOpt feature for helping Radeon iGPU performance, fixing faulty BHI mitigation selection for some kernel configurations, a big improvement for FAT32 especially with synchronous mounts, AMDGPU driver fixes for HDMI 2.2 FRL, and numerous fixes for "nasty long standing bugs" in the core memory management code. Plus the usual assortment of bug fixes as well as the seemingly never-ending flow of AI/LLM generated patches and bug reports.

Linux 7.4-rc2 Git tag

Linux creator Linus Torvalds wrote in the 7.4-rc2 announcement:

"Ok, a big -rc2 to go with the largest ever -rc1. But the diffstat looks fairly benign, and is dominated by some automated coccinelle updates that I got for the merge window but left for rc2 because I didn't want to deal with them when I was on the road (and had a hard time finding the motivation to deal with them afterwards too, to be honest).

That said, the scripted updates are largely just one- and two-liners, and they [really] are very straightforward so they "dominate" the diffstat only in the sense that they are very spread out and do add a lot of noise.

When masking that noise out from the diffstat, the shape of it changes - not spread out over thousands of files any more. But it does not look unusual: a third is drivers (gpu, networking and sound account for most of it, but there's a bit of everything), another third is networking and bpf, and the final third is "the rest" (mostly filesystems, mm, arch updates).

And yes, much of this was driven by various AI fixes. I think I'll stop repeating that, and we can just take it for granted. But this time around Alexei claims that on the bpf side at least the fixes are now coming in faster than the new reports, and that sounds lovely if true.

I think most other areas haven't reached that point yet, but it's at least a sign that we _may_ be starting to see the tide starting to turn.

Don't hold your breath, but maybe cross your fingers we'll be getting there in the not entirely distant future.

In the meantime, please keep testing,"

See our Linux 7.4 feature overview for a look at all the changes coming to this kernel aiming for a stable release around the end of December.

Slax developer Tomas Matejicek has announced Slax 2026.11, a new version of the lightweight, portable Linux distribution designed to run from a USB drive. Based on Debian 13 and powered by the Linux kernel 6.12, the release features a redesigned desktop, a built-in AI assistant, Secure Boot support, and a graphical installer, all packed into a 512 MiB ISO image.

The desktop has been overhauled with Alt+Tab window previews, live taskbar thumbnails, and four virtual workspaces. Users can view all workspaces simultaneously with Alt+F3 or switch between them using Ctrl+F1 through F4.

The desktop also supports files and folders, and the taskbar includes keyboard layout switching and volume controls. Application interfaces have been adjusted for a more consistent appearance across older and newer programs.

The application launcher has been improved as well. Optional applications are marked with a download icon, letting users install and launch them from the menu. Traditional package management through APT remains available.

One of the most notable additions is the Slax AI Assistant, which allows users to troubleshoot problems, inspect their systems, and execute commands using natural-language instructions. It helps identify disk space usage, investigate system issues, and perform administrative tasks. The assistant requires an internet connection and user sign-in.

Slax 2026.11 also includes a graphical installer for Windows and Linux. Users can create bootable USB drives or install Slax alongside an existing operating system on supported configurations. Additionally, UEFI Secure Boot is now supported through a signed bootloader and kernel, eliminating the need to disable Secure Boot on compatible machines.

Another improvement concerns persistent sessions. A single USB drive can store multiple named sessions, each retaining its own applications, files, and settings. Users can select a session at startup, duplicate it using F4, or rename it with F6, as these sessions can be carried between computers.

For disk maintenance and recovery, Slax includes a graphical partition manager that supports creating, resizing, and formatting partitions. Additional utilities support LVM, LUKS encryption, and filesystems such as XFS. VirtualBox, VMware, and SPICE integration is also included for virtual machine environments.

However, users depending on Slax’s modular system should note an important change. The distribution now uses OverlayFS instead of AUFS, so the slax activate and slax deactivate commands can no longer dynamically load or unload .sb modules during a running session.

Modules can still be included before boot, while installing software through APT and preserving changes in persistent sessions remain supported.

For more information, see the announcement.

The aerynOS team has published its latest unstable stream update, introducing Linux kernel 7.2.15, which marks the final release in the 7.2 series. The team is preparing to move to version 7.3, expected to arrive in the volatile repository soon.

The update also includes Linux LTS 6.18.62, along with newer versions of several system components, including systemd 261.5, LLVM 23.1.5, and glibc 2.44 development snapshots.

On the package management side, Moss now displays help when users enter the older moss install and moss remove commands or their aliases. Boulder and Ent have also been updated to use a new versioning format for packages built from Git commits.

Desktop updates include KDE Gear 26.08.3, Hyprland 0.57.1, Dux suite 2.1 (formerly Dank Material Shell), Waybar 0.16, and Mir 2.31, accompanied by a rebuild of Miracle WM.

KWin receives a fix for crashes involving DisplayLink docking stations when running fullscreen applications. Additional upstream NVIDIA fixes address graphical glitches, flickering, and buffer allocation problems.

COSMIC Player receives missing GStreamer dependencies, restoring audio and video playback. Meanwhile, both Ghostty and Kitty have fixes for Bash shell startup integration.

Other notable package updates include GStreamer 1.28.9, Poppler 26.11, Zed 1.27, Signal Desktop 8.34, and PowerStation 0.9. The Poppler update includes printing fixes, while additional character maps required by Ghostscript have been added.

Moreover, Rsync now includes daemon service units and the rrsync restricted helper. Zulip Desktop also gets a fix for flashing when using dark mode, along with a new application theme selector.

Finally, several new packages have been added to the repositories, including the terminal-based bandwidth monitor bandwhich, the disk usage utility duf, Gitea’s official command-line client, GNU Stow, and openfortivpn.

KDE’s KeepSecret password manager and the JetBrains Mono typeface are also newly available.

For more information, see the announcement.

I’ve been doing the OverTheWire Bandit over the past couple of days and have become stuck on the earlier levels. I deem this very embarrassing as this is supposed to be an “easy” and “recommended for beginners” type of puzzle that requires hands on understanding of the Linux terminal. But I have been using Linux for 9 months now, I wouldn’t do the most complicated things (other than break my whole os) only the things required to make my overall user experience somewhat enjoyable. Now this makes me very sad to come to the conclusions that I may be below the average Linux beginner which I didn’t know was possible according to my knowledge. I am only asking of tips and tricks to these puzzles and maybe to positive reinforcement to make feel better about myself. Now I will not tolerate spoilers as in the official rules of OverTheWire clearly states, and I hope you will follow this rule for the better sake of my learning and understanding of the Linux terminal ( and for the sake of the game itself)

Even before the Linux v7.4 merge window was over, there were already two pull requests of drm-misc-next material targeting for what will be Linux 7.5. This week already saw the third drm-misc-next pull request of more feature patches targeting this next kernel version.

This week's drm-misc-next pull brings Rockchip RK3568 support to the Rockchip DRM display driver. The RK3568 is a quad-core Arm Cortex-A55 SoC with a Mali-G52 2EE GPU and a small NPU and VPU too. The RK3568 is found in some industrial/embedded PCs, some NAS devices, and single board computers. Nice seeing the continued work on improving mainline kernel support for Rockchip SoCs.

Separately there are also a number of additional display panels now supported by the mainline kernel including the DCLTek 300249 5.5", DLCTek 300248 10.5", Novetake NT37705, xiaomi-lavender, Tianma TL063FVMC43-02, Tianma TL063FVMCA01-00, Tianma TL060FVXS16-00, TXD TXDI600YANPA-43V3, AUO B101UAN01, Truly NT36850 WQHD, Novatek NT36850, Samsung AMS644VK04, Hitachi TX10D07VM0BAA, LG LH400WV3-SD04, and Mingjun MJ070BI30IA2.

AMD Ryzen AI

The AMDXDNA accelerator driver for Ryzen AI NPus meanwhile saw support added for a new 6.0 firmware release, adding NPU3 classic device support, get/set power mode handling for new AIE4 hardware, and other AIE4 enabling like suspend and resume, clock / DPM frequency / resource information queries, AIE4 command submission, and other important additions. Over the course of this year and the past few kernel versions there's been a lot of enablement work around the AIE4 hardware that presumably is the next-gen Ryzen AI NPU to be found with the upcoming Zen 6 based client platforms launching in the new year. Hopefully with Linux 7.5 the AIE4 hardware support will be in good standing.

The full list of drm-misc-next feature patches for the week via this pull request.

me and fedora have been boxing for a while now and I’m thinking I want to try something else after I finish designing my next home server case for it.

I’m considering NASty as it’s doing pretty much everything out of box I want to do with this next one already, and even though it’s young, it’s build on nixOS, which I consider mature at this point.

But I have no experience with nixOS. It sounds like it’s a less obnoxious form of fedora coreOS. Any opinions?

Currently running mint on a 15+ year old HP laptop but I want to update to a 'modern' second hand Thinkpad. The second hand market is just full of different model numbers and I'm not sure how to filter to what I'm after.

I get most tech basics (ram, ssh) but I'm not sure what all the models numbers, generations or processors mean.

Looking for something with a memory card spot, HDMI output and ideally touchscreen.

I don't use it for gaming but have an ultra wide screen high res monitor (possibly 2k cant quite remember) that I'd like to take advantage of.

Larger SSD and 16gb ram wouldn't hurt too but I assume I can upgrade them.

I don't need the Yoga tablet style folding.

TUXEDO Computers has just announced that its upcoming Debian-based TUXEDO OS has entered the final stage of its open beta. That brings the Linux distro right up to the point of being fully transitioned away from Ubuntu.

The new edition, known as TUXEDO OS “Continuous Debian,” replaces the distribution’s traditional Ubuntu foundation with Debian Testing. The change denotes a significant shift for TUXEDO OS, which is developed by German Linux hardware manufacturer TUXEDO Computers.

Open beta testing started in August, and since then the dev team has issued five beta ISOs. The company has reported a large number of bug reports as a result of the testing, as well as a lot of positive feedback from users who have been running the new system without any issues.

As for the software, the current beta runs KDE Plasma 6.7.4 on Wayland, alongside KDE Frameworks 6.30, Qt 6.11.2, and Linux kernel 7.2. Unlike Debian itself, which periodically promotes its Testing branch to Stable, TUXEDO OS will remain permanently based on Debian Testing.

TUXEDO Computers will also continue maintaining its own package repositories and providing updates for key components, including the kernel, graphics drivers, and KDE Plasma.

Throughout November, the development team is concentrating on handling outstanding bug reports and handling remaining issues before the first stable release. Users participating in the testing program are encouraged to report not previously identified bugs or unanticipated behavior as soon as possible.

However, bug fixing is not the only thing left to do. TUXEDO Computers also needs to establish and validate a suite of structured, automated QA test procedures. Those tests have to be run before they can actually set a release date.

As for when the stable Debian-based TUXEDO OS will be arriving, the developers have not given us a date at this point. They do, however, expect to be able to release it fairly soon once the final testing and QA are complete.

For additional information, see the announcement.

Those interested in testing the upcoming Debian-based TUXEDO OS before its stable release can download the latest beta ISO images from the preview download directory.

Clarification: I normally physically log on to and play media on host A using mpv, displaying the video on an external monitor HDMI-A-2 and playing the audio from host A's headphone jack connected to external speakers. Today, I tried not physically logging on to host A, but remotely logging in from host B (my phone) using ssh from the same network and running the mpv command from host B. mpv then displays the video on the expected display HDMI-A-2, but it doesn't play any audio.

Symptomatically, if I haven't logged on physically to host A, mpv only displays video, plays no audio and throws errors. Why do I need to be physically logged on to host A for mpv to be able to access audio? You'd think a video feed would be more guarded than an audio one. But maybe this isn't about security at all? Please enlighten me! 😊

I got a pc that suffers from severe heating problems because of its poorly designed passive cooling case. I tried several strategies to put temperature under control, did a lot of tests with thermald, but ended up hacking a fan into the case. However, I still have problems with ssd temperatures.

Right now, as I write this, the nvme ssd is at 67ºC and easily goes beyond 80 or 90 during data transfers. I already lost 2 ssds before realizing this was the problem, because I was controlling just the cpu temperature.

There's no physical way to force airflow where the ssd is, so I was wondering if there's some way to throttle data transfer of something to prevent the ssd temperatures from reaching a threshold. All I could find was a vibecoded github repository. I don't care if data transfer gets ridiculously slow, as long as the ssd remain safe, and I can't consider getting any new hardware right now.

I'm currently running fedora 44 on that machine

Edit: I thought there was an easier software mitigation to that, but apparently, solutions will tend to the hardware side, so here are the hardware details:

• It's an unbranded chinese cheap mini pc with a heat dissipation case that doesn't dissipate well
• The ssd is mounted on the back of the motherboard. The model is a sandisk M.2 1TB 2280
  Here's a photo of the case, for the reference (don't judge me lol):

Timestamps:

00:00 Intro

00:38 Sponsor: Internxt

02:43 Affinity confirms Linux version is coming

04:33 Proton apologizes, publishes Al manifesto

08:10 Cutefish runs native macOS apps now

11:20 SUSE to let go of 10% of their workforce

13:24 Fedora 45 released

14:56 Linux Mint shows more of their new apps

17:08 OpenAl found about 1000 flaws in the kernel

19:07 Nvidia drivers update with better Wayland support

20:23 Discord ditches electron for their client, for Rust

21:46 News publishers sue Brave for selling heir content to Al providers

23:37 Macs get their Apple Silicon Proton in the form of Hadron

25:55 Sponsor: Tuxedo Computers

Links

Affinity confirms Linux version is coming

https://www.omgubuntu.co.uk/2026/11/affinity-linux-release-confirmed

Proton apologizes, publishes Al manifesto

https://www.techradar.com/vpn/vpn-services/proton-apologizes-to-community-after-internal-memo-shows-force-behind-proposed-ai-use-in-building-its-privacy-products

https://proton.me/blog/ai-manifesto

Cutefish runs native macOS apps now

https://cutefish.org/blog/running-mac-apps/

https://cutefish.org/blog/mac-apps-first-milestone/

SUSE to let go of 10% of their workforce

https://www.theregister.com/software/2026/11/02/suse-to-cut-one-in-ten-employees-because-of-ai/5306950

Fedora 45 released

https://fedoramagazine.org/announcing-fedora-linux-45/

Linux Mint shows more of their new apps

https://blog.linuxmint.com/?p=5093

OpenAl found about 1000 flaws in the kernel

https://www.phoronix.com/news/OpenAI-948-Linux-LPE-Bugs

Nvidia drivers update with better Wayland support

https://9to5linux.com/nvidia-620-linux-graphics-driver-released-with-wayland-improvements

Discord ditches electron for their client, for Rust

https://www.theverge.com/news/1027379/discord-ditching-electron-web-app

News publishers sue Brave for selling heir content to Al providers

https://techcrunch.com/2026/11/02/new-york-times-and-other-outlets-sue-web-browser-brave-over-alleged-content-scraping/

Macs get their Apple Silicon Proton in the form of Hadron

https://github.com/Broyojo/hadron

cross-posted from: https://lemmy.world/post/54110939

Unredacted hardened Kernel

Hardened debian kernel built on top of graphene os patches by the redacted non profit . Details for apt repo are here.

https://git.unredacted.org/unredacted/linux-hardened-unredacted

Figured Id share for those interested. Text below copied from git readme.

What this kernel changes

On top of upstream Linux, this build applies the anthraxx/linux-hardened patch set under a kernel .config composed from anthraxx's own Arch packaging config.x86_64 (pinned by sha256 + signed-commit-verified in configs/upstream-seed.toml) layered with our project overlay (configs/intent.common.config plus the x86-only configs/intent.x86_64.config; per-symbol rationale in configs/POLICY.md). Each build re-fetches the pinned seed, verifies its signature, merges our intent, runs olddefconfig, and aborts unless every intent line lands — so new hardening features anthraxx adopts flow through automatically, while regressions on the symbols we explicitly pin fail fast at configure time. Full design in docs/operators/config-architecture.md. The hardening falls into four buckets: memory-safety (heap and stack zero-init, stack-erase-on-return, hardened usercopy, FORTIFY_SOURCE, slab freelist hardening and canaries, KASLR, KFENCE); integrity (W^X for kernel and module text, forced module-signature verification, integrity-mode lockdown under Secure Boot); attack-surface reduction (/dev/mem, /proc/kcore, kexec, and several legacy syscalls removed); and restrictive sysctl defaults (unprivileged user namespaces off; perf, BPF, and ptrace restricted to root).

That hardening comes with friction worth knowing before you install:

• Out-of-tree modules (NVIDIA, ZFS, VirtualBox) must be rebuilt against our headers and signed. DKMS is designed to do this with a machine-local MOK key you enroll once at reboot (not yet validated against a published release — see docs/users/dkms.md).
• Rootless containers (Docker, Podman), the Chromium sandbox, Snap, and Flatpak depend on unprivileged user namespaces, which are off by default. Re-enable them via the opt-in in docs/users/incompatibilities.md.
• kexec/kdump, hibernation, and /dev/mem-based tools do not work.
• Every module must be signed. An unsigned out-of-tree module will not load (MODULE_SIG_FORCE).

Per-symptom workarounds are in docs/users/incompatibilities.md. Keep your distro's stock kernel installed as a recovery fallback; both coexist and GRUB lists both.

Embracing ABI compatibility, AlmaLinux OS branches out with new features and capabilities while maintaining compatibility with RHEL.

https://x.com/craigaloewen/status/2118409933259735094

https://wiki.cachyos.org/virtualization/wsl/

I have 2 monitors, 2 keyboards, 2 mice, and 1 computer. How can I set it up for shared use?

I know this was possible on X but with Wayland maturing I assume it's moved over.

Several days ago, I tried to update my CachyOS system. And seen the below warning from Pacman itself

Update notice: Kernel 7.3.0-2 has issues with amdgpu particularly causing black screen on AMD dGPUs

At first, I was like gonna do the update, because I don't have an AMD CPU/GPU. Then I went to check on the internet and found lots of issues with both Kernel 7.3 and KDE Plasma 6.8.1. Even affecting NVIDIA GPU.

Not every link I shared is completely relevant to me, but the amount of issues on Kernel 7.3 and KDE Plasma 6.8.1. Even affecting NVIDIA GPU made me hesitant.

Because of this hesitation, I also didn't update Firefox CA-Certificates security update.

Should I update now?

I am running DietPi on a RPI in my network with some docker containers on it.

I recently got the idea to switch off containers when not needed, e.g. during the night, since this will allow my hard drive to switch off and saves a bit of energy.

I do not recall how I found out, but for some reason what I did was to just edit the /etc/crontab file that DietPi has with sudo. Worked like a charm, I had my containers stopped and started just as specified.

But then I wanted to make some changes, change some times, add some other stuff. I did it the same way, edit the /etc/crontab file with sudo. Didn't work, none of my new additions worked.

I searched online and figured out the better way to do this is use the command "crontab -e", edit stuff there, then also check with "crontab -l" right after. That worked, now my new containers are all behaving as they should.

But how do I now get rid of the stuff I defined in /etc/crontab? I removed it all from that file, saved it, restarted the system, nothing removed these, they are somehow persisting. I know they do because I use a different log file for these and that log file still gets generated now. How can I fix this?

Bonus question about log files, how can I make them more useful in terms of information? Right now they just name the command, not even a timestamp or anything.

Thanks!

cross-posted from: https://lemmy.bestiver.se/post/1434334

Comments

Edit: This question can be ignored after waiting 20 minutes. Flatpak finally responded and to told me a flatpak was installed but the flatpak remote was no longer there.

Hello,

Recently Discover stopped being able to do updates because it gets stuck on looking for flatpak updates. So I went to the terminal and used the flatpak update command and there it also gets stuck looking for updates.

So I tried doing it with Sudo and than it started working. So now I am "stuck" using the terminal everytime I want to update. I tried flatpak repair and dnf reinstall flatpak but nothing changed. Upgraded to from Fedora 44 to 45 in the vein hope that would solve but I am out of troubleshooting steps. Would anyone know how to solve this?

Thank you to anyone willing to give me the time of day.

Fen