diff slack/kernel-source vanilla/kernel-source
in [Slackware]
|
From: Eef Hartman on 13 Apr 2010 08:06 caio <elcaio(a)gmail.com> wrote: > Then if there no patch at /usr/src, it's safe to download kernel > source from kernel.org, make our configurations and install it and > still keep slackware on a good place. > Btw, I think it is a good practice to installpkg (no upgradepkg) last > kernel-* pkgs, and then download/make/install our personal kernel > source. Is it right? > How do you usually do your kernel upgrades? I get a new kernel source from kernel.org, unpack in /usr/src/linux-<version). Then get the config from the running kernel (either a previous "own-build" or the /boot/config-<version> from the Slackware one), put it IN there as ..config, do "make oldconf" to process it AND see the the new changes and additions and then proceed from there. I must admit, I mostly DO use my "own" kernel in Slackware, i.e. my 12.2 system at home is using 2.6.30.5, not the 2.6.27.7 it came with, and the systems here are using 13.0 (optional -64) with the 2.6.32.8 kernel (it was released with 2.6.29.6). -- ******************************************************************* ** Eef Hartman, Delft University of Technology, dept. SSC/ICT ** ** e-mail: E.J.M.Hartman(a)tudelft.nl - phone: +31-15-278 82525 ** *******************************************************************
From: Henrik Carlqvist on 13 Apr 2010 16:04 caio <elcaio(a)gmail.com> wrote: > Then if there no patch at /usr/src, it's safe to download kernel > source from kernel.org, make our configurations and install it and > still keep slackware on a good place. > Btw, I think it is a good practice to installpkg (no upgradepkg) last > kernel-* pkgs, and then download/make/install our personal kernel > source. Is it right? > How do you usually do your kernel upgrades? Yes, most likely downloading and compiling a new kernel will work fine on Slackware today. However, during the years I have been burned a few times and avoid upgrading the kernel. Instead I carefully apply my own patches if there is some kind of upgrade that the stock kernel need. Earlier attempts to upgrade the kernel have for me resulted in missing modules which didn't come with the kernel source (alsa, drivers for X, kqemu). I have also heard of others who have gotten problems when using a glibc not compiled for the currently used kernel and upgrading glibc is soemthing you probably don't want to do, I have only tried that once. But lately several people have reported that upgrading the kernel is rather painless so it probably works fine today. regards Henrik -- The address in the header is only to prevent spam. My real address is: hc3(at)poolhem.se Examples of addresses which go to spammers: root(a)localhost postmaster(a)localhost
From: Richard Herbert on 13 Apr 2010 18:25
On Tue, 13 Apr 2010 05:58:52 +0000, Emilio Lazardo wrote: > In the 32.11 and 33.2 trees that I am working with, there is no > 'include/ generated' directory in either the pristine source or a > post-compile tree. Perhaps you are looking at something other than > kernel source? The 'include/generated' directory is a result of running 'make oldconfig' against 2.6.33.x sources, IIRC. This directory has been created in my kernel sources directory ever since I upgraded to a 2.6.33.x kernel. It has thrown more than one third-party software compile for a loop, but it seems the upstream providers are 'providing' for it with patches to their sources. In any case, I never knew this directory and its contents existed until I upgraded to a 2.6.33.x kernel and third party sotfware started failing to compile. -- Richard Herbert Registered Linux user 14329 If there's nothing wrong with me, then ... there must be something wrong with the Universe! |