The Linux Thread - The Autist's OS of Choice

Ok so this was actually debunked in the 80s
I'll point you to a lecture I think everyone needs to watch about early Unix development and why stallman had to do what he did
Gpl didn't come into existence for no reason, people were either using proprietary licenses like Unix or permissive licenses which were then called copy-center as opposed to copyleft or copyright
The problem with this license people found was nobody wanted to collaborate on projects when businesses want proprietary software licenses. So the Gpl actually did prevent this and companies weren't just flippantly violating Gpl every time they needed gpled code, but they were doing that with permissive licensed software like bsd, and that has been a major problem for them that affects them to this day.
I am not talking directly about OS forks. I am talking about how in spirit it is subverted.

I am talking about what really happens today in the era where much of the software built today is web-based and built on AWS, GCP, Azure and the like.

Google isn't violating GPL if they run their own GPL fork internally on their servers. However, they can serve their own proprietary web applications that lock your data into their platform on that OS. So the freedoms of the GPL are subverted. How is the GPL protecting anyone's freedoms then? It isn't. More people probably use Google products than Microsoft products at this point, and their whole web presence is probably tied to their Google account; their office docs, their files, etc. are all in Google's proprietary cloud.

Furthermore, there are whole proprietary development platforms where the whole development model is to tie you into their platform. They do this by making you dependent on the design, data and how the data structures are stored. Much like web apps like Google Maps.

Jaron Lanier wrote a lot about how the design of systems is more important than the implementation using MIDI as an example in "You Are Not a Gadget" nearly 20 years ago.

The whole GPL vs BSD licence debate is completely moot at this point because large companies lock you into the data and the design of their systems.

It is another example of people fighting a war that was lost at this point over a decade ago.
 
Última edición:
I checked out plasma-bigscreen today on my HTPC. It sucks ass and this is the supposedly stable version that is in the repositories yet it managed to crash. By default it doesn't support controller navigation you have to go back to desktop settings, enable a janky setting that allows using your controller as a mouse and keyboard.

I hope it improves since KODI is on its last legs and steam big picture isn't the gretest either since there's no way to configure it so you don't have to dig through the library to get to jellyfin. For now I'm back to using Batocera.
Have you checked out flex-launcher? It's my htpc desktop homescreen. Have quick launchers for Kodi, VacuumTube, Moonlight-QT, and Power. Does everything I need it to do. I just run it with Openbox and it just werks.

Plasma-bigscreen got the shaft once KDE 6 got pushed everywhere. Switched to flex-launcer and openbox ever since and I've been happy.
 
