My very own Kernel build script for Debian/Ubuntu-based systems
Linux - KernelThis forum is for all discussion relating to the Linux kernel.
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.
Good work, but wouldn't it be the correct way to make a package from the compiled kernel and then to install the package? This way your script would be compatible with DKMS and the kernelmodules for Virtualbox, proprietary drivers and so would be automatically compiled to fit the new build kernel. The way you do it Virtualbox, nVidia drivers, ATI drivers, etc will not work with the newly installed kernel. You can find more info for building packages from kernels here.
The problem is that that would conflict with my intention to have the script be able to allow you to customize the kernel (i.e. install only those modules to support *your* hardware) without having to run all those extra commands. That's why this script runs 'make xconfig' by itself in the first place!
I have some questions, and some suggestions regarding your script:
Why is it necessary to install all those filesystem-tools and things like ppp and isdnutils?
You install grub-pc in your script. This is okay for all people that are running grub2, but if someone runs grub-legacy (i.E. Debian Stable users) this can lead to problem and may be unwanted. At least you can warn the users and let them ask a question, if they want to do that, or, maybe even better, ask a question with three choices what to install: no bootloader, grub-legacy, grub-pc. the update-grub command is also available for grub-legacy (in grub-pc it is only a wrapper for the grub-mkconfig command, for compatibility), so this should be doable.
And a suggestion for the future: Instead of installing all needed packages in the beginning of the script, I think it would be better (and the Debian way of doing it) to make a packe from your script that depends on all that needed packages.