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
 
LinkBack Search this Thread
Old 01-23-2010, 10:35 AM   #1
Crashbox
Member
 
Registered: Jun 2004
Location: USA
Distribution: Slackware
Posts: 136

Rep: Reputation: 21
Upgrading Slackware64 Kernel Packages


Alright, so I have a question that might sound weird, but allow me to explain.

I have a Slackware64 system (full install) which I've kept current through Dec 19, 2009. The changelog entry for Jan 4th (and the subsequent one on Jan 9th) are a bit more than standard upgrades, as Pat pointed out.

As an experienced Slacker (6+ years) the changes required regarding IDE drives isn't really a big deal, but I decided to go ahead and follow Robbie's howto (he and AlienBob really need to be on the Slackware payroll, IMHO BTW). My root and home partitions are on an IDE hard drive and I have an optical drive and 2nd hard drive on SATA.

It's the first step of the howto that has caused me pause though:

Code:
1. Upgrade the kernel and kernel-modules packages normally.
That sounds simple except that day-to-day, I don't run a stock Slackware kernel. I compile and run my own and always have. As I look back on my history with Slackware, I don't think I've ever upgraded kernel packages once I got a system up and running. When there's been big changes (2.4 to 2.6, for example), I've done a full re-install.

Most recently when I made the jump to 64bit, I did a full install using the huge.s kernel and once everything worked, I downloaded the current source from kernel.org and was on my way. I haven't booted huge.s since that day.

I do, of course, know how to upgrade my own custom kernel, but I like having huge.s installed as a backup. If I upgrade gcc/glibc, compile a new custom kernel and update lilo.conf/fstab without upgrading huge.s, then I will be left with only one working kernel.

So, my question is: is it simply a matter of running upgradepkg on the 6 kernel packages (headers, modules, firmware, generic, huge and source)? or is there more to it than that..ie, what about the system maps and symlinks in /boot?
 
Old 01-23-2010, 06:00 PM   #2
GazL
Senior Member
 
Registered: May 2008
Posts: 3,231

Rep: Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828Reputation: 828
That's about the size of it. upgradepkg or installpkg your new kernel packages and then edit things like /etc/fstab to reflect the new devices names as per Robby's howto.

The system.map and config files and symlinks under /boot aren't actually used for anything (Don't confuse them with /boot/map though, which is part of lilo). I think they're there for debugging/documentation purposes more than anything else.

One thing I do is avoid using the vmlinuz symlink in /boot. Explicitly specifying both kernel and a version tagged initrd in lilo.conf, like such:
Code:
image = /boot/vmlinuz-generic-2.6.32.5
  initrd = /boot/initrd-2.6.32.5.gz
  root = /dev/rootvg/lvroot
  label = Linux64
  read-only
It allows for a nice clean backout as you can have multiple versions in your lilo, just incase you cock something up.

Once up and running on the new kernel, you can then removepkg the old ones.

Last edited by GazL; 01-23-2010 at 06:05 PM.
 
1 members found this post helpful.
Old 01-28-2010, 12:12 PM   #3
Crashbox
Member
 
Registered: Jun 2004
Location: USA
Distribution: Slackware
Posts: 136

Original Poster
Rep: Reputation: 21
Thank you. Sometimes you just need confirmation from someone else.

I agree regardign the vmlinuz symlink. As long as you edit lilo to point to the correct vmlinuz-2.6.XX file, it shouldn't be a problem. Eliminating the use of it has been on my list of "things to do the next time I fiddle with my kernel" for some time now.

I'm going to mark this one 'Solved' even though I haven't actually done the upgrade yet (things got really busy at work really quickly). Chances are if I end it with a problem, I will have fouled things up so bad as to justify a new thread.
 
  


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
Trackbacks are Off
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware64 current multilib, do the 32 bit packages need to be updated as well? damgar Slackware 11 02-01-2010 11:08 AM
Kernel panic after upgrading slackware64-current to 2.6.32.x kernel Lenard Spencer Slackware 4 01-22-2010 10:54 AM
The steps likely required for upgrading Slackware to Slackware64. Shingoshi Slackware 49 08-29-2009 07:28 AM
Getting packages for Slackware64-current. glore2002 Slackware 13 08-25-2009 06:28 PM
Packages from Slamd64 who work into Slackware64 ROXR Slackware 2 07-13-2009 01:13 AM


All times are GMT -5. The time now is 04:27 PM.

Main Menu
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