SlackwareThis Forum is for the discussion of Slackware Linux.
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.
I would like to install a Slack Pack which apparently was compiled for the 220.127.116.11 kernel. However I am running kernel 2.6.20. This should not normally be an issue but when I unpacked the archive to view the contents before installing, I noticed a "..../lib/modules/18.104.22.168/kernel/drivers/net/wireless" folder structure. Since I am running kernel 2.6.20 my structure would show this value rather the the 22.214.171.124. My question is, is it possible to unpack and modify the package to change the name of the 126.96.36.199 directory to 2.6.20 and have the entire archive repackaged into a genuine Slack Pack?
What is the package? It sounds like a kernel module of some sort. If that is the case it will need to be recompiled for your present kernel. With any luck the package will include a slackbuild script. If it does, extract the slackbuild script, obtain the source and run the script and you should have a package built against your kernel. Full instructions for using slackbuilds are here at slackbuilds.org
A precompiled package with a kernel module inside can not be used on another kernel.
You can re-build the package using the sources however, and create a kernel module for your version of the kernel.
What package are you referring to by the way?
Yeah, just untar it in a test directory that has nothing else in it. And then make your change, go to the base directory of your test, and as root "makepkg foo.tgz"
But If it is just a directory structure, you could also go to that directory and create a soft link from one directory to the other: ln -s 188.8.131.52 2.6.20.
But now I look at where it is installed: Kernel modules from one version do not work with kernels of a different version number, so I don't think your 184.108.40.206 module that it is placing in there will actually work.