u-root
nixpkgs
Our great sponsors
| u-root | nixpkgs | |
|---|---|---|
| 9 | 974 | |
| 2,437 | 15,656 | |
| 1.3% | 5.3% | |
| 9.7 | 10.0 | |
| 8 days ago | 2 days ago | |
| Go | Nix | |
| BSD 3-clause "New" or "Revised" 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.
u-root
-
Monogon: A Linux userland in pure Go
It looks similar to u-root https://github.com/u-root/u-root, yes, used as part of host firmware. There's a description of u-root in chapter 6 of https://link.springer.com/book/10.1007/978-1-4842-7939-7, too.
-
Gokrazy – Go Appliances
"A fully Go userland with Linux bootloaders! u-root can create a one-binary root file system (initramfs) containing a busybox-like set of tools written in Go." https://github.com/u-root/u-root
- Gokrazy Is Cool
- O que vocês acham da linguagem Goolang?
-
Is it possible to install a linux specific package on osx?
I am trying to build something with github.com/u-root/u-root/pkg/strace, but the issue I am running into is that my dev environment is an ARM Mac, while the package is specific to Unix systems.
-
Coreutils Rewritten in Rust
I've seem a few attempts. This is just one example: https://github.com/u-root/u-root/tree/master/cmds/core
- u-root – many Linux tools in a single Golang binary, initramfs, and bootloader
-
Writing an init with Go (part 1)
Great material! This approach is also used in u-root - Golang busybox created for LinuxBoot. I really enjoy working with it so far!
nixpkgs
- 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...
-
GitHub Disabled the Xz Repo
True, but irrelevant -- _some packages_, _somewhere_, do depend on xz, which, if built, requires pulling the source from GitHub (see the default.nix: https://github.com/NixOS/nixpkgs/blob/nixos-23.11/pkgs/tools...)
It's not the vulnerability that's a problem right now (NixOS was protected by a couple of factors) but rather GitHub's hamfisted response.
That is the problem.
What are some alternatives?
booster - Fast and secure initramfs generator
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
dracut-sshd - Provide SSH access to initramfs early user space on Fedora and other systems that use Dracut
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
nhi - :tv: Automatically capture all potentially useful information about each executed command (as well as its output) and get powerful querying mechanism
git-lfs - Git extension for versioning large files
router7 - router7 is a small home internet router completely written in Go. It is implemented as a gokrazy appliance.
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
coreutils - Cross-platform Rust rewrite of the GNU coreutils
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
nushell - A new type of shell
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.