Quote:
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. |
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.
|
Quote:
|
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 ?
|
Quote:
|
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. |
The solution to get LILO booting other Linuxes is in the other thread that now has no title.
|
Quote:
Again, based on the lilo.conf portion posted I would be inclined to believe that everything is set up properly... |
@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. |
Quote:
/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. |
Quote:
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 |
Quote:
|
Quote:
if what t3slider said is right, this might not matter at all since lilo points out the physical address. |
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 :)
|
Quote:
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? |
All times are GMT -5. The time now is 06:42 PM. |