Linux - SoftwareThis forum is for Software issues.
Having a problem installing a new program? Want to know which application is best for the job? Post your question in this forum.
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've just compiled a new kernel (2.4.22) on debian. I'm using Lilo as my boot loader. The kernel starts to boot fine but hangs as Samba is starting. I get a message saying that Samba is probing some addresses. Address 0x0c00-0x0cff comes up as 'clean', but then is halts with:
cs: IO port probe 0x0800-0x08ff:
and just sits there without doing anything. I have to switch off the machine "manually" go boot again. Now, on the next boot, the harddrive is checked. This results in an error that has to be fixed by running fsck manually. The problem is that the file system (after the disk check) has now been mounted read-only, so I can't make any changes to the boot process or remove samba all together.
Also at startup I do not get a 'boot-prompt', so I have not been able to enter ineractive mode either.... And guess what? The boot disk I made when I installed the new kernel does nbot work. This gives me an error message saying: 'End of data input' or 'No more data to read' or something like that. (I'm at work and not at my machine at the moment. And I don't remember the exact message)
I'm REALLY stuck here. I'm just hoping that this is a 'newbie' problem, and that there is some way of solving it. Maybe if I could somehow mount the filesystem as write I could apt-get remove samba??