LinuxQuestions.org
Latest LQ Deal: Linux Power User 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 08-09-2018, 12:44 AM   #16
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,209

Rep: Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982

I might get sucked into some of those threads, but my main reason on being in this forum is to learn and help others. That SlackDocs article came together after I learned everything from other posts on here as well as a few other sites, including Arch's wiki. I'm just glad the article has been useful!
 
1 members found this post helpful.
Old 08-12-2018, 06:49 AM   #17
Lysander666
Member
 
Registered: Apr 2017
Location: London
Distribution: Slackware 14.2 + Xfce
Posts: 527
Blog Entries: 1

Original Poster
Rep: Reputation: 397Reputation: 397Reputation: 397Reputation: 397
Today I added the generic kernel. Generic booted fine though Huge went into a kernel panic. This was the end of lilo.conf:

Code:
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-4.4.144
  initrd = /boot/initrd-4.4.144.gz
  root = /dev/disk/by-uuid/ff624ae7-b3d4-4ef5-887a-8d505669bfd0
  label = Generic
  read-only
# Linux bootable partition config ends

# Linux bootable partition config begins
image = /boot/vmlinuz
# root = /dev/sda1
  root = /dev/disk/by-uuid/ff624ae7-b3d4-4ef5-887a-8d505669bfd0
  label = Huge
  read-only
# Linux bootable partition config ends
So I added the line

Code:
initrd = /boot/initrd-4.4.144.gz
to Huge. But I think now both are just pointing to the same generic kernel. I was thinking of amending lilo.conf to

Code:
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-4.4.144
initrd = /boot/initrd-4.4.144.gz
#root = /dev/disk/by-uuid/ff624ae7-b3d4-4ef5-887a-8d505669bfd0
label = Generic
read-only
# Linux bootable partition config ends

# Linux bootable partition config begins
image = /boot/vmlinuz
root = /dev/sdc1
label = Huge
read-only
# Linux bootable partition config ends
Will lilo.conf point to the right kernels now? I am slightly wary about commenting out the UUID line for generic but apparently it is not needed.
 
Old 08-12-2018, 07:58 AM   #18
Lysander666
Member
 
Registered: Apr 2017
Location: London
Distribution: Slackware 14.2 + Xfce
Posts: 527
Blog Entries: 1

Original Poster
Rep: Reputation: 397Reputation: 397Reputation: 397Reputation: 397
EDIT: seems that the huge kernel section was not pointing to huge, so I changed it. lilo.conf now reads:

Code:
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-4.4.144
  initrd = /boot/initrd-4.4.144.gz
  root = /dev/disk/by-uuid/ff624ae7-b3d4-4ef5-887a-8d505669bfd0
  label = Generic
  read-only
# Linux bootable partition config ends

# Linux bootable partition config begins
image = /boot/vmlinuz-huge-4.4.144
  initrd = /boot/initrd-4.4.144.gz
# root = /dev/sda1
  root = /dev/disk/by-uuid/ff624ae7-b3d4-4ef5-887a-8d505669bfd0
  label = Huge
  read-only
# Linux bootable partition config ends
Both boot fine. Huge takes slightly longer to boot to login.

Slightly confused as to why /boot shows five entries for vmlinuz, but everything is working fine. I imagine that -generic and -huge are from the first kernel upgrade that i did through slackpkg before I blacklisted automatic kernel upgrades.

Code:
lysander@psychopig-xxxiv:/boot$ ls
README.initrd		    config		    inside.bmp	  vmlinuz
System.map		    config-generic-4.4.144  inside.dat	  vmlinuz-generic
System.map-generic-4.4.144  config-huge-4.4.144     map		  vmlinuz-generic-4.4.144
System.map-huge-4.4.144     elilo-ia32.efi	    onlyblue.bmp  vmlinuz-huge
boot.0800		    elilo-x86_64.efi	    onlyblue.dat  vmlinuz-huge-4.4.144
boot.0820		    grub		    slack.bmp
boot_message.txt	    initrd-4.4.144.gz	    tuxlogo.bmp
coffee.dat		    initrd-tree		    tuxlogo.dat

But everything works fine. In theory I should be able to remove -generic and -huge but I'll leave them for now.

Last edited by Lysander666; 08-12-2018 at 08:07 AM.
 
Old 08-12-2018, 03:02 PM   #19
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,209

Rep: Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982
[QUOTE=Lysander666;5890846]EDIT: seems that the huge kernel section was not pointing to huge, so I changed it. lilo.conf now reads:

Code:
# Linux bootable partition config begins
image = /boot/vmlinuz-generic-4.4.144
  initrd = /boot/initrd-4.4.144.gz
  root = /dev/disk/by-uuid/ff624ae7-b3d4-4ef5-887a-8d505669bfd0
  label = Generic
  read-only
# Linux bootable partition config ends

