nixpkgs/pkgs/os-specific/linux/kernel/linux-3.2.nix

{ stdenv, fetchurl, ... } @ args:

import ./generic.nix (args // rec {
  version = "3.2.58";
  extraMeta.branch = "3.2";

  src = fetchurl {
    url = "mirror://kernel/linux/kernel/v3.x/linux-${version}.tar.xz";
    sha256 = "1mszzixiv4k61m241dl2n5s8rca26l6hc40v23lha814nrahjkn1";
  };

  # We don't provide these patches if grsecurity is enabled, because
  # the grsec 3.2 -stable patchset already includes them.
  kernelPatches = args.kernelPatches ++ (
    stdenv.lib.optional (!(args.features.grsecurity or false))
      [ { name = "0001-AppArmor-compatibility-patch-for-v5-network-controll";
          patch = ./apparmor-patches/3.2/0001-AppArmor-compatibility-patch-for-v5-network-controll.patch;
        }
        { name = "0002-AppArmor-compatibility-patch-for-v5-interface";
          patch = ./apparmor-patches/3.2/0002-AppArmor-compatibility-patch-for-v5-interface.patch;
        }
        { name = "0003-AppArmor-Allow-dfa-backward-compatibility-with-broke";
          patch = ./apparmor-patches/3.2/0003-AppArmor-Allow-dfa-backward-compatibility-with-broke.patch;
        }]);

  features.iwlwifi  = true;
} // (args.argsOverride or {}))
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 22:56:48 +01:00			`{ stdenv, fetchurl, ... } @ args:`
Linux 3.2-rc1 svn path=/nixpkgs/trunk/; revision=30336 2011-11-08 16:58:20 +00: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 22:56:48 +01:00			`import ./generic.nix (args // rec {`
linux: minor updates, probably often fixing CVE-2014-0196 2014-05-13 13:07:58 +01:00			`version = "3.2.58";`
linux: add git repository and branch meta 2014-02-14 08:45:36 +00:00			`extraMeta.branch = "3.2";`
Linux 3.2-rc1 svn path=/nixpkgs/trunk/; revision=30336 2011-11-08 16:58:20 +00: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 22:56:48 +01:00			`src = fetchurl {`
			`url = "mirror://kernel/linux/kernel/v3.x/linux-${version}.tar.xz";`
linux: minor updates, probably often fixing CVE-2014-0196 2014-05-13 13:07:58 +01:00			`sha256 = "1mszzixiv4k61m241dl2n5s8rca26l6hc40v23lha814nrahjkn1";`
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 22:56:48 +01:00			`};`
Linux 3.2-rc1 svn path=/nixpkgs/trunk/; revision=30336 2011-11-08 16:58:20 +00: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-07 23:59:29 +01:00			`# We don't provide these patches if grsecurity is enabled, because`
			`# the grsec 3.2 -stable patchset already includes them.`
			`kernelPatches = args.kernelPatches ++ (`
			`stdenv.lib.optional (!(args.features.grsecurity or false))`
			`[ { name = "0001-AppArmor-compatibility-patch-for-v5-network-controll";`
			`patch = ./apparmor-patches/3.2/0001-AppArmor-compatibility-patch-for-v5-network-controll.patch;`
			`}`
			`{ name = "0002-AppArmor-compatibility-patch-for-v5-interface";`
			`patch = ./apparmor-patches/3.2/0002-AppArmor-compatibility-patch-for-v5-interface.patch;`
			`}`
			`{ name = "0003-AppArmor-Allow-dfa-backward-compatibility-with-broke";`
			`patch = ./apparmor-patches/3.2/0003-AppArmor-Allow-dfa-backward-compatibility-with-broke.patch;`
			`}]);`

			`features.iwlwifi = true;`
grsecurity: Fix building grsec-3.x.0 kernels 2014-01-29 18:06:45 +00:00			`} // (args.argsOverride or {}))`