nix-bundle VS not-os

I admit that there is an element of, "but I chose an obscure and challenging linux variant, waaah why isn't it supported" here, but (a) there's currently no flatpak and (b) when, for goodness sakes, will major linux projects begin packaging for Nix/NixOS as a matter of course?

It's not hard, and the benefits go far outside merely supporting Nix, as e.g. a flake.nix file would allow this project to generate docker images, and appImage images, as basically afterthoughts. (See e.g. https://github.com/matthewbauer/nix-bundle.)

Nix flake support would also provide a perfectly reproducible build environment, which can help clarify dependencies, and thus help the project build achieve idempotence, but I'll save the full shill for some github issue.

In fact, I'm inclined to roll up my shirtsleeves and help make this real.

https://github.com/matthewbauer/nix-bundle perhaps?

Another way to approach this would be to advocate Nix as the build system for Flatpak or AppImage. Don't know what the status is of nix-bundle, but if it is possible to turn a Nix package into an AppImage with little extra work that would be ideal.

Nix itself is more focused on "distribute from this host with nix, to this other host with nix".

Though, here is e.g. https://github.com/matthewbauer/nix-bundle, which is supported as an experimental command in nix 2.4.

I believe this tool does: https://github.com/matthewbauer/nix-bundle

Yes, it's extremely powerful once you truly understand Nix.

There are efforts to improve documentation, but it still is lacking (I think the biggest problem is that Nix is so big, not just the OS but it can be utilized as a build system).

Just with NixOS is not exactly clear how can you for example build your custom image.

I think https://nix.dev/ is approaching the documentation from the right direction.

There are also many pieces that people built that you need to find.

For example some things that I found accidentally:

* https://github.com/matthewbauer/nix-bundle

* https://github.com/cleverca22/not-os

Unfortunately those side projects often have even worse documentation.

Hi. I'm new to nix and want to ask if you have an idea how to build an ISO image file of not-os and run it on QEMU virt vanager?

Maybe not-os?

oh oops, I think I was intending to type "crowd source" but I really met "crowd fund".

I do want to finish my FreeBSD cross PR, but is is hard. We already have NetBSD working, including building the kernel, so I think it is better to start there.

I opened https://github.com/cleverca22/not-os/issues/16 because I think that would be the absolute easiest first step, with the fewest moving parts. But I don't know how kernels, even Linux, are packaged into bootable thingies at all.

I also found this: https://github.com/cleverca22/not-os

It's like an OS that has builtin salt/ansible/chef/puppet.

Because Nix language describe the OS instead of what to change/configure it's superior to these tools, and solves the problem that supposedly same machines are drifting apart.

For example if in the CM you tell it to install a package, then change your mind and remove the entry that does it. The package will remain installed.

With NixOS if you remove the package from configuration, it's gone.

I personally really like Nix's building capability. For example I can use it to generate a minimal docker container. It requires some knowledge, but I can also modify compilation options in dependencies (like remove unneeded functionality).

It looks like there's also an option to similarly build lightweight OS images[1]. I haven't tried it yet but looks cool.

[1] https://github.com/cleverca22/not-os

You might want to check out https://github.com/telent/nixwrt and https://github.com/cleverca22/not-os as solutions with similar goals. The former is a promising but yet-unfinished way of using Nix to manage a router, while the latter is a similar way of using Nix to generate an immutable OS image.