diff slack/kernel-source vanilla/kernel-source
in [Slackware]
|
From: caio on 12 Apr 2010 19:07 Hi guys, Which differences exist on the provided slackware kernel-source pkg and the vanilla kernel line? I can compare both trees with diff but I want to know which kind of customizations are made on slackware kernel src. Or where can find documentation about it.. For example I see: diff -urN linux-2.6.33.1/include/generated/compile.h usr/src/linux-2.6.33.1/include/generated/compile.h --- a/linux-2.6.33.1/include/generated/compile.h 1969-12-31 21:00:00.000000000 -0300 +++ b/linux-2.6.33.1/include/generated/compile.h 2010-03-26 16:44:11.000000000 -0300 @@ -0,0 +1,9 @@ +/* This file is auto generated, version 1 */ +/* SMP */ +#define UTS_MACHINE "i386" +#define UTS_VERSION "#1 SMP Fri Mar 26 14:44:11 CDT 2010" +#define LINUX_COMPILE_TIME "14:44:11" +#define LINUX_COMPILE_BY "root" +#define LINUX_COMPILE_HOST "midas" +#define LINUX_COMPILE_DOMAIN "slackware.lan" +#define LINUX_COMPILER "gcc version 4.4.3 (GCC) " Thanks your comments, Caio
From: Henrik Carlqvist on 13 Apr 2010 01:52 caio <elcaio(a)gmail.com> wrote: > Which differences exist on the provided slackware kernel-source pkg > and the vanilla kernel line? Usually no differences at all. Slackware prefers to take the kernel unmodified from kernel.org. If there for any reason has to be some patch applied that patch is usually also included in /usr/src to clearly mark that the kernel has been patched and why it has been patched. Such patches has only been included in a few versions of Slackware during the years. > For example I see: > +/* This file is auto generated, version 1 */ Read the above line once again... > +/* SMP */ > +#define UTS_MACHINE "i386" > +#define UTS_VERSION "#1 SMP Fri Mar 26 14:44:11 CDT 2010" > +#define LINUX_COMPILE_TIME "14:44:11" > +#define LINUX_COMPILE_BY "root" > +#define LINUX_COMPILE_HOST "midas" > +#define LINUX_COMPILE_DOMAIN "slackware.lan" > +#define LINUX_COMPILER "gcc version 4.4.3 (GCC) " If you look carefully at those "differences" you will realize that the contents of those lines are not part of the original source code but generated at compile time. The above is the data that you see if you do uname -a or cat /proc/version 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: Emilio Lazardo on 13 Apr 2010 01:58 On Mon, 12 Apr 2010 16:07:06 -0700, caio wrote: > Hi guys, > Which differences exist on the provided slackware kernel-source pkg and > the vanilla kernel line? I can compare both trees with diff but I want > to know which kind of customizations are made on slackware kernel src. > Or where can find documentation about it.. > > For example I see: > > diff -urN linux-2.6.33.1/include/generated/compile.h > usr/src/linux-2.6.33.1/include/generated/compile.h --- > a/linux-2.6.33.1/include/generated/compile.h 1969-12-31 > 21:00:00.000000000 -0300 > +++ b/linux-2.6.33.1/include/generated/compile.h 2010-03-26 > 16:44:11.000000000 -0300 > @@ -0,0 +1,9 @@ > +/* This file is auto generated, version 1 */ +/* SMP */ > +#define UTS_MACHINE "i386" > +#define UTS_VERSION "#1 SMP Fri Mar 26 14:44:11 CDT 2010" +#define > LINUX_COMPILE_TIME "14:44:11" +#define LINUX_COMPILE_BY "root" > +#define LINUX_COMPILE_HOST "midas" > +#define LINUX_COMPILE_DOMAIN "slackware.lan" +#define LINUX_COMPILER > "gcc version 4.4.3 (GCC) " > > Thanks your comments, > Caio 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? With rare and clearly documented exceptions (e.g. CHANGES_AND_HINTS.TXT), such as late breaking security patches, there are no changes to what is available at kernel.org. To illustrate, I used kernel.org incremental patches to get from the Slackware 33.7 kernel source package to 33.11 cleanly (no rejects). Cheers, -- Laugh while you can, etc.
From: Emilio Lazardo on 13 Apr 2010 02:09 On Tue, 13 Apr 2010 05:58:52 +0000, Emilio Lazardo wrote: > On Mon, 12 Apr 2010 16:07:06 -0700, caio wrote: > >> Hi guys, >> Which differences exist on the provided slackware kernel-source pkg and >> the vanilla kernel line? I can compare both trees with diff but I want >> to know which kind of customizations are made on slackware kernel src. >> Or where can find documentation about it.. .... > are no changes to what is available at kernel.org. To illustrate, I > used kernel.org incremental patches to get from the Slackware 33.7 > kernel source package to 33.11 cleanly (no rejects) Make that '32.7 to 32.11'. -- Laugh while you can, etc.
From: caio on 13 Apr 2010 06:23
On Apr 13, 2:52 am, Henrik Carlqvist <Henrik.Carlqv...(a)deadspam.com> wrote: > caio <elc...(a)gmail.com> wrote: > > Which differences exist on the provided slackware kernel-source pkg > > and the vanilla kernel line? > > Usually no differences at all. Slackware prefers to take the kernel > unmodified from kernel.org. If there for any reason has to be some patch > applied that patch is usually also included in /usr/src to clearly mark > that the kernel has been patched and why it has been patched. Such patches > has only been included in a few versions of Slackware during the years. > > > For example I see: > > +/* This file is auto generated, version 1 */ > > Read the above line once again... > > > +/* SMP */ > > +#define UTS_MACHINE "i386" > > +#define UTS_VERSION "#1 SMP Fri Mar 26 14:44:11 CDT 2010" > > +#define LINUX_COMPILE_TIME "14:44:11" > > +#define LINUX_COMPILE_BY "root" > > +#define LINUX_COMPILE_HOST "midas" > > +#define LINUX_COMPILE_DOMAIN "slackware.lan" > > +#define LINUX_COMPILER "gcc version 4.4.3 (GCC) " > > If you look carefully at those "differences" you will realize that the > contents of those lines are not part of the original source code but > generated at compile time. The above is the data that you see if you do > > uname -a > > or > > cat /proc/version Oh I see, yes, it was generated from my machine. Thanks for your answers. 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? Thanks again. Claudio |