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 fairly new to linux, and a few days ago, as I was updating my system, I got the "EBDA is big ; kernel setup stack overlaps LILO second stage" error after reboot.
I use a 3- boot, ( Win XP / Debian / Debian) and Windows XP works fine, but I can't launch any of the Debian.
The only problem problem is that when I try to chroot, I got another message, "chroot: failed to run command `/bin/bash': No such file or directory"
I googled this message too, but found no relevant answers.
I am now using a knoppix usb drive to try to repair the lilo, but I ran out of ideas ...
Any iclue, either for the lilo or chroot problem ??
Thanks for the answers !
Well, before chrooting, you'll have to mount the / partition of your Ubuntu. The chroot-command as you've executed it provides, that / of Ubuntu is mounted to /mnt. Please check this. In your output of "df -h" there is nothing mounted on /mnt. Therefore you get the errormessage about /bin/bash not found.
1.Boot to the LiveCD Desktop . The Live CD must be the same as the system you are fixing - either 32-bit or 64-bit (if not then the chroot will fail). 2.Open a terminal 3.Determine your normal system partition - (the switch is a lowercase "L")
sudo fdisk -l
If you aren't sure, run
df -Th. Look for the correct disk size and ext3 or ext4 format. 4.Mount your normal system partition:
Substitute the correct partition: sda1, sdb5, etc.
sudo mount /dev/sdXX /mnt # Example: sudo mount /dev/sda1 /mnt 5.Only if you have a separate boot partition:
sdYY is the /boot partition designation (for example sdb3)
sudo mount /dev/sdYY /mnt/boot 6.Mount the critical virtual filesystems:
sudo mount --bind /dev /mnt/dev
sudo mount --bind /dev/pts /mnt/dev/pts
sudo mount --bind /proc /mnt/proc
sudo mount --bind /sys /mnt/sys 7.Chroot into your normal system device:
sudo chroot /mnt 8.Do your work 9.Exit chroot: CTRL-D on keyboard 10.Unmount virtual filesystems:
sudo umount /mnt/dev/pts
sudo umount /mnt/dev
sudo umount /mnt/proc
sudo umount /mnt/sys
If you mounted a separate /boot partition:
sudo umount /mnt/boot 11.Unmount the LiveCD's /usr directory:
sudo umount /mnt/usr 12.Unmount last device:
sudo umount /mnt 13.Reboot.
Ok, this is fixed. I was trying to mount sda1, the boot partition, whereas I should have mounted sda5, the partition where my system was. I made the mistake because my disk has 8 partitions, 1 boot, 2 linux, and 5 others ... I wasn't sure wich to choose