LinuxQuestions.org
Share your knowledge at the LQ Wiki.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 05-08-2014, 09:53 AM   #1
czezz
Member
 
Registered: Nov 2004
Distribution: Slackware/Solaris
Posts: 935

Rep: Reputation: 44
Slackware's kernel mystery...


Here is something I dont quite understand with Slackware kernel packages.
Here you can see kernel which is provided as default with Slackware 14.1 installation:

Code:
kernel-generic-3.10.17-x86_64-3.txz	23-Oct-2013 21:29 	3.6M
MD5 Hash: 79a63b9f88ce68282e73d69125846b49
Here, you can see kernel package which is to be found in patch repository for Slackware 14.1
Code:
kernel-generic-3.10.17-x86_64-2.txz	14-Feb-2014 22:40 	3.6M
MD5 Hash: 0ac63878bb367d8565118fec3e41285b
Here is my questions:
The kernel available in patch repository is newer as I can verify that by timestamp 14-Feb-2014 22:40 vs 23-Oct-2013 21:29. However, looking at the naming convention, it seems that that this is actually regression 3.10.17-x86_64-2 vs 3.10.17-x86_64-3.

Its little bit misleading here as I would expect that newer kernel would be greater than 3.
Does anyone know explanation of this ?
 
Old 05-08-2014, 09:55 AM   #2
willysr
Senior Member
 
Registered: Jul 2004
Location: Jogja, Indonesia
Distribution: Slackware-Current
Posts: 4,753

Rep: Reputation: 1856Reputation: 1856Reputation: 1856Reputation: 1856Reputation: 1856Reputation: 1856Reputation: 1856Reputation: 1856Reputation: 1856Reputation: 1856Reputation: 1856
it's a typo indeed, but use the one in patches since it fixed the problem
 
Old 05-11-2014, 09:52 AM   #3
czezz
Member
 
Registered: Nov 2004
Distribution: Slackware/Solaris
Posts: 935

Original Poster
Rep: Reputation: 44
Hi,
thank you for explanation.
However, here is another mystery. Slackware 12 repository: http://mirrors.slackware.com/slackware/slackware-12.0/

Default kernel:
Code:
kernel-generic-smp-2.6.21.5_smp-i686-2.tgz	19-Jun-2007 19:53 	2.2M
iD8DBQBGexqCakRjwEAQIjMRAlNUAJsEsT9zaMNluN2j3Z2HMPyhgQsWhQCZAUN+
tnVjrvEGuXn9jk073CnpZe8=
=vCX9
Most updated kernel for Slack12 available in patch repository:
Code:
kernel-generic-smp-2.6.21.5_smp-i686-2_slack12.0.tgz	11-Feb-2008 23:16 	2.2M
iD8DBQBHsN73akRjwEAQIjMRAvvHAJ4hAEYGj9XaMWPJN8QKpsM/nR2LEQCfd+rH
LPsntnLpESrmct5rBWASpyM=
=0AK8
As you see, looking at name it seems to be this same version 2.6.21.5.
The only what makes me to believe it is not this same file is again timestamp and PGP SIGNATURE.
Is that again typo error ?

Last edited by czezz; 05-11-2014 at 09:54 AM.
 
Old 05-11-2014, 10:46 PM   #4
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860

Rep: Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228
Heaven forbid that you would just look in the Changelog.txt file that's part of all the mirrors.

Code:
+--------------------------+
Mon Feb 11 17:46:22 CST 2008
patches/packages/kernel-generic-2.6.21.5-i486-2_slack12.0.tgz:
  All of these kernel upgrades fix yesterday's local root exploit.
  For more information, see:
    http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-0010
    http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-0163
    http://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2008-0600
  (* Security fix *)
patches/packages/kernel-generic-smp-2.6.21.5_smp-i686-2_slack12.0.tgz:
  (* Security fix *)
patches/packages/kernel-huge-2.6.21.5-i486-2_slack12.0.tgz:
  (* Security fix *)
patches/packages/kernel-huge-smp-2.6.21.5_smp-i686-2_slack12.0.tgz:
  (* Security fix *)
If you use lilo, don't forget to run it again after the upgrade.
+--------------------------+
and
Code:
+--------------------------+
Thu Jun 21 19:37:47 CDT 2007
Still working through the pile, so if you don't see your bug report fixed yet,
it could still be coming.  But, we figured these things should get tested
sooner rather than later.  :-)
a/aaa_elflibs-12.0.0-i486-2.tgz:  Upgraded expat library.
a/cryptsetup-1.0.5-i486-2.tgz:  Fixed locale directory.
  Thanks to Robby Workman, Greg' Ar Tourter, Cristian Contescu, and Selkfoster.
