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 01-10-2011, 03:59 PM   #16
igadoter
Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: slack 12.2, debian-Trinity , openbsd
Posts: 729

Rep: Reputation: 56

Quote:
Originally Posted by Miter_J View Post
0.0 Sorry.. I'm really a newbie so I'm not sure if I can catch your point.
My slackware is installed in /dev/sda1 and Ubuntu is in /dev/sda5. I mounted the disk sda5 to /mnt/hd and then I added the info using files in /mnt/hd/boot/. So I think I'm running Ubuntu kernel...
Is there a way to detect whether I'm running Ubuntu or Slackware kernel?
BTW, I have no "ub" folder in slackware(at least I didn't find it - -).
Look at this
image = /boot/vmlinuz
root=/dev/hda1
. label = myLinux
image = /boot/vmlinuz
root=/dev/hda2
label=alsomyLinux

The kernel is in fact the same but root partitions are different. Lilo will look at some fixed partition and in the /boot and load the vmlinuz kernel. According to your choice the kernel will mount /dev/hd1 or /dev/hda2. Slackware huge kernel may runs ubuntu because it is huge - it doesn't need additional drivers. Try dmesg command.
 
Old 01-10-2011, 05:57 PM   #17
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,298

Rep: Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722
From the lilo.conf entry posted it looks like Ubuntu's kernel is being booted properly when loading Ubuntu -- /mnt/hd/boot/vmlinuz. If it wasn't mounted properly lilo would spit out an error, and unless there's crazy symlinking going on that is Ubuntu's kernel. LILO also references inodes instead of file paths, so assuming the Ubuntu /boot partition was mounted on /mnt/hd I see no reason to assume that Slackware's kernel is being used. If you're paranoid you can check the output of `uname -a` in Slackware and in Ubuntu. They should differ in key places.
 
Old 01-10-2011, 06:58 PM   #18
Robert.Thompson
Member
 
Registered: Nov 2009
Location: Montreal, Quebec, Canada
Distribution: Slackware 13.37 -32 Bit
Posts: 578

Rep: Reputation: 49
Quote:
Originally Posted by igadoter View Post
I get the error: page not found.
Try this: http://www.gentoo.org/doc/en/handboo...part=1&chap=10
 
Old 01-10-2011, 06:59 PM   #19
igadoter
Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: slack 12.2, debian-Trinity , openbsd
Posts: 729

Rep: Reputation: 56
I don't understand how lilo is at all able to mount any partition under some mount point. Does during a boot lilo mounts /dev/sda1 under /mnt on /dev/sda5 ?
 
Old 01-10-2011, 07:03 PM   #20
igadoter
Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: slack 12.2, debian-Trinity , openbsd
Posts: 729

Rep: Reputation: 56
Quote:
Originally Posted by Robert.Thompson View Post
Not much help. It's about (the lilo part) configuring three different kernels for the same root and additionally a W$ partition.
 
Old 01-10-2011, 07:19 PM   #21
Robert.Thompson
Member
 
Registered: Nov 2009
Location: Montreal, Quebec, Canada
Distribution: Slackware 13.37 -32 Bit
Posts: 578

Rep: Reputation: 49
You are probably more enthusiastic than I but when I had the same problem yesterday with Windows XP, OpenSuse and Slackware (LILO saw windows & Slackware), I installed Mint Debian onto the OpenSuse partitions (I didn't like it) and installed grub to the MBR as part of the install - now I can boot into Windows, Slackware or Mint.

Originally it was suggested that if I were to re-install Slackware, selecting LILO to MBR, that LILO would pick up OpenSuse as well - I must have don something wrong because it didn't. That's why I installed Mint Debian.

So, if you re-install Ubuntu, it will probably pick up Slackware.

I know, doesn't solve the problem, just circumvents it.
 
Old 01-10-2011, 07:25 PM   #22
bonixavier
Member
 
Registered: Sep 2010
Distribution: Slackware
Posts: 320

Rep: Reputation: 62
The solution to get LILO booting other Linuxes is in the other thread that now has no title.
 
Old 01-10-2011, 09:15 PM   #23
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,298

Rep: Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722Reputation: 722
Quote:
Originally Posted by igadoter View Post
I don't understand how lilo is at all able to mount any partition under some mount point. Does during a boot lilo mounts /dev/sda1 under /mnt on /dev/sda5 ?
LILO doesn't mount anything. LILO is significantly different from GRUB in its execution. GRUB mounts the disk at run-time and tries to load the kernel image/initrd it finds. This means you don't have to rerun anything when you update GRUB, and that you can specify kernel images manually on the GRUB command-line to troubleshoot. LILO takes a much simpler and much more direct route -- less can go wrong, but it isn't as flexible (you must manually run `lilo` to update the MBR after changing lilo.conf). When you run `lilo` after updating lilo.conf, it writes the location of the kernel image and initrd (if there is one) to the MBR directly in the form of inode locations. By doing this, it bypasses the need for any run-time mount points and points directly to the physical location on the hard disk. In GRUB you would specify the location that the kernel image *will have* when the system is booted so it can find it. In LILO you specify the location that the kernel image *has now* and it doesn't need to find it at boot-time since it determines the physical location of that file when writing to the MBR.

Again, based on the lilo.conf portion posted I would be inclined to believe that everything is set up properly...

Last edited by T3slider; 01-10-2011 at 09:16 PM.
 
1 members found this post helpful.
Old 01-11-2011, 03:19 AM   #24
igadoter
Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: slack 12.2, debian-Trinity , openbsd
Posts: 729

Rep: Reputation: 56
@T3Slider
image=/mnt/hd/boot/vmlinuz......(can't remember)
initrd=/mnt/hd/boot/initrd......
label=Ubuntu
root=/dev/sda5
read-only
For me it is absurd. As I understand lilo works during boot it will look under /mnt/hd/ but there should be nothing cause it is used (by default) as a mount point and the directory should be rather empty.
 
Old 01-11-2011, 03:29 AM   #25
igadoter
Member
 
Registered: Sep 2006
Location: wroclaw, poland
Distribution: slack 12.2, debian-Trinity , openbsd
Posts: 729

Rep: Reputation: 56
Quote:
Originally Posted by T3slider View Post
When you run `lilo` after updating lilo.conf, it writes the location of the kernel image and initrd (if there is one) to the MBR directly in the form of inode locations. By doing this, it bypasses the need for any run-time mount points and points directly to the physical location on the hard disk.
Sorry but it is very dirty solution. If only what lilo needs is a kernel and initrd it is better to create a directory
/ubuntu on the Slackware partition and tpcopy both the kernel (ubuntu) and its initrd into this directory.

Honestly I think that ubuntu kernel should be booted by GRUB, I dont trust ubuntu developers. They are unable to do anything in a simple manner.
 
Old 01-11-2011, 03:34 AM   #26
SeSoX
LQ Newbie
 
Registered: Aug 2009
Posts: 18

Rep: Reputation: 0
Quote:
Originally Posted by Miter_J View Post
Haha~ The first "sda7" was just a QUOTE that someone else took for an example~
Now I got this solved.
Just mount the disk and then finding the "image" and "initrd" file would be very easy.
And add

and that's okey~
Now I'm in Ubuntu already.
Thank you, SeSoX
Hi Miter_J, glad it worked

I also have to say that the paths are quite weird, wouldn't imagine it would work but if you say it does, I won't say the opposite

image=/mnt/hd/boot/vmlinuz......(can't remember)
initrd=/mnt/hd/boot/initrd......
label=Ubuntu
root=/dev/sda5
read-only

With those paths you were showing us I'd say you should use something like the following without the '/mnt/hd/' because that's just a directory in your slackware to mount ubuntu, therefore the real path would be '/boot/file'.

image=/boot/vmlinuz......(can't remember)
initrd=/boot/initrd......
label=Ubuntu
root=/dev/sda5
read-only
 
Old 01-11-2011, 04:39 AM   #27
brianL
LQ 5k Club
 
Registered: Jan 2006
Location: Oldham, Lancs, England
Distribution: Slackware & Slackware64 14.1
Posts: 7,139
Blog Entries: 52

Rep: Reputation: Disabled
Quote:
Originally Posted by bonixavier View Post
The solution to get LILO booting other Linuxes is in the other thread that now has no title.
Yeah. I asked for that thread to be merged with this one, but something went badly wrong. Ah well...(what's the smilie for "shrugs shoulders"? )
 
Old 01-11-2011, 06:16 AM   #28
Miter_J
LQ Newbie
 
Registered: Jan 2011
Posts: 24

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by SeSoX View Post
Hi Miter_J, glad it worked

I also have to say that the paths are quite weird, wouldn't imagine it would work but if you say it does, I won't say the opposite

image=/mnt/hd/boot/vmlinuz......(can't remember)
initrd=/mnt/hd/boot/initrd......
label=Ubuntu
root=/dev/sda5
read-only

With those paths you were showing us I'd say you should use something like the following without the '/mnt/hd/' because that's just a directory in your slackware to mount ubuntu, therefore the real path would be '/boot/file'.

image=/boot/vmlinuz......(can't remember)
initrd=/boot/initrd......
label=Ubuntu
root=/dev/sda5
read-only
i added this in my slack and these files are in another disk of ubuntu,so l can only mount it first, or l cant find themů
if what t3slider said is right, this might not matter at all since lilo points out the physical address.
 
Old 01-11-2011, 06:29 AM   #29
SeSoX
LQ Newbie
 
Registered: Aug 2009
Posts: 18

Rep: Reputation: 0
Yes, probably what t3slider said is right and that's why it works, then you will have to mount it and use the full path, totally right Miter_j
 
Old 01-11-2011, 06:31 AM   #30
Miter_J
LQ Newbie
 
Registered: Jan 2011
Posts: 24

Original Poster
Rep: Reputation: 0
Quote:
Originally Posted by igadoter View Post
@T3Slider
image=/mnt/hd/boot/vmlinuz......(can't remember)
initrd=/mnt/hd/boot/initrd......
label=Ubuntu
root=/dev/sda5
read-only
For me it is absurd. As I understand lilo works during boot it will look under /mnt/hd/ but there should be nothing cause it is used (by default) as a mount point and the directory should be rather empty.
hi igoadoter, if lilo points to the physical address instead of an address as the disk path,this shall not be absurd at all.
im now confused about whether lilo is based on slack or not,and also,whether grub is based on ubuntu. if yes, when slack collapsed, will l be able to boot lilo?if no,how could grub know where to search or which to access since l have 2 root(/) for ubuntu and slack?
 
  


Reply

Tags
lilo, ubuntu


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
what do I add to /etc/lilo.conf to boot windbloze ? rob.rice Linux - General 4 12-27-2010 12:35 AM
[SOLVED] How do add lilo entry for ubuntu Tim Johnson Slackware 16 07-03-2010 07:08 PM
How to add Ubuntu 9.04 to lilo sevic33 Linux - Newbie 2 05-27-2009 11:33 AM
Can't add "read-write" to lilo.conf natewlew Slackware 5 07-10-2006 12:33 PM
how to add the line 'compact' to /etc/lilo.conf. kuertensun Linux - Newbie 6 06-23-2005 11:02 PM


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