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.
Ok! when installing windows, it will detect your drivers
and if you put your drivers on a disk it will ask for the
disk! is it possible to install the drivers by default
when installing Linux on a new HD!??
Sorry buddy but that doesn't make any sense to me.
When you install Linux, a lot of the mainstream distros have pre-built kernels with certain things enabled, and even some with almost everything at least Modulized. If this is what you mean, then you shouldn't be having many problems as long as you choose to load the correct kernel???
Originally posted by FreakboY ya exactly!!!
thats what i mean!!!
i want to enable things on my kernel!!!
good.. i really didn't know how to say it!!
Well, in that case, the prebuilt kernel might be your best bet, you can't really build your kernel on most distros during the initial install. But most distros will provide certain prebuilt kernels to help you get your system going enough to get a new kernel and build it to your likings. Some distros will actually "modulize" almost all available options on the default kernel, making it easier for you to get your system working. If these drivers you speak of are not part of a generic kernel (I call it Vanilla) and you need them to get your system to a point to even be able to build a kernel, you might wanna see if you can use a sort of "test" system to do this on. Build the kernel on another system, apply the patches, get the thing working exactly as you need it in the other machine, then save it to a cdrom or floppy (if possible), along with /lib/modules/<kernel-version> and insert them in the newly built system.
what i want to do is...
everytime i install vallhalla(vanilla :-)
i want my Sound card to be automatikly configured
by my kernel so i want to install my audigy live
driver by default!! thats what i want to do!!
Well this would work but only for the current kernel, as soon as you update you would need to apply the patch again.
Anyway, just build the kernel (vanilla of course) and apply the patch. The modules are stored in /lib/modules/<kernel version>. You will also have a System.map file in the bottom of your source tree (the base directory for your vanilla kernel) that you will want on the disc. Copy all 3 of these things to a disc. SO:
apply your patch, build your kernel, make modules, and make modules_install. And copy the kernel, /lib/modules/<kernel version>, and System.map to a disc (probably a CDR if that's available). Remember, you are building the kernel to work on the hardware for your specific system, not the host system.
Now whenever you put a new distro on your computer, copy the kernel image and System.map file to the /boot directory, and the /lib/modules/kernel version to the /lib/modules directory, and you should be fine. This would at least save you the time of building a new kernel for every distro, and also save you if you have to reformat/reinstall for whatever reason.
You will have to go through the basic install first of course, this would be applied afterwards, and would require an entry to be made in your boot loader to show the kernel.