SlackwareThis Forum is for the discussion of Slackware Linux.
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.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I'm a newbie to kernel compiling and package creation, and I guess just about anything in Linux. I have been using it a while, but been distro hoping a lot.
Replace the 2.6.24 kernel with the 2.6.26 or 2.6.27 from kernel.org.
Edit each slackbuild in each of the folders in the directory to 2.6.26 or 2.6.27rc4
Run each slackbuild and then I should have up to date kernel packages I just install and then run the nvidia drivers script again.
Why do you want packaging the kernel ? Just curious
Use the packages on other PCs ?
Yes I think you right, edit the kernel version on slackbuild and it should work in that case
but may require a 'make oldconfig' in the kernel source tree before as the new kernel may have new features
Why do you want packaging the kernel ? Just curious
Use the packages on other PCs ?
Yes I think you right, edit the kernel version on slackbuild and it should work in that case
but may require a 'make oldconfig' in the kernel source tree before as the new kernel may have new features
So what would be the best way to compile a Huge Slackware kernel just like the ones included in the Slackware DVD/CD/Online, so that I end up with a tgz file that I can install/uninstall with the package manager?
I would do it in 2 steps:
- Kernel compilation
- Kernel packaging
For the Kernel compilation:
- do it as Alien Bob tutorial, looks good
For the Kernel packaging:
- Now it is the tedious part, there is 2 packages to make: kernel and kernel-modules
Look at the file lists in /var/log/packages to give you an idea, look also at the corresponding scripts in /var/log/scripts
But I am sure Slackbuild scripts exists somewhere, look in slackware sources directories
I wonder if it is worth it to make a kernel package if you don't use it in other PCs...
If it is for install/uninstall, there is not advantage to make a package imho, you just replace the kernel in /boot and the modules in /lib/modules (and this last operation is done for you when you issue make modules_install in kernel compilation)
[edit]
You will have to install the kernel and modules before make the packages anyway
You wouldn't make a kernel package with an un-tested kernel, would you ?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.