SlackwareThis Forum is for the discussion of Slackware Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
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
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
You have to add something like this (to the bottom of your lilo.conf):
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?
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?
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.
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.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.