I was really hoping this would be American Sign Language linux. All you’d need to do is develop a writing system with hand shape, face shape, location, and motion characters then build an entire operating system around it…
I exhaled from my nose, but at the end this joke doesn’t seem fair.
I’ve been running Artix for years, because I wanted to try it out for fun and now am too lazy to switch, cause most things just work. I update weekly just fine and sometimes I have to write an init file for openrc.
The biggest pain point was when I was trying to debug an issue which crashed KDE and realised that there is no journalctl ofc.
Like with most technology, init should be based on use-case.
Some setups are not made for quick reboots and that’s ok. When all your container does is run ddclient you might find that even cron can work just as well as systemd.timers
Heck even moving it to another partition isn’t really a re-install as it’ll happily create the exact 1:1 same system based on nothing but the configuration file, change nothing but the id of the root partition (you’ll have to move over /home manually, though).
And if you mess up your configuration either roll back instantly, or fix it in situ in case you already gc’ed the old stuff. It’s practically impossible to get it into a non-booting state without literally ripping out the disk it’s installed on (or, well, Windows messing up the bootloader or something). Even if you run unstable on the whole system every single commit on that branch is tested to not break boot and rollback.
Oh just one thing: Don’t skimp on the size of your EFI partition. 100M are definitely borderline when you have both NixOS and Windows booting from it, those kernels and initrds have gotten quite large over the years and you’ll need to be able to fit, bare minimum, two of both.
Just moved from Endeavor to NixOS. It’s a huge learning curve and takes a while to build your config or flakes, but damn does it feels nice to just roll back if you mess up over re-installing.
Because I made it unbootable by doing something dumb or one of its tools was horribly broken and made my system unbootable? :) This was years ago, though, it’s probably more stable these days.
You probably don’t have much on that system and/or you have a lot of discipline…
I did reinstall it after max 1 1/2 years (Arch btw.), either because of breakage, or weird behavior, or it was a chaotic dumpster fire.
At some point I discovered NixOS and was sold (and am still sold after 3 1/2 years using it). But it has a steep learning curve, though it certainly got better over that time.
He’s good in doing so, compared to the old guy with a neckbeared using his fingers to count to one. Oh, do you know his name? It’s Microsoft, named after his dick xD
I want to see Debain users and Fedora users faces when they noticd they don’t have access the AUR or PKGBUILDs.
I want to see them running sudo make install to install stuff from git.
Also reading the Arch wiki for so long is something new arch users probably do. I installed arch for tens of times btw and for me the system already runs with the installation media.
I am very sure no Debian or Fedora user is done after the installer finishes. Then comes the tricky part of the setup. The one that takes days. Adding ppas and making stuff work fedora doesn’t package.
This process starts with arch right away. From the moment i chroot into my installation.
I actively maintain ~9 computers in my house running arch. Many of them have dual boot arch. E.g. one arch for work, one arch for everything else. One arch for music production, one arch for everything rlse. I run arch on my webserver. I run arch on my home sevrer. I run arch on my wifes gaming desktop. I run arch on my wifes laptop. I run arch on my kids netbook. i run arch on rasberry pi.
I am always a bit disapointed when I install debian every couple of years.
Like, after 1.5 hours, I am like “what, that was all?” Most of the stuff I need is installed by default, just add Jetbrains toolbox, install my ide, add a few more packages and git clone my current project.
I know a little linux, but obviously I’m still learning. I’ve picked up everything I know on my own, for the most part - internet guides from the linux community tend to be pretty solid, and I know enough to not totally FUBAR my system.
Is there a listing of standard linux directories and what they’re for? Lite /etc, things like that. Because I seem to find bits of different stuff in a variety of directories.
I’ve recently moved to linux on my gaming rig, which is my daily driver - that being said, it is mainly for gaming. Anything can surf the web or play videos and shit, for the most part.
Fixing things in place in windows is a nightmare for the most part. Users are dumb fucks. Power users and admins are mostly the same. With a consequence that when you have a real obscure problem, there is no documentation by anyone anywhere. Certainly not microsoft with their posh ‘documentation’ that really doesn’t explain a thing.
Doesn’t really help either that they change things with every minor update. And their basic structure is one big mess of mixed environments and totally diffferent visions. Let’s not even talk about their scripting language where nothing has standard behaviour.
Ffs I hate microsoft. I’ve been managing that piece of shit for way too long.
Last September I installed Debian 12 in my laptop with an encrypted LVM. Then I tried to add a secondary SSD, also as an encrypted volume, by following some random tutorial I found (spare me, it was my first time fiddling around with an encrypted installation). The next thing I remember is that I was in an initramfs shell trying to fix the boot process 😅🤣. Since I was running low on patience (and it was like 3 AM) I simply decided to nuke the install and start again. Eventually I was able to configure the SSD correctly, but this event reminded me how easily is to brick your system if you’re not careful enough. Fun times.
I’ve always loved Linux, even when it was kicking my ass. I can’t imagine approaching it with the attitude “Ugh, I have to force myself to use this thing, and I know that it’s going to frustrate me”.
That sort of thing is a self-fulfilling prophecy, because everybody has cognitive biases. Since you expect it to be frustrating, you’re going to remember all the times that it is and forget the times when it isn’t.
What kind of things do you need to do? For software development my experience is that it’s just install and you can start working. Maybe one tutorial to get kubernetes running locally.
Get on it. If you can manage to daily drive it for a few months I think you’ll learn a lot. When I jumped ship I only knew basic commands like cd and ls.
While RHEL and Fedora are siblings we can’t mix em’ like that. At least I haven’t ever seen a server with Fedora pre-installed, or anyone offering support on a Fedora server…
We have a piece of fancy and expensive radio equipment in the office, the control part is a Fedora server, with precompiled binaries that run that piece of hardware. Every system library has frozen version, if you upgrade the OS the whole system stops working, and you just reinstall the disk image from the archive, and by reinstall I mean use dd to overwrite the hard drive partition from a supplied DVD.
Huh, at least it’s Linux I guess? I’ve seen plenty Windows XP hanging around controlling expensive medical equipment and one time even a system were the control part was Windows 3.1. Air gapped not for security but because the server didn’t have a NIC.
linuxmemes
Active
This magazine is from a federated server and may be incomplete. Browse more on the original instance.