I’m a new user, well not yet because I could not get discover to work. It said I needed to do something about a back channel or something. How is it possible for Discover to not be enabled in KDE?
Exact message was; NixOS is not configured for installing apps through Discover-only app add-ons.
To use Discover for apps, install your preferred module on the Settings page, under Missing Backends.
Add:
{
services.flatpak.enable = true;
}
To your config. Note that you can’t use a GUI to manage native packages on NixOS, you have to use flatpaks or add packages via configuration.nix.
How and where can I edit this file?
Maybe because I’m trying this in a vm?
See the configuration chapter of the manual: NixOS Manual
I’m surprised you got here without being aware of that file, the point of NixOS is that it’s a distro that can be managed entirely through a configuration file. You might not enjoy the distro very much.
I agree. Not for me but thanks just the same.
The graphical installer makes that possible…
I am still the opinion, the way it is now, was a mistake to add. We should remove it, focus on a GUI to edit the config, and once that works, we can add an installer again, that allows for manual intervention in the config…
I’m getting around to that opinion, though the manual process should probably be streamlined a bit for people who don’t like using parted to partition their disks if the graphical installer is removed.
Maybe a middle ground that launches you into GNOME with a terminal and the manual open is an option?
Or triple down and make disko the only officially supported way to partition for NixOS?
Anyway, yeah, I don’t think you should be able to accidentally install NixOS without ever seeing a configuration.nix.
Im strictly against streamlining disko, unless they fixed the issues with flexible disk management.
I’m using LVM to create “partitions” at will (and destroy them), and from all what I’ve heard, disko doesn’t allow for this, without dropping and recreating everything else.
Not to say that I consider disko DSL much more complicated than running parted or cdisk or whatever.
Does it? I’ve switched to btrfs for this purpose, and not had any issues creating new subvolumes. LVM may be different, to be fair.
But that’s besides the point; I agree that disko isn’t any easier than parted & co., the alternative to a graphical installer is just some fully streamlined nix config installer in my mind.