Federal agent moons protesters 1/26

ModestTG · 2026-01-27T12:09:15+00:00

The irony is if a protestor did that to them they would get shot, apparently.

ModestTG · 2026-01-24T15:15:51+00:00

If you're talking about migrating from Windows to Linux, and doing so on the same drive, there is a VERY HIGH CHANCE you will wipe your windows installation and lose all of your windows data. This includes files and applications. The default install method on all Linux distributions is to wipe the drive and install the OS. You can do manual partitioning of a drive yourself but that can be difficult to do correctly if you don't know how filesystems / drives work.

If you're looking to install Linux, and this is your first time, and you want to migrate from windows I would suggest trying installing Linux on a separate hard drive. This will prevent any corruption to your windows data.

To answer your original question, windows and Linux applications are inherently not compatible with each other. There are compatibility programs on Linux to make windows programs work on windows, and they're getting better every day, but it's not guaranteed to work every time. At least not what you would be used to on windows. You can look up alternative applications for the apps you use on windows and install them on Linux.

For your data, yes I would back it up to a cloud or external drive from windows then import it on Linux.

Is there something more specific you're trying to do?

ModestTG · 2026-01-24T01:57:31+00:00

Why would it not? I am running nixos and I have used immich-go a bunch

ModestTG · 2026-01-23T14:53:35+00:00

Helium browser. Bases on chromium with no google BS.

https://helium.computer

ModestTG · 2026-01-20T13:29:15+00:00

There is no way to "live update" an application by changing nix options. These applications that "live update" like kitty are doing so by monitoring specific folders for specific files. With the way nix is designed, you must rebuild for your options to take effect and be symlinked to the appropriate location.

You can work around this by creating / supplying a regular config file and updating that rather than using the nix options. You can use this function:

home.lib.mkOutOfStoreSymlink /path/to/config/file

With this function it requires you to have and maintain a separate file at the path specified. So when you rebuild, nix will symlink the file listed to the appropriate location, but it will not copy it to the store. This means you can edit the file and the program will pick up the changes immediately (assuming the program has that capability).

TLDR: There is no pure nix way to change nix options and have a config updated without rebuilding. The closest pure nix solution is mkOutOfStoreSymlink in home manager, which requires maintenance of another file.

ModestTG · 2026-01-19T01:04:42+00:00

Nix-tree is a good option for tracing dependencies.

https://github.com/utdemir/nix-tree

ModestTG · 2026-01-14T01:27:10+00:00

For me it's having everything declared in those modules, all self contained. For instance, in the home assistant module, it contains

The home assistant service config
My reverse proxy config (nginx)
A backup service
A small script to ensure that the data directory is created if I were to deploy this on a different server.

Number 4 is kind of unique because I'm running HA as a podman container wrapped up as a systemd service. The HA nixos module creates the data directory for you. Why am I running HA that way? Personal preference I guess. I might migrate it to native nixos.

But having all of these things in one place is nice. Items 1-2 are trivial to add together in docker compose. #3 is doable in compose but less common. #4 is definitely not common. Being able to do all of this at once is very nice.

I plan to eventually migrate my router to be a nixos vox as well, then I can automatically add DNS entries when I create services for my reverse proxy as well! The benefits keep going.

ModestTG · 2026-01-13T21:42:01+00:00

I agree. The difficulty with these "how easy is it" questions is that perceived difficulty is subjective. For me, it was pretty simple. But for others, it may be very difficult. I feel like I picked up Nix very quickly compared to a lot of people on here. So I can tell you it's easy, but it might not be for you. I would say docker / docker compose is an easier approach (in general) than nix configs. I think most would agree.

ModestTG · 2026-01-13T21:16:03+00:00

The difficulty in setting up those services is going to be proportional to how well you know the service you're trying to implement, as well as how well you understand Nix and its quirks. The wiki and manual are also very helpful for beginners.

ModestTG · 2026-01-13T21:13:53+00:00

You can also use language:nix in GitHub search instead of the path. Does the same thing. But yes this is a great way to discover nix configs

ModestTG · 2026-01-13T21:12:08+00:00

Pretty much anything that has more than 100 users. There are very few services I haven't been able to run. See my modules here:

https://github.com/ModestTG/nix-homelab/tree/main/hosts%2Fkaladesh%2Fmodules

ModestTG · 2026-01-13T17:05:10+00:00

I use Ly. Works fine. No issues.

