nixpkgs VS nixos-hardware

https://github.com/NixOS/nixpkgs/commits?author=neon-sunset

I see two signers in the top 6 displayed on https://github.com/NixOS/nixpkgs/graphs/contributors

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,

```

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...

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...

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

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...

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.

Always useful to look at the seemingly endless stream of Linux information, the Arch wiki:

https://wiki.archlinux.org/title/ASUS_ROG_Zephyrus_G14_(2022...

Also NixOS has a nixos-hardware repository with configurations for some laptops:

https://github.com/NixOS/nixos-hardware/tree/master/asus/zep...

Reasonably legible if you ever programmed anything

{ imports = [ # Include the results of the hardware scan. ./hardware-configuration.nix # Additional hardware specific configuration # https://github.com/NixOS/nixos-hardware ];

You could try this repo for hardware support on various laptops if yours is on it: https://github.com/NixOS/nixos-hardware

https://github.com/NixOS/nixos-hardware

Btw, for starters, I think you can learn a lot by checking other's configurations and from things like https://github.com/NixOS/nixos-hardware. There are a lot of useful/essential configurations that are not enabled by default.

in that case do note that this module assumes you use nixos-hardware, otherwise you can remove lines 161-165. I can also send you my VM's libvirtd .xml file when you get around to creating it.

My computer is a Lenovo Legion 5 Pro with a dual GPU setup (AMD iGPU + Nvidia DGPU) where I'm using a "hybrid mode" configuration provided by nixos-hardware, using PRIME offload.

Not too long ago nixos-hardware changed the default Xorg driver for AMD to modesetting from amdgpu.