rfcs
not-os
Our great sponsors
rfcs | not-os | |
---|---|---|
46 | 10 | |
487 | 744 | |
5.3% | - | |
5.0 | 6.1 | |
5 days ago | 23 days ago | |
Nix | ||
Creative Commons Attribution Share Alike 4.0 | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
rfcs
-
Build System Schism: The Curse of Meta Build Systems
Nix with dynamic derivations (RFC92) could potentially beat this curse.
https://github.com/NixOS/rfcs/blob/master/rfcs/0092-plan-dyn...
-
Show HN: Flox 1.0 – Open-source dev env as code with Nix
See: A plan to stabilize the new CLI and Flakes incrementally https://github.com/NixOS/rfcs/pull/136
- RSS can be used to distribute all sorts of information
-
I like gentoo's package deprecation process
NixOS recently introduced "problem" infrastructure to deal with such problems more gracefully and explicitly:
https://github.com/NixOS/rfcs/blob/master/rfcs/0127-issues-w...
-
NixOS and Flakes Book: An unofficial book for beginners (free)
For some more context: Flawed as they are, Flakes solve a large number of problems Nix experiences without them. This is why I, and presumably many others, use them even in their current experimental state.
An RFC was recently accepted to commit to forming a plan towards stabilization of Flakes: https://github.com/NixOS/rfcs/pull/136
Personally, I don't believe there won't be any breaking changes, but I also believe that the stabilization of Flakes is still a ways away and hope that there will be a reasonable migration path.
- NixOS RFC 136 approved: A plan to stabilize the new CLI and Flakes incrementally
- NixOS RFC 136 accepted: A plan to stabilize the new CLI and Flakes incrementally
-
The NixOS Foundation's Call to Action: S3 Costs Require Community Support
NixOS needs to merge https://github.com/NixOS/rfcs/pull/133 to solve the issue
- Bootspec
-
Super Colliding Nix Stores: Nix Flakes for Millions of Developers
> Afterwards, Flakes itself and its CLI components can be stabilized. The final design of Flakes will also require another RFC.
That seems like Flakes are still quite a ways away.
[1] - https://github.com/NixOS/rfcs/pull/136
First, the non-Flakes CLI wll be stabilized, in phases.
not-os
-
Building and running not-os image in QEMU?
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?
-
NixOS
Maybe not-os?
- Not-OS – NixOS-based OS generator that outputs an OS with 47MB squashfs (2022)
- Not-OS – NixOS-based OS generator that outputs a 47MB OS
-
Gobolinux
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.
-
What does the minimal version of NixOS consist of?
I also found this: https://github.com/cleverca22/not-os
-
NixOS 21.05 Released
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.
-
Is it possible to deploy configuration as code?
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.
- Is it possible to replace systemd with runit?
What are some alternatives?
nix-ros-overlay - ROS overlay for the Nix package manager
nixGL - A wrapper tool for nix OpenGL application [maintainer=@guibou]
nixpkgs - Nix Packages collection & NixOS
matrix.to - A simple stateless privacy-protecting URL redirecting service for Matrix
nix - Nix, the purely functional package manager
nixos-generators - Collection of image builders [maintainer=@Lassulus]
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
emacs-overlay - Bleeding edge emacs overlay [maintainer=@adisbladis]
nix-1p - A (more or less) one page introduction to Nix, the language.
flake-utils-plus - Use Nix flakes without any fluff.