Upgrade 22 LTS upgrade to Ubuntu 24 LTS failed and I forgot the upgrade didn’t succeed when I rebooted. Unlike NixOS, it doesn’t roll all the changes back when the upgrade is unsuccessful
Upgrade 22 LTS upgrade to Ubuntu 24 LTS failed and I forgot the upgrade didn’t succeed when I rebooted. Unlike NixOS, it doesn’t roll all the changes back when the upgrade is unsuccessful
I’ve broken both Fedora and Ubuntu already, so I had to find better solutions. With NixOS I can roll back to a previous revision easily on boot
Then how come we have more packages than the AUR?
And don’t say it’s because we packaged Python and Haskell stuff since we have more non-unique packages too
Nix, if it’s not obvious from my other posts
I’m okay with this, as long as it’s the one I’m using
There are only two options that fix dependency hell. Nix and Guix
You’re re-inventing the Nix tool which is exactly a script that sets up all the programs and services you want to install
If you improve the installer to the point it can install any combination of software together (including incompatible versions of deps) you end up with NixOS again
The services it installs are systemd, though
No need to make a new distro, just package it into NixOS
Not low at all. After you contribute the maintainer be like “can you rebase it all to one commit”
And then you end up force pushing and ping 4000 people
Or you accidentally close your pull request
It was just as easy to install linux, it came with a graphical installer
When in doubt, put it behind nginx
I never run into this. Mostly because I don’t use grub
I still don’t know what people use to create services other than systemd
If you’re writing bash scripts you’re basically replicating a lot of the functionality of systemd but with larger foot guns
You choose any of the previous configurations at boot; so if the current one doesn’t boot you use an older one
People here running *nix OSes while I run a Nix*OS
I think an immutable system package manager like Nix is perfect to supplement Flatpak.