LinuxQuestions.org
Help answer threads with 0 replies.
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 01-09-2018, 07:08 AM   #16
kjhambrick
Senior Member
 
Registered: Jul 2005
Location: Round Rock, TX
Distribution: Slackware64 14.2 + Multilib
Posts: 1,313

Rep: Reputation: 707Reputation: 707Reputation: 707Reputation: 707Reputation: 707Reputation: 707Reputation: 707

Quote:
Originally Posted by Lysander666 View Post
Thank you for that. I do indeed have a mounted partition for root!

Is that done via clean-system? I took a look at it yesterday but it listed what I thought was a lot of compiled packages in /tmp, and I want to keep those for the moment.
Lysander666 --

Sorry, I don't know `clean-system` ?

I do my cleanup the old way via rm or mv ...

-- kjh
 
Old 01-09-2018, 07:23 AM   #17
GazL
Senior Member
 
Registered: May 2008
Posts: 4,714
Blog Entries: 13

Rep: Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212Reputation: 2212
Quote:
Originally Posted by Lysander666 View Post
One more thing I am confused about though - the upgrade section of Slackdocs says "never upgrade your working kernel", as written by Eric Hameleers.

https://docs.slackware.com/howtos:sl...:systemupgrade


I suppose this is just precautionary but still, 'never upgrade' seems pretty strong wording! Or does the 'working kernel' here refer to not upgrading beyond 4.4.xx for 14.2?
What he's saying is don't upgrade in-place the kernel/modules you're currently booted from. And here's just one small example of why it's a bad idea;

A while back someone who shall remain nameless thought sod it, I'll be lazy and I'll just do upgradepkg kernel-generic* kernel-modules*, He fired off the command and all seemed to be going well: it deleted all the old images and modules and installed the new. He built the initrd for the new kernel without problem and then went to copy them to the /boot/efi partition.
"mount /boot/efi" said he.
"vfat module not found" said the kernel.
"Oh fiddle-sticks, ain't I a clever one!" said he.

Another issue with taking such shortcuts is that if the machine had crashed during any point of the above, it would have been left unbootable.


Best to do it properly: install new, configure new, reboot new, remove old; and avoid any such silliness.


And yes, it was I.


P.S. I've never used slackpkg. I prefer to do it manually (albeit with a little help from a few scripts to take the hard work out of it).

Last edited by GazL; 01-09-2018 at 07:25 AM.
 
4 members found this post helpful.
Old 01-09-2018, 01:23 PM   #18
ChuangTzu
Member
 
Registered: May 2015
Location: Where ever needed
Distribution: Slackware/Salix, Devuan, FreeBSD
Posts: 809

Rep: Reputation: 582Reputation: 582Reputation: 582Reputation: 582Reputation: 582Reputation: 582
and now you notice the level of advice and help Slackers provide.
https://docs.slackware.com/howtos:slackware_admin:start

PS: clean-system will remove any non Slackware packages, ie: SBo, third party packages etc... use with caution.
https://slackpkg.org/documentation.html
https://docs.slackware.com/slackware:slackpkg
 
Old 01-09-2018, 01:37 PM   #19
Lysander666
Member
 
Registered: Apr 2017
Location: London
Distribution: Debian, Slackware
Posts: 350

Original Poster
Rep: Reputation: 186Reputation: 186
Quote:
Originally Posted by SavoTU View Post
I can see how this can be confusing, to install Slackware packages you use installpkg and to upgrade them upgradepkg.

To upgrade your kernel use installpkg this will then install the new kernel without touching the old one so if anything goes wrong you still have a working machine.
I upgraded the kernel with

#slackpkg upgrade-all

I wonder if I was just fortunate. Though the slackpkg documentation does say

Quote:
upgrade-all
Keep your packages synced with the slackware tree. This is the "good" way to upgrade the whole system. Remember use install-new before run upgrade-all.
https://slackpkg.org/documentation.html

ChuangTzu - indeed and thank you very much for the documentation. I'll have a look through it.
 
1 members found this post helpful.
Old 01-09-2018, 01:54 PM   #20
ChuangTzu
Member
 
Registered: May 2015
Location: Where ever needed
Distribution: Slackware/Salix, Devuan, FreeBSD
Posts: 809

Rep: Reputation: 582Reputation: 582Reputation: 582Reputation: 582Reputation: 582Reputation: 582
Quote:
Originally Posted by Lysander666 View Post
I upgraded the kernel with

#slackpkg upgrade-all

I wonder if I was just fortunate. Though the slackpkg documentation does say



https://slackpkg.org/documentation.html

ChuangTzu - indeed and thank you very much for the documentation. I'll have a look through it.
yes and no...slackpkg upgrade-all is generally safe, however, if you want to be more Kevlar bullet proof then blacklist the kernel in slackpkg and upgrade (ie: installpkg separately).
https://docs.slackware.com/howtos:sl...:systemupgrade
 
