DebianThis forum is for the discussion of Debian Linux.
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.
When I boot up Etch, I occasionally (but increasinlgy often) get the message
Target file system doesn't have /sbin/int
after which the booting process comes to a halt and I get thrown into BusyBox.
Rebooting once or twice eventually does get me into the system.
I haven't got a clue what could be wrong. Someone suggested reinstalling udev but that didn't help a bit. In fact, since I did, I have the impression that I'm getting the error more often if anything.
Could this be related to the "controller bug" that is/was known to affect Etch: on systems with multiple controllers, Etch may fail to recognize the proper controller. I have three controllers (Promise PCI Sata card, onboard JMicron and Intel ICH8) so that would leave plenty of room for mistakes.
Or could it be a consequence of the boot directory being on xfs? I hear that XFS does have some adverse effects on GRUB but then again, I'm booting from the GRUB that was installed by Mandriva, which is on ext3. I originally installed Etch with Lilo on the MBR but that failed (I suspect this was precisely because of the controller bug I already mentioned). Whatever, everything ran fine until a month ago - then those messages started coming up; on top of that, I was suddenly having audio issues where the system failed to recognize my Soundblaster and started using OSS by default instead of ALSA (I have been able to solve this onein the meantime, by the way).