The Linux Thread - The Autist's OS of Choice

  • Want to keep track of this thread?
    Accounts can bookmark posts, watch threads for updates, and jump back to where you stopped reading.
    Create account
That being the repos it uses.
And the thing with systemd and everything it implies is, that most software actually works perfectly fine without it. The only major contender is DBus. I had some minor nightmares on Artix and finding an Optimus solution that actually worked with it as a result (there's like 5 different ways to run Optimus, each with its own programs), and the Artix repo is effectively just the Arch repo except with patches on top to mitigate around (mostly) DBus and init. It still uses the Arch universe, it simply applies an overlay over the Arch repository instead of simply adding its own besides it (which it still does for Artix-only packages, like the artix keyring).

There could possibly be a bigger split in repositories further down the line if systemd gets more pozzed or Artix becomes more gung-ho against Wayland (how I wish there was a KDE Plasma fork without any of this Wayland shit, and there very likely will be by 2027 when X11 loses support), but for now Artix remains a mildly modded base Arch. You can Artixify an Arch-based installation, though mileage may vary depending on what distribution and desktop environment you're running.
 
As a linux newb, what is the issue with Wayland?
Read the thread, it goes over it at least ten times. My issue with it being automatically bundled with KDE right now is that I don't want it and it's completely irrelevant when I'm using X11. That doesn't even concern Wayland itself, it's just bad development practice to bundle prerequisites that have nothing to do with your usecase. In the future it'll also be the fact that KDE will no longer support X11 at all, but it's got two-ish more years.

TL;DR: Wayland is fundamentally flawed and used by trannies as a cudgel much like pronouns or Rust and it's used as a means of corporate takeover over another software ecosystem by Red Hat and Canonical. The proponents would remind you that it's the new thing and therefore inherently better (it isn't), that it's more secure than X.Org (it isn't, and X.Org would be more secure if it was allowed to develop) and that it can run newer graphics features such as multiple monitors (lie through omission) or HDR (it can, so could X.Org if it wasn't artificially held back). If you want more, go look at
This fundamental difference between x11 and wayland is called "mechanism over policy" or "mechanism not policy" (for x11) and "policy over mechanism" (for wayland). ...
Xlibre won't be packaged in the big distros until it's out of beta, and any distro with stake in hating on X11 (eg Fedora) won't ship it unless they're forced to. I would expect the BSD people to flock to this project since they rely entirely on X11, so it might not take too long to mature.
And look up XLibre in this thread (and the response it had, despite essentially being a continuation of X11 development and little more).
 
Here is a Wayland-friendly evaluation of Wayland in 2026 from a power-user perspective, the author of the tiling X window manager i3. https://michael.stapelberg.ch/posts/2026-01-04-wayland-sI'm glad that way-in-2026/

He doesn't hold their feet to the fire or anything and focuses on the tech, but Wayland is still not ready for him to switch.
I thought it was weird how nobody mentioned the mouse movement being weird in wayland compositors before (compared to the xorg server). I see this issue in every wayland compositor. It feels sluggish, even if you disable mouse acceleration. It feels like mouse acceleration is still enabled or something like that and it also feels like there is added latency. There isn't a direct 1 to 1 mapping of the mouse movement to cursor position. I notice that immediately but nobody else talks about it except for that post.
I run X11 without a compositor, games without vsync and I use xterm which has the lower latency of all terminals and oled 144hz for lower latency as well. I guess everybody else must be running latency inducing shit and are used to high latency.
 
Rockchip for the win. I have an old RK322x box and that little piece of shit Android box that I bought for $3 is insanely capable when you toss Armbian on it. It might not outperform modern ARM SBCs, but you treat it right and it's got no problem with 1080p60. I'm glad to read that the heritage continues. Rockchip appears to pay attention to what us hackers are doing with its hardware and helps out here and there.
Unfortunately RK locked down their new chips. They got double raped by a new chinese gov requirement (bootloaders must be "secure" and cannot be edited by non-oems without license, which is an extreme PITA, you have to take a 100 question test in 30 mins and only miss 4, bend over and prove you're a company in IT, and you can only have 10 unlocks a year), and the US goverment threatened to add them to the OFAC sanctioned list over the RFAF using them in the war SMO.
My understanding is that they will no longer provide any documentation or SDK to non-approved parties, hence the sudden allwinner interests in some Chinese OEM/ODMs
Weird to me. From like 2000 to 2010, Gigabyte was my preferred mainboard. I had a special DualBIOS rig specially hardware modded to run CoreBoot and trigger the DualBIOS refresh if I bricked it. I've only built two PCs since then, AsRock and ASUS.
Asrock and Asus are one, and nothing is worse than ECS or Biostar. I had a Bioshart board randomly just fail out a DIMM slot exactly 2 days after warranty ended, and I had an ECS board play wackamole with which SATA port was working every few months.
state actors
Unfortunately the only recent (within 5 years) x86_64 CPU that's powerful and doesn't contain IME/PSP are not available to the consumer... On the second hand market in China maybe, but you risk being prosecuted for interacting with OFAC's SPL.


Anyways, I'm glad I can split tunnel with linux... Trying to get across the national firewall/ self host behind a triple-quadruple CG-NAT really sucks, especially when you're ip4 only and VPS is not easily accessible to consumers.
 
Last edited:
Never go full system D
Can someone tell me what the issue is with systemd? I haven't had terribly many issues with it once I learned what its purpose is. (When I installed Arch for the first time, I kept putting shit into my .xinitrc file)

Look at all these amateurs who don't just run as UID 0 all the time.
CTRL+ALT+Fx => login: root
simple as.

STOP this niggerlicious bullshit IMMEDIATELY and use SECURE MOTHERFUCKING SHELL (that's SSH if you really are a nigger and not just pretending). THIS is what it's THERE FOR, so you're NOT using some horrendous scarcely-used SECURITY RISK in its place. There is NO EXCUSE. Literally ANY CONNECTIVITY PROBLEM that you have can be resolved using SSH in order to connect via SSH securely.
YOU WILL FUCKING USE NATIVE TECHNOLOGIES AND YOU WILL LIKE IT. NONE OF THIS STUPID BULLSHIT WRAPPER NONSENSE. COMPUTERS ARE MADE WITH NATIVE TECHNOLOGIES IN MIND. WE USE THE IP, FTP, SSH. NONE OF THIS ELECTRON GARBAGE. OPEN YOUR FUCKING TERMINAL, TYPE IN SSH, AND YOU'RE OFF, HOW FUCKING EASY WAS THAT COMPARED TO GIT CLONE HTTPS://FAGGOT.GITHUB.ORG/FAGGOTCODING/RETARDED-SSH-WRAPPER, CD RETARDED-SSH-WRAPPER, MKDIR BUILD, CD BUILD, MAKE, MAKE INSTALL?? YOU LOOK LIKE A RETARDED MONKEY WRITING ALL THAT, ONLY FOR IT TO FAIL MIRACULOUSLY BECAUSE YOU DIDN'T READ THE DOCUMENTATION RIGHT OR YOU'RE ON THE WRONG DISTRO BECAUSE FUCK YOU, I ONLY ALLOW ARCH BASED DISTRO'S TO USE MY SHITTY VIBECODED NONSENSE. BY THE WAY, YOU NEED TO INSTALL 500 DIFFERENT FUCKING DEPENDENCIES BECAUSE MY MONKEY BRAIN CAN'T MAKE ANYTHING NATIVELY, FUCK YOU. DEPENDENCY PROBLEM? FUCK YOU, I DIDN'T MAKE IT, THAT'S ON YOU.

Bring back native FTP in browsers...
 
Can someone tell me what the issue is with systemd? I haven't had terribly many issues with it once I learned what its purpose is
Single point of failure for basically everything on your OS. init systems used to init, not manage every service while your device exists. For most, not really something they think about, but modularization was just the name of the game for *nix for the longest time (and still is on *BSD)
 
Can someone tell me what the issue is with systemd? I haven't had terribly many issues with it once I learned what its purpose is.
mango_reseller gives a good argument. Ideally, there should be no difference between init systems. The problem is that systemd practically ends up as bloatware because the project is trying to do literally everything.

I bit the bullet early and used systemd-networkd to configure my network. This functionality is better than NetworkManager and other popular alternatives. I use systemd-resolved as well, which requires a restart every so often. My current Gentoo has no fstab because I do it all with .mount units.

Systemd is not a big deal to me because this PC is running Chrome so it's used to wasteful design. But the more resource constrained the system, the less you want systemd. This is why Alpine has traditionally used the BusyBox init, which has its own quirks. And if you want fast, small, and elite, the clear choice is s6.
 
The problem is that systemd practically ends up as bloatware because the project is trying to do literally everything.
Is it not just an init system? What does it do beyond just initializing and keeping services that I've set up running?

systemd-networkd to configure my network.
Would iwd be part of systemd or is that a different thing?
 
Is it not just an init system? What does it do beyond just initializing and keeping services that I've set up running?
systemd-devours-all.gif
 
What does it do beyond just initializing and keeping services that I've set up running?
cgroups, sandboxing/supervision, logging, hooks into udev, manages login/time/locale/DNS(???), tries to replace cron, launches services in parallel instead of sequentially during init (this is my personal autistic gripe you can ignore this one fully)
 
Good, because wifi has been the real hold-back for BSD for a while now.
Since the early 2000s. It's the only damn reason I still live with Linux these days. I don't *like* the Linux ecosystem, and if SmartOS was more 2.6 than the fucktarded 9, I'd probably run that, provided it had support (Someone was porting core drivers to OpenSolaris over a decade ago, but that's sailed as well).
 
Read the thread, it goes over it at least 100 times
FTFY
Would iwd be part of systemd or is that a different thing?
Its a separate thing. It does use dbus for some of the backend communication. But that's the same for a things like network manager. And dbus isn't strictly tied into systemd. In the sense that you need systemd to use dbus. (Besides dbus-broker, which is a second implementation of the dbus protocol, that tries to be more efficient, that does need systemd)
 
Posting this here because I think it's really cool and don't know where else would appreciate it.


Someone found a magnetic tape copy of Unix v4, which had only twenty actual copies produced, in some storage closet at the University of Utah where stuff was being gotten rid of. Nearly lost media. It's also been made available online in various places for programmers to peruse.
 
The further we stray away from God...or, make sure to check what license your software is under:


It is mildly humorous I'm unable to use the media tag in the Linux thread to point to a video on Odysee.
 
Back
Top Bottom