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.
I have a 160 GB hard drive that I have created 3 partitions on, sda1 which is ext3, sda2 which is NTFS, and sda3 which is ext3 also. I have installed two different Linux distro's, Backtrack2 on sda1, and then Linux Mint on sda3. GRUB recognizes the NTFS partition and the Mint partition, both Windows and Mint boot fine. However, the Backtrack 2 partition was not recognized, so I added it myself to menu.lst:
## ## End Default Options ##
title Backtrack 2
kernel /boot/vmlinuz root=/dev/sda1 ro quiet splash
title Linux Mint (KDE), kernel 2.6.17-10-generic
kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/sda3 ro quiet splash
title Linux Mint (KDE), kernel 2.6.17-10-generic (recovery mode)
kernel /boot/vmlinuz-2.6.17-10-generic root=/dev/sda3 ro single
title Linux Mint (KDE), memtest86+
### END DEBIAN AUTOMAGIC KERNELS LIST
# This is a divider, added to separate the menu items below from the Debian
title Other operating systems:
# This entry automatically added by the Debian installer for a non-linux OS
# on /dev/sda2
title Windows Vista/Longhorn (loader)
The partition can be mounted in Linux Mint, so I based my grub entry on the lilo.conf file:
As I mentioned, when I try to boot the Backtrack 2 entry in GRUB, it fails with an error stating that the partition cannot be mounted. I have very little experience with GRUB, how can I get this to work?
That's what I did, but there was only one initrd in the boot folder:
tsnow@Mint-laptop:/Backtrack2/boot$ ls -a
. .. map splash.bmp splash.initrd vmlinuz
Could it be somewhere else? This distro is based on SLAX, but I installed the full version to the hard drive, so it should be able to boot, assuming I used lilo. Isn't there a way I can install lilo to that partition, then have GRUB load lilo? Cause I know that you chainload the NTLDR for Windows...
I prefer to have a separate boot partition; then copy the images into that, then you can use something similar to what you have (except the root directive of course).
Means you have to think up names for your kernel images ...
At this point, I suggest re-installing Backtrack. Install the bootloader to the boot sector of the partition (not to the MBR). Pay careful attention to the partition selection and format options.
Then edit the grub config in Mint to read:
The chainloader option works just as well as specifying the kernel parameters and initrd. It works because the bootloader for that partition is completely installed in (hd0,0) boot sector, and you just pass the boot process over to that bootloader.