1pakch

Setting up NixOs with LUKS encrypted root

Here are my working notes on getting a system up and running.

WARNING: You can run into a hidden problem that will prevent a correct partition setup and /etc/nixos/configuration.nix from working: if you are setting up a UEFI system, then you need to make sure you boot into the NixOS installation from the UEFI partition of the bootable media. You may have to enter your BIOS boot selection menu to verify this. For example, if you setup a NixOS installer image on a flash drive, your BIOS menu may display several boot options from that flash drive: choose the one explicitly labeled with “UEFI”.

References

I used these resources:

1pakch

# Use via nix-shell --argstr package-names ipython,quandl --command fish

{ package-names, python-version ? "36" }:
with builtins;
let
  pkgs = import <nixpkgs-fork> {};
  from = where: what: getAttr what where;

  v = python-version;
  python = from pkgs "python${v}";

1pakch

with import <nixpkgs-fork> {};
let
  p = python36;
  pp = python36Packages;
in stdenv.mkDerivation {
  name = "blabla";
  buildInputs = [ stdenv p pp.ipython pp.quandl ];
}

1pakch

{ config, pkgs, lib, ...}:

with lib;

let
  cfg = config.services.dummy;

in {
  imports = [];

1pakch

{ config, pkgs, lib, ...}:

with lib;

let
  cfg = config.services.echo;

in {
  imports = [];

1pakch

# A standard way to use Robert Kern's line profiler
# https://github.com/rkern/line_profiler
# is to wrap a function of interest using the @profile decorator
# and then to run the script via
#     kernprof -l script_to_profile.py
# or
#     python -m line_profiler script_to_profile.py.lprof
#
# This approach does not work, however if the function of interest
# is defined outside of the top-level script (or module) since @profile