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 need help... am running red hat 9 in a dual boot environment with windoze and everything has been fine until today. There have been a number of unclean shutdowns in the past few days due to an incorrectly configured power-save mode for my laptop but on each reboot I have run the interactive filechecking tool and it has shown a clean /root filesystem. When I boot the windows bootloader goes first and then it's GRUB as I must have said windoze is the default on install.
I logged into GNOME today, used some apps, then went to get a cup of tea, came back and the system rebooted with the kernel panicing. I have had various kernel panic messages(aiee interrupt handler, no init) as well as the system message " the amount of memory in the system has changed"(twice then it went away) Things seem erratic: I can sometimes get into windoze and sometimes the windows bootloader screen freezes. Grub is messed up as it refuses to show itself.
What I have done:
-did a hard drive diagnostic--it passed
-resat the memory and the hardrive
-searched for the answer on Google, here
-gotten into windows and replaced the bootsect.lnx file and checked boot.ini (now instead of skipping altogether it says GRUB)
-entered into rescue mode with the CD and inspected /boot and grub.conf, which seem allright, though I am a newbie.
-booted from the boot diskette and entered the kernel params "linux root=/dev/hda6" (kernel panic no init code before says:
EXT3-fs: INFO recovery required on readonly filesystem
EXT3-fs: write access will be enabled during recovery
kjournald starting . Commit interval 5 seconds
EXT3-fs: recovery complete
EXT3-fs: mounted filesystem with ordered data mode
pivotroot: pivot_root (/sysroot/sysroot/initrd failed: 2
umount /initrd/proc failed: 2
Freeing unused kernel memory: 132K freed
Kernel panic: no init...
So here I am-how can I diagnose this and fix it?
Use your installation cd in rescue mode, then unmount all your partitions ('mount' will tell you which /dev/hdX are mounted) and run fsck on all of them. It should be able to fix all errors (but only if the partitions are not mounted).
When you can't unmount it usually means one of the processes is using it (or probably you're in a directory on that disk on one of the consoles). But you are probably after a reinstall, so it doesn't matter...