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.
Because it will overwrite any other operating system's bootup. In some Linux distributions you have to explicitly tell LILO (or grub) about your windows partition for it to be able to boot into, for others it will automatically check to see if you have windows and add that as an option on the bootup menu.
When you install lilo, it will put a copy of the overwritten sector in " /boot/boot.nnnn.
( look in your /boot-dir, i have a file /boot/boot.0300 wich is 512 bytes long )
you can restore it by using the " -u " option or copy it with "dd"
( see " man lilo " ).
Worked perfectly. It totally wiped the MBR. I had installed RH and was switching back to Slack, but kept getting GRUB stopping the boot. Apparently RH wrote stuff to the MBR and even deleting all partitions with cfdisk wasn't getting rid of the data. Entering the dd command wiped all the partitions from the disk. Going back into cfdisk and there was just one undefined partition.
Guess it could be a bad joke if you had something to loose