Slackware This 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.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
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.
|
 |
08-23-2013, 07:51 AM
|
#1
|
LQ Newbie
Registered: Oct 2012
Location: SP, Brazil
Distribution: slackware64-current
Posts: 22
Rep: 
|
versions of kernels
Hi,
Which file should I change it to updating the kernel with slackpkg and continue with previous versions? I remember that I can define the number of versions of kernels that would like to keep on the PC.
Sorry for asking but since I tried searching and so far I can not find the file. I remember seeing this tip here.
Thanks,
|
|
|
08-23-2013, 08:57 AM
|
#2
|
LQ 5k Club
Registered: Nov 2002
Location: Somewhere inside 9.9 million sq. km. Canada
Distribution: Slackware 15.0, current, slackware-arm-currnet
Posts: 6,378
|
If I understand you correctly, you are trying to prevent an update to a newer kernel? If yes, then edit the file /etc/slackpkg/blacklist. From that file :
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
|
Hope this helps.
|
|
|
08-23-2013, 09:13 AM
|
#3
|
LQ Newbie
Registered: Oct 2012
Location: SP, Brazil
Distribution: slackware64-current
Posts: 22
Original Poster
Rep: 
|
Hi,
No. I want to upgrade my kernel with slackpkg, keeping previous versions. Are there any files that can not remember which, I choose how many versions I want to keep the pc.
Example: VERSIONS_KERNEL=2****** (keep 2 previous versions)
Thanks.
Last edited by dbfontes; 08-23-2013 at 09:16 AM.
|
|
|
08-23-2013, 09:16 AM
|
#4
|
LQ Newbie
Registered: Oct 2012
Location: SP, Brazil
Distribution: slackware64-current
Posts: 22
Original Poster
Rep: 
|
****It is only an example, this parameter does not exist!
|
|
|
08-23-2013, 09:27 AM
|
#5
|
Senior Member
Registered: Apr 2005
Posts: 2,727
|
If you want a new kernel, you need to download and build it yourself, Alien Bob's guide is all you need:
http://alien.slackbook.org/dokuwiki/...kernelbuilding
If you follow this guide you will be able to keep your old kernel(s). It's a good idea to keep hold of the Slackware generic and huge kernels as backups in case of problems.
(it refers to 2.6.x but is still relevant for 3.x)
|
|
|
08-23-2013, 09:34 AM
|
#6
|
LQ Newbie
Registered: Oct 2012
Location: SP, Brazil
Distribution: slackware64-current
Posts: 22
Original Poster
Rep: 
|
Yes, it is a solution but is not exactly that.
I have the current version and I want to keep some old versions of kernels. There is a file that I set up to keep the old versions after upgrading with slackpkg.
|
|
|
08-23-2013, 09:35 AM
|
#7
|
LQ Newbie
Registered: Oct 2012
Location: SP, Brazil
Distribution: slackware64-current
Posts: 22
Original Poster
Rep: 
|
I'm going crazy, I can not remember what that file.
|
|
|
08-23-2013, 10:14 AM
|
#8
|
LQ Veteran
Registered: Jan 2008
Location: florida panhandle
Distribution: Slackware Debian, Fedora, others
Posts: 7,844
|
Are you sure it was in slackware and not Ubuntu or Debian. If I'm not mistaken both of them have the option to keep only so many kernel versions. In slackware you have to blacklist the kernels as already mentioned then download the new kernel packages manually and install using installpkg to install.
|
|
|
08-23-2013, 11:34 PM
|
#9
|
LQ Veteran
Registered: Feb 2007
Distribution: Slackware64-current with KDE4Town.
Posts: 9,712
|
Quote:
Originally Posted by dbfontes
Hi,
Which file should I change it to updating the kernel with slackpkg...
|
As far as I know, but could be wrong, there is no way to do that "automagically."
You don't want to upgrade a kernel, but installpkg each version, edit lilo.config manually and then run lilo.
|
|
|
08-25-2013, 02:01 PM
|
#10
|
Member
Registered: Jun 2010
Distribution: Slackware Current 64 bit KDE 5
Posts: 380
Rep:
|
I let slackpkg update the kernels for me. I tried switching to the generic kernel, but had issues re-installing the broadcom-sta drivers and decided it was best to just keep the huge kernel and let slackpkg update when an update came out.
|
|
|
08-25-2013, 09:55 PM
|
#11
|
Member
Registered: Nov 2006
Distribution: Slackware
Posts: 294
Rep:
|
slackpkg, if I'm not mistaken, will not allow this setup.
You should just install multiple kernels manually (installpkg) and blacklist the kernel in slackpkg blacklist.
|
|
|
08-26-2013, 10:56 AM
|
#12
|
LQ Newbie
Registered: May 2012
Posts: 11
Rep: 
|
Slackpkg is upgrading kernels just fine. I did it this weekend - the disadvantage is that slackpkg removes the old kernel automatically. So you will need to be sure that the new kernel works on the system. I just forgot to switch to 'init 1' before the upgrade so I had some problems with the modules and needed to fix that by hand.
I also used the opportunity to switch to generic, which worked flawlwssly.
lvdd
|
|
|
08-26-2013, 11:04 AM
|
#13
|
LQ Newbie
Registered: May 2012
Posts: 11
Rep: 
|
hm, on second thought I think I used 'upgradepkg' and used the dry-run option before actually doing it.... It was late...
|
|
|
08-27-2013, 06:32 AM
|
#14
|
Member
Registered: Nov 2007
Posts: 312
Rep:
|
Quote:
Originally Posted by dbfontes
Hi,
Which file should I change it to updating the kernel with slackpkg and continue with previous versions?
|
Read this:
http://www.linuxquestions.org/questi...6/#post4723910
Quote:
Originally Posted by Alien Bob
I always blacklist the kernels and kernel modules. That way a "slackpkg upgrade-all" will leave my existing, working, kernel untouched.
|
The file is /etc/slackpkg/slackpkg.conf
|
|
|
08-27-2013, 06:44 AM
|
#15
|
Member
Registered: Jul 2007
Location: In a van down by the river...
Distribution: MX Linux 21
Posts: 237
Rep:
|
You just want to add the list of kernels available at boot time? Is the file, /etc/lilo.conf, what you are looking for?
|
|
|
All times are GMT -5. The time now is 07:20 PM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|