a/glibc-solibs-2.5-i486-4.tgz:  Recompiled.
a/glibc-zoneinfo-2.5-noarch-4.tgz:  Rebuilt.
a/gettext-0.16.1-i486-3.tgz:  Rebuilt.
a/kernel-generic-2.6.21.5-i486-2.tgz:
  Recompiled Linux 2.6.21.5 single processor generic.s (requires initrd) kernel.
a/kernel-generic-smp-2.6.21.5_smp-i686-2.tgz:
  Recompiled Linux 2.6.21.5 SMP gensmp.s (requires initrd) kernel.
a/kernel-huge-2.6.21.5-i486-2.tgz:
  Recompiled Linux 2.6.21.5 single processor huge.s (full-featured) kernel.
a/kernel-huge-smp-2.6.21.5_smp-i686-2.tgz:
  Recompiled Linux 2.6.21.5 SMP hugesmp.s (full-featured) kernel.
a/kernel-modules-2.6.21.5-i486-2.tgz
  Recompiled Linux 2.6.21.5 UP single processor kernel modules.
a/kernel-modules-smp-2.6.21.5_smp-i686-2.tgz
  Recompiled Linux 2.6.21.5 SMP kernel modules.
d/kernel-headers-2.6.21.5_smp-i386-2.tgz:
  Rebuilt Linux 2.6.21.5 SMP kernel headers.
a/pkgtools-12.0.0-noarch-2.tgz:  Added rc.snmpd to the services setup menu in
  the installer.
a/shadow-4.0.3-i486-14.tgz:  Added plugdev to the list of groups that a user
  logging in through /bin/login at the console will automatically be added to.
  With a login manager such as kdm, users will still need to be added to
  the plugdev group manually.
ap/vim-7.1.012-i486-1.tgz:  Upgraded to vim-7.1.012.
d/gettext-tools-0.16.1-i486-3.tgz:  Added back "archive.tar.gz" which is not
  useless and is required in some cases by the autotools.  If anyone else
  notices any more "useless" stuff being installed by "make install", please
  inquire with the developers of the upstream source before requesting that
  it be removed.  Thanks.  :-)
k/kernel-source-2.6.21.5_smp-noarch-2.tgz
  Rebuilt the Linux 2.6.21.5 SMP kernel source, removing the
  CONFIG_HEADERS_CHECK option.  Thanks to Cardoe in #hal for cluing us in
  that there were some problems with trying to use the headers found in
  /usr/src/linux/usr/include as the userspace headers under /usr/include,
  such as a missing "#define SG_FLAG_LUN_INHIBIT 2" in scsi/sg.h.
kde/amarok-1.4.6-i486-1.tgz:  Upgraded to amarok-1.4.6.
l/esound-0.2.38-i486-1.tgz:  Upgraded to esound-0.2.38.
l/expat-2.0.1-i486-1.tgz:  Upgraded to expat-2.0.1.
l/gamin-0.1.8-i486-2.tgz:  Changed options to --disable-dnotify and
  --enable-inotify, which is a superior filesystem tracking method on
  2.6.13+ kernels.  Thanks to Andrey V. Panov.
l/glibc-2.5-i486-4.tgz:  Recompiled against the correct 2.6.21.5 headers.
l/glibc-i18n-2.5-noarch-4.tgz:  Rebuilt.
l/glibc-profile-2.5-i486-4.tgz:  Recompiled.
l/libglade-2.6.1-i486-1.tgz:  Upgraded to libglade-2.6.1.
l/mhash-0.9.9-i486-1.tgz:  Upgraded to mhash-0.9.9.
n/mcabber-0.9.3-i486-1.tgz:  Upgraded to mcabber-0.9.3.
n/net-snmp-5.4-i486-5.tgz:  Recompiled without the --enable-reentrant which
  was causing snmpd to not work.  Added a more simple, Slackware-like rc.snmpd.
  Thanks to Piter Punk for fixing this.
n/network-scripts-12.0-noarch-1.tgz:  Rebuilt to include the better-commented
  rc.inet1.conf that was added to source/n/network-scripts/ back in May.
  Thanks to Eric Hameleers for noticing that the package never got a rebuild
  after that change.
