efe6967e93
bcc doesn't really need kernel itself, it just cares about module path. It's actually better to use /run/booted-system/kernel-modules/lib/modules for two reasons: - no need to rebuild bcc for each new kernel - can use a newer bcc with a booted kernel that doesn't match the current system |
||
---|---|---|
.. | ||
agda-packages.nix | ||
aliases.nix | ||
all-packages.nix | ||
beam-packages.nix | ||
config.nix | ||
coq-packages.nix | ||
cubocore-packages.nix | ||
darwin-packages.nix | ||
default.nix | ||
dhall-packages.nix | ||
dotnet-packages.nix | ||
emacs-packages.nix | ||
emscripten-packages.nix | ||
gnuradio-packages.nix | ||
haskell-packages.nix | ||
haxe-packages.nix | ||
impure.nix | ||
java-packages.nix | ||
kodi-packages.nix | ||
linux-kernels.nix | ||
lua-packages.nix | ||
make-tarball.nix | ||
metrics.nix | ||
nim-packages.nix | ||
nixpkgs-basic-release-checks.nix | ||
ocaml-packages.nix | ||
octave-packages.nix | ||
packages-config.nix | ||
perl-packages.nix | ||
php-packages.nix | ||
pure-packages.nix | ||
python-aliases.nix | ||
python-packages.nix | ||
python2-packages.nix | ||
qt5-packages.nix | ||
release-alternatives.nix | ||
release-cross.nix | ||
release-haskell.nix | ||
release-lib.nix | ||
release-python.nix | ||
release-r.nix | ||
release-small.nix | ||
release.nix | ||
ruby-packages.nix | ||
splice.nix | ||
stage.nix | ||
unixtools.nix | ||
wine-packages.nix |