LinuxQuestions.org
Welcome to the most active Linux Forum on the web.
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 05-14-2016, 01:58 PM   #1
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 437

Rep: Reputation: 196Reputation: 196
Suggestion: In slackpkg, disable LILO prompting after each kernel update


Hi fellow Slackers,

I have a suggestion. I run Slack64-current in a dualboot config in parallell with Windows 10. GRUB is my boot manager.

As many of you, I use slackpkg in order to keep Slack updated. Now, I am talking to a buddy who is a Ubuntu user and he is thinking about moving to Slack. He's ready to take the jump. He downloaded a recent Slack64 current ISO from AlienBob, but there has been some updates after that that he would have to apply (I plan to keep him on Slack 14.2 after it is released....). Some of these updates, as you might imagine, are kernel updates. And here goes my suggestion.

When slackpkg upgrades kernels, it very thoughtfully suggest us to run LILO, and put Y (yes) as the default option.

Now, here's the problem. Most computers now use UEFI for boot, and therefore we must use something like elilo or GRUB or whatnot, but NOT LILO. Running LILO after a kernel update, I assume, would wreak all sorts of havoc in a GRUB system.

When slackpkg prompts me to run Lilo, it's no trouble for me. I just say no. But I think of my Ubuntu friend here; he might be inclined to press Enter and then see his system ruined.

So, this is my suggestion for slackpkg: make that "lilo" thing configurable, so that we could disable that prompting. Then, after upgrading my friend's laptop to Slack, I could just simply disable that Lilo prompting while I show him the ropes.
 
Old 05-14-2016, 02:02 PM   #2
montagdude
Senior Member
 
Registered: Apr 2016
Distribution: Slackware
Posts: 1,481

Rep: Reputation: 1103Reputation: 1103Reputation: 1103Reputation: 1103Reputation: 1103Reputation: 1103Reputation: 1103Reputation: 1103Reputation: 1103
Quote:
Originally Posted by sombragris View Post
Hi fellow Slackers,

I have a suggestion. I run Slack64-current in a dualboot config in parallell with Windows 10. GRUB is my boot manager.

As many of you, I use slackpkg in order to keep Slack updated. Now, I am talking to a buddy who is a Ubuntu user and he is thinking about moving to Slack. He's ready to take the jump. He downloaded a recent Slack64 current ISO from AlienBob, but there has been some updates after that that he would have to apply (I plan to keep him on Slack 14.2 after it is released....). Some of these updates, as you might imagine, are kernel updates. And here goes my suggestion.

When slackpkg upgrades kernels, it very thoughtfully suggest us to run LILO, and put Y (yes) as the default option.

Now, here's the problem. Most computers now use UEFI for boot, and therefore we must use something like elilo or GRUB or whatnot, but NOT LILO. Running LILO after a kernel update, I assume, would wreak all sorts of havoc in a GRUB system.

When slackpkg prompts me to run Lilo, it's no trouble for me. I just say no. But I think of my Ubuntu friend here; he might be inclined to press Enter and then see his system ruined.

So, this is my suggestion for slackpkg: make that "lilo" thing configurable, so that we could disable that prompting. Then, after upgrading my friend's laptop to Slack, I could just simply disable that Lilo prompting while I show him the ropes.
If he's going to use grub2, why not just remove or blacklist lilo?
 
1 members found this post helpful.
Old 05-14-2016, 02:19 PM   #3
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 437

Original Poster
Rep: Reputation: 196Reputation: 196
Quote:
Originally Posted by montagdude View Post
If he's going to use grub2, why not just remove or blacklist lilo?
Interesting idea. Thanks!
 
Old 05-14-2016, 02:39 PM   #4
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,955

Rep: Reputation: 3648Reputation: 3648Reputation: 3648Reputation: 3648Reputation: 3648Reputation: 3648Reputation: 3648Reputation: 3648Reputation: 3648Reputation: 3648Reputation: 3648
Also, keep in mind that having a lilo warning is good to make sure you knew you updated the kernel and to verify you've done the needed steps in your chosen bootloader to ensure booting of the new kernel can occur.