xap/pan-0.131-i486-1.tgz:  Upgraded to pan-0.131.
xap/pidgin-2.0.2-i486-1.tgz:  Upgraded to pidgin-2.0.2.
xap/vim-gvim-7.1.012-i486-1.tgz:  Upgraded to vim-7.1.012 for GTK+.
  This also requires the main VIM package...
extra/linux-2.6.21.5-nosmp-sdk/:  Upgraded the kit to transform the Linux
  kernel sources in /usr/src/linux/ from SMP to non-SMP without having to
  recompile them.  NOTE:  it is probably best to use the SMP kernel even in
  a single processor machine if it will run.  The non-SMP kernels should
  really be used only in machines that are not at least a Pentium-Pro, or
  that (for some other reason) will not properly run the SMP kernel.
kernels/hugesmp.s/*:  Recompiled the hugesmp.s 2.6.21.5 SMP kernel.
kernels/huge.s/*:  Recompiled the huge.s 2.6.21.5 single processor kernel.
kernels/speakup.s/*:  Updated speakup from CVS (2007-06-20) and recompiled.
testing/packages/gutenprint-5.0.1-i486-1.tgz:  Upgraded to gutenprint-5.0.1.
+--------------------------+
So, yeah, I guess that Pat forgot to increment the build number.

Since we are discussing Slackware 12.0, I'll also quote
Code:
+--------------------------+
Thu Jun 14 05:02:39 UTC 2012
####################################################################
# NOTICE OF INPENDING EOL (END OF LIFE) FOR OLD SLACKWARE VERSIONS #
#                                                                  #
# Effective August 1, 2012, security patches will no longer be     #
# provided for the following versions of Slackware (which will all #
# be more than 5 years old at that time):                          #
# Slackware 8.1, 9.0, 9.1, 10.0, 10.1, 10.2, 11.0, 12.0.           #
# If you are still running these versions you should consider      #
# migrating to a newer version (preferably as recent as possible). #
# Alternately, you may make arrangements to handle your own        #
# security patches.  If for some reason you are unable to upgrade  #
# or handle your own security patches, limited security support    #
# may be available for a fee.  Inquire at security@slackware.com.  #
####################################################################
 
Old 05-12-2014, 01:41 PM   #5
czezz
Member
 
Registered: Nov 2004
Distribution: Slackware/Solaris
Posts: 935

Original Poster
Rep: Reputation: 44
Thank Heaven and Richard for changlog

I understand that Slack 12 is end of life. However, what I want to do, is to patch my installation as much as I can.
First, I was thinking just to use latest kernel package from patch repository.
But now Im thinking to compile a new kernel and here is my new mystery:


1. I was thinking to use last 2.6.21 kernel source from kernel.org archive: https://www.kernel.org/pub/linux/kernel/v2.6/
That would be probably the most painless way forward.
But here I can see that the latest 2.6.21 is dated: 26-Apr-2007 03:23 and has no subversion. Am I looking in a wrong place or the kernel.org archival is incomplete ?
(I was hoping to play little bit around and create tgz package)

2. What should stop me to go with last longterm 2.6.32.61 or even 3.12.19. Dependencies and... what else ?
3. As I guess point 2 is impossible or very painful, what would be the latest kernel version I can compile and apply pain-free for Slack 12 ?
 
Old 05-12-2014, 03:13 PM   #6
Richard Cranium
Senior Member
 
Registered: Apr 2009
Location: McKinney, Texas
Distribution: Slackware64 15.0
Posts: 3,860

Rep: Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228Reputation: 2228
Quote:
Originally Posted by czezz View Post
Thank Heaven and Richard for changlog
Thank Pat. It's his changelog.

Quote:

I understand that Slack 12 is end of life. However, what I want to do, is to patch my installation as much as I can.
First, I was thinking just to use latest kernel package from patch repository.
But now Im thinking to compile a new kernel and here is my new mystery:


1. I was thinking to use last 2.6.21 kernel source from kernel.org archive: https://www.kernel.org/pub/linux/kernel/v2.6/
That would be probably the most painless way forward.
But here I can see that the latest 2.6.21 is dated: 26-Apr-2007 03:23 and has no subversion. Am I looking in a wrong place or the kernel.org archival is incomplete ?
(I was hoping to play little bit around and create tgz package)

2. What should stop me to go with last longterm 2.6.32.61 or even 3.12.19. Dependencies and... what else ?
3. As I guess point 2 is impossible or very painful, what would be the latest kernel version I can compile and apply pain-free for Slack 12 ?
OK, you'll have to look at the file Documentation/Changes that is part of the kernel source to see what the minimum version of various libraries that are required by the kernel to compile/run. If Slack 12 has those versions or later, then you should be able to compile/run the kernel you want to use.

For instance, the kernel used by Slackware 14.1 requires...
Code:
Current Minimal Requirements
============================

Upgrade to at *least* these software revisions before thinking you've
encountered a bug!  If you're unsure what version you're currently
running, the suggested command should tell you.

Again, keep in mind that this list assumes you are already functionally
running a Linux kernel.  Also, not all tools are necessary on all
systems; obviously, if you don't have any ISDN hardware, for example,
you probably needn't concern yourself with isdn4k-utils.

o  Gnu C                  3.2                     # gcc --version
o  Gnu make               3.80                    # make --version
o  binutils               2.12                    # ld -v
o  util-linux             2.10o                   # fdformat --version
o  module-init-tools      0.9.10                  # depmod -V
o  e2fsprogs              1.41.4                  # e2fsck -V
o  jfsutils               1.1.3                   # fsck.jfs -V
o  reiserfsprogs          3.6.3                   # reiserfsck -V
o  xfsprogs               2.6.0                   # xfs_db -V
o  squashfs-tools         4.0                     # mksquashfs -version
o  btrfs-progs            0.18                    # btrfsck
o  pcmciautils            004                     # pccardctl -V
o  quota-tools            3.09                    # quota -V
o  PPP                    2.4.0                   # pppd --version
o  isdn4k-utils           3.1pre1                 # isdnctrl 2>&1|grep version
o  nfs-utils              1.0.5                   # showmount --version
o  procps                 3.2.0                   # ps --version
o  oprofile               0.9                     # oprofiled --version
o  udev                   081                     # udevd --version
o  grub                   0.93                    # grub --version || grub-install --version
o  mcelog                 0.6                     # mcelog --version
o  iptables               1.4.2                   # iptables -V

Last edited by Richard Cranium; 05-12-2014 at 03:14 PM.
 
1 members found this post helpful.
Old 05-15-2014, 09:25 AM   #7
czezz
Member
 
Registered: Nov 2004
Distribution: Slackware/Solaris
Posts: 935

Original Poster
Rep: Reputation: 44
Brilliant! Thats very useful
I have checked my Slack12 and it seems softwares are with lower version fsck and iptables.
I will try to compile minimum version for it and will see if that works.

Code:
gcc (GCC) 4.1.2
GNU Make 3.81
GNU ld (Linux/GNU Binutils) 2.17.50.0.17.20070615
fdformat from util-linux-2.12r
module-init-tools 3.2.2
e2fsck 1.39 (29-May-2006)
fsck.jfs version 1.1.11, 05-Jun-2006
xfs_db version 2.8.16
pppd version 2.4.4
showmount for 1.1.0
procps version 3.2.7
oprofiled: oprofile 0.9.2 compiled on Jun 24 2007 02:04:01
udevinfo, version 111
iptables v1.3.8

Anyway, mysteries are gone now, thanks
 
Old 05-25-2014, 11:03 AM   #8
czezz
Member
 
Registered: Nov 2004
Distribution: Slackware/Solaris
Posts: 935

Original Poster
Rep: Reputation: 44
So, I managed successfully to add to my Slack12, kernel 2.6.32.62 which is the latest currently available 2.6.x with long term support.

Here is what I did:
1. I re-aligned all software that was outdated for this kernel
- built up e2fsprogs 1.41.4 from sources using for that SlackBuild available with Slackware 12. Had to modify it slightly
- built up iptables 1.4.2 from sources. Here SlackBuild available in Slackware 12 was not helpful at all. But the one from Slackware 12.2 worked perfectly. Probably I would have skipped SlackBuild and use iptables package available for Slack 12.2 but oh well… more fun for me
2. Then compiled kernel:
- compiled kernel 2.6.32.62 using Eric's lazy-guide: http://alien.slackbook.org/dokuwiki/...kernelbuilding (Thanks Eric). I decided to skip building package for kernel as compiling procedure introduced under that link is pretty straight forward.

All went painless and seems to work OK.
Next step is to try with latest 3.x kernel
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware Current Mystery Boot Messages Woodsman Slackware 3 11-26-2008 02:01 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:36 PM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration