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.
Hi. I've just got a few minor issues that I'm not able to
resolve by myself, so any help would be greatly appreciated.
My first problem is with LILO. I've configured
it to boot Windows 2000 and Linux. It boots into Windows
2000 without problems, but when I try to boot into Linux,
I get a message "Block Error ...". As soon as the error a
ppears, it returns to the "boot: linux" prompt, so I can't
properly make out the entire error message. But I think
there is a hexadecimal number. The only way that I can boot
into Linux is if I hold down the "Enter" key for a few
seconds, after which it boots straight intoLinux without
Next problem is with XMMS. After installing XMMS, I'm able
to play MP3s without any problems, but I'm not able to
control the volume from within XMMS. I can adjust the volume
from Kmix though, but I would prefer to do it in XMMS. Is
this a problem with how I've installed XMMS or my sound
configuration? (I've used kernel modules maestro3.o and
Here is some info about my system:
Debian Linux 3.0 r2 'Woody'
9GB Primary Master IDE HDD
Win2k on partition 1 - 1.5GB
Linux on partition 2 - 1.5GB
Swap on partition 3 - 64MB
30GB Secondary Master IDE HDD
ESS Allegro Sound Card
One more thing, I've noticed that Linux sets the Win2k
partition to /dev/hda2, even though it's the first partition
on the drive. Also, my second HD has only one big partition
on it, yet linux sets it to /dev/hdc5. Why is this?
Sorry for the lengthy post, and thanks in advance.
I used my Debian CD to boot into the computer. The fsck command couldn't be found, but there was the e2fsck command which I decided to try out. I ran "e2fsck /dev/hda3" and it reported that it was "clean". I tried it again with the -c option to check for bad blocks. It complained that there was an inode with a zero length, after which it prompted me to fix it. After answering yes, it finished the rest of the checks with no further problems. I rebooted the computer into Linux, but LILO still reported a block error. Did I have to use fsck? If so, how can I run it after I've booted in with my CD?
I solved the XMMS problem. The permissions for /dev/mixer weren't set properly. After changing the permissions, I was able to adjust the volume from within XMMS.
And about the Windows partition being hda2: I accidentally ran e2fsck on /dev/hda1, and it reported that it might have been a zero length partiton.
All the checks completed with no problems. Is there a way for me to log the output from the LILO boot propmt, or to slow down the output. Maybe knowing the exact error message might help, but it goes by so fast that I can't make it out.