silverblue-nix
nixpkgs
silverblue-nix | nixpkgs | |
---|---|---|
18 | 976 | |
- | 15,844 | |
- | 3.4% | |
- | 10.0 | |
- | 1 day ago | |
Nix | ||
- | 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.
silverblue-nix
-
How do you make /nix read write like /home /var on microos
On silverblue, you just follow this guide and it uses a systemd service that uses the command chattr to make / immutable (temporary) but not the reclusive directories (that means only / not the contents inside the directories) by doing chattr -i / creates /nix and /var/lib/nix mkdir /nix mkdir /var/lib/nix then it bind mounts it mount --bind /var/lib/nix /nix then it uses chattr again to make / immutable again chattr +i / . The problem with microos is that the chattr command can't change atributes on the / directory. But is there like a way to have a /nix subvolume like how there is writable /var and /home subvolumes? Like how can you make it not part of the immutable part. you can go into the transactional update shell and type mkdir /nix and /nix is there but is not writable. Is there a way to make a subvolume and mount it as /nix and have it readable and writable?
-
How has your experience with Silverblue/Kinoite been?
agreed with that I only install drivers, distrobox, and qemu/virt manager on the immutable part and everything else is done with either flatpak, containers, or nix (it works on silverblue quite well. there is a guide for it)
-
conflicted with silverblue
fedora silverblue is good if you want a reliable system. you can also get traditional package management by using containers from distrobox or toolbox or you can use nix on silverblue
-
Does anyone else use the nix package manager on silverblue?
I find it quite useful for silverblue. I can install packages user wide or system wide without the need to layer packages. It gives me a mutable eviroment while keeping the core system safe. Proot isn't available for fedora but it is available with nix so I can have proot system wide with nix which is not possible with podman. Applications with nix start way faster than starting a podman container. It is quite useful. only downside is that you need to set SELinux to permissive (which really isn't an issue for me) there is a guide for installing nix on silverblue too.
-
I think the nix package manager should be in the official repositories or at least in copr.
Installing nix, you would have to disable selinux and if you use silverblue, you have to do these extra steps. it would be nice if all you got to do is type sudo dnf install nix (or sudo rpm-ostree install nix if you are on silverblue) and it would automaticly add selinux policies and automaticly have the .desktop files in ~/.nix-profile/share/applications or ~/nix/var/nix/profiles/default/share/applications for system wide automaticly show up in the DE launcher and also have sudo work with nix better. it should also work for workstation and silverblue too.
-
How stable is Fedora workstation compared to Silverblue ?
maybe install it on toolbox, distrobox, or even nix if you want to install something that isn't a flatpak. nix is good for installing other terminals, shells, and fetch programs so I don't need to layer. it also supports user wide and system wide packages. only downside is that you need to disable selinux.
-
Day 15 with silverblue, loving how rock stable the whole system feels! Exactly the kind of distro i've always wanted.
you should give nix on silverbluea try
-
What's great about Fedora?
here is a guide to install it on silverblue https://gitlab.com/ahayzen/silverblue-nix
-
Well, technically...
the nice thing is you can install nix package manager on other distros. it is very useful to use different shells and using neofetch without layering on silverblue. there is a guide for it
-
NixOS 22.11 “Raccoon” Released
Never mind traditional package managers... you plug it in right, you can run Nix on Silverblue!
https://gitlab.com/ahayzen/silverblue-nix
NixOS people will prefer NixOS, but Silverblue seems like a nice complement to Nix if you need an FHS base system and want to retain some Nix-ish features like rollbacks and atomic upgrades.
nixpkgs
-
Tracexec: TUI for tracing execve and pre-exec behavior
This will drop you into a shell where `tracexec` is installed.
[1]: https://github.com/NixOS/nixpkgs/pull/310158
-
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
What are some alternatives?
nix-autobahn
asdf - Extendable version manager with support for Ruby, Node.js, Elixir, Erlang & more
nix-configuration - Nix configurations files for corytertel
Home Manager using Nix - Manage a user environment using Nix [maintainer=@rycee]
silverblue-update - Daily Fedora Silverblue Update
git-lfs - Git extension for versioning large files
vanitygen-plusplus - A vanity address generator for BTC, ETH, LTC, TRX and 100+ more crypto currencies.
easyeffects - Limiter, compressor, convolver, equalizer and auto volume and many other plugins for PipeWire applications
core - OPNsense GUI, API and systems backend
spack - A flexible package manager that supports multiple versions, configurations, platforms, and compilers.
nix-ld - Run unpatched dynamic binaries on NixOS
waydroid - Waydroid uses a container-based approach to boot a full Android system on a regular GNU/Linux system like Ubuntu.