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'm getting this absolutely whacky bootup problem ever sice I upgraded to fedora core 2.I have a dual partition system with debian woody.Each time I shutdown my system from fedora,i can't boot it the next time I power up.The system simply stops after doing the boot checks.I don't get a login prompt and HD led goes off showing no hard disk activity.Fedora boots up fine after power on if I shutdown the system from Debian.I'm totally flumoxxed as to what the problem could be.
One possible reason could have been that I had allocated only 100 megs to the boot partition.But when I saw that the boot image was very small,I modifie the boot to 15 megs.But even when I had a 100 mb /boot,I used to get the same problem.Please advise,coz to access fedora I have to first boot to debian and then back.
Distribution: RedHat (RHEL, FC, CentOS), openSuSE, Mac OS X
so you run fc, reboot fc, nada
but you run fc, reboot to debian, reboot to fc, presto?
neat ... erm ... i'm thinking framebuffer/xserver
try changing your /etc/inittab to go to a default run level of 3 instead of 5 in FC, if you get something that way ... i'm not sure what to do next ... hee hee hee
alternatively i was just thinking, could be that ... do you have two /boot ? ie one for FC and one for debian ? or is your lilo.conf file (or grub) pointing at the right partitions for the corresponding /boot directories?
u seem to have duplicate /boot partitions.....
check wchich one is being loaded and see the lilo.conf or grub.conf files that are being used...
if u cant fix the problem then do linux rescue ....in the distro whose /boot is being mounted each time!
I'm using GRUB as my boot manager.I tried checking the grub.conf file,but there seemed to be a single boot image in the conf file.To throw more light on the issue,when I upgraded to core 2 from core 1,during the install process i got an error saying that ""a previous bootloader had incorrectly configured the boot image.You may choose to ignore but this can cause problems later.Ï ignored it coz I thought that the install would wipe out the previous boot image and create new one.But now I do have problems.What can I do to correct this error?
copy one of the /boot partitions to a common partiotion or a cd ...i know when u r in one of the distros accsseing the other /boot is a pain coz it wont be mounted....but u have to some how make a bck up of those files and then delete that partition and copy non duplicate files to the existing /boot then boot with the first fedora cd
then just before anaconda starts up type linux rescue and then type chmod /mnt/sysimage and rescue the other distro
i.e make a proper mbr....