LinuxQuestions.org
Visit Jeremy's Blog.
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-29-2016, 09:44 PM   #1
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484
Blog Entries: 15

Rep: Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175
Salix OS and Editing the lilo.conf file


I'm running Slackware 14.01 however; I just recently installed Salix OS and have an issue with LILO.

Korora was already on the 1 TB drive before I installed Salix OS.

I've tried editing the /etc/lilo.conf file 3 different ways to the sun and re-running LILO hasn't changed anything. When Salix boots I don't see any option to boot Korora.


Code:
   Device Boot      Start         End      Blocks   Id  System
/dev/sdb1            2048     1026047      512000   83  Linux
/dev/sdb2         1026048  1863026687   931000320   8e  Linux LVM
/dev/sdb3   *  1863041985  1953520064    45239040   83  Linux
The sdb1 is Korora's journaling fs. sdb2 is the swap for Korora and sdb3 is my fresh install of Salix OS.

I've tried both instances of:
Code:
other = /dev/sdb
label = /korora
and
other = /dev/sdb1 and or 2
This is what I have now-
Code:
image = /boot/vmlinuz
root = /dev/sdb3
label = salix
read-only
If I edit the file I get:
Code:
Fatal: First sector of /dev/sdb1 (or sdb2) doesn't have a valid boot signature
I figured out what the problem was-
the line I was trying to add had to say:
Code:
other = /dev/sdb
Without 1 or 2 after sdb.

Code:
root[linuxcat]# nano /etc/lilo.conf
root[linuxcat]# lilo
Added salix  *
Added /korora
I'm glad that's over-

Pressing the Tab key should allow me to boot Korora when LILO starts with Salix right?
 
Old 06-30-2016, 03:10 AM   #2
Alien Bob
Slackware Contributor
 
Registered: Sep 2005
Location: Eindhoven, The Netherlands
Distribution: Slackware
Posts: 8,559

Rep: Reputation: 8086Reputation: 8086Reputation: 8086Reputation: 8086Reputation: 8086Reputation: 8086Reputation: 8086Reputation: 8086Reputation: 8086Reputation: 8086Reputation: 8086
You know that Salix is not Slackware, right?
Sure, it is binary compatible and uses a lot of the same packages, but there is still a difference, and that difference is in the OS tooling. Who knows what Salix does to your LILO?
Better ask this in the Salix forum.
Or re-install Slackware of course.
 
Old 06-30-2016, 04:01 AM   #3
Didier Spaier
LQ Addict
 
Registered: Nov 2008
Location: Paris, France
Distribution: Slint64-14.2.1 on Lenovo Thinkpad W520
Posts: 10,410

Rep: Reputation: Disabled
Quote:
Originally Posted by Alien Bob View Post
You know that Salix is not Slackware, right?
Sure, it is binary compatible and uses a lot of the same packages, but there is still a difference, and that difference is in the OS tooling. Who knows what Salix does to your LILO?
Better ask this in the Salix forum.
Or re-install Slackware of course.
No worries, our friend is just in a distro hopping mood, so tomorrow he will have installed yet another distribution (that he will really use it or not would be another topic).

Also, I understand that he still has Slackware somewhere in /dev/sda.

Also he says "sdb2 is the swap for Korora" but this partition's type is 8e (LVM) not 82 (swap). But this doesn't matter much as he probably will not use Korora long enough to need a swap partition anyway.

So Ztcoracat, my best advice for today, is "do some reading and learn how to use your system, whatever it be".

For instance you could begin with typing these commands in a terminal:
Code:
man lilo
man lilo.conf
Have a good day.

PS I like your pictures

Last edited by Didier Spaier; 06-30-2016 at 07:53 AM. Reason: URL of a search on LQ doesn't seem t hold...
 
1 members found this post helpful.
Old 06-30-2016, 05:20 PM   #4
hitest
Guru
 
Registered: Mar 2004
Location: Northern Canada
Distribution: Slackware, OpenBSD, VM: FreeBSD, NetBSD, Void, Arch
Posts: 7,034

Rep: Reputation: 3399Reputation: 3399Reputation: 3399Reputation: 3399Reputation: 3399Reputation: 3399Reputation: 3399Reputation: 3399Reputation: 3399Reputation: 3399Reputation: 3399
Quote:
Originally Posted by Alien Bob View Post
You know that Salix is not Slackware, right?
Sure, it is binary compatible and uses a lot of the same packages, but there is still a difference, and that difference is in the OS tooling. Who knows what Salix does to your LILO?
Better ask this in the Salix forum.
Or re-install Slackware of course.
^^^^^^
Agreed.
 
Old 06-30-2016, 07:29 PM   #5
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175
Yes, I am well aware that Salix is not Slackware and I've been running Slackware for about 4 years now and love it. Slackware is on a 500 GB HDD /dev/sda and runs efficiently.

Quote:
Who knows what Salix does to your LILO?
LILO is ok now after editing the file several times trying 3 different methods.

Quote:
But this doesn't matter much as he probably will not use Korora long enough to need a swap partition anyway.
Korora has been installed on this desktop for 4 months now and seems stable. I intend on keeping it unless it suddenly is no longer maintained. Glad you like my pic's.


I read online documentation about how to edit the lilo.conf file. I posted to see if anyone knew how to mount the other distro from the LILO menu because I wasn't sure how when it launches. And I still don't today.

If anyone is in a dual boot with Slackware can you please provide how to make another distro from the Slackware LILO Menu boot? What key?

Last edited by Ztcoracat; 06-30-2016 at 07:46 PM.
 
Old 06-30-2016, 09:15 PM   #6
aaazen
Member
 
Registered: Dec 2009
Posts: 358

Rep: Reputation: Disabled
Quote:
Originally Posted by Ztcoracat View Post
Yes, I am well aware that Salix is not Slackware and I've been running Slackware for about 4 years now and love it. Slackware is on a 500 GB HDD /dev/sda and runs efficiently.


LILO is ok now after editing the file several times trying 3 different methods.


Korora has been installed on this desktop for 4 months now and seems stable. I intend on keeping it unless it suddenly is no longer maintained. Glad you like my pic's.


I read online documentation about how to edit the lilo.conf file. I posted to see if anyone knew how to mount the other distro from the LILO menu because I wasn't sure how when it launches. And I still don't today.

If anyone is in a dual boot with Slackware can you please provide how to make another distro from the Slackware LILO Menu boot? What key?
It appears that Korora is a derivative of Fedora.

http://distrowatch.com/thttp://distr...ibution=Korora

While testing a kernel bug, I installed a beta version of Fedora to test the bug.

https://www.linuxquestions.org/quest...9/#post5475533

I mounted the fedora file system (/dev/sda15) as /fedora and ran lilo.

Here is my lilo entry:

Code:
# Linux Fedora bootable partition config begins
image = /fedora/boot/vmlinuz-4.4.0-0.rc4.git2.1.fc24.x86_64
  label = fedora
  append = "root=UUID=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee ro nomodeset rhgb quiet LANG=en_US.UTF-8"
  initrd = "/fedora/boot/initramfs-4.4.0-0.rc4.git2.1.fc24.x86_64.img"
# Linux Fedora bootable partition config ends
Look up the UUID for your Korora (Fefora) partition under /dev/disk/by-uuid/ and fill it in above. And of course change the names of the kernel and the initramfs files.

I found these details by looking at the grub configuration files for Fedora and by looking in the /fedora/boot directory
 
1 members found this post helpful.
Old 06-30-2016, 09:23 PM   #7
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175
Quote:
Originally Posted by comet.berkeley View Post
It appears that Korora is a derivative of Fedora.

http://distrowatch.com/thttp://distr...ibution=Korora

While testing a kernel bug, I installed a beta version of Fedora to test the bug.

https://www.linuxquestions.org/quest...9/#post5475533

I mounted the fedora file system (/dev/sda15) as /fedora and ran lilo.

Here is my lilo entry:

Code:
# Linux Fedora bootable partition config begins
image = /fedora/boot/vmlinuz-4.4.0-0.rc4.git2.1.fc24.x86_64
  label = fedora
  append = "root=UUID=aaaaaaaa-bbbb-cccc-dddd-eeeeeeeeeeee ro nomodeset rhgb quiet LANG=en_US.UTF-8"
  initrd = "/fedora/boot/initramfs-4.4.0-0.rc4.git2.1.fc24.x86_64.img"
# Linux Fedora bootable partition config ends
Look up the UUID for your Korora (Fefora) partition under /dev/disk/by-uuid/ and fill it in above. And of course change the names of the kernel and the initramfs files.

I found these details by looking at the grub configuration files for Fedora and by looking in the /fedora/boot directory

Thank You.
 
Old 06-30-2016, 10:54 PM   #8
astrogeek
Moderator
 
Registered: Oct 2008
Distribution: Slackware [64]-X.{0|1|2|37|-current} ::12<=X<=14, FreeBSD_12{.0|.1}
Posts: 5,876
Blog Entries: 23

Rep: Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881
Hi Ztcoracat!

It is not clear to me which lilo.conf for which distro that you are editing.

A few things to to remember about lilo.conf -

** The image (and initrd if used) path in each stanza (i.e. the kernel you want to boot) must be mounted and accessible when you run lilo.

This means that if you are including a stanza for salix in the korora lilo.conf, you must mount the salix partition and specify the path in the korora lilo.conf. Something like this (example only).

