Linux - NewbieThis Linux forum is for members that are new to Linux.
Just starting out and have a question?
If it is not in the man pages or the how-to's this is the place!
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.
Introduction to Linux - A Hands on Guide
This guide was created as an overview of the Linux Operating System, geared toward new users as an exploration tour and getting started guide, with exercises at the end of each chapter.
For more advanced trainees it can be a desktop reference, and a collection of the base knowledge needed to proceed with system and network administration. This book contains many real life examples derived from the author's experience as a Linux system and network administrator, trainer and consultant. They hope these examples will help you to get a better understanding of the Linux system and that you feel encouraged to try out things on your own.
Click Here to receive this Complete Guide absolutely free.
Hi,I am a noob inching towards intermediate state.
Simply put,when I face problems, I look up in google and troubleshoot accordingly and that's that.
Also I am a distro hopper, but keep openSUSE 11.4 KDE installed permanently. A couple days back I tried to install PCLOS 2012.2 and mint12 KDE along with win 7(games only! ) making it a triple boot (dual boot+1) machine. Now as PCLOS uses grub legacy and mint uses grub2 I am having either mint+7 or PCLOS+7 but not all three. I tried installing the bootloaders on their respective /boot partitions and also on MBR(stupid eh?).
Also tried "redo-mbr" from PCLOS which was supposed to make it alri8.
now when I use 2 distro both using grub2, it's all fine and sunshine, but not with grub1 and grub2.
What do I need to do?
plz offer complete guidance.
long live LQ.
Neither grub legacy or grub2 always find every available operating system. In grub legacy, you have to edit the menu.lst. You would have to edit whatever the equivalent in grub2. This is usually fairly simple when some are already detected because you have sort of a template to go by. So choose one or the other and stick with it until every system is available. Then make a copy of the appropriate file for future reference.
The grub2 manual (GNU GRUB Manual 1.99) section (4.1.2 Chain-loading an OS) describes chainloading. Since OpenSuse is the distro you keep permanently, you should do it from OpenSuse. That way, you can change other distros at will without affecting your OpenSuse installation in any adverse way.
@bigrigdriver, but openSUSE has grub legacy. Currently I cant get into the other linux os (the one that uses grub2)
So how do I do it?
@liberalchrist, in openSUSE I can look around and find the menu.lst but do i write in it? a mere mentioning of the other distro(mint) sure won't make it bootable?
If you are going to hop around different distros, you need to learn as much as you can about booting. It took me a long time to learn about grub. I later switched to lilo, and that took a while as well. Go to the grub homepage, http://www.gnu.org/software/grub/, and read the documentation. I personally find legacy easier to understand, but you may want to be more progressive. Yes, you do want to write in the menu.lst. That is the only way you can make changes.
@lc,so i went to openSUSE's bootloader, added mint, specified it's /boot partition and rebooted. -> mint didn't boot
again I went to bootloader, edited mint and specified it's / partition and rebooted -> mint didn't boot.
(Is this the same thing as editing menu.lst? coz both time the menu.lst showed mint as an entry...)
just to make sure this is not mint's fault,installed chakra 2012.2 and tried again. same result.
here's menu.lst of openSuSE
"# Modified by YaST2. Last modification on Tue Feb 21 22:20:30 IST 2012
# THIS FILE WILL BE PARTIALLY OVERWRITTEN by perl-Bootloader
# For the new kernel it try to figure out old parameters. In case we are not able to recognize it (e.g. change of flavor or strange install order ) it it use as fallback installation parameters from /etc/sysconfig/bootloader
First, you need to decide what operating system you are trying to install and stick with it. Only one bootloader can be installed on the MBR at one time. This needs to be openSuse because this is your permanent system. Assuming this is the bootloader you have installed, each time you add or change another distro, you need to edit this menu.lst with a text editor. In order to chainload, you would have to choose the option to install Grub in the root partition when installing Chakra. I don't know how chainloading works between Grub Legacy and Grub2, but I doubt that the quotation marks at the end of the chainloader +1 belong there.
Normally, between linux installations it is better to use a regular grub entry such as the one's you have for openSuse. It would look something like this. You have to make sure you are identifying the right partition in your root line and the right kernel and initrd locations in your other entries.
title Chakra 2012.2
kernel /boot/vmlinuz-3.1.0 root=/dev/sda10
Read this tutorial. Also read all the Grub website documentation for your brand of Grub as I suggested in my earlier post. You will not get a complete tutorial in a post on this forum.
Last edited by liberalchrist; 02-21-2012 at 02:43 PM.
You refer in one of your post to a separate boot partition for Mint as well as the root partition for the filesystem. Have you now removed Mint and replaced it with Chakra? Do you actually have a separate boot partition? I use PCLinux to boot Ubuntu, Mint, etc.. with an entry like this:
Ubuntu is on sda5 so you will need to change your entry to (hd0,9) if your system is on sda10.
I'm not sure why your chainloader entry didn't work. You might try googling bootinfoscript, downloading it and running it from Opensuse and posting the results.txt file it produces. It will show a lot of details about your system and boot files which should help to resolve your issue.
I fail to see why chainloading a Linux OS is a good idea. Using the installed legacy grub, you need to point it to a valid kernel, and a valid initramdisk (assuming the target Linux uses one).
title Your Target OS, whatever it is
kernel /boot/vmlinuz-2.6.xx.yy-something root=/dev/hdxn
You will have to figure out what to use to tell grub which partition it is supposed to use to find the boot directory for the specified OS. The parameters 'x' and 'y' in the example should be replaced by the hard-disk number (starting from zero) and the partition number on that disk, also numbered from zero, respectively. If you have three hard disks, and the target OS is on the third one, and the boot partition is the second partition on that disk, the root parameter would look like
This tells grub how to find a partition. Now, tel grub what files make up the bootable OS:
# From a Debian 5 installation
kernel /boot/vmlinuz-2.6.26-2-686 root=/dev/hda1 ro
The specified directories are expected to be found on the partition identified to grub as the 'root', above. The kernel name and initrd are simply the names of the respective files in the specified directory. Give the kernel a pointer to what it is supposed to mount as a root filesystem. Use Linux syntax (/dev/hdc1) rather than grub syntax.
You can mount the various partitions on your system to poke around and find where the desired boot directories are. Use the kernel and initrd images that you find there.
I agree with theNbomr, chainloading makes no sense. I do know, however, that some distributions have tweaked themselves so much that they need a whole list of boot options appended to their kernel line to present themselves the way they want. Even so, the boot options can be transcribed to the working menu.lst.
@lc, I'l surely go through whatever documentation I can find on grub1 and 2,somehow I feel this area has been overlooked from a noob's perspective.
@yancek, yes I installed Chakra over the partitions of Mint. that means / of Chakra was on / of mint (formatted) and /boot on /boot.
And yes I have two /boot now. one of openSUSE and other of chakra(which was mint BEFORE).
@Rod, I learned the (hdx,y) thing the hard way, but how do I get access to the /boot partitions of chakra while I'm on SUSE? it's plain impossible to view the files even if I grant root privilege.
Damn! I already feel I should stick with dual booting . Also I appreciate the help you all are trying to give, but plz understand that I have already tried rescatux,super grub cd,Dedoimedo's tutorials on his website and few others. and I am yet to find a result. Can sum1 tell me if I can install Grub2 on openSUSE?