The setup-alpine install script is generally good, although it will do things like write your wpa_supplicant configuration for your initial network twice into the config file (which doesn't cause any problems) if you Ctrl-C halfway through.
OK, I have been loving using Alpine. Getting five hour battery life out of a old Chromebook that easily charges from a phone charger, hell, it will trickle charge overnight from USB 5V. This feels even better than using ChromeOS.

The one sticking point I had initially had was with networking on a device where I wanted to be able to connect to wireless networks without hassle. There are instructions on the Alpine wiki for switching to networkmanager, but the way that works has never really rubbed me right. Linux networking works so well if you just avoid that sort of shit, I have been simultaneously connected to four different customer VPNs at once on Linux before, something that would NEVER work with official clients on Windows.

Well, I initially tried connman but encountered problems getting that working (in that it was connecting to wireless networks and then immediately disconnecting for no reason and doing that repeatedly until the wifi router flagged it as malicious activity). I will try again, as connman does make it easy to do easy USB and Bluetooth tethering, which are semi-useful. BUT 99.9% of the time you don't need that shit. As it turns out, wpa_supplicant is not just a tool that everything else uses to connect to wireless networks. As long as wpa_supplicant is running as a daemon and wpa_supplicant.conf has something like the following up the top:
Código:
ctrl_interface=DIR=/var/run/wpa_supplicant GROUP=netdev
update_config=1
then a tool designed to interact with its sockets interface (not homoBUS) like the nice simple wpa_gui app can just connect to it, view status information, and add and connect to new networks (i.e. 99.9% of the 'networking setup' that anyone needs to do which can't be handled by configuring a single file once for your ethernet interface).
 
I have news: the systemd timer I set for my home server executed and finished without issue! Timer was specifically to execute a script that updates all my system packages and my Docker Compose services every Wednesday at midnight.

For the record: I know that the correct solution would be to skip systemd timers wholesale and stick with cron jobs. I specifically avoided the cron job route for two reasons:

#1) I repurposed my old gaming PC into a home server explicitly for the sake of learning home server Linux stuff. I wouldn't learn anything new about cron jobs because I've already set up cron jobs on my old Linux Mint install that I had on my old gaming PC before purging the drives and turning it into a home server.

#2) While I loathe Poetterware modernity and "know" of all the reasons why systemd is awful (re: functionally monolithic despite allegedly being modular, ecosystem consolidation, aggressive feature and scope creep that deliberately breaks POSIX assumptions, bugs and CVEs for one part of systemd completely unrelated to what you're doing but it somehow affects you anyway, etc etc), that's all within a "home user dealing with systemd" mental model. systemd is immensely aggravating for seasoned sysadmins, and I wanna learn the server side of why systemd sucks. What's that old saying? Learn about what you hate so you can be well-informed with your hatred?

As it stands, the systemd timer is doing its job without incident and my uptime's been stupidly long especially with Ubuntu Pro's livepatch service enabled. I have no reason to whinge quite yet... but I am open to the moment when I finally have a reason to commence the kvetching.
 
Última edición:
I'm crying with despair because he's using, and may Allah forgive me for uttering this next word... PLASMA. Okay, enough hyperbole. He's in the same boat you're in where Plasma was kinda sorta janky at first but it was able to be tamed and made functional with minimal headache. Frustration yes, but no headache. I personally feel the wound in my ego over him flouting X11 supremacy for Wayland modernity, doubly so for flouting Cinnamon and embracing modern Plasma 6 degenerate lunacy. My only comfort was that he took one look at GNOME Shell and said "Fuck no, this shit looks gay."
Give him time, he'll want to fuck with more interesting DEs and embrace the Holy Command Line, he just wants at least one system that Just Werks to get things done on. A lot of why I've stuck to Fedora and Plasma on my desktop after ripping off the Windows bandaid is because I want my desktop to Just Werk while not waiting a decade for feature updates on software, and if it's going to be corposlop I want the better variety (Red Hat opposed to Canonical). My decrepit old laptop is where I can distro hop and install stupid bullshit I can blow away because I don't keep anything important on there.
 
Since the topic of the *BSDs has come up again, I must once again remind the thread that while Linux is full of woke bullshit because of troons, BSD is full of woke bullshit because it is run by fat, middle-aged anglo eunuchs and that is probably worse because they'll dedicate talks entirely to their ebin chud-owning exploits:
If I'm not mistaken, the openbsd people aren't too trooned out.

I mean it's open source/tech (in general) so I'm sure there are some trannies somewhere around the project.
 
If I'm not mistaken, the openbsd people aren't too trooned out.
Unlikely. Most of the dudes I've encountered that used OpenBSD would turn up at Real Ale Festivals.
I mean it's open source/tech (in general) so I'm sure there are some trannies somewhere around the project.
OpenBSD IIRC didn't want to implement the CoC(k) and other such bullshit.
Most of the people in OpenBSD land are quite level-headed.

Generally the lunatics get the most attention because they make the most noise.
 
Paraphrasing what he told me about his experiences with the AUR: "Any random douchebag can host their own build scripts on the AUR, I'm a complete and total noob who can't read this gibberish, and frontier model token limits are infuriating to deal with, Fuck the AUR, I'm just rolling with Pacman, Flatpaks, and nothing else."
Any random douchebag can contribute to OSS so he should using Linux entirely.
 
Not using the AUR because you can get a bad package is like just using the Microsoft Store because you can download a bad .exe

Common sense and reading the PKGBUILD is all you need, and the AUR page shows comments and everything you need to audit the package. If you want to minimize exposure just delay updates on AUR packages until after you read the updates.
 
Have you checked out flex-launcher? It's my htpc desktop homescreen. Have quick launchers for Kodi, VacuumTube, Moonlight-QT, and Power. Does everything I need it to do. I just run it with Openbox and it just werks.

Plasma-bigscreen got the shaft once KDE 6 got pushed everywhere. Switched to flex-launcer and openbox ever since and I've been happy.
it looks like the developer for flex-launcher is workign on a more advanced version, called big-launcher
Not using the AUR because you can get a bad package is like just using the Microsoft Store because you can download a bad .exe

Common sense and reading the PKGBUILD is all you need, and the AUR page shows comments and everything you need to audit the package. If you want to minimize exposure just delay updates on AUR packages until after you read the updates.
I’ve been trying to teach nana common sense for twenty years but she still flips out when Firefox changes its logo because she thinks a virus has deleted her internet
 
Not using the AUR because you can get a bad package is like just using the Microsoft Store because you can download a bad .exe

Common sense and reading the PKGBUILD is all you need, and the AUR page shows comments and everything you need to audit the package. If you want to minimize exposure just delay updates on AUR packages until after you read the updates.
Not being a fucking idiot and installing anything with yay - just how you wouldn't install a fucking .exe from fasebook.com. It's so demoralizing that you're just allowed to be an idiot and people who know better have to suffer. People that complain that "The AUR got compromised" are the same niggers who would call up Rasjnikav from Microsoft tech support because they have installed vairoos.
 
What's the point of an atomic distro for the average user?
"All these newgen Linux-posers filling up my feed,
they like proprietary software and KDE."

1783532241403.png

"Bazzite is an all-around distro for all-around users" kek.
 
RTFM, DankPods, it's not that difficult. Stop using Bazzite, nigger, you are a dumb moron.

fuck_you_wade_seriously.mp4

Then when anyone DOES give normies advice, they shit out rebuffs along the lines of "well then what's the point of[...], many are saying this, this is generally agreed upon (without citation), it's not that deep[...]". Act like a difficult retard, get talked down to like one.
 
Atrás
Top Abajo