If you’re running unstable system packages, immutability won’t really save your stability.
So don’t complicate it, and just use Debian with nix and home-manager. That way you have a stable base, and you can create a list of bleeding edge packages that should be installed. In any case it should be essentially only docker + whatever can’t be dockerised.
Debian + nix unstable and you get the best of both worlds. Bleeding edge userland, and the system always boots^btw
AFAIK no distro forces you to reboot, but they all require it for some updates to take effect. You can’t reload the kernel while the system is running.
Fedora just makes that clearer to the user by only installing those updates when they’re going to be active - after a reboot. I think it also blocks new system updates until the current set is completely finished.
You can disable offline updates in the system settings, but I think they’re a good idea, especially for the average user.
Sudo apt… is not the problem. Home-manager and a list of packages are so much better and easier to manage. That’s why I’m currently running nix on top of Debian.
The problems start when you want to modify something, or when you want to use tools that expect fhs complience. Then you run into a skill mountain and discover that the documentation is not great.
At least that’s my experience with guixos and nix. I haven’t tried nixos, and if I do, it’ll be only to generate docker images and such.
For a workstation, in most cases, there are simply not enough benefits to deal with the bs that comes with a declarative os.
If you’re doing more complex stuff, maybe spend a few days learning the basics of bash
How is the rust replacement?
fd > find. It’s a lot faster, and I find the syntax to be better.
Nice, thanks
That’s a really hacky method and should not be in the manual tbh.
That’s why I’m asking, it seemed really odd.
home-manager
Thanks, this makes a lot more sense. Any good resources besides the wiki? Is there a way to break down home.packages into smaller chunks for modularity?
As for flakes: No, you don’t require them to do any of this. They solve an entirely different problem.
So they’re just to ensure reproducibility?
Belta lik pashang! Keting dzemang to vedi du, paxoniseki?
Na kopeng, mi pensa im say you a welwala…
If stability is a spectrum, you’ve got to admit that Arch is on one end and Debian on the other.
I ran it on multiple devices for like 3 years. It breaks. Updates are stressful, especially if you have horrible internet in a foreign country.
Arch has many benefits, but it’s dishonest to call it stable. No amount of relativism will change that.
If you don’t do anything crazy, it will be stable, exactly like any other distro
Tell me you haven’t used a stable distro without telling me you haven’t used a stable distro.
Do you know why Debian, a stable distro, releases noncritical updates every ~2 years? Because they test their packages and make sure grub doesn’t release a faulty update and leave your machine in an unbootable state.
Slapping an installation wizard on top of arch doesn’t make it a different distro…
Check out if KDE connect works for you. You can launch any scripts you make, and control the input from your phone.
If it does, any stable distro like Debian should work fine for that purpose.
Auto launch depends on the DE
OP posts about how they’re annoyed with low effort “I deleted windows” posts, makes a low effort “recommend me a wm” post. You can’t make this shit up…
Try them out, find out what you like, ask specific questions when you get stuck on something.
Ever heard of Mojang?
The first time I installed Fedora after like a decade I updated to new minor version -> sudo reboot because I was already in the terminal -> reinstalled because it wouldn’t boot anymore
Regarding Vivaldi: Why isn’t Vivaldi browser open-source?
To save anyone else from losing time on this bullshit:
They’re scared of their FOSS fork being forked. The rest of the article is just an attempt to make them sympathetic, and muddy the waters. That’s why GPL > BSD
A new project based on our code might implement features that are fundamentally in opposition to our ethics (e.g., damaging to privacy, human rights or to the environment). Even though we would not be associated with the project in any way, it can deeply affect how people see Vivaldi (and how we see ourselves), damaging a reputation we have taken pains to earn.
Fuck off
You never saw an IRC chatroom archive?