LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
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-06-2018, 07:12 AM   #16
Darth Vader
Senior Member
 
Registered: May 2008
Location: Romania
Distribution: DARKSTAR Linux 2008.1
Posts: 2,727

Rep: Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235Reputation: 1235

Just of records, to note that RHEL's YUM, DNF or even the freaking Yast2 of SuSE does NOT play at all with bootloaders while updating packages.

Basically, who do this thing is the very Package Manager (aka RPM) because in pre-install and post-install scripts from packages are coded commands for.

Also to note that they does NOT *upgrade* kernel packages, usually they have an install/remove only policy for these particular packages. And this thing I will love to see adopted also in Slackware.

Last edited by Darth Vader; 06-06-2018 at 07:46 AM.
 
Old 06-06-2018, 09:45 AM   #17
bormant
Member
 
Registered: Jan 2008
Posts: 328

Rep: Reputation: 189Reputation: 189
Quote:
Originally Posted by allend View Post
If you install a stock Slackware kernel package, the /boot/vmlinuz symlink is created to point to the kernel in that package.
... and may be this is the another reason to ignore /boot/vmlinuz symlink: if you have both kernel-generic and kernel-huge packages installed then 'slackpkg upgrade-all' at post-install step will always see the /boot/vmlinuz as symlink to the huge kernel (or huge-smp for 32 bit). Yes, because 'kernel-huge' sorted after 'kernel-generic' and doinst.sh from kernel-huge package overwrites symlink to huge kernel later than kernel-generic's do.

Last edited by bormant; 06-06-2018 at 09:50 AM.
 
Old 06-06-2018, 10:26 AM   #18
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,141

Rep: Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820
Quote:
Just of records, to note that RHEL's YUM, DNF or even the freaking Yast2 of SuSE does NOT play at all with bootloaders while updating packages.

Basically, who do this thing is the very Package Manager (aka RPM) because in pre-install and post-install scripts from packages are coded commands for.

Also to note that they does NOT *upgrade* kernel packages, usually they have an install/remove only policy for these particular packages. And this thing I will love to see adopted also in Slackware.
And your point is?
Quote:
... and may be this is the another reason to ignore /boot/vmlinuz symlink: if you have both kernel-generic and kernel-huge packages installed then 'slackpkg upgrade-all' at post-install step will always see the /boot/vmlinuz as symlink to the huge kernel (or huge-smp for 32 bit). Yes, because 'kernel-huge' sorted after 'kernel-generic' and doinst.sh from kernel-huge package overwrites symlink to huge kernel later than kernel-generic's do.
And the script will fall through to prompting to running lilo without building an initrd.
 
Old 06-06-2018, 12:29 PM   #19
bormant
Member
 
Registered: Jan 2008
Posts: 328

Rep: Reputation: 189Reputation: 189
Quote:
Originally Posted by allend View Post
And the script will fall through to prompting to running lilo without building an initrd.
Yes, this part of post-install will be disabled in this scenario and initrd will not be upgraded... But when slackpkg is done user will change /boot/vmlinuz symlink to generic kernel and has no chance to use slackpkg initrd autoupdate feature.
This is the reason to not to use vmlinuz symlink as an indicator to recreate initrd.
 
Old 06-06-2018, 01:02 PM   #20
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,141

Rep: Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820Reputation: 1820
Quote:
But when slackpkg is done user will change /boot/vmlinuz symlink to generic kernel and has no chance to use slackpkg initrd autoupdate feature.
The focus of this thread is how to allow slackpkg to make a sensible suggestion to the system adminstrator to update the initrd if the generic kernel has been updated. If slackpkg is done, and the symlink has been changed, then the resulting environment is out of scope.
 
Old 06-06-2018, 02:54 PM   #21
bormant
Member
 
Registered: Jan 2008
Posts: 328

Rep: Reputation: 189Reputation: 189
Quote:
Originally Posted by allend View Post
The focus of this thread is how to allow slackpkg to make a sensible suggestion to the system adminstrator to update the initrd if the generic kernel has been updated.
... and if slackpkg will use /boot/vmlinuz to make the suggestion it cannot make sensible suggestion in the simplest case when kernel-generic and kernel-huge are both installed (as in recommended full install).
In this case (1) kernel-generic is installed but (2) initrd will not be updated. Surprise.
 
Old 06-06-2018, 03:06 PM   #22
zerouno
Member
 
Registered: Oct 2009
Location: Italy
Distribution: Slackware
Posts: 567

Original Poster
Rep: Reputation: 161Reputation: 161
Note: the focus is not initrd+generic but kernel+initrd.
I use a kernel huge but I need an initrd since some driver is not included in the huge.

The script should not check for kernel type but should search the initrd.
 
  


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] elilo vs kernel and initrd on /boot wowbaggerHU Slackware - Installation 4 02-05-2017 05:57 PM
lilo vs elilo? coralfang Linux - Software 2 04-02-2016 10:14 PM
LILO + initrd leads to kernel freeze immediately after the LILO menu ppencho Slackware 11 01-16-2016 08:57 AM
lilo x elilo x grup2 x UEFI afreitascs Slackware 5 09-09-2012 10:55 AM
slackpkg upgrade from 12.1 to 12.2 and now LILO can't find my HD thrash242 Slackware 4 03-17-2009 09:15 AM

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

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