# Linux bootable partition config begins
image = /boot/vmlinuz-huge-4.4.144
  initrd = /boot/initrd-4.4.144.gz
# root = /dev/sda1
  root = /dev/disk/by-uuid/ff624ae7-b3d4-4ef5-887a-8d505669bfd0
  label = Huge
  read-only
# Linux bootable partition config ends
Both boot fine. Huge takes slightly longer to boot to login.[q/uote]

You can simplify your root option on the huge (since you don't need it with the initrd ) by using:

Code:
root = "UUID=ff624ae7-b3d4-4ef5-887a-8d505669bfd0"
But the way you did it works too.

Quote:
Originally Posted by Lysander666 View Post
Slightly confused as to why /boot shows five entries for vmlinuz, but everything is working fine. I imagine that -generic and -huge are from the first kernel upgrade that i did through slackpkg before I blacklisted automatic kernel upgrades.

Code:
lysander@psychopig-xxxiv:/boot$ ls
README.initrd		    config		    inside.bmp	  vmlinuz
System.map		    config-generic-4.4.144  inside.dat	  vmlinuz-generic
System.map-generic-4.4.144  config-huge-4.4.144     map		  vmlinuz-generic-4.4.144
System.map-huge-4.4.144     elilo-ia32.efi	    onlyblue.bmp  vmlinuz-huge
boot.0800		    elilo-x86_64.efi	    onlyblue.dat  vmlinuz-huge-4.4.144
boot.0820		    grub		    slack.bmp
boot_message.txt	    initrd-4.4.144.gz	    tuxlogo.bmp
coffee.dat		    initrd-tree		    tuxlogo.dat

But everything works fine. In theory I should be able to remove -generic and -huge but I'll leave them for now.
If you do an ls -l, it will likely show that the other files are symlinks to the actual kernel files (the files with the version at the end). Symlinks aren't needed if you reference the kernel versions directly in lilo.conf.
 
1 members found this post helpful.
Old 08-12-2018, 04:01 PM   #20
Lysander666
Member
 
Registered: Apr 2017
Location: London
Distribution: Slackware 14.2 + Xfce
Posts: 527
Blog Entries: 1

Original Poster
Rep: Reputation: 397Reputation: 397Reputation: 397Reputation: 397
Quote:
Originally Posted by bassmadrigal View Post
You can simplify your root option on the huge (since you don't need it with the initrd ) by using:

Code:
root = "UUID=ff624ae7-b3d4-4ef5-887a-8d505669bfd0"
Ahem, one day soon I'll be brave enough to change it, I assure you.

Quote:
Originally Posted by bassmadrigal View Post
If you do an ls -l, it will likely show that the other files are symlinks to the actual kernel files (the files with the version at the end). Symlinks aren't needed if you reference the kernel versions directly in lilo.conf.
Indeed, it gives:

Code:
root@psychopig-xxxiv:/boot# ls -l
...
lrwxrwxrwx  1 root root      23 Aug 12 12:00 vmlinuz -> vmlinuz-generic-4.4.144
lrwxrwxrwx  1 root root      23 Aug 12 12:00 vmlinuz-generic -> vmlinuz-generic-4.4.144
-rw-r--r--  1 root root 4435184 Jul 26 18:31 vmlinuz-generic-4.4.144
lrwxrwxrwx  1 root root      20 Aug 12 12:00 vmlinuz-huge -> vmlinuz-huge-4.4.144
-rw-r--r--  1 root root 7713648 Jul 26 18:46 vmlinuz-huge-4.4.144
So I could always change it, but indeed, no need since I'm referencing things directly, as you say. But this makes me understand things more. I didn't realise vmlinuz was a symlink.
 
Old Yesterday, 10:29 AM   #21
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 5,209

Rep: Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982Reputation: 2982
Quote:
Originally Posted by Lysander666 View Post
Ahem, one day soon I'll be brave enough to change it, I assure you.
If you're really worried it will break, you could add an extra stanza in your lilo.conf both linking the same things. One with the root specified and one without. That way, if the one without breaks, you can always boot the other one.

Quote:
Originally Posted by Lysander666 View Post
So I could always change it, but indeed, no need since I'm referencing things directly, as you say. But this makes me understand things more. I didn't realise vmlinuz was a symlink.
That symlink should be generated by the doinst.sh that is part of the package.
 
  


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
Persistent naming with three internal HDDs Lysander666 Slackware 16 01-16-2018 05:58 AM
Persistent Naming of a Block Device CentOS 6 bluefish1 Linux - Server 9 10-05-2012 08:05 PM
Persistent naming of /dev/sd[a-z] devices. How could I achieve this? Devyn Linux - Server 5 12-26-2011 10:55 PM
persistent device naming problem d-niX Linux - Server 7 02-24-2011 02:42 AM
Changing UDEV persistent naming schemes orbit Slackware 5 04-21-2008 09:22 PM

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

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