Code:
mount /dev/sdb3 /mnt/salix-boot

then in lilo.conf...

image /mnt/salix-boot/boot/vmlinuz
root = /dev/disk/by-uuid/xxxx-yyyy-zzzz (symlink to /dev/sda3)
label = Salix
That can become pretty messy when booting multiple, frequently changing distros across multiple devices!

I think the tendency for most of us is to think that we can put everything into a single lilo.conf, and we then beat ourselves up badly trying to make that work!

My approach is as follows...

** Assign one distro to manage the MBR lilo.conf for each device and create a separate lilo.conf for that, name it lilo-mbr.conf
** Set the default /etc/lilo.conf in each distro to install ONLY to its own / partition (or /boot if separate)
** Chain load all the addon distros from the MBR on its device
** Reference all devices by ID or UUID

In this way, the chance of one distro clobbering the boot sector of another is greatly reduced, and should it still happen, recovery is usually very easy. When adding a new distro, have its lilo.conf install to its own / partition, then add a new chain stanza for it in the MBR lilo.conf for that device. (and of course rerun lilo in each case).

The basic idea is that each distro manages its own boot sector on its own partition, so it rarely confuses itself and you don't have to mount its boot/ path from another distro. Everything else is chained from the 0x80 boot device by UUID so you have an easily managed hierarchy of boot options. If one breaks, it rarely affects others.

Using this approach I easily manage a mix of multiple Slackware and FreeBSD instances across multiple drives using lilo and rarely have any surprises.

Last edited by astrogeek; 06-30-2016 at 11:34 PM.
 
Old 06-30-2016, 11:41 PM   #9
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175
Quote:
It is not clear to me which lilo.conf for which distro that you are editing.
I was trying to edit the lilo.conf file for Salix.
Now that is done and Korora shows in the Salix Lilo bootloader when it boots.
Using the arrow key to highlight Korora doesn't work so I will have to either do Grub repair using the Korora Live USB or perform a fresh install and allow Korora to take over LILO because I can't mnt Korora at all.

Furthermore I can't get to /dev/disk/by-uuid to reference Korora.
It doesn't matter if I'm booted into Slack or into Salix the only thing that I can mnt is:

Code:
/run/media/linuxcat/41a88f97-16e1-49d0-90a2-f888a5f182ff/
That's the directory for Korora that's showing me the initramfs.

Quote:
I think the tendency for most of us is to think that we can put everything into a single lilo.conf, and we then beat ourselves up badly trying to make that work!
Agreed - However I did manage to edit correctly as Korora is now in the LILO Menu it just won't boot.

Thanks for taking the time to explain things.

Last edited by Ztcoracat; 06-30-2016 at 11:47 PM.
 
Old 07-01-2016, 01:00 AM   #10
astrogeek
Moderator
 
Registered: Oct 2008
Distribution: Slackware [64]-X.{0|1|2|37|-current} ::12<=X<=14, FreeBSD_12{.0|.1}
Posts: 5,876
Blog Entries: 23

Rep: Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881
Quote:
Originally Posted by Ztcoracat View Post
I was trying to edit the lilo.conf file for Salix.
Now that is done and Korora shows in the Salix Lilo bootloader when it boots.
Using the arrow key to highlight Korora doesn't work so I will have to either do Grub repair using the Korora Live USB or perform a fresh install and allow Korora to take over LILO because I can't mnt Korora at all.

Furthermore I can't get to /dev/disk/by-uuid to reference Korora.
It doesn't matter if I'm booted into Slack or into Salix the only thing that I can mnt is:

Code:
/run/media/linuxcat/41a88f97-16e1-49d0-90a2-f888a5f182ff/
That's the directory for Korora that's showing me the initramfs.


Agreed - However I did manage to edit correctly as Korora is now in the LILO Menu it just won't boot.

Thanks for taking the time to explain things.
I am totally ignorant of fedora, korora (and salix for that matter), but lilo "should be" the same across distros.

Based on comet.berkley's post and the path in your last post, then something like this should work in your salix lilo.conf...

Code:
image = /run/media/linuxcat/41a88f97-16e1-49d0-90a2-f888a5f182ff/boot/vmlinuz-4.4.0-0.rc4.git2.1.fc24.x86_64
  initrd = /run/media/linuxcat/41a88f97-16e1-49d0-90a2-f888a5f182ff/boot/initramfs-4.4.0-0.rc4.git2.1.fc24.x86_64.img
  label = korora
...with suitable append args (not shown). The root should be the context seen by korora at boot if you cannot identify it by UUID. What is in the korora fstab?

The all important thing is that the image and initrd be mounted and accessible by that path when you run lilo from salix.

Last edited by astrogeek; 07-01-2016 at 01:09 AM.
 
