mirror of
https://abf.rosa.ru/djam/kernel-5.10.git
synced 2025-02-25 01:32:48 +00:00
No description
2216dad38b
The source code of the kernel and the patchset are the same for both 2014.1 and the "current" platform, so are the scripts used during the build. 1. I updated create_configs-withBFQ so that it creates different kernel configuration files depending on its --with-enhanced-security parameter. If --with-enhanced-security is set, * SELinux is used instead of TOMOYO; * Memory sanitization facilities are compiled in (but are disabled by default - should be enabled at boot time with boot options pax_sanitize_slab=1 paxsanitize_pages=1). Similar to other packages, I added a conditional in the spec that enables enhanced security features when building for 'current' (i.e. for the future cert. systems) and leaves everithing as is. Besides, I fixed create_configs-withBFQ: even if --user-cpu=... was given, it still generated the configs for all architectures, a waste of time. Now it creates the config only for the architecture corresponding to --user-cpu=... if it is set and for all otherwise. ---------------- The changes in the configs listed below are for i586 and x86_64 only. 2. Added the following to make lxc-checkconfig happy: * CONFIG_MEMCG=y * CONFIG_MEMCG_SWAP=y * CONFIG_MEMCG_KMEM=y 3. Added the following options that 'make oldconfig' adds anyway during the build: * CONFIG_MM_OWNER=y * CONFIG_ARCH_SUPPORTS_ATOMIC_RMW=y * CONFIG_IOSF_MBI=m * CONFIG_LRU_CACHE=m * (x86_64 only) CONFIG_ARCH_ENABLE_HUGEPAGE_MIGRATION=y 4. Removed the following options (they are no longer available in 3.14): * CONFIG_CPU_FREQ_TABLE * CONFIG_IP_NF_MATCH_PSD * CONFIG_IP_NF_TARGET_IFWLOG 5. Increased CONFIG_SERIAL_8250_NR_UARTS from 4 to 8: some of our users have unusual boards with more than 4 serial ports. Also added CONFIG_SERIAL_8250_MANY_PORTS=y: needed for these users too. 6. Unset CONFIG_DRM_RADEON_UMS: it has been deprecated for quite some time and was seemingly ignored. 'radeon' driver the kernel provides works via KMS rather than UMS now and its UMS support is obsolete and buggy. 7. Finally dropped support for Mach64 GPUs. If there are enough users with such hardware, we could enable it is some kernel flavour in contrib (project: https://abf.io/import/kernel-other/). 8. Changed CONFIG_FB_TILEBLITTING to "y": 'make oldconfig' already does this during the kernel build because it is needed for Matrox GPUs (CONFIG_FB_MATROX). BTW, some of our users do seem to have Matrox GPUs. Consequently, I had to disable CONFIG_FB_CON_DECOR: it needs CONFIG_FB_TILEBLITTING unset. 9. Changed CONFIG_X86_VERBOSE_BOOTUP=n to # CONFIG_X86_VERBOSE_BOOTUP is not set 10. (x86_64 only) Changed CONFIG_X86_ESPFIX32=y to CONFIG_X86_ESPFIX64=y This is what 'make oldconfig' does with that option anyway. |
||
|---|---|---|
| .abf.yml | ||
| cpupower.config | ||
| cpupower.service | ||
| disable-mrproper-prepare-scripts-configs-in-devel-rpms.patch | ||
| kernel-1.spec | ||
| kernel.rpmlintrc | ||
| linux-3.14.tar.sign | ||
| patch-3.14.25.sign | ||
| README.kernel-sources | ||
Hello Mandriva, OpenMandriva, MagOS and Rosa Linux Users, linux-userspace-headers contains the headers for the source code of Linux kernel. All source code necessary to compile a new kernel is included in two packages linux-userspace-headers, and kernel-source. You will need to install both linux-userspace-headers (needed for general Linux compilation), and kernel-source in order to compile a new kernel. The kernel is the central process of your Linux machine, the mediator between the hardware and your programs. It is responsible for memory allocations, process managing, device access... Although modern kernels are very flexible thanks to dynamic modules, you may need to compile your own kernel for various reasons: your found a new module which need a more recent kernel, you need a feature of a new kernel, etc... Here is a short sum-up of what you can find in the Kernel-HOWTO. Consult it in case of a problem or if the shortcut here provided does not meet your needs. You should also consult the README of kernel-sources. 1. Configure your new kernel You should never build a kernel as root, so as a normal user: Copy the source in /usr/src/linux/ to ~/kernel/ Change to ~/kernel/ and clean-up previous compilations, by issuing "make mrproper", In console mode, run "make menuconfig", Under X11, run "make xconfig". Then configure all sections of your kernel making each feature you need available constantly or as a module. Note that you should compile most features as a module, as it consume less memory, taking into account that some of them cannot be modules as you may need them at boot time, before dynamic modules be loaded... 2. Compile it Just issue "make" to create a compressed kernel image and the modules you configured. 3. install your new kernel Now you need root privilegies, so: Issue "su" and enter root password. Issue "make modules_install" This will copy your modules and needed files to /lib/modules/ Issue "make install" This will copy your new kernel and system.map to boot dir (/boot/) with correct names including version, and change respective links. It finally runs lilo to take into account your new kernel. 4. Modify Lilo to allow your booting on old kernel * This step is optional, although recommended * See lilo.conf man page. Your are encouraged during this step to create a new section in your lilo.conf file, in order to enable you to boot on your both kernels, the old and the new one. You need to run lilo then to take your changes into account. You may also use linuxconf to do all that with a nice GUI. 5. Reboot your machine... And pray. Anyway if something goes wrong, you just need to reboot and choose your old kernel with lilo. Enjoy! ======================================================================== (c) 1999-2006 Mandriva, Camille B<>gnis <camille@mandriva.com> (c) 2006 Thomas Backlund <tmb@mandriva.org> (c) 2011 Thomas Backlund <tmb@mageia.org> (c) 2011 Nicol<6F> Costanza <abitrules@yahoo.it>