In wake of the 2022 OpenSSL library, Nix can support in mitigating the library by downgrading (or replacing) the SSL library.
why is openssl broken since 2022?
https://duckduckgo.com/?q=2022+OpenSSL
OpenSSL has released a security advisory to address two vulnerabilities, CVE-2022-3602 and CVE-2022-3786, affecting OpenSSL versions 3.0.0 through 3.0.6.
funny how all comments were censored as "off topic", because some idiots clicked on the "report" button.
github takes such "reports" serious. no surprise, because either github is already subverted by the woke mob, or github is afraid of the woke mob.
the linked thread on discourse.nixos.org was censored by the nixos admins
here are 2 archived versions, but discourse is hard to archive:
see also:
https://github.com/milahu/hate-maintainers-censored
my censored "hate-maintainers" is hosted on the darknet:
http://it7otdanqu7ktntxzm427cba6i53w6wlanlh23v5i3siqmos47pzhvyd.onion/milahu/hate-maintainers
http://gg6zxtreajiijztyy5g6bt5o6l3qu32nrg7eulyemlhxwwl6enk6ghad.onion/milahu/hate-maintainers
this thread was censored by the nixos admins
here are 2 archived versions, but discourse is hard to archive:
see also:
https://github.com/milahu/hate-maintainers-censored
my censored "hate-maintainers" is hosted on the darknet:
http://it7otdanqu7ktntxzm427cba6i53w6wlanlh23v5i3siqmos47pzhvyd.onion/milahu/hate-maintainers
http://gg6zxtreajiijztyy5g6bt5o6l3qu32nrg7eulyemlhxwwl6enk6ghad.onion/milahu/hate-maintainers
this thread was censored by the nixos admins
here are 2 archived versions, but discourse is hard to archive:
see also:
https://github.com/milahu/hate-maintainers-censored
my censored "hate-maintainers" is hosted on the darknet:
http://it7otdanqu7ktntxzm427cba6i53w6wlanlh23v5i3siqmos47pzhvyd.onion/milahu/hate-maintainers
http://gg6zxtreajiijztyy5g6bt5o6l3qu32nrg7eulyemlhxwwl6enk6ghad.onion/milahu/hate-maintainers
Devops With Nix tips & practices.
Tutorial successfully combining NixOS & TerraformDev
NIX_PATHA colon-separated list of directories used to look up Nix expressions enclosed in angle brackets (i.e., <path>). For instance, the value
It would be helpful to
<path> will work with the prefixless format, but not with the prefixed one, and it may be helpful to spell this out explicitly.
0 [14:16:19] nix repl
Welcome to Nix version 2.3.10. Type :? for help.
nix-repl> :l <nixpkgs/doc>
Added 40 variables.
nix-repl> :l <doc>
error: file 'doc' was not found in the Nix search path (add it using $NIX_PATH or -I)
I always saw a NIXPATH used with the prefix syntax so far:
$ echo $NIX_PATH
nixpkgs=/nix/var/nix/profiles/per-user/root/channels/nixos:nixos-config=/etc/nixos/configuration.nix:/nix/var/nix/profiles/per-user/root
but NIX_PATH documentation shows that the prefixless format is also valid.
$ export NIX_PATH=/home/toraritte:/nix/var/nix/profiles/per-user/root/channels/nixos
$ printenv NIX_PATH
/home/toraritte:/nix/var/nix/profiles/per-user/root/channels/nixos
$ nix repl
Welcome to Nix version 2.3.10. Type :? for help.
nix-repl> :l <nixpkgs>
Added 12439 variables.
> (square: (x: y: square x + square y) 3 7) (x: x*x)58
This can be written up in many other forms, plus the possibility of currying deserves to be pointed out:
$ nix repl
nix-repl> (sq: (x: y: sq y + sq x) 2 7) (x: x*x)
53
nix-repl> (sq: (x: y: sq y + sq x)) (x: x*x)
«lambda @ (string):1:11»
nix-repl> (sq: (x: y: sq y + sq x)) (x: x*x) 2
«lambda @ (string):1:14»
nix-repl> (sq: (x: y: sq y + sq x)) (x: x*x) 2 7
53
nix-repl> (sq: x: y: sq y + sq x) (x: x*x) 2 7
53
Why is Nix written in C++ rather than a functional language like Haskell?[ ] Mainly because Nix is intended to be lightweight, easy to learn and portable (zero dependencies). Since 24. April 2017 thanks to Shea Levy and the crowdfunding of 54 community members, nix does not have Perl as dependency anymore.
There is hnix that is still actively developed (as of 2020/06/21).
with import <nixpkgs> {};
It is kind of an anti-pattern using the angle bracket notation and the linked post also makes a suggestion:
{ pkgs ? import (fetchTarball https://github.com/NixOS/nixpkgs/archive/3590f02e7d5760e52072c1a729ee2250b5560746.tar.gz) {};
}:
# ...
with import <nixpkgs> {};
It is kind of an anti-pattern using the angle bracket notation and the linked post also makes a suggestion:
{ pkgs ? import (fetchTarball https://github.com/NixOS/nixpkgs/archive/3590f02e7d5760e52072c1a729ee2250b5560746.tar.gz) {};
}:
# ...
with import <nixpkgs> {};
It is kind of an anti-pattern using the angle bracket notation and the linked post also makes a suggestion:
{ pkgs ? import (fetchTarball https://github.com/NixOS/nixpkgs/archive/3590f02e7d5760e52072c1a729ee2250b5560746.tar.gz) {};
}:
# ...
Basic Install environment.systemPackages = with pkgs; [ vim ]; or environment.systemPackages = with pkgs; [ vim_configurable ];
What is the difference between the vim and vim_configurable packages?
I believe the source for the latter is here.
The easiest way I've found to manage that is to copy hardware-configuration.nix and a minimal version of configuration.nix and import it into the NixOps config for the corresponding machine. (I keep them in a git submodule, but keeping them in the same repo could also make sense.) 1 Pick your reaction
If I understood it correctly, take the hardware-configration.nix from the target machine, and put it into the NixOps config.
Also relevant: Minimal NixOS config for Nixops deployment (discourse)
Install the latest version of NixOps. $ nix-env -i nixops
... or list it in environment.systemPackages in /etc/nixos/configuration.nix, and nixos-rebuild switch.
One way (are there others?) to pin Nixpkgs, and ditch channels.
extraUsers
extraUsers have been renamed to users. See related commits.
# cryptsetup luksFormat $LVM_PARTITION
Got a warning here but it seems to be safe to ignore.
WARNING: Locking directory /run/cryptsetup is missing!
Networking
This didn't work out of the box, therefore worth looking at the Arch linux wpa_supplicant docs.
wpa_cli also wouldn't work, and needed to make sure that I had the right SSID so this link is also helpful to list available wifi networks.
Note that from here on in we’ll be in root prompts the whole time. The NixOS install environment helpfully drops you in a shell with root logged in.
On 20.03 install drops users to a non-privileged terminal so sudo su has to be entered to become root. (Otherwise the first steps in "Networking" will fail immediately.)
Saving this here for posterity: https://stackoverflow.com/questions/55191125/cant-seem-to-get-sudo-working-under-nixos
Nix ecosystem introduction ("Talk at my company")
How we use Nix at IOHK?
Last commit that included nightly rust
but nixos has ways, you could look at how bootloader installation is done
Generates the configuration.nix on iso build