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 no idea how she did this, but a friend of mine repartitioned her laptop this weekend and installed Ubuntu (dual-boot). Problem is, Windows won't boot anymore (saying something about hal.dll being missing).
Her fdisk output is really odd, and I don't know how to translate it well to grub in the first place, so I am hoping that somebody here can help fix her grub config file? This is what she sent me:
$ cat menu.lst | grep -v \#
title Ubuntu, kernel 2.6.20-15-generic
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=f84949bd-0bf4-49ef-a420-6ae8488621a8 ro quiet splash
title Ubuntu, kernel 2.6.20-15-generic (recovery mode)
kernel /boot/vmlinuz-2.6.20-15-generic root=UUID=f84949bd-0bf4-49ef-a420-6ae8488621a8 ro single
title Ubuntu, memtest86+
title Other operating systems:
title Windows XP Media Center Edition
$ cat fstab
Device Boot Start End Blocks Id System
/dev/sda1 10569 11801 9904072+ 83 Linux
/dev/sda2 * 1 10568 84881836 7 HPFS/NTFS
/dev/sda3 12068 12161 755055 5 Extended
/dev/sda4 11802 12067 2136645 83 Linux
/dev/sda5 12089 12161 586341 82 Linux swap / Solaris
/dev/sda6 12068 12088 168619+ 82 Linux swap / Solaris
What do you think needs to be done so that XP will boot again?
Yes, XP didn't have any trouble for me before I installed Linux, either. I think the install process changed something on the partition level on the disks, in a way that Windows has trouble coping with.
Anyway, you may have to re-install GRUB to the MBR once you're done. You'll need some kind of Linux disk to boot off and get into a command line. Ubuntu/Kubuntu and Knoppix work great for this. You'll need to run the grub shell, and run commands something like this:
grub> setup (hd0,1)
grub> install (hd0)
BEFORE YOU DO, though, read the instructions here http://www.gnu.org/software/grub/man...-natively.html
They will help figure out exactly what (hd_) arguments to use, as it depends on your paritions and hard disks.
As more background on the problem: I'm not sure if it's the same thing, but I know for a while there was a problem with a lot of the Linux installers disk partition utility (disk druid, maybe?) that had a slightly different notion of partition tables, and caused problems for Windows after creating Linux partitions. The old school fdisk didn't have this problem.
The good news is that repairing the information (MBR, if I remember right) made both Linux and Windows happy.
What ended up happening is something related to that odd partition scheme, and the fact that Gateway's new laptops all have SATA hard drives. The WinXP recovery console doesn't have the right drivers to find the hard drives, so that doesn't work. And reinstalling XP from off-the-shelf CDs doesn't work either, for the same reason (it's the scenario where you need to hit F6 to install additional drivers, RAID or SATA, etc, but XP (and Vista, apparently?!) still insists on looking for those drivers on a floppy disc. You can't make it look at a USB drive. Computers don't come with floppy drives anymore, especially not laptops! Come into the 21st century, Microsoft!!!11 >_<)
What she ended up doing was wiping the drive, deleting all the partitions, repartitioning with gparted to a more intuitive scheme, ripping the XP disc to .iso, opening that with an ISO editor, following the instructions for adding SATA drivers into the XP install disc itself, and reinstalling that way. Then she reinstalled Ubuntu, and let it use Grub on the MBR. XP's still not perfect, but it's usable again