LinuxQuestions.org
Latest LQ Deal: Complete CCNA, CCNP & Red Hat Certification Training Bundle
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-07-2018, 01:21 AM   #16
teoberi
Member
 
Registered: Jan 2018
Location: Romania
Distribution: Slackware64-current (servers) / Ubuntu (workstations)
Posts: 47

Rep: Reputation: 12

Quote:
Originally Posted by allend View Post
This is horseshit. The only person able to update the kernel on a default Slackware system is the system administrator. If the system administrator screws up, there the blame lies.
Totally agree!
On a server system, updates are always installed manually by me with upgradepkg.
Often after updating, some settings need to be reconfigured.
 
Old 06-07-2018, 03:38 AM   #17
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 815

Rep: Reputation: 295Reputation: 295Reputation: 295
How I upgrade the kernel (Slackware-current).

I use lilo, I have two kernels defined. One labeled Slackware, the other labeled LastWorking. Since I happen to agree with "Automated upgrade of kernel packages aren't a good idea" especially with -current, the "kernel" is of course blacklisted. When a new kernel is indicated in ChangeLog.txt I normally take care of all updates first.

Then take care of the kernel. I edit my blacklist file as follows:
Code:
#kernel-generic
#kernel-headers
kernel-huge
#kernel-modules
#kernel-source
Next I use 'slackpkg download kernel' deselect kernel-firmware and download the rest.

Next I edit blacklist again to blacklist the kernel packages.

Next up... installpkg /var/cache/packages/slackware64/a/*.t?z
I repeat with the d and k series

I then remove those downloaded files.

Next I point the symlinks for my "working" kernel to point to the currently running kernel, the new generic kernel links are already pointed correctly from running installpkg.

As a side note: Rather than type to remove links and the link then again, I use mc to edit the links to my working kernel. Ctrl-X, Ctrl-S makes it easy.

Once that is done I run the following:
Code:
mkinitrd -F -k 1.14.47 
mkinitrd -F - k 1.14.44 -s initrd-working-tree -o initrd-working.gz 
lilo
At this point I reboot.

After the reboot, I remove the oldest kernel.

On Slackware 14.2 installs I don't bother with blacklisting (except for huge or generic as applicable). I let slackpkg do it thing, run mkinitrd if needed and then lilo after slackpkg is done, then reboot. I have never had a problem doing this.

I see no need to use upgradepkg to install a kernel. That is what installpkg is for, IMHO.

Last edited by chrisretusn; 06-07-2018 at 02:46 PM.
 
Old 06-07-2018, 12:48 PM   #18
the3dfxdude
Member
 
Registered: May 2007
Posts: 563

Rep: Reputation: 239Reputation: 239Reputation: 239
I need both operations for kernel packages. Sometimes I use installpkg, sometimes I use upgradepkg. Both are important for the chosen task. Intercepting the user intent is bad. Correct execution should be left to the admin, and higher level of automation designed for the system.
 
3 members found this post helpful.
Old 06-08-2018, 05:58 AM   #19
travis82
Member
 
Registered: Feb 2014
Distribution: Slackware
Posts: 424

Rep: Reputation: 199Reputation: 199
I'm using huge kernel and have not had any problem with slackpkg upgrade-all so far. fortunately slackpkg is smart enough to ask for running lilo after every kernel upgrade.
 
Old 06-11-2018, 08:44 PM   #20
slacker1337
Member
 
Registered: Jun 2012
Location: Connecticut, USA
Distribution: Slackware
Posts: 120

Rep: Reputation: 36
I'm not a huge fan of having multiple kernels installed in my systems, so I just upgrade everything. It's only burned me a few times where I've forgotten to rebuild the initrd or re-run lilo. Nothing that couldn't be fixed by booting into the installer from pxe or cdrom.

Quote:
Originally Posted by a4z View Post
seems I did a lot wrong in the past.
always used slackpkg update , slackpkg upgrade-all
if there was a new kernel, it was installed,
manualy boot entry of course, if, than also initrd, but I became lazy recently and boot the huge kernel.
just works, never had any problem,
 
Old 06-12-2018, 04:17 AM   #21
chrisretusn
Member
 
Registered: Dec 2005
Location: Philippines
Distribution: Slackware
Posts: 815

Rep: Reputation: 295Reputation: 295Reputation: 295
Quote:
Originally Posted by slacker1337 View Post
I'm not a huge fan of having multiple kernels installed in my systems, so I just upgrade everything. It's only burned me a few times where I've forgotten to rebuild the initrd or re-run lilo. Nothing that couldn't be fixed by booting into the installer from pxe or cdrom.
Speaking of multiple kernels, I forgot to remove the old ones from the last couple of updates. Thanks for reminding me. I prefer to keep two kernels, the last working kernel and the current kernel. That said, I've only had to boot to the last working kernel maybe twice since I started doing this.

I don't forget to rebuild initrd or run lilo, only because I have in the past so... those two task are deeply burned in to my memory. <grin>

Last edited by chrisretusn; 06-12-2018 at 04:18 AM.
 
  


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] X: "loading extension glx" "no screens found" "fatal server error" (w/ nvidia driver) Geremia Slackware 7 12-29-2014 11:00 AM
upgrade to kernel 2.6.16.1 : "make bzImage" print "parse error" math_physics Red Hat 2 06-29-2007 11:04 PM
How to install/upgrade packages from "unstable" ? rangalo Debian 9 03-13-2007 04:00 AM
Can't install "glibmm" library. "configure" script can't find "sigc++-2.0&q kornerr Linux - General 4 05-10-2005 02:32 PM
how to install the "packages that have been held back" when doing "apt-get upgrade&qu zero79 Debian 5 06-27-2004 08:19 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 03:47 PM.

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