Also, once 14.2 is released, kernel updates won't happen frequently. There was only one kernel security update for 14.1, so for your friend trying to keep 14.2 up-to-date, hopefully there won't be too many updates that'd require "updating lilo".
 
Old 05-14-2016, 02:53 PM   #5
sombragris
Member
 
Registered: Jul 2004
Location: Asuncion, Paraguay, South America
Distribution: Slackware
Posts: 437

Original Poster
Rep: Reputation: 196Reputation: 196
Quote:
Originally Posted by bassmadrigal View Post
Also, keep in mind that having a lilo warning is good to make sure you knew you updated the kernel and to verify you've done the needed steps in your chosen bootloader to ensure booting of the new kernel can occur.
Good; but even then, the current situation of putting "yes" as default, is problematic. If there's a warning about running Lilo, I think it should not be set with "yes" as its default.

But even then, we should keep in mind that Lilo is slowly being put out of service with the emergence of UEFI machines. I think it would be good to improve the current situation. Right now, it's a hindrance for Slackware would-be users. This makes them in need of a handholding that sometimes it's just not available.

Quote:
Also, once 14.2 is released, kernel updates won't happen frequently. There was only one kernel security update for 14.1, so for your friend trying to keep 14.2 up-to-date, hopefully there won't be too many updates that'd require "updating lilo".
That's right, but until 14.2 is released, he should expect kernel updates to happen.

Last edited by sombragris; 05-14-2016 at 02:58 PM.
 
Old 05-14-2016, 03:15 PM   #6
Tonus
Member
 
Registered: Jan 2007
Location: Paris, France
Distribution: Slackware-current
Posts: 466
Blog Entries: 3

Rep: Reputation: 130Reputation: 130
Suggestion: In slackpkg, disable LILO prompting after each kernel update

I have grub too. I think I haven't lilo installed. Anyway I always blacklist all kernel stuff and installpkg before removing older after successfully booting with newer...
 
1 members found this post helpful.
Old 05-14-2016, 03:23 PM   #7
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1.2 on Lenovo Thinkpad W520
Posts: 8,834

Rep: Reputation: Disabled
Slightly off topic: the problem can arise when using both grub and lilo.

But there is no issue installing both lilo and elilo (and that is allowed by Slackware). This allows to switch between UEFI/Legacy modes of the firmware, being able to boot in both modes.

Last edited by Didier Spaier; 05-14-2016 at 03:56 PM.
 
2 members found this post helpful.
Old 05-16-2016, 03:16 AM   #8
tty13
Member
 
Registered: Aug 2006
Distribution: Slackware64-14.2
Posts: 50

Rep: Reputation: 7
I would rather see a warning about that you may have to build an initrd.gz and run lilo but leave the actual deed to the user.

But I guess this works fine for huge setup.
 
Old 05-16-2016, 06:59 AM   #9
allend
LQ 5k Club
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 5,177

Rep: Reputation: 1849Reputation: 1849Reputation: 1849Reputation: 1849Reputation: 1849Reputation: 1849Reputation: 1849Reputation: 1849Reputation: 1849Reputation: 1849Reputation: 1849
Quote:
I would rather see a warning about that you may have to build an initrd.gz and run lilo but leave the actual deed to the user.
It can be done. http://www.linuxquestions.org/questi...ml#post4957315
 
2 members found this post helpful.
  


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] [Suggestion] Linux Kernel 3.18 it's Longterm now, suggestion for Slackware Current sardinha Slackware 27 04-03-2015 05:17 PM
[SOLVED] [SUGGESTION] - Small modification to slackpkg samac Slackware 6 01-19-2014 11:58 AM
Suggestion: Modify /etc/slackpkg/blacklist samac Slackware 2 01-09-2010 03:36 PM
why clamav keep prompting me to update when its already updated Niceman2005 Linux - Software 10 04-27-2006 03:35 AM
firefox always prompting me for update thekowgomoo Mandriva 2 03-22-2005 11:02 PM

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

All times are GMT -5. The time now is 12:53 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
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration