LinuxQuestions.org
Share your knowledge at the LQ Wiki.
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 04-04-2018, 02:19 AM   #31
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,303

Rep: Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808

2.83.0beta2 available - minor changes, but I wanted to get them out just in case: https://slackpkg.org/
 
5 members found this post helpful.
Old 04-07-2018, 08:52 AM   #32
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware, Debian, CentOS, FreeBSD
Posts: 1,090

Rep: Reputation: 455Reputation: 455Reputation: 455Reputation: 455Reputation: 455
Making slackpkg $ROOT aware

Just.to touch base, I have not found any problems, and it is running rock solid for my everyday use case.
 
1 members found this post helpful.
Old 04-07-2018, 10:16 AM   #33
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 4,965

Rep: Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715
I would still like to advocate for a user using lilo and a generic kernel to be prompted to create a new mkinitrd. I think it is safe to assume that the user is upgrading the currently running system.
Attached Files
File Type: txt lookkernel.patch.txt (1.4 KB, 12 views)

Last edited by allend; 04-07-2018 at 10:50 AM.
 
Old 04-07-2018, 11:20 AM   #34
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,340

Rep: Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115
Hello,

Quote:
Originally Posted by allend View Post
I would still like to advocate for a user using lilo and a generic kernel to be prompted to create a new mkinitrd. I think it is safe to assume that the user is upgrading the currently running system.
That the user be upgrading a running system does not preclude having other systems installed that we should not take the risk of making not bootable.

I gave some thought about this for Slint and got to the conclusion that it's better to suggest that something should be done but let the user do what's to be done (as stated in the ChangeLog).

I have in mind use cases like multi-boot where grub comes into play (possibly run from another distribution), several disks and several boot sectors or files. Just in my laptop I have two hard disks, several systems, grub installed in one disk, lilo and elilo in another one. And the user could have installed lilo at some point of time but then switched to another boot loader. then installing lilo could override the boot loader in use.

As very small detail: just in case the user press an unexpected key, line #18 I'd rather write:
Code:
+                               if [ "$ANSWER" = "y" ] || [ "$ANSWER" = "y" ]; then
Maybe the safe bet would be not to bet, and in case of an upgraded kernel install the new one alongside the previous one, as does Debian. Then let the user remove the previous one when it has be verified that booting the new one is OK.

Last edited by Didier Spaier; 04-07-2018 at 12:36 PM. Reason: code corrected
 
Old 04-07-2018, 11:39 AM   #35
mralk3
Senior Member
 
Registered: May 2015
Distribution: Slackware, Debian, CentOS, FreeBSD
Posts: 1,090

Rep: Reputation: 455Reputation: 455Reputation: 455Reputation: 455Reputation: 455
Quote:
Originally Posted by Didier Spaier View Post
Maybe the safe bet would be not to bet, and in case of an upgraded kernel install the new one alongside the previous one, as does Debian. Then let the user remove the previous one when it has be verified that booting the new one is OK.
This seems like a good idea, instead of assuming the user only uses Slackware. CentOS does this too. I usually keep the last three most recent kernels installed on my CentOS systems. It would be a great feature to add to slackpkg while we are reviewing it's behavior regarding kernels and boot loaders. Sure Slackware expects you to read the change log in order to maintain a granular control over the system. It might be good to have slackpkg leave the existing kernels in place and let the admin decide when to remove them.

While it seems like a good idea to do so, maybe there are other complications I have not thought up. However, I have not read the source of slackpkg in it's entirety.
 
Old 04-07-2018, 12:23 PM   #36
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,303

Rep: Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808
Quote:
Originally Posted by allend View Post
I would still like to advocate for a user using lilo and a generic kernel to be prompted to create a new mkinitrd. I think it is safe to assume that the user is upgrading the currently running system.
At some point, there will likely be the need for something along those lines, but we are not at that point yet :-)
 
1 members found this post helpful.
Old 04-07-2018, 12:41 PM   #37
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 8,340

Rep: Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115Reputation: 3115
Quote:
Originally Posted by rworkman View Post
At some point, there will likely be the need for something along those lines, but we are not at that point yet :-)
I take this as a confirmation that a generic kernel + an initrd adapted to the system being installed will replace the huge kernel in next Slackware installer

Last edited by Didier Spaier; 04-07-2018 at 03:10 PM. Reason: s/hardware/system being installed/
 
1 members found this post helpful.
Old 04-07-2018, 01:07 PM   #38
glorsplitz
Member
 
Registered: Dec 2002
Distribution: slackware!
Posts: 598

Rep: Reputation: 118Reputation: 118
Quote:
Originally Posted by allend View Post
I think it is safe to assume that the user is upgrading the currently running system.
and should know what they are doing.

When kernel is updated, doesn't it say "Your kernel has been updated, do you want to run lilo?". To me this means run mkinitrd.

My lilo has two bootable partitions, 'image = /boot/vmlinuz-generic' using 'initrd = /boot/initrd.gz' and 'image = /boot/vmlinuz-huge'.

If I forget to run mkinitrd and generic doesn't boot, huge will boot whatever it links to.

I can then run mkinitrd to get generic initrd back.
 
1 members found this post helpful.
Old 04-07-2018, 03:24 PM   #39
rworkman
Slackware Contributor
 
Registered: Oct 2004
Location: Tuscaloosa, Alabama (USA)
Distribution: Slackware
Posts: 2,303

Rep: Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808Reputation: 808
Quote:
Originally Posted by Didier Spaier View Post
I take this as a confirmation that a generic kernel + an initrd adapted to the system being installed will replace the huge kernel in next Slackware installer
Discussion along those lines has taken place, and it is at least a long-term goal. I don't know if it's fair to say "next" though...
 
1 members found this post helpful.
Old 04-07-2018, 09:14 PM   #40
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 4,965

Rep: Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715
Quote:
At some point, there will likely be the need for something along those lines, but we are not at that point yet :-)
Cool bananas. I can just keep it for myself.
Code:
+                               if [ "$ANSWER" = "Y" ] || [ "$ANSWER" = "y" ]; then
That does look more correct, but is not the way the code is written in slackpkg. I suspect that it is to do with the BATCH= and DEFAULT_ANSWER= options in /etc/slackpkg/slackpkg.conf.
 
Old 04-07-2018, 09:31 PM   #41
allend
Senior Member
 
Registered: Oct 2003
Location: Melbourne
Distribution: Slackware-current
Posts: 4,965

Rep: Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715Reputation: 1715
Quote:
When kernel is updated, doesn't it say "Your kernel has been updated, do you want to run lilo?". To me this means run mkinitrd.
So, you need to remember to make a new mkinitrd and then run lilo after the slackpkg run has completed. The point of my proposal is to protect new users that do not fully grasp that concept. Sophisticated users with multiple OS partitions and boot loaders should be capable of handling their own setups.
 
1 members found this post helpful.
Old 04-08-2018, 05:43 AM   #42
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu
Posts: 267

Original Poster
Rep: Reputation: 36
For the record: I am out of the country for some days and do not have access to a computer. I will test this new build when I will be back.
😁
 
Old 04-13-2018, 12:06 PM   #43
burdi01
Member
 
Registered: Dec 2010
Location: The Netherlands
Distribution: Slackware, Xubuntu
Posts: 267

Original Poster
Rep: Reputation: 36
I tested slackpkg-2.83.0beta2 with and without the $ROOT and $CONF parameters and did not notice anything out of the ordinary.
 
1 members found this post helpful.
Old 04-13-2018, 05:42 PM   #44
zerouno
Member
 
Registered: Oct 2009
Location: Italy
Distribution: Slackware
Posts: 556

Rep: Reputation: 157Reputation: 157
A note about the advice for slackware-14.2 vs slackware-current

latest aaa_base have a new feature:
Code:
 Thu Apr 12 23:00:51 UTC 2018
a/aaa_base-14.2-x86_64-3.txz:  Rebuilt.
  If the system is running -current, append a "+" to /etc/slackware-version.
  Identify the system as stable or current in /etc/os-release by setting
  VERSION_CODENAME to either stable or current. In PRETTY_NAME, really
  spell it out, e.g: PRETTY_NAME="Slackware 14.2 (pre-15.0 -current)"
so slackpkg now advice:
You have selected a mirror for Slackware -current in /etc/slackpkg/mirrors,
but Slackware version 14.2+ appears to be installed.

14.2+ == current, so the check may be changed

and the note
Slackpkg will not show this warning again unless you remove the
/var/lib/slackpkg/current file.

may be no more needed

Last edited by zerouno; 04-13-2018 at 05:53 PM.
 
Old 04-13-2018, 07:43 PM   #45
Xsane
Member
 
Registered: Jan 2014
Posts: 140

Rep: Reputation: 101Reputation: 101
Robby,

You never commented on this patch set:

https://www.linuxquestions.org/quest...ch-4175507086/

I've been using it for about 4 years and find it very useful. Any thoughts?
 
  


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] Slackware ARM 14.1 slackpkg file at the root of the package Linux.tar.gz Slackware - ARM 3 10-04-2016 06:21 AM
BUG slackpkg upgrade does not work with $ROOT zerouno Slackware 3 01-15-2016 05:29 PM
[SOLVED] Slackpkg, Slackpkg Plus, Slackware 14.1 x86_64 install.log delay or slow to write bamunds Slackware 7 04-22-2014 11:12 AM
[SOLVED] slackpkg creates /.gnupg (in the root of the file system) Woodsman Slackware 3 04-07-2011 06:18 PM
Making Apache Aware of a WebSite sefarlow Linux - Newbie 1 04-18-2009 07:20 AM

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

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