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.
rayne. from my experience, install to the mbr. Lilo should most definitely load. if it doesnt detect your windows installation, you can edit your lilo.conf file quite easily, look it up on the net.
If you muck up your mbr you can always restore it using the windows XP installation cd - Repair utililty - command FIXMBR.
(assuming you use windows XP, im sure you could do something about the same with windows 2000). If anyone knows a better solution, please post it.
You didn't supply a whole lot of information, digital_dreams. You say that mandrake will dual-boot? What boot manager is that? What boot manager is it that you're trying to use with RH? Have you tried manually installing the boot manager?
Mandrake works with either grub or lilo. Redhat wont boot with either, it is a known issue on the net, i just thought there may be a known solution as to why windows continues to load automatically instead of lilo/grub.
I havent installed the boot loader manually, maybe will in the near future if i find time.
The BIOS and its bootstrap loader look in the MBR of the first bootable device. If it finds some boot code, it loads it into memory and executes it. If the code that it finds IS boot code, then upon execution IT will look further, using whatever instructions are there, for code that will load either an OS's kernel or load a boot manager that will control the loading of some OS's kernel.
In the Windoze case. the BIOS and bootstrap loader finds code on the MBR that points to a specific boot sector. The bootstrap loader, loads whatever is in that bootsector to memory and executes it. If its Win9x, the bootsector code just points to the location of the kernel executables. If its Win2K/WinXP/WinNT, the boot sector code points to ntldr which manages loading a kernel.
If the the code that the BIOS and bootstrap loader find has nothing to do with Grub/Lilo, then neither Grub nor Lilo will be executed -- ever. With Win9x, it is absolutely essential that Grub or Lilo have code on the MBR, or some third party boot manager code on the MBR that includes some means of booting Linux. With Win2K/WinXP, you have the option of using ntldr, plus an appropriate boot.ini entry, which executes a copy of the Linux bootsector (as a file) when selected.
If you have installed both a Windoze and a Linux and are unable to boot one or the other, then you have made an error during the installation. It has nothing to do with RedHat, or Mandrake, or Slack, or any other Linux distro, it is simple human error due to lack of understanding!!