SUSE / openSUSEThis Forum is for the discussion of Suse 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 had this posted originally under the Ubuntu distribution, but now it has changed to Suse.
I just install Open Suse 10.2, but I need help with editing the menu.lst
I have Freesprie on hdb1, Open Suse 10.2 on hdb2, Kubuntu on hdb3, and swap hdb4. I have already edited it adding Kubuntu. Kubuntu boots part way and then stops. I will post my Suse Grub menu.lst now, maby someone can look at it and right away see what is wrong with it. I just copied and pasted my Kubuntu entry into this Suse menu.lst. I am not prepared right now the post the boot error message but if someones needs it I will post that later:
Code:
# Modified by YaST2. Last modification on Wed Jan 10 04:35:52 UTC 2007
default 1
timeout 10
gfxmenu (hd1,1)/boot/message
###Don't change this comment - YaST2 identifier: Original name: linux###
title openSUSE 10.2
root (hd1,1)
kernel /boot/vmlinuz-2.6.18.2-34-default root=/dev/hdb2 vga=0x31a
resume=/dev/hdb4 splash=silent showopts
initrd /boot/initrd-2.6.18.2-34-default
###Don't change this comment - YaST2 identifier: Original name: hidden
(alt1) (/dev/hdb1)###
title hidden (alt1) (/dev/hdb1)
title Kubuntu, kernel 2.6.15-23-386
root (hd1,2)
kernel /boot/vmlinuz-2.6.15-23-386 root=/dev/hdb3 ro quiet splash
initrd /boot/initrd.img-2.6.15-23-386
###Don't change this comment - YaST2 identifier: Original name: Freespire
Ver. 1.0.13 (/dev/hdb3)###
title Freespire Ver. 1.0.1
I have Freespire on hdb1, Open Suse on hdb2 and Kubuntu on hdb3. Freespire boots ok, Suse boot ok, but Kubuntu was missing from the menu.lst so I added that enty. Kubuntu is the one that will not boot. It does look like it is going to load but then I get the above text.
Quote:
ps. i think you missed a little of ur menu.lst off the bottom.
np bud. hope tommorrow is better, post the rest of what you put in for the Freespire and we'll see. btw, i dunno where you get them, but if you get a copy of mepis testing that is a live cd, i think it has a tool that can repair grub on it. really grub isnt that complex, so we should be able to piece it back together.
ALTHOUGH, you could boot up in kubuntu and get kubuntu or even freespire to manage the bootloader, then im pretty sure it would be as you'd expect:
title
root
kernel
then initrd
to do that, boot of a rescue (or one of the installs) and seup grub as thus --
Code:
# grub
# root (hd1,2)
# setup (hd0)
but seeing as you have 3 distribs im sure uve become familliar with grub anyhow.
it wouldn't be as pretty as suse, granted although you could probably skin it to some fancy picture, but it'd sure work.
When I posted this in the LQ Ubuntu distributions forum, I was telling about I resized all my partitions after I made the fresh installs of Freespire, Suse, and Kubuntu with Gparted live. I have never had any problems with Gparted before, and this was the most recent version (0.3.2).
But I think resizing all three partitions corrupted my file sytems. Originally I formatted them all Reiserfs, but now I started all over from scratch and reformatted them to ext3, and did another fresh install of all my distros and now everything is ok. I doubt very much if ext3 had anything to do with it, but just in case I thought it wouldn't hurt to try ext3, it is supposed to be more stable, but you couldn't prove it by me !
A lot of extra work, but all is well............did I learn anything from all of this ?......hmmmmm
If you did all three partitions at the same time you could have had a disk reread issue. I get that sometimes with random disks after altering partitions. They don't always say they dont quite understand the changed config, if it were me i'd restart between each resize.
anyhoo.....
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.