New kernel in current

hua · 03-09-2011, 02:44 PM

I've been building my new kernel 2.6.37.3 (actually completed the compilation) from the kernel.org source and when I get to osuosl.org.
What did I see there?
A new kernel package.

Still I want to give a chance to my new kernel. But I am a little new in this so I have few questions.

1. Do I need to upgrade my glibc shared libraries?

Quote:

2. Upgrade your glibc shared libraries. This is important, or things
might go haywire during the next part of the upgrade:

upgradepkg /root/slackware/a/glibc-solibs-*.t?z

2. Do I need to upgrade anything else before I reboot? (I don't mean my initrd or lilo here, but some additional packages)

Quote:

1. Upgrade your package utilities and related tools:

upgradepkg /root/slackware/a/pkgtools-*.tgz
upgradepkg /root/slackware/a/tar-*.tgz
installpkg /root/slackware/a/xz-*.tgz
upgradepkg /root/slackware/a/findutils-*.txz

(Sorry if my questions are stupid?)

piratesmack · 03-09-2011, 02:58 PM

I followed steps 0, 1, and 2 in UPGRADE.TXT, then used Slackpkg to upgrade the rest.
Worked well for me

EDIT:

Oh, are you on 13.1 trying to use the kernel from current?

The kernel from current may not work on 13.1, but I have done this successfully in the past. You only have to install the kernel-smp and kernel-modules-smp packages.

I suggest you install the new kernel with "installpkg" and not "upgradepkg", so you have the old kernel to fall back on if it doesn't work.

hua · 03-09-2011, 03:42 PM

Actually I started compile from the "vanila source" (hope I used the right word). I was checking yesterday (or a day before) the current and there was some older kernel. So I decided to give a try to compile it from the source. I used this link:
http://muaythaimaster74.blogspot.com...re-kernel.html
And many others to get some insight.

GazL · 03-09-2011, 05:07 PM

hehe. Yep, Pat usually manages to do that to me too. Day after I build a kernel, he'll release a new one.

I was initially happy that Slackware was sticking with the long-term 35.y kernels, but given how long this release has been maturing, I think Pat's made the correct choice moving forward this time.

Running RC1 here. Everything seems ok so far, but I'm not a KDE user, so I don't have as much exposure as others.

wargus · 03-09-2011, 07:24 PM

Quote:

Running RC1 here. Everything seems ok so far

Here too... had update issues, but I guess I just started during my mirror was syncing

now it's running fine (though it's only a headless system)

hitest · 03-09-2011, 07:28 PM

The latest -current updates are looking good. We are at RC1! Woot.

Code:

Linux valhalla 2.6.37.3-smp #2 SMP Mon Mar 7 21:10:03 CST 2011 i686 Intel(R) Pentium(R) D CPU 2.80GHz GenuineIntel GNU/Linux

willysr · 03-09-2011, 09:33 PM

no problem on RC 1 here

hua · 03-10-2011, 06:05 AM

Well ... it works!

Quote:

Linux stardust 2.6.37.3-smp #1 SMP Thu Mar 10 12:19:04 CET 2011 i686 Pentium(R) Dual-Core CPU E5200 @ 2.50GHz GenuineIntel GNU/Linux

hitest, I noticed that you have 2.6.37.3-smp #2. What is the #2 a patch??

It is interesting that everything else is still from 13.1. KDE is running, all I had to do was reinstalling the NVIDIA driver. I think my sound is off two but everything else seems to work.

I am thinking right now about - it is possible to run just like this?? What will happen if I don't upgrade the other packages (applications). My cause it some problem in long term.
Its clear to me that new versions of applications are improved so it is useful to upgrade them, but anyway.