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 screwed up my system .
I have xp and slackware as a dual boot.
I was running out of room on my "/" root partition, hdc5 so I decided to make a bit more room by moving things over.
I defragged xp and reduced it by 1 gig. Moved my swap and reduced it to 800 mb. Then increased my "/" root partition by 1+ gig. Now my system wont boot. Grrrrrrr. Im currently running from a live cd.
When I boot my computer I only get this,"99 99 99 99 99 99 99 99 99."
How can I fix this? Your help would be much appreciated!
Changing the size of swap probably did her in. I use bootitng for my boot manager, I can move swap around and my Linux systems will boot and resume swap without editing anything, but I haven't tried changing the size of swap.
Some Linux may still keep track of the exact location of the partition on the drive and refuse to boot if they are not where expected.
Some Linux may not work if the start of the / partition's location has changed.
With my boot manager and the distributions I've installed, these issues are not an issue.
Personally, I don't think that the change of the swapsize is responsible for the 99. Reason is that the system (to my knowledge) has not even attempted yet to setup the swap.
Did you run lilo (as a command) after you made the changes?
If not, the following is what I would try (no guarantee whatsoever)
boot from slack CD and login (like with install)
chroot to the directory where you mounted hdc5
if no errors, reboot
else fix them in the lilo configuration file (no slack at hand, so not sure what the file is called (menu.lst? lilo.conf?))
hope it does the trick
PS make backups if your data is important
Last edited by Wim Sturkenboom; 03-08-2008 at 12:52 AM.
Reason: added PS
The chroot was a new one for me.
I tried to run lilo on my hd by
But that did not work.
Just put "lba32" (without the quotes) in my lilo.conf and run lilo again?
The reason was that you had to change to the mount point of the chroot you desired.
The easiest way would be to use the install cd1 to boot the system as if you were going to install. Then after you get to the login from the cli (command line);
~#mkdir /slacktemp #temporary mount point
~#mount /dev/your_device /slacktemp #this is the device you installed to
~#chroot /slacktemp #change to yours
~#cd /slacktemp/etc #change to directory with lilo.conf
~#vi lilo.conf #edit lilo.conf, if need be
~#lilo -v -t -b /dev/your_device #sda, hda this will only test
~#lilo -v -b /dev/your_device #this will write MBR to your_device