NixOS mentioned 👀👀👀❄️
You seem like an expert.
I want the following software:
- kde x11
- flatpak
- iscsi
- qemu/kvm
- timeshift
- kup
Will I have any issues when using nixos with either installion or documentation?
I mean apt works for me fine. But even mint is somehow having issues with the native steam binary. The flatpak runs though…
All of these tools have options or packages available in nixpkgs, so they’ll work easily
I don’t think you’ll have many problems with those packages unless they’re not on nixpkgs (if that’s the case you’ll have to make the package yourself) You also have to consider that NixOS works differently than most Linux distros: the filesystem is different so installing apps through any other means other than nix will be difficult if not compromising reproducibility of the system (the main promise of NixOS) I’m not sure how compatible flatpak is with NixOS too. KDE does work well though. I overall wouldn’t recommend this OS to anyone who isn’t willing to fight the terminal and read the docs furiously (for around 2 days, after that you’ll stabilize and be grateful you did it). NixOS is a wonderful operating system. Works marvels.
Sounds promising xD. Just like my totally stable debian install that suddenly decided to reboot after 60 seconds. (probably my fault but I can’t figure out what is actually the problem.)
Good luck if you actually try it! Make sure there’s nothing important you’ll have to do with your computer in at least 2 days. That’s enough time to get everything ready and working.
I can still Gentoo Linux as an alternative if you’re willing to take a step towards better package management but don’t want to deal with all of the NixOS baggage.
Nope those should all work fine
deleted by creator
Same; especially NixOS 😸❄️
#linux #bludgeontheinfidels
I prefer .deb for me
Imperative package management detected. Deploying rocks.
What exactly is imperative and why does it suck pls and ty
So let’s say you do a clean install of a Linux distro. You then have to tell the system you want to install this web browser, change this setting, open these firewall ports, enable SSH, etc.
Telling the fresh system to do each of those things is imperative.
In NixOS, you write one big config file (you can split it up) that declares all the packages, settings, ports, etc. Then you run a command that tells the system “This is the end-state I want you to be in. Do whatever you need to do to end up in that state”. That’s declarative.
It means you can set up a new box by just pointing at at your config and telling it to build it. That means, you don’t have to remember what you did to solve that problem that one time – you’ve put it into your configuration and now it’s solved forever.
Edit to add: the imperative method isn’t “bad” necessarily – we’re mostly just goofing around.
Holy shit that’s cool! Reminds me of a good docker compose yml for a bunch of containers. Thanks for the explanation. Apparently I’m installing nixos wtf
Docker-compose is also declarative, so you’re right on the money!
Have fun and ask questions – it can be a bit overwhelming at first, but when it clicks, it clicks.
deleted by creator
Drop tha rocks on tha Packagelowdaaaaa! Make dem Imperatives pay for all dem impuretees!
This actually happened to me btw. I am now in the afterlife and my soul has been cursed to configure NixOS & Nix Home Manager for all eternity
emerge for life!
