How upgrade the 13.37 to Current if my actual kernel is 3.4.4?
SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
if you make sure there's _no_kernel_ showing in /var/log/packages, and run a mass updatepkg, wouldn't you be ok? Make sure you can rescue yourself (BACKUP) before you try it.
If you were planning to use slackpkg to upgrade to -current just edit /etc/slackpkg/blacklist which tells slackpkg which packages to leave alone. From /etc/slackpkg/blacklist :
Quote:
# Automated upgrade of kernel packages aren't a good idea (and you need to
# run "lilo" after upgrade). If you think the same, uncomment the lines
# below
#
#kernel-firmware
#kernel-generic
#kernel-generic-smp
#kernel-headers
#kernel-huge
#kernel-huge-smp
#kernel-modules
#kernel-modules-smp
#kernel-source
It's pretty straightforward. Now as far as how the system will run, my guess is it will run just fine, but there's only one way to know for sure..........
Check installed kernel packages, for example: "ls -l /var/log/packages/ | grep kernel"
if the output is blank you don't have any kernel packages installed, so "slackpkg upgrade-all" will no download and install kernel and you will still have 3.4.4.
If you have kernel packages installed slackpkg will download and install kernel version 3.2.21 and overwrite yours /boot/vmlinuz kernel image.
The safest way is to blacklist kernel packages (just edit the /etc/slackpkg/blacklist file and uncoment lines with "kernel")
Check installed kernel packages, for example: "ls -l /var/log/packages/ | grep kernel"
if the output is blank you don't have any kernel packages installed, so "slackpkg upgrade-all" will no download and install kernel and you will still have 3.4.4.
If you have kernel packages installed slackpkg will download and install kernel version 3.2.21 and overwrite yours /boot/vmlinuz kernel image.
The safest way is to blacklist kernel packages (just edit the /etc/slackpkg/blacklist file and uncoment lines with "kernel")
Quote:
Originally Posted by ReaperX7
The only kernel package you NEED to update is the kernel-headers for GLIBC. The rest can be safely ignored unless you have built other kernel modules.
I have these packages installed but comes from the old kernel (now i'm using 3.4.4)..Still I using it?
Code:
root@Hackslack:/home/alchemik# ls -l /var/log/packages/ | grep kernel
-rw-r--r-- 1 root root 6134 Jun 27 19:29 kernel-firmware-2.6.37.6-noarch-2
-rw-r--r-- 1 root root 1010 Jun 27 19:29 kernel-generic-2.6.37.6-x86_64-2
-rw-r--r-- 1 root root 21062 Jun 27 19:32 kernel-headers-2.6.37.6-x86-2
-rw-r--r-- 1 root root 1007 Jun 27 19:29 kernel-huge-2.6.37.6-x86_64-2
-rw-r--r-- 1 root root 176299 Jun 27 19:30 kernel-modules-2.6.37.6-x86_64-2
-rw-r--r-- 1 root root 2299643 Jun 27 19:33 kernel-source-2.6.37.6-noarch-2
Last edited by Alchemikos; 07-03-2012 at 07:58 PM.
Unless you update glibc you don't need to install the new kernel headers from the FTP. These two packages are tied together and each version is built just for that specific version of the kernel released with Slackware.
For kernel-generic, huge, modules and source you can safely remove them since you are running 3.4.4. For headers and firmware you should upgrade them when you upgrade to current.
Actually, I don't think that upgrading the other kernel packages should cause a problem either as long as you don't use /boot/vmlinuz as a link to your 3.4.4 kernel. When you install/upgrade the install copies the new kernels into /boot and changes the symbolic link /boot/vmlinuz to point to the new kernel. lilo uses /boot/vmlinuz, that way lilo.conf does not need to be updated when upgrading slackware kernels.
Personally I do not create a symbolic link for my non-slack kernels but rather in lilo I specify the kernel directly. That way I don't care what /boot/vmlinuz points to and it is easier to have multiple kernels installed at the same time.
Im running kernel 3.4.1 with no problem. After you install the 3.4 kernel uncheck all the kernel packages when you update thereafter. If you are using lilo its pretty easy to boot different kernel images. Here is an excerpt from my lilo.conf:
If you arent naming your kernel image and system.map vmlinuz and System.map, just make sure that the version numbers are appended to vmlinuz and System.map and that the version numbers match the version numbers for the /lib/modules dir for that kernel.
You need the GPG key of Slackware Linux Project <security@slackware.com>.
To download and install that key, run:
# slackpkg update gpg
You can disable GPG checking too, but it is not a good idea.
To disable GPG, edit slackpkg.conf and change the value of the CHECKGPG
variable to off - you can see an example in the original slackpkg.conf.new
file distributed with slackpkg.
What were the exact steps you made to upgrade the system and when exactly did you get errors?
There shouldn't be incompatibilities with the newer kernel.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
