LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Slackware-No critical - Lilo conf & Grub (http://www.linuxquestions.org/questions/slackware-14/slackware-no-critical-lilo-conf-and-grub-4175468605/)

PeterUK 07-05-2013 11:57 AM

Slackware-No critical - Lilo conf & Grub
 
I am installing all again and I forgotten you first install Slackware then Ubuntu for multi- booting.

So I did the other way around and at the time I selected auto to lilo and it just messed it up.

it just make the config to only Slackware booting, after looking in the next I found you could change the lilo config file to add another booting but I was not very clear due to there are in different partitions.

I stated as not Critical due to I am re-installing Ubunutu as I write, I figure about it was going to take me more time to get try this and get it right plus ubuntu do lots of kernel update and it will be harder to update lilo every time (Maybe Ubuntu can do it auto with lilo?)

Now this is more a learning exercise, Do you know how to set the second booting into the lilo config file? I know now some bits but I dont know the writing

STDOUBT 07-05-2013 01:08 PM

PeterUK,
No offense, but you really need to include more information in your posts.

For example: how can we advise you regarding your lilo.conf entries when we can't see what you
put in there? Show us your lilo.conf!

Also, keep in mind you always need to run "lilo" as root at the command line any time you
make a change to lilo.conf.

shm0 07-05-2013 01:27 PM

You have to add something like this (to the bottom of your lilo.conf):
Code:

image = /boot/vmlinuz
  root = /dev/sda1
  label = Ubuntu Linux
  read-only

Make sure you:
  1. Replace /dev/sda1 to the root partition of your Ubuntu Linux
  2. Make sure the image exists
  3. Save the file and then run /sbin/lilo as root

You can see a full walkthrough here.

PeterUK 07-05-2013 01:52 PM

Quote:

Originally Posted by STDOUBT (Post 4984822)
PeterUK,
No offense, .

No taken!

I didnt post it because I rearch and I didnt find a solution happy about it, also look at another machine grup script and I could not relate to it

But now is installed and working with grub and it supposing both OS

For those which like to lose in code: here is lilo.conf

Code:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append=" vt.default_utf8=0"
boot = /dev/sdaxx

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/slack.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 255,0,255,0,255,0
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 60,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 65,27,0,255

# Standard menu.
# Or, you can comment out the bitmap menu above and
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 1200
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# Normal VGA console
vga = normal
# Ask for video mode at boot (time out to normal in 30s)
#vga = ask
# VESA framebuffer console @ 1024x768x64k
#vga=791
# VESA framebuffer console @ 1024x768x32k
#vga=790
# VESA framebuffer console @ 1024x768x256
#vga=773
# VESA framebuffer console @ 800x600x64k
#vga=788
# VESA framebuffer console @ 800x600x32k
#vga=787
# VESA framebuffer console @ 800x600x256
#vga=771
# VESA framebuffer console @ 640x480x64k
#vga=785
# VESA framebuffer console @ 640x480x32k
#vga=784
# VESA framebuffer console @ 640x480x256
#vga=769
# End LILO global section
# Linux bootable partition config begins
image = /boot/vmlinuz
  root = /dev/sdaxxxxx
  label = Linux
  read-only
# Linux bootable partition config ends



---------- Post added 07-05-13 at 07:53 PM ----------

Quote:

Originally Posted by shm0 (Post 4984827)
You have to add something like this (to the bottom of your lilo.conf):
Code:

image = /boot/vmlinuz
  root = /dev/sda1
  label = Ubuntu Linux
  read-only

Make sure you:
  1. Replace /dev/sda1 to the root partition of your Ubuntu Linux
  2. Make sure the image exists
  3. Save the file and then run /sbin/lilo as root

You can see a full walkthrough here.

Thanks wring again realize there is a file called config example , upsss

PeterUK 07-05-2013 02:04 PM

UPDATE:
Grub
pull Slakcware like
setparams 'Linux (on /dev/sda6)'

insmod part_msdos
insmod ect2
set root='(hd1,msdos6)
serach --no-floppy --fs-uuid --set=root xxxxxxxxx <- big number the media mounting
Linux /bootable/vmlinuz root=/dev/sda6 ro vt.default_utf8=0 vga = normal

There us the ubuntu version but i think none one is interested on see that, right?

PeterUK 07-05-2013 03:41 PM

Quote:

Originally Posted by shm0 (Post 4984827)
You have to add something like this (to the bottom of your lilo.conf):
Code:

image = /boot/vmlinuz
  root = /dev/sda1
  label = Ubuntu Linux
  read-only

Make sure you:
  1. Replace /dev/sda1 to the root partition of your Ubuntu Linux
  2. Make sure the image exists
  3. Save the file and then run /sbin/lilo as root

You can see a full walkthrough here.

If I do this I get:

Code:

Warning: LBA32 addressing assumed
Added Linux  *
Fatal: open /boot/initrd.img-3.5.0-23-generic: No such file or directory


PeterUK 07-05-2013 03:48 PM

UPDATE: You know when you do something trying to avoid something to happy... well it did.

On my Slackware installation I did the "slackpkg upgrade-all" and updated the kernel so I had to allow lilo to be updated so now lilo is back and I cannot run Ubuntu, I added on the config file as:

the thing is Ubuntu is sitting into a partition that Slakeware has mount. I think that is the problem?

my addition is:

Quote:

image = /boot/vmlinuz-3.5.0-23-generic
label = "Ubuntu 12.04"
root = /dev/sda4
read-only
initrd = /boot/initrd.img-3.5.0-23-generic
But this is not working

Didier Spaier 07-05-2013 04:15 PM

The kernel and initrd for ubuntu are probably not in the /boot partition of Slackware

You should mount the partition where Ubuntu lies, for instance:
Code:

mkdir /ubuntu
mount -t auto /dev/sda4 /ubuntu # assuming that ubuntu / partition is /dev/sda4

then write:
Code:

image = /ubuntu/boot/vmlinuz-3.5.0-23-generic
label = "Ubuntu 12.04"
root = /dev/sda4
read-only
initrd = /ubuntu/boot/initrd.img-3.5.0-23-generic


PeterUK 07-05-2013 07:29 PM

Quote:

Originally Posted by Didier Spaier (Post 4984914)
The kernel and initrd for ubuntu are probably not in the /boot partition of Slackware

You should mount the partition where Ubuntu lies, for instance:
Code:

mkdir /ubuntu
mount -t auto /dev/sda4 /ubuntu # assuming that ubuntu / partition is /dev/sda4

then write:
Code:

image = /ubuntu/boot/vmlinuz-3.5.0-23-generic
label = "Ubuntu 12.04"
root = /dev/sda4
read-only
initrd = /ubuntu/boot/initrd.img-3.5.0-23-generic


I didnt do this but I gave the mounted path and the ran the command: sbin/lilo... and then I edited the like again to the right sda and to the folder boot in the ubuntu partition. reboot and ran the Linux Ubuntu updated it keep saying there was not hard drive driver but I manage to log in as root into Ubuntu user but it looked to badly booted I about the booting and re install Ubuntu for the third time in one day : :-o, now I have Grub working again booting both systems.

PeterUK 07-08-2013 08:37 AM

How can I which manually between lilo or Grub?

kikinovak 07-08-2013 12:57 PM

Quote:

Originally Posted by PeterUK (Post 4986188)
How can I which manually between lilo or Grub?

42.

jtsn 07-08-2013 02:10 PM

Quote:

Originally Posted by PeterUK (Post 4984795)
I am installing all again and I forgotten you first install Slackware then Ubuntu for multi- booting.

Multi-booting different Linux distributions is way harder than multi-booting Linux with any other operating system. My recommendation is:

Install Ubuntu and Slackware in different primary partitions and let them make their own partitions bootable with their own bootloader. Install Slackware with LILO into sda1 and Ubuntu with GRUB into sda2. Don't let them touch the MBR.

Install an independent boot manager like BootEasy v1.7 into the MBR to switch between the partitions. This way you can update either Slackware's LILO and Ubuntu's GRUB2 configuration without breaking your multi-boot system.


All times are GMT -5. The time now is 04:32 AM.