Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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 cannot boot Windows XP after installing RH9 Linux. When I get to GRUB, the Red Hat Linux boot works fine, but the Windows XP hangs after the following GRUB commands:
I have tried adding "makeactive" after and before "chainloader +1", but it doesn't make a difference.
I have changed GRUB to be installed in the first sector of the HDD instead of the MBR, but it still doesn't make a difference.
I have 1 HDD with 250GB. I tried several installation configurations, but always with the same result as noted above:
- installing Windows in a small partition in the beginning, then Linux;
- creating a small partition in the beginning (1024 issue?) for the /boot directory, then windows and then linux (/ and swap)
- installing Windows first, but in the end of the HDD; then installing Linux in the beginning.
I also tried installing Linux first and in the beginning of the HDD, then Windows XP. In this last case, I lost GRUB and Windows XP took over and it seems GRUB was not called. I then tried to re-install Linux just to get GRUB to be called, but it did not work either.
Also, before I forget:
- I also tried LILO... did not work either!
- I do not have a floppy disk drive; just a CD/RW and DVD.
- I have searched this site and others... it seems the best to resolve my problem is located at enterprisedt.com/publications/dual_boot.html. Do you think this solution will resolve my problem?
I think I'm still missing something, so please allow me to ask two questions:
1) Why do I need to edit grub.conf and re-install GRUB? GRUB is already installed and the commands for the Windows boot (rootnoverify and chainloader) are already there, as per my description above. What am I missing?
2) Why do I need to do fdisk? When installing RH9, you can review the partition allocations as part of the view screen in Disk Druid. Do I need anything else?
I don't mean that you have to re-install GRUB.
The ./grub-installer /dev/hda means that GRUB will put itself into the MBR of hda.
You don't need to do an fdisk. I meant you could do it beforehand.
It is just easy to know where your /root is. But if you can use Disk Druid, is also good.
or if you memorize all the partitions then it is also not needed.
The fdisk part is just a help to edit the grub.conf file to write down the right locations of your /root and kernel image.
The grub.conf contains the pointers to where linux is and where windows is located.
If the grub.conf contains no info, then your boot will hang because grub won't know where to find linux.