It’s a customized Arch Linux. Basically manjaro, but with XFS BTRFS file system (as mentioned in the release note )
BTRFS is now the default selected file system instead of XFS. The XFS file system and all others can still be selected by the users and configured.
It used to default to XFS, according to ZDNet
CachyOS gets part of its speed by defaulting to the XFS file system. This is a curious choice for a desktop file system, I’d argue, mostly because XFS is a journaling file system designed to support very large files and ensure the file system’s integrity in the case of system crashes. XFS has been around since the early '90s and has been employed by large servers and storage arrays. - zdnet.com
if you’ve already been exposed to Linux and are looking to jump on board the Arch Linux train, CachyOS is a great option.
It also compiles packages with newer architecture feature support than mainline arch. All of its packages are compiled for x86_64-v3 and x86_64-v4, as compared to the x86_64-v2 of standard arch. This improves performance at the cost of older CPU support
If I’m being honest, So many little distros just come and go that I’ve stopped bothering to learn about any of them until they have enough support that I know the devs aren’t going to just vanish in six months.
I get that. Still if im going to stretch it would be for performance. Features should really be able to be implemented on any os its just a convenience thing at that point.
Not sure if Windows has that but I believe on macOS what happens is the app tries to record the screen, and if it fails macOS blocks the request and opens the security settings to enable the permission, and you have restart the whole application for the permission to take.
What’s done for Wayland is the portal system: applications can use portals to request access to specific things like screen recording, the DE does what it needs to do and it starts feeding the data to the application through the portal. It’s working fairly well, I haven’t had issues with those in a while. The application just requests what it wants, and the DE prompts the user (or auto accept the request) optionally remembering the choice as well.
Generally the solution for X11 problems is to implement a modern API for it in either Wayland or as a portal. Which breaks old stuff, but once updated it works fine.
The main obstacle is getting Gnome to agree to the protocols.
except the portal keeps popping up whenever I touch my controller, and the remember option does not work. It pops up in the foreground anytime I even accidentallytouch my contoller’s touchpad. In home streaming is basically impossible for me rn.
That’s not really a Wayland thing, that’s an (apparently badly implemented) attempt to bridge X11 apps to a permission system they were never written for.
I don’t know how it works on a technical level, but:
On macOS the app can request permission. In case of screen reading, it can’t just ask with a simple allow/deny prompt like with many other permissions (e.g. location), but most app requiring permission usually open the system settings app at the correct page (accessibility > screen readers or something). This page shows a list of all installed applications that specify that they have screen reader capabilities. The user can check a box next to the app’s name to allow screen reading.
On Windows, a “classic” win32 application can essentially see anything running under the same user as itself. It can probably capture windows of applications running as another user (administrator), but afaik it can’t send keystrokes to them. Appx apps generally have a permission system, but I’m not sure how screen readers are handled.
This actually exists, but for a different operating system. The AS400 (aka iSeries) had a command line where programs had a standard way to specify parameters, so that pressing a prompt key (F4) would allow you to build the proper command line by filling a form. I do miss that, pity it doesn’t exist for Linux.
I don’t know about Wayland or MacOS, but In Windows, you can access quite a lot of information via WPF, UWP, WinUI, etc. This is to allow assistive tech to be able to do what they need to do, such as screen readers.
As long as you know how to search for window and control handles, you can read, store, and digest pretty much everything you as a person can see. No questions or elevation of privileges needed.
The caveat is that you’d have to have local access at a minimum.
CachyOS is designed to deliver lightning-fast speeds and stability, ensuring a smooth and enjoyable computing experience every time you use it. Whether you’re a seasoned Linux user or just starting out, CachyOS is the ideal choice for those looking for a powerful, customizable and blazingly fast operating system. - cachyos.org
Appreciate the work they’re doing, but… according to Linus, most changes were in bcachefs (27 commits IIRC) yet this summary mentions nothing about it.
I guess because most people reading it won’t run bcachefs?
Whoa I’m a stickler for getting as much as I can out but even I have .zshenv and some other too hard to figure out things in there. How’d you manage a total wipeout?
zsh is actually easy and it is detailed in the archwiki
You have to set $ZDOTDIR in /etc/zsh/zshenv and iirc that was the only location that required root to edit.
For the rest of stuff, here is how I fix steam for example and you can check the rest of my dotfiles for how I configured zsh and all of that.
Although I haven’t updated them, I still had a .local directory back then, it was 1 week ago that I changed .local for Local and that let to an issue with distrobox which I made a PR fixing it that’s still open though.
It’s empty lol, it’s a directory on tmpfs that i use to build programs and similar stuff to not be hammering my ssd with unnecessary writes.
I have $XDG_CACHE_HOME in tmp as well and I moved the mesa sharer caches to $XDG_STATE_HOME as that’s really the only thing so far I’ve needed to preserve.
You’re not alone in that. I remember when Blender 2.80 was about to release and it was a big mileatone and everybody online was hyping about “Blender 2.8”. I think even Blender themselves went with the flow and changed the marketing.
Using the flatpak is the right answer. Seriously though flatpaks are separate from the base system so this isn’t an issue.
The bigger issue is that you are running tumbleweed on a production critical machine. If you want to run it on a personal machine that isn’t critical that’s fine but for production stick with well tested. Things will break and its best to stick with slow and stable. Think Linux Mint or Debian with Flatpak apps.
linux
Oldest
This magazine is from a federated server and may be incomplete. Browse more on the original instance.