Linux - EnterpriseThis forum is for all items relating to using Linux in the Enterprise.
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 have installed 2 FC qlogic cards into a machine running 2xopterons and hardware raid1 ultra320 scsi disks. The scis is shown to trhe system as just one disk. the kernel is 2.6.13 and has both the LSI(scsi raid controller) and the qlogic drivers compiled in statically. When I boot the system with the two FCs connected to my san... i can see the disks that are presented while the machine boots but i think becuase it detects the FCs first it assignes them sda in /dev which was hte original SCSI boot drive and so can get past boot.
I've googled for similar problems and they all revolve around loading the modules in a different order at boot time. But what shuild i do if ive compiled the drivers into kernel statically?
Don't compile them in statically, there's no way you can fix the problem without mucking with the order in which the kernel starts the drivers anyway so the best fix is to just run a modular kernel, like you should anyway.