1 members found this post helpful.
Old 07-01-2016, 01:51 AM   #11
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175
After reading and thinking about your instructions I knew that what you posted in code tags in post # 10 would of worked had I edited the lilo.conf exactly like the way you did. Thank you for showing me that.

Quote:
The all important thing is that the image and initrd be mounted and accessible by that path when you run lilo from salix.
Had I known that earlier this issue with LILO would of never happened.

What you said lead me to the decision of installing the new release of Fedora 24 as I found out that Korora 23 wouldn't be supported for much longer.

Grub took over LILO and both distributions FC and Salix now boot:-

Your a real gem astrogeek; thanks again.-
 
Old 07-01-2016, 01:54 AM   #12
astrogeek
Moderator
 
Registered: Oct 2008
Distribution: Slackware [64]-X.{0|1|2|37|-current} ::12<=X<=14, FreeBSD_12{.0|.1}
Posts: 5,876
Blog Entries: 23

Rep: Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881Reputation: 3881
You are always welcome!
 
1 members found this post helpful.
Old 07-01-2016, 01:57 AM   #13
Ztcoracat
LQ Guru
 
Registered: Dec 2011
Distribution: Slackware, MX 18
Posts: 9,484

Original Poster
Blog Entries: 15

Rep: Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175Reputation: 1175
Quote:
Originally Posted by astrogeek View Post
You are always welcome!
Enjoy the weekend!
 
Old 07-01-2016, 02:15 AM   #14
kikinovak
MLED Founder
 
Registered: Jun 2011
Location: Montpezat (South France)
Distribution: CentOS, OpenSUSE
Posts: 3,453

Rep: Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154Reputation: 2154
Quote:
Originally Posted by Didier Spaier View Post
No worries, our friend is just in a distro hopping mood, so tomorrow he will have installed yet another distribution (that he will really use it or not would be another topic).

Also, I understand that he still has Slackware somewhere in /dev/sda.

Also he says "sdb2 is the swap for Korora" but this partition's type is 8e (LVM) not 82 (swap). But this doesn't matter much as he probably will not use Korora long enough to need a swap partition anyway.
Come on, give the guy a break.
 
Old 07-01-2016, 07:04 AM   #15
bassmadrigal
LQ Guru
 
Registered: Nov 2003
Location: West Jordan, UT, USA
Distribution: Slackware
Posts: 8,733

Rep: Reputation: 6522Reputation: 6522Reputation: 6522Reputation: 6522Reputation: 6522Reputation: 6522Reputation: 6522Reputation: 6522Reputation: 6522Reputation: 6522Reputation: 6522
An alternate to astrogeek's method (possibly to be used in the future) is to have "one lilo to rule them all". What this means, is you just pick one lilo to manage everything. Personally, I would pick the distro you use the most frequently (that's Slackware, right? ) and modify that lilo.conf. Then the easiest way to manage it would be to move all kernels from other distros into your primary /boot partition. I would pick logical names like vmlinuz-slackware64-4.4.14, vmlinuz-fedora24-4.4.0-0.rc4.git2.1.fc24.x86_64, vmlinuz-salix-3.10.17, etc and the same thing for initrds (if you're using them): initrd-slackware64-4.4.14.gz, initrd-fedora24-4.4.0-0.rc4.git2.1.fc24.x86_64.gz, initrd-salix-3.10.17.gz, etc. You can name them whatever you want, but I'd just suggest something to keep them unique and known to you.

Then you'd just have your lilo.conf reference the correct files and the root partition of the other distro.

Code:
image = /boot/vmlinuz-slackware64-4.4.14
  initrd = /boot/initrd-slackware64-4.4.14.gz
  root = /dev/sda1
  label = Slackware
  read-only

image = /boot/vmlinuz-fedora24-4.4.0-0.rc4.git2.1.fc24.x86_64
  initrd = /boot/initrd-fedora24-4.4.0-0.rc4.git2.1.fc24.x86_64.gz
  root = /dev/sdb1
  label = Fedora
  read-only

image = /boot/vmlinuz-salix-3.10.17
  initrd = /boot/initrd-salix-3.10.17.gz
  root = /dev/sdb3
  label = Salix
  read-only
 
1 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
lilo.conf editing Daunted Linux - Newbie 6 10-16-2004 10:13 PM
Editing lilo.conf alex101 Mandriva 2 10-15-2003 05:17 AM
No new kernel-option in LILO after editing lilo.conf corwax Debian 3 08-26-2003 08:55 PM
Editing lilo.conf & fstab moebush Linux - General 2 07-04-2003 04:49 PM
editing lilo.conf... SOMEONE PLEASE RESPOND! I AM DESPERATE!!!!! Colonel Panic Linux - Newbie 13 07-26-2001 02:20 PM

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

All times are GMT -5. The time now is 01:43 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
Open Source Consulting | Domain Registration