Old 01-16-2018, 04:58 AM   #21
PROBLEMCHYLD
Member
 
Registered: Apr 2015
Posts: 554

Rep: Reputation: Disabled
You should upgrade

Code:
 Mon Jan 15 23:13:01 UTC 2018
patches/packages/linux-4.4.111/*: Upgraded.
       This kernel includes mitigations for the Spectre (variant 2) and Meltdown
       speculative side channel attacks.
       Be sure to upgrade your initrd after upgrading the kernel packages.
       If you use lilo to boot your machine, be sure lilo.conf points to the correct
       kernel and initrd and run lilo as root to update the bootloader.
       If you use elilo to boot your machine, you should run eliloconfig to copy the
       kernel and initrd to the EFI System Partition.
       For more information, see:
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5715
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5754
       (* Security fix *)
 
Old 01-16-2018, 05:01 AM   #22
Lysander666
Member
 
Registered: Apr 2017
Location: London
Distribution: Debian, Slackware
Posts: 350

Original Poster
Rep: Reputation: 186Reputation: 186
Quote:
Originally Posted by PROBLEMCHYLD View Post
You should upgrade

Code:
 Mon Jan 15 23:13:01 UTC 2018
patches/packages/linux-4.4.111/*: Upgraded.
       This kernel includes mitigations for the Spectre (variant 2) and Meltdown
       speculative side channel attacks.
       Be sure to upgrade your initrd after upgrading the kernel packages.
       If you use lilo to boot your machine, be sure lilo.conf points to the correct
       kernel and initrd and run lilo as root to update the bootloader.
       If you use elilo to boot your machine, you should run eliloconfig to copy the
       kernel and initrd to the EFI System Partition.
       For more information, see:
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5715
       https://cve.mitre.org/cgi-bin/cvename.cgi?name=CVE-2017-5754
       (* Security fix *)

Excellent news. I'm still not sure how to upgrade 'manually' [have not read the documentation fully] so will likely use slackpkg upgrade-all again, methinks.

EDIT apparently it's quite easy to do it another way
Quote:
Installation instructions:
+------------------------+

Upgrade the packages as root:
# upgradepkg kernel-*.txz

If you are using an initrd, you'll need to rebuild it.

For a 32-bit SMP machine, use this command (substitute the appropriate
kernel version if you are not running Slackware 14.2):
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.111-smp | bash

For a 64-bit machine, or a 32-bit uniprocessor machine, use this command
(substitute the appropriate kernel version if you are not running
Slackware 14.2):
# /usr/share/mkinitrd/mkinitrd_command_generator.sh -k 4.4.111 | bash

Please note that "uniprocessor" has to do with the kernel you are running,
not with the CPU. Most systems should run the SMP kernel (if they can)
regardless of the number of cores the CPU has. If you aren't sure which
kernel you are running, run "uname -a". If you see SMP there, you are
running the SMP kernel and should use the 4.4.111-smp version when running
mkinitrd_command_generator. Note that this is only for 32-bit -- 64-bit
systems should always use 4.4.111 as the version.

If you are using lilo or elilo to boot the machine, you'll need to ensure
that the machine is properly prepared before rebooting.

If using LILO:
By default, lilo.conf contains an image= line that references a symlink
that always points to the correct kernel. No editing should be required
unless your machine uses a custom lilo.conf. If that is the case, be sure
that the image= line references the correct kernel file. Either way,
you'll need to run "lilo" as root to reinstall the boot loader.

If using elilo:
Ensure that the /boot/vmlinuz symlink is pointing to the kernel you wish
to use, and then run eliloconfig to update the EFI System Partition.
http://www.linuxcompatible.org/news/...slackware.html

I don't know if I am using an initrd though.

EDIT 2: apparently I'm not and I'm on the huge kernel. It's not so hard to switch to generic

https://docs.slackware.com/slackware:beginners_guide

Last edited by Lysander666; 01-16-2018 at 05:30 AM.
 
Old 01-16-2018, 10:42 AM   #23
NakedRider
Member
 
Registered: Nov 2008
Posts: 32

Rep: Reputation: 3
Are you supposed to upgrade the generic and huge kernel packages?
 
Old 01-16-2018, 10:58 AM   #24
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,279

Rep: Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052
Quote:
Originally Posted by NakedRider View Post
Are you supposed to upgrade the generic and huge kernel packages?
Yes, as stated here.
 
Old 01-16-2018, 11:11 AM   #25
Lysander666
Member
 
Registered: Apr 2017
Location: London
Distribution: Debian, Slackware
Posts: 350

Original Poster
Rep: Reputation: 186Reputation: 186
I've never used two kernels before.

Wondering if I should create an initrd, update lilo for generic, reboot and then upgrade both?
 
Old 01-16-2018, 11:31 AM   #26
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,279

Rep: Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052Reputation: 3052
You only use one kernel at a time, but you can have many installed.

If you want to use the generic one, preferably keep a stanza for the huge one in /etc/lilo.conf. Read below "Switch to a generic kernel" in the Beginner's Guide.

Also, upgrade first, only then make the initrd and switch to the generic one.

After that, run lilo.

Last edited by Didier Spaier; 01-16-2018 at 11:33 AM.
 
1 members found this post helpful.
Old 01-16-2018, 12:05 PM   #27
Lysander666
Member
 
Registered: Apr 2017
Location: London
Distribution: Debian, Slackware
Posts: 350

Original Poster
Rep: Reputation: 186Reputation: 186
Great, thank you. It seems upgrading went well, I can switch to generic now, with huge as a backup.

Can you label them anything you like?
 
Old 01-16-2018, 12:26 PM   #28
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: Newport News, VA
Distribution: Slackware
Posts: 5,066

Rep: Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864Reputation: 2864
Quote:
Originally Posted by Lysander666 View Post
Can you label them anything you like?
Lilo has limitations for the label. I know it has a length limitation, but I'm not sure if they have character limitations. If you run lilo -t, it will test your current config and report any issues.
 
Old 01-16-2018, 03:59 PM   #29
Lysander666
Member
 
Registered: Apr 2017
Location: London
Distribution: Debian, Slackware
Posts: 350

Original Poster
Rep: Reputation: 186Reputation: 186
bass, that worked great, I renamed them with no issue. I've noticed also that there are some old files related to 4.4.88 in /boot. I wonder why they weren't removed when the new kernel was installed:

Code:
lysander@lysurfer_viii:/boot$ ls
README.initrd                       initrd.gz
System.map                          inside.bmp
System.map-generic-4.4.88           inside.dat
System.map-generic-smp-4.4.111-smp  map
System.map-huge-4.4.88              onlyblue.bmp
System.map-huge-smp-4.4.111-smp     onlyblue.dat
boot.0800                           slack.bmp
boot_message.txt                    tuxlogo.bmp
coffee.dat                          tuxlogo.dat
config                              vmlinuz
config-generic-4.4.88               vmlinuz-generic
config-generic-smp-4.4.111-smp      vmlinuz-generic-4.4.88
config-huge-4.4.88                  vmlinuz-generic-smp
config-huge-smp-4.4.111-smp         vmlinuz-generic-smp-4.4.111-smp
elilo-ia32.efi                      vmlinuz-huge
elilo-x86_64.efi                    vmlinuz-huge-4.4.88
grub                                vmlinuz-huge-smp
initrd-tree                         vmlinuz-huge-smp-4.4.111-smp
Is it OK to remove them?
 
Old 01-16-2018, 03:59 PM   #30
Lysander666
Member
 
Registered: Apr 2017
Location: London
Distribution: Debian, Slackware
Posts: 350

Original Poster
Rep: Reputation: 186Reputation: 186
bass, that worked great, I renamed them with no issue. I've noticed also that there are some old files related to 4.4.88 in /boot. I wonder why they weren't removed when the new kernel was installed:

Code:
lysander@lysurfer_viii:/boot$ ls
README.initrd                       initrd.gz
System.map                          inside.bmp
System.map-generic-4.4.88           inside.dat
System.map-generic-smp-4.4.111-smp  map
System.map-huge-4.4.88              onlyblue.bmp
System.map-huge-smp-4.4.111-smp     onlyblue.dat
boot.0800                           slack.bmp
boot_message.txt                    tuxlogo.bmp
coffee.dat                          tuxlogo.dat
config                              vmlinuz
config-generic-4.4.88               vmlinuz-generic
config-generic-smp-4.4.111-smp      vmlinuz-generic-4.4.88
config-huge-4.4.88                  vmlinuz-generic-smp
config-huge-smp-4.4.111-smp         vmlinuz-generic-smp-4.4.111-smp
elilo-ia32.efi                      vmlinuz-huge
elilo-x86_64.efi                    vmlinuz-huge-4.4.88
grub                                vmlinuz-huge-smp
initrd-tree                         vmlinuz-huge-smp-4.4.111-smp
Is it OK to remove them?
 
  


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] keyboard stopped working in X when I upgraded udev from 1.75 to 1.82After I upgraded RandomTroll Slackware 3 07-26-2012 02:48 PM
upgraded to 11.4 Chr47 Linux - Newbie 2 07-21-2011 11:31 PM
Help! upgraded from 6.06 - 6.10 cornish Ubuntu 9 11-09-2006 04:06 PM
Upgraded to 2.6.9 cry0x Slackware 3 02-22-2005 12:20 PM
Just upgraded to 9 and... Finlay Slackware 2 05-28-2003 11:58 AM

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

All times are GMT -5. The time now is 08:18 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