LinuxQuestions.org
Go Job Hunting at the LQ Job Marketplace
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 06-19-2013, 08:52 AM   #1
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,960

Rep: Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976
Keep kernel-* packages for 3.2.29 and 3.2.45 side by side?


Hi,

I'm normally using slackpkg to keep my machines upgraded (on Slackware stable). Now recently there have been two consecutive kernel upgrades, with all the kernel-* 3.2.29 packages replaced by kernel-* 3.2.45 packages.

On a "normal" machine I don't care if the old kernel-* packages are replaced by the updates. But I'm running a few virtual machines as "build boxes", and I'd like to keep the old and the new kernel installed, to be able to boot on both, in order to build kernel modules for machines still running the 3.2.29 kernel.

In other words, is there a way to make Slackware behave like a RHEL/CentOS machine, where 'yum upgrade' updates all packages except the kernel packages, where new packages are merely installed alongside older versions?

Cheers,

Niki
 
Old 06-19-2013, 09:36 AM   #2
Didier Spaier
Senior Member
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slackware{,64}-{14.1,current} on a Lenovo Thinkpad W520
Posts: 4,676

Rep: Reputation: 1239Reputation: 1239Reputation: 1239Reputation: 1239Reputation: 1239Reputation: 1239Reputation: 1239Reputation: 1239Reputation: 1239
I'd try to blacklist kernels in /etc/slackpkg/blacklist but when an upgrade shows, install it (kernel+ modules) with installpkg or slackpkg install (neither upgradepkg nor slackpkg upgrade, of course). In addition you will just have to change the stanza in /etc/lilo.conf to give the full path of the old kernel instead of /boot/vmlinuz before running lilo manually. Then I think that you would just have to set the kernel against which you build the new modules as a build option.

OT: I need a proofreader for French translation of Slackware scripts' messages in slint. And I know that you would catch any typo, mistranslation or clumsiness

Last edited by Didier Spaier; 06-19-2013 at 09:51 AM.
 
Old 06-19-2013, 09:56 AM   #3
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 5,393

Rep: Reputation: Disabled
http://docs.slackware.com/howtos:sla...ystemupgrade?s[]=kernel&s[]=installpkg#considerations_about_the_kernel

Always use installpkg for kernel and kernel-modules. Blacklist them in /etc/slackpkg.conf .

Eric
 
Old 06-19-2013, 11:58 AM   #4
GazL
Senior Member
 
Registered: May 2008
Posts: 3,503

Rep: Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026Reputation: 1026
One trick I use in order to help in not having any upgradepkg accidents with my home-grown kernel packages is to slightly modify the package name so that the version number is included in the package name field and not the version field, i.e.
kernel-3.9.6-custom-none-x86_64-1_local

Doing it this way means I can use "upgradepkg --install-new *" without fear of a new kernel clobbering the old one.

Last edited by GazL; 06-19-2013 at 12:01 PM.
 
Old 06-19-2013, 12:10 PM   #5
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,960

Original Poster
Rep: Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976
Quote:
Originally Posted by Didier Spaier View Post
OT: I need a proofreader for French translation of Slackware scripts' messages in slint. And I know that you would catch any typo, mistranslation or clumsiness
Yeah I can do that. Just send me all the files by mail, Didier.

info@microlinux.fr
 
Old 06-19-2013, 12:12 PM   #6
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,960

Original Poster
Rep: Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976
Quote:
Originally Posted by Alien Bob View Post
http://docs.slackware.com/howtos:sla...ystemupgrade?s[]=kernel&s[]=installpkg#considerations_about_the_kernel

Always use installpkg for kernel and kernel-modules. Blacklist them in /etc/slackpkg.conf .

Eric
Thanks, Eric. According to the documentation, I've been living dangerously until now. I've been using slackpkg upgrade-all to upgrade even the kernel, then hardcoded the kernel version in mkinitrd.conf and rebuilt the initrd before the first reboot.

I'll mark this thread as solved.
 
Old 06-19-2013, 03:28 PM   #7
digger95
Member
 
Registered: Oct 2007
Location: Indiana, PA
Distribution: Slackware 14
Posts: 330

Rep: Reputation: 45
I have my kernel packages blacklisted in /etc/slackpkg/blacklist to keep them from being overwritten but there are two instances where I do allow slackpkg to upgrade them for me. Firstly if I have just performed a clean install the first thing I do is update the system anyway and since I haven't yet even switched to the generic kernel I go ahead and let slackpkg upgrade my kernel. It just makes for a more clean and tidy install for me. Secondly, if the upgrade is to the same kernel version like recently... 3.2.45(1) to 3.2.45(2) to 3.2.45(3) I will go ahead and allow slackpkg to upgrade it.
 
Old 06-20-2013, 01:13 AM   #8
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,960

Original Poster
Rep: Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976
Now this is strange. On a machine running the stock 3.2.29 kernel from the installation disc, I downloaded the updated kernel sources from patches/linux3.2.45 and tried to install them manually using installpkg.

Here's what I get:

Code:
[root@virtualbox:packages] # ls
kernel-source-3.2.45_smp-noarch-3.txz
[root@virtualbox:packages] # installpkg kernel-source-3.2.45_smp-noarch-3.txz 
Verifying package kernel-source-3.2.45_smp-noarch-3.txz.
xz: (stdin): File format not recognized
Installing package kernel-source-3.2.45_smp-noarch-3.txz:
PACKAGE DESCRIPTION:
WARNING:  Package has not been created with 'makepkg'
Package kernel-source-3.2.45_smp-noarch-3.txz installed.
Any idea what's going on here?
 
Old 06-20-2013, 01:30 AM   #9
ruario
Senior Member
 
Registered: Jan 2011
Location: Oslo, Norway
Distribution: Slackware
Posts: 1,902

Rep: Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963Reputation: 963
Partial download perhaps? Check the md5sum and/or signature.

Edit: In fact you should always do that before you install a package you manually downloaded. Slackpkg would have done that but since you aren't using it in this case it is up to you.

Last edited by ruario; 06-20-2013 at 01:37 AM.
 
1 members found this post helpful.
Old 06-20-2013, 01:55 AM   #10
kikinovak
Senior Member
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: Slackware, Slackware64
Posts: 1,960

Original Poster
Rep: Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976Reputation: 976
Quote:
Originally Posted by ruario View Post
Partial download perhaps? Check the md5sum and/or signature.
OK, found the culprit. Wrong md5sum. I re-downloaded the package from another mirror, and everyting worked fine.
 
  


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
[SOLVED] Generate SPECIAL alphanumeric WORDLIST - no repeating characters side-by-side Stanley_212 Programming 30 08-17-2013 12:39 PM
Side-by-side install of multiple versions of packages from source into /opt deskt0plinux Linux - Newbie 2 09-07-2012 02:50 AM
Mounting multiple NFS or Samba shares: client-side or server-side? mariogiov Linux - Server 4 04-03-2012 09:11 AM
LXer: Comparing Kernel Dmesgs: Remove Timing Info and Diff Side by Side LXer Syndicated Linux News 0 08-04-2010 08:31 PM


All times are GMT -5. The time now is 08:40 AM.

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
identi.ca: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration