nixwrt
nixpkgs
nixwrt | nixpkgs | |
---|---|---|
4 | 975 | |
200 | 15,753 | |
- | 2.2% | |
0.0 | 10.0 | |
over 2 years ago | about 12 hours ago | |
Nix | Nix | |
MIT License | 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.
nixwrt
-
Mobile NixOS for Phones and Tablets
tl;dr: here are three commercial embedded NixOS uses and a couple of other embedded NixOS projects
1. LumiGuide uses NixOS for their embedded systems, which track automatic bicycle rentals at little solar-powered stations IIRC: https://av.tib.eu/media/39625 (also some coverage here: https://www.worksonarm.com/blog/nixos/ )
2. Yakkertech uses NixOS for their embedded systems, which do baseball pitch tracking: https://av.tib.eu/media/50713
3. Swift Navigation uses NixOS for CI/CD for the embedded systems they use for GPS and navigation: https://blog.swiftnav.com/using-nixos-to-manage-hardware-tes...
I'd only heard of the first two, and discover the third just now.
There are also two downstream distros/related projects that target embedded systems, but idk how much commercial use they've yet seen, if any:
a. https://github.com/telent/nixwrt
b. https://github.com/cleverca22/not-os
-
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.
-
Why do people prefer a certain flavour of Linux? What are the differences that make someone say 'I prefer X distro over Y'?
And, if you take into consideration my personal, subjective opinions on what a distro must be (declarative, fearless to tinker with, mostly binary based but with easy overrides, mostly stateless, easy to roll back in case something goes wrong), then that leaves pretty much two options: NixOS and Guix, and because I don't really like LISP syntax, I go with NixOS as my favourite distro for desktops and servers. For embedded, I've recently tried NixWrt and it seems to work quite well, however I'm still using OpenWRT for "mission-critical" routers.
- Need some guidance in creating a nix distribution for RouterOS routers.
nixpkgs
-
Nix: The Breaking Point
I don't think so. The article is probably intended for the Nix community, so the author doesn't need to convince HN that something is going on. If as an outsider you are interested then you need to look into it yourself, the community has no obligation to make their internal conflicts legible to the outside world.
As an outsider myself, it certainly looks like something is going on as more than 20 Nixpkg maintainers left in a week: https://github.com/NixOS/nixpkgs/issues?q=label%3A%228.has%3...
- Maintainers Leaving
-
Air Force picks Anduril, General Atomics to develop unmanned fighter jets
https://github.com/NixOS/nixpkgs/commits?author=neon-sunset
-
Eelco Dolstra's leadership is corrosive to the Nix project
I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors
-
3rd Edition of Programming: Principles and Practice Using C++ by Stroustrup
For a single file script, nix can make the package management quite easy: https://github.com/NixOS/nixpkgs/blob/master/doc/languages-f...
For example,
```
- NixOS/nixpkgs: There isn't a clear canonical way to refer to a specific package
-
NixOS Is Not Reproducible
Yes, Nix doesn't actually ensure that the builds are deterministic. In fact it works just fine if they aren't. There are packages in nixpkgs that aren't reproducible: https://github.com/NixOS/nixpkgs/issues?q=is%3Aopen+is%3Aiss...
-
The xz attack shell script
I'm not familiar with Bazel, but Nix in it's current form wouldn't have solved this attack. First of all, the standard mkDerivation function calls the same configure; make; make install process that made this attack possible. Nixpkgs regularly pulls in external resources (fetchUrl and friends) that are equally vulnerable to a poisoned release tarball. Checkout the comment on the current xz entry in nixpkgs https://github.com/NixOS/nixpkgs/blob/master/pkgs/tools/comp...
-
Debian Git Monorepo
NixOS uses a monorepo and I think everyone's love it.
I love being able to easily grep through all the packages source code and there's regularly PRs that harmonizes conventions across many packages.
Nixpkgs doesn't include the packaged software source code, so it's a lot more practical than what Debian is doing.
https://github.com/NixOS/nixpkgs
-
From xz to ibus: more questionable tarballs
In this specific case, nix uses fetchFromGitHub to download the source archive, which are generated by GitHub for the specified revision[1]. Arch seems to just download the tarball from the releases page[2].
[1]: https://github.com/NixOS/nixpkgs/blob/3c2fdd0a4e6396fc310a6e...
[2]: https://gitlab.archlinux.org/archlinux/packaging/packages/ib...