Linux - GeneralThis Linux forum is for general Linux questions and discussion.
If it is Linux Related and doesn't seem to fit in any other forum then this is the place.

Notices

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.

as someone constantly suffering from driver troubles: and as i like to shunt the same OS across several computers, i was wondering: can i compile all the software, the drivers, everything: into one big vmlinuz for easy transportation?

If you know the scope of the machines then a list of drivers necessary would be the best choice. By placing everything in the kernel you are not necessarily doing yourself any favors let alone the systems. Just do a inventory for the machines that are going to be used then compile for each. Look at 'Drivers - Linux Kernel Newbies' tutorial for aid installing or developing Drivers. Don't forget;

By inclusion of everything into the kernel you will be opening doors that may create problems. Size of the kernel created is not the problem unless you are changing a current Gnu/Linux distribution then size may be restricted because of media size! Some Gnu/Linux are at the fringe of the media limitations. Rebuild limitations for the ISO will be dependent on the media type.

Kernel distribution method will be dependent on the hardware to be used. Network or storage media? Don't forget that you will need to get the source for newer hardware to compile for said hardware. Some newer hardware drivers will/may still be in development stage.

For the network or storage media you can create build trees for each machine type that is to be serviced. Each build will be for a specific machine's hardware class. Much easier than to build huge kernel to service multiple machine environments. Especially changing machine environments.

Kernel modules have strengths and utility to allow one to modify. You should learn to use whenever possible. You will not see any monumental gains for built in.

Your wish to have a 'huge' kernel to suit multiple machine type environments is doable but not the best choice. If you have the same family for a hardware class with just minor differences then modules are the way to utility the service for hardware.

If your needs are for different processor architecture or families then you have different suite of problems for the machines in question. Then 'builds' to suit each is the best choice. Therefore the kernel can be customized for each architecture install.

Don't forget that some Gnu/Linux do provide different architecture support. You could then hopefully provide specific module drivers for any hardware not supported by that Gnu/Linux.

"Knowledge is of two kinds. We Know a subject ourselves, or we know where we can find information upon it."- Samuel Johnson