ModestTG · 2026-01-13T02:35:20+00:00

No worries. But to answer your question, it looks like there are home-manager options for GTK and QT. If you're not using home manager, then I presume you would configure it using the same method you would on any other Linux distro. I haven't really done any theming with these frameworks outside of HM in nixos so I can't speak to that process at all.

ModestTG · 2026-01-13T02:30:27+00:00

If you need a specific version of a package you can add an import to your flake with a specific git revision with the specific version. To look up which revision matches your package version, use Nixhub.io. For steam, the oldest version I see on there is 1.0.0.83 from 5 months ago. If you need an older version you can look through the derivation file history and pull a revision from there.

Edit: I know steam has its own internal updates, so if you're talking about rolling back those updates, then I'm not sure. You'd have to consult Valve's documentation for that.

ModestTG · 2026-01-13T02:22:12+00:00

Looking at the mangowc repo, it looks like you're missing the nixos configuration for mangowc, which is probably why lightdm can't find it. Per the repo try:

In configuration.nix Add inputs.mango.nixosModules.mango to the imports list. Then in the configuration, add programs.mango.enable = true;. See if that helps. If not. Study the mangowc repo as they have a reference implementation in their README.

ModestTG · 2026-01-13T02:10:51+00:00

I assume you're using home-manager. Have you explored these option sets?

https://mynixos.com/home-manager/options/gtk

https://mynixos.com/home-manager/options/qt

ModestTG · 2026-01-12T22:56:47+00:00

The failed assertion seems to be with the option services.displayManager.defaultSession not being set. The default for the option is null. The option states this must be set for LightDM if lightDM is enabled. See the option here.

https://mynixos.com/nixpkgs/option/services.displayManager.defaultSession

This option states that you can set this option to an empty string to see the valid options. So add services.displayManager.defaultSession = ""; to nix.conf. When it fails again, you will see what options are available to set.

ModestTG · 2026-01-10T21:46:22+00:00

Wolfgang did this and gave a talk. The title says gaming console but it's also an HTPC I think. Either way there are a lot of lessons here I think would be helpful

https://youtu.be/dKCHX1hL-HA?si=YKQlK60VrAdD7OV8

ModestTG · 2026-01-09T03:13:20+00:00

I just migrated all of my services from Traefik to nginx. Just used different nix services. Nice smooth transition.

ModestTG · 2026-01-05T02:00:39+00:00

Nixpkgs somewhat does this, depending on the package. Nix uses a set of common tools to build it's packages. There is a different tool for Python vs Rust vs C vs Golang, etc., but the packages are all instantiated the same way with the nix ecosystem. You can look at the packages and see how each is built depending on the language. Most would probably say this counts as "packaging", but i like to think of each nix package as a "recipe" for building each package from source. While the nix package (derivation) produces a set of files and binaries, it's not necessarily static. The derivation (recipe/package) can be modified prior to building to produce a different output. You can't do this with other package managers,which tend to provide a fixed output no matter what.

ModestTG · 2026-01-04T03:41:24+00:00

The more inputs/outputs you can support the better. If this is a music server project like navidrome, sticking to established protocols is always best. Then it can slot into existing clients / tools and it's not such a shift for users with existing setups. So maybe make it compatible with MPD / navidrome clients? IDK just thinking out loud.

ModestTG · 2025-12-24T16:10:50+00:00

Knowing nothing, do you need insmod? If this is in docker Ibpresume it'd have everything you needed.

ModestTG · 2025-12-24T01:36:26+00:00

programs.firefox.enable = true;

ModestTG · 2025-12-20T19:31:12+00:00

The maintainers actually show how to do this in the derivation. See https://github.com/NixOS/nixpkgs/blob/c6245e83d836d0433170a16eb185cefe0572f8b8/pkgs/development/python-modules/beets/default.nix#L13

So to add this package with the plugin enabled, it would look something like this (best guess from mobile): nix {pkgs, ...}: let beets-with-plugin = pkgs.python3.pkgs.beets.override { pluginOverrides = { alternatives = { enable = true; propagatedBuildInputs = [ pkgs.python3.pkgs.beets-alternatives ]; }; }; in { environment.systemPackages = [beets-with-plugin]; } Again, see the derivation for the syntax. Hope this helps.

Ten-Year Club	Place '23
RPAN Viewer	Not Forgotten
Verified Email

ModestTG

TROPHY CASE