- Joined
- Dec 13, 2022
Jesus Cornelius Christ! Is there no end to that gay muppet's retardation?Here's a typical resource, with a foreword by, well, you'll never guess:
The Linux Thread - The Autist's OS of Choice
- Thread starter tehpope
- Start date
-
🐕 I am attempting to get the site runnning as fast as possible. If you are experiencing slow page load times, please report it.
std::string
kiwifarms.net
- Joined
- May 17, 2018
Going through the unixsocks Lemmy, arch arch arch ubuntu arch arch fedora arch arch popOS arch arch openBSD (is that you catler) arch arch
I don't see any Void installs yet so probably that.
- Joined
- Mar 4, 2019
- Joined
- Feb 21, 2018
Serious answer, but I'd say Debian, not because I like it if you go into linux no experience it's fucking annoying as hell to use, but it's the distro everyone else copies and I mean debian is pretty solid.
Everything else is just a meme distro or this "beginner-friendly" piece of shit that's literally worse than Debian in every way. Linux Mint, Ubuntu, Manjaro, Gentoo, Elementary OS, Fedora, fuck all these bitches.
- Joined
- Mar 30, 2023
Cinnamon is the very best DE, But I concede Mint makes a lot of changes to make it easier for normies to use. Second best is KDE, but if you're using a fast moving DE on a slow moving Distro you're an idiot.
- Joined
- Aug 15, 2022
QubesOS might be getting proper GPU virtualization support soon( = within the next year or so) so I'm expecting that to rapidly become the new shilled (kind of) distro that all the trannies use once support is in.
The NixOS documentation is a glorified API reference, their graphical installer used to save the plaintext encryption key on the unencrypted partition and I don't remember seeing any news about it on the usual channels and you will be in a lot of pain trying to figure out how to install something the idiomatic way. Also you'll be running into weird Nix specific problems like scripts not working because they assume bash is installed at /bin/bash.
If you are willing enough to spend time, are a programmer and already know your way around Linux I might consider giving it a look but the learning curve is really bad.
p.s. QubesOS entirely supports the workflow I want, but QubesOS needs a really specific hardware setup to work nicely.
I currently use NixOS. I wouldn't switch to anything else as it is the only thing that can easily handle the workflow and setup I want but I would never ever recommend it to someone else.
The NixOS documentation is a glorified API reference, their graphical installer used to save the plaintext encryption key on the unencrypted partition and I don't remember seeing any news about it on the usual channels and you will be in a lot of pain trying to figure out how to install something the idiomatic way. Also you'll be running into weird Nix specific problems like scripts not working because they assume bash is installed at /bin/bash.
If you are willing enough to spend time, are a programmer and already know your way around Linux I might consider giving it a look but the learning curve is really bad.
p.s. QubesOS entirely supports the workflow I want, but QubesOS needs a really specific hardware setup to work nicely.
- Joined
- Jul 4, 2022
Ubuntu uses dash as /bin/sh, same issue there. You can look for the checkbashisms program to check your scripts, it is part of the debian devscripts package that might also be packaged separately for your distro.
I use gentoo, so dev-util/checkbashisms.
Belisarius Cawl
kiwifarms.net
- Joined
- Mar 16, 2024
I'll bite. I've been using Linux since middle school, have a GitHub (no self-dox), experience with SBCs, blah-blah-blah. Why should I ditch Mint for Debian? The former is working fine and very rarely gets in my way.
- Joined
- Jan 5, 2015
Exactly, you don't have to ditch Mint for Debian. My personal biases towards using Debian over Mint (specifically Linux Mint Debian Edition) come from wanting to stick to the vanilla upstream distributions. But, that's just my bias.
- Joined
- Nov 15, 2021
Rocky Linux. Gregory Kurtzer is cool.
- Joined
- Sep 16, 2018
- Joined
- Mar 4, 2019
I think the issue here is that the scripts have /bin/bash hardcoded in the shebang, because it's customarily installed there. IIRC, in Nix it's actually something like /run/current-system/sw/bin/bash (which you can obviously also get using #!/bin/env bash, but people tend not to use that because they're lazy) and, I think, symlinked to /usr/bin/bash.
- Joined
- Jul 4, 2022
Yeah, having bash in the shebang is fine, you are after all declaring your script to be using bash extensions, rather than assuming /bin/sh understands bash constructs.
I'm more inclined to stick with the FHS standard, with separate /bin and /usr/bin, and that's how I like it. Even env itself is getting into trouble today since it is customarily put it in /usr/bin/env, not /bin/env, not a really a problem for distros that just dump everything into /bin and link /usr/bin to it.
- Joined
- Mar 4, 2019
Now that red hat/poettering have had their way, everyone is going to start dumping everything in /usr/bin and symlink /bin to that instead.
std::string
kiwifarms.net
- Joined
- May 17, 2018
If you're the type of person that files bug reports then it's useful to be close to upstream. Ubuntu (and Mint by extension) can get pretty fucking weird sometimes in the packages they decide to pull from Debian and now you're not really sure if something is an Ubuntu bug or a Debian bug.
msttcorefonts-installer for example had a bug that lingered in Ubuntu for years after it was fixed in Debian and they just...never fucking pulled the newer version.
Otherwise who cares.
- Joined
- Dec 19, 2022
- Joined
- Aug 17, 2022
This is one Poetteringism I agree with.
The differences between /bin, /usr/bin, /sbin, and /usr/sbin were always pretty arbitrary.
- Joined
- Nov 21, 2020
Not really. /bin and /sbin were stuff needed to boot and were on the root drive/partition.
/usr was less critical stuff and would be available once the /usr partition was mounted.
/sbin was supposed to be critical statically linked stuff that would be usable in case you blew up the dynamic linker/libc/whatever. Obviously that's sort of morphed into "stuff for the superuser"
We didn't always have 4T boot drives.
My lawn something something.
- Joined
- Mar 4, 2019
In isolation, probably nothing. The fact that it's red hat throwing its weight around so poettering can set up another part of his total subsumation of Linux into systemd is the issue. It's a necessary step to implement signed, read only root images, which he wants because it will make his laptop boot ever so slightly faster (and because it ties into his current plan for systemd to control the entire boot process and system installation), and Rh wants because it grants them more control over their customers.
Last edited: