cafkafk/nixpkgs
cafkafk/nixpkgs
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 2
nixpkgs/pkgs/os-specific/linux/kernel/linux-3.4.nix

28 lines
1,010 B
Nix
Raw Normal View History

Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
{ stdenv, fetchurl, ... } @ args:
Adding linux 3.4. svn path=/nixpkgs/trunk/; revision=34209
2012-05-22 17:29:51 +02:00
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
import ./generic.nix (args // rec {
linux_*: update, including CVE-2014-4699 (most likely) CC #3196. No updates yet on 3.2 and 3.12 branches.
2014-07-09 22:49:12 +02:00
version = "3.4.98";
linux: add git repository and branch meta
2014-02-14 09:45:36 +01:00
extraMeta.branch = "3.4";
Adding linux 3.4. svn path=/nixpkgs/trunk/; revision=34209
2012-05-22 17:29:51 +02:00
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
src = fetchurl {
url = "mirror://kernel/linux/kernel/v3.x/linux-${version}.tar.xz";
linux_*: update, including CVE-2014-4699 (most likely) CC #3196. No updates yet on 3.2 and 3.12 branches.
2014-07-09 22:49:12 +02:00
sha256 = "0kkd6q80w4rh1sjdd4j5a2fmib4mjwhsf5fm555jl2w3zsy0kr45";
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
};
Adding linux 3.4. svn path=/nixpkgs/trunk/; revision=34209
2012-05-22 17:29:51 +02:00
kernel: enable AppArmor by default AppArmor only requires a few patches to the 3.2 and 3.4 kernels in order to work properly (with the minor catch grsecurity -stable includes the 3.2 patches.) This adds them to the kernel builds by default, removes features.apparmor (since it's always true) and makes it the default MAC system. Signed-off-by: Austin Seipp <aseipp@pobox.com>
2014-05-08 00:59:29 +02:00
kernelPatches = args.kernelPatches ++
[ { name = "0001-UBUNTU-SAUCE-AppArmor-Add-profile-introspection-file";
patch = ./apparmor-patches/3.4/0001-UBUNTU-SAUCE-AppArmor-Add-profile-introspection-file.patch;
}
{ name = "0002-UBUNTU-SAUCE-AppArmor-basic-networking-rules";
patch = ./apparmor-patches/3.4/0002-UBUNTU-SAUCE-AppArmor-basic-networking-rules.patch;
}
{ name = "0003-UBUNTU-SAUCE-apparmor-Add-the-ability-to-mediate-mou";
patch = ./apparmor-patches/3.4/0003-UBUNTU-SAUCE-apparmor-Add-the-ability-to-mediate-mou.patch;
}];
Unify the Linux kernel configurations Having N different copies of the NixOS kernel configuration is bad because these copies tend to diverge. For instance, our 3.10 config lacked some modules that were enabled in older configs, probably because the 3.10 config had been copied off an earlier version of some older kernel config. So now there is a single kernel config in common-config.nix. It has a few conditionals to deal with new/removed kernel options, but otherwise it's pretty straightforward. Also, a lot of cut&paste boilerplate between the kernel Nix expressions is gone (such as preConfigure).
2013-07-31 23:56:48 +02:00
features.iwlwifi = true;
features.efiBootStub = true;
features.needsCifsUtils = true;
features.netfilterRPFilter = true;
})
Reference in a new